Qovery Console Standards
Qovery/console
Qovery Console coding standards, architecture guidelines, naming conventions, testing practices, and development workflows.
A skill your agent uses when writing, reviewing, or refactoring TypeScript or React code for craftsmanship — naming, function and component shape, error handling, data modeling, tests, and…
Install Clean Code TS React
$ npx skills add pproenca/dot-skills --skill clean-code-ts-react -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pproenca/dot-skills clean-code-ts-react --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/clean-code-ts-react .claude/skills/clean-code-ts-react && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "clean-code-ts-react" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code-ts-react into .claude/skills/clean-code-ts-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code-ts-react", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code-ts-reactType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pproenca/dot-skills --skill clean-code-ts-react -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pproenca/dot-skills clean-code-ts-react --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.experimental/clean-code-ts-react .agents/skills/clean-code-ts-react && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clean-code-ts-react" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code-ts-react into .agents/skills/clean-code-ts-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code-ts-react", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill clean-code-ts-react -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pproenca/dot-skills clean-code-ts-react --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.experimental/clean-code-ts-react .cursor/skills/clean-code-ts-react && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "clean-code-ts-react" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code-ts-react into .cursor/skills/clean-code-ts-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code-ts-react", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.experimental/clean-code-ts-react--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pproenca/dot-skills --skill clean-code-ts-react -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pproenca/dot-skills clean-code-ts-react --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.experimental/clean-code-ts-react .gemini/skills/clean-code-ts-react && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "clean-code-ts-react" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code-ts-react into .gemini/skills/clean-code-ts-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code-ts-react", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pproenca/dot-skills clean-code-ts-reactInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pproenca/dot-skills --skill clean-code-ts-react -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.experimental/clean-code-ts-react .github/skills/clean-code-ts-react && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "clean-code-ts-react" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code-ts-react into .github/skills/clean-code-ts-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code-ts-react", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill clean-code-ts-react -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pproenca/dot-skills clean-code-ts-react --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.experimental/clean-code-ts-react .opencode/skills/clean-code-ts-react && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "clean-code-ts-react" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code-ts-react into .opencode/skills/clean-code-ts-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code-ts-react", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
clean-code-ts-react- GitHub stars
- 214
- Token cost
- ~3.1k tokens
- SKILL.md length
- 984 words
- Files
- 66 (incl. references, assets)
- Skills in repo
- 182
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing, reviewing, or refactoring TypeScript or React code for craftsmanship — naming, function and component shape, error handling, data modeling, tests, and…
- Works in 11 steps: Meaningful Names (CRITICAL) → Functions, Components & Hooks (CRITICAL) → Self-Documentation: Types & Comments… → …
- Refactoring TypeScript
- SKILL.md covers What Makes This Skill Different, When to Apply, Rule Categories by Priority and Quick Reference, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Clean Code TS React is an agent skill from pproenca/dot-skills. Use when writing, reviewing, or refactoring TypeScript or React code for craftsmanship — naming, function and component shape, error handling, data modeling, tests, and abstraction. Translates Robert C. Martin's Clean Code principles into modern TS+React idioms (TS 5.x, React 19), with first-class "When NOT to apply" guidance and a Meta category for principle conflicts (DRY vs SRP, small functions vs deep modules, type safety vs ergonomics). Triggers on code review, refactoring for clarity, naming…
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 68 other files, including reference files and assets (for example `AGENTS.md`, `assets/templates/_template.md` and `metadata.json`).
It sits in Development, covering Code quality, Refactoring and Type safety. It works with React and TypeScript. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.
When your agent uses it
- Refactoring TypeScript
- React code for craftsmanship — naming
- Function and component shape
- Refactoring for clarity
Example prompts
- “When NOT to apply”
- “is this clean?”
- “make this more readable”
- “/clean-code-ts-react”
Workflow steps
11 steps, taken from the step headings in SKILL.md.
- Meaningful Names (CRITICAL)
- Functions, Components & Hooks (CRITICAL)
- Self-Documentation: Types & Comments (HIGH)
- Formatting Beyond Prettier (HIGH)
- Error Handling (HIGH)
- Data Shape & Immutability (MEDIUM-HIGH)
- Boundaries (MEDIUM-HIGH)
- Composition over Inheritance (MEDIUM-HIGH)
- Tests (MEDIUM)
- Emergence & Simple Design (MEDIUM)
- Meta: When Principles Conflict (MEDIUM)
What it can do on your machine
Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Clean Code TS React loads about 3.1k tokens when it runs, and up to ~45k if it reads all its reference files. Until then it costs about 206 tokens; SKILL.md has 984 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 984 words, ~3,079 tokens.
Download SKILL.mdSave it as
.claude/skills/clean-code-ts-react/SKILL.md (or your agent's skills folder). This skill also uses 65 other files; get the full folder from GitHub.- name
- clean-code-ts-react
- description
- Use when writing, reviewing, or refactoring TypeScript or React code for craftsmanship — naming, function and component shape, error handling, data modeling, tests, and abstraction. Translates Robert C. Martin's Clean Code principles into modern TS+React idioms (TS 5.x, React 19), with first-class "When NOT to apply" guidance and a Meta category for principle conflicts (DRY vs SRP, small functions vs deep modules, type safety vs ergonomics). Triggers on code review, refactoring for clarity, naming, function/component design, "is this clean?", "make this more readable", "right abstraction?" — even when the user doesn't say "clean code". Does NOT cover React-specific APIs (RSC, hooks API surface) — use the `react` skill. Does NOT cover TS compiler perf or tsconfig — use the `typescript` skill.
Robert C. Martin (Uncle Bob) TypeScript 5.x + React 19 Best Practices
Craftsmanship principles from Robert C. Martin's Clean Code (2008), re-expressed for modern TypeScript and React. Contains 61 rules across 11 categories, prioritized by cognitive cost across a code change's lifetime. Examples use TS 5.x and React 19 idioms — but the rules are about timeless principles, not specific APIs.
What Makes This Skill Different
Three things set this apart from a generic clean-code copy:
- Modern idioms as vehicle. Examples use TS 5.x (
satisfies, branded types, discriminated unions,consttype parameters) and React 19 (function components, hooks,use(), Server Components where relevant). But the rule is always the principle, never the syntax. - "When NOT to apply" is first-class. Every rule has 2-3 concrete scenarios where the principle should bend — not generic disclaimers, real situations. Loop counters can be
i. Single-use code shouldn't be DRY. Some HOCs are unavoidable. - Meta category for principle conflicts. Category 11 names the most common tensions explicitly — DRY vs Single Responsibility, small functions vs deep modules (Ousterhout), type precision vs ergonomic APIs, tests as spec vs documentation. The mark of seniority is knowing which to bend.
When to Apply
Reference these guidelines when:
- Writing new TypeScript or React code and wanting craftsmanship feedback
- Reviewing a pull request for clarity, naming, or abstraction
- Refactoring existing code for readability or maintainability
- Designing function, hook, or component APIs
- Deciding whether to extract, abstract, or duplicate
- Resolving a tension between two clean-code rules (see Category 11)
Skip this skill and use:
reactfor React 19 API patterns (concurrent rendering, Server Components, ref-as-prop,useActionState,<Context>-as-provider)typescriptfor compiler performance, tsconfig tuning, type-system perfrefactorfor mechanical refactoring workflowstddfor the TDD workflow itself
Rule Categories by Priority
Order reflects cognitive cost across a change's lifetime (read → understand → modify → verify → ship → maintain). Earlier stages cascade — bad names taint every read.
| Priority | Category | Impact | Prefix | Rules |
|---|---|---|---|---|
| 1 | Meaningful Names | CRITICAL | name- | 8 |
| 2 | Functions, Components & Hooks | CRITICAL | func- | 8 |
| 3 | Self-Documentation (Types & Comments) | HIGH | doc- | 5 |
| 4 | Formatting (Beyond Prettier) | HIGH | fmt- | 4 |
| 5 | Error Handling | HIGH | err- | 7 |
| 6 | Data Shape & Immutability | MEDIUM-HIGH | data- | 6 |
| 7 | Boundaries | MEDIUM-HIGH | bound- | 4 |
| 8 | Composition over Inheritance | MEDIUM-HIGH | comp- | 6 |
| 9 | Tests | MEDIUM | test- | 5 |
| 10 | Emergence & Simple Design | MEDIUM | emerge- | 4 |
| 11 | Meta: When Principles Conflict | MEDIUM | meta- | 4 |
Total: 61 rules.
Quick Reference
1. Meaningful Names (CRITICAL)
name-intention-revealing— Use names that reveal intentname-avoid-disinformation— Avoid misleading namesname-meaningful-distinctions— Make meaningful distinctionsname-component-pascal-case— Components are PascalCase noun phrasesname-hook-use-prefix— Hooks areuseXverb phrasesname-handler-convention— Event handlers useonX/handleXname-boolean-predicate— Boolean variables useis/has/canname-types-pascal-case— Types and interfaces are PascalCase
2. Functions, Components & Hooks (CRITICAL)
func-small— Keep functions, components & hooks smallfunc-one-thing— Do one thingfunc-abstraction-level— One level of abstraction per functionfunc-minimize-arguments— Prefer object parameters over long listsfunc-no-side-effects— Avoid hidden side effects (especially in render)func-command-query-separation— Separate commands from queriesfunc-dry— DRY — until concepts divergefunc-custom-hook-extract— Extract custom hooks for reusable stateful logic
3. Self-Documentation: Types & Comments (HIGH)
doc-types-over-comments— Prefer types over commentsdoc-satisfies-narrows-with-check— Usesatisfiesfor inferred-but-checked valuesdoc-jsdoc-public-api— JSDoc for public APIs and non-obvious side effectsdoc-avoid-redundant-comments— Avoid redundant commentsdoc-delete-commented-out-code— Delete commented-out code
4. Formatting Beyond Prettier (HIGH)
fmt-vertical-density— Keep related code close, unrelated farfmt-newspaper-order— Order files top-down like a newspaperfmt-team-rules-over-preference— Team conventions over personal preferencefmt-imports-grouped— Group imports by source
5. Error Handling (HIGH)
err-early-return— Use early returns to flatten error pathserr-result-vs-throw— Choose throw vs Result deliberatelyerr-narrow-unknown— Always narrowunknownin catch blockserr-error-boundaries— Use error boundaries for render-time failureserr-suspense-for-loading— Use Suspense for loading stateserr-no-swallow— Never swallow errors silentlyerr-null-vs-undefined— PicknullORundefinedper domain
Show full SKILL.md (376 more words)Show less
6. Data Shape & Immutability (MEDIUM-HIGH)
data-discriminated-unions-over-flags— Discriminated unions over boolean flagsdata-readonly-by-default— Mark read-only datareadonlydata-branded-types— Brand types for domain invariantsdata-dto-vs-domain— Separate DTOs from domain typesdata-demeter-prop-drilling— Prop drilling often smells like Demeterdata-structural-typing-pitfalls— Beware structural typing aliasing
7. Boundaries (MEDIUM-HIGH)
bound-wrap-third-party-hooks— Wrap third-party hooks in custom hooksbound-learning-tests— Write learning tests for third-party behaviorbound-isolate-framework— Isolate framework-specific code at the edgesbound-type-assertions-at-edges— Type assertions belong only at boundaries
8. Composition over Inheritance (MEDIUM-HIGH)
comp-children-over-props— Compose withchildrenover configuration propscomp-small-components— Keep components small and cohesivecomp-avoid-hoc-stacks— Avoid higher-order component stackscomp-context-only-when-needed— Context for DI, not prop avoidancecomp-render-props-vs-hooks— Prefer hooks over render props for logic reusecomp-separate-construction-from-use— Separate setup from rendering
9. Tests (MEDIUM)
test-behavior-not-implementation— Test behavior, not implementationtest-mock-at-boundaries— Mock only at true boundariestest-first-principles— Apply FIRST principlestest-one-concept— One concept (not one assert) per testtest-clean-as-production— Test code deserves production-grade care
10. Emergence & Simple Design (MEDIUM)
emerge-four-rules— Apply the four rules of simple design in orderemerge-yagni-types— Avoid premature type genericsemerge-premature-abstraction— Resist premature abstractionemerge-reveal-intent— Maximize expressiveness — code as communication
11. Meta: When Principles Conflict (MEDIUM)
This is the signature category — explicit guidance on when one clean-code principle yields to another.
meta-dry-vs-srp— Bend DRY when concepts drift apartmeta-small-vs-deep— Small functions lose to deep modules when indirection > comprehensionmeta-types-vs-ergonomics— Type safety loses to ergonomics at stable boundariesmeta-tests-as-spec-vs-doc— Pick tests-as-spec or tests-as-documentation per file
How to Use
For an ad-hoc question ("is this naming OK?", "should I extract this?"), jump straight to the relevant rule file via the Quick Reference above.
For a code review or refactor, scan the categories in priority order — names and function shape first (highest cascade), then errors and data shape, then composition and tests. The category-major sweep is more efficient than file-major.
When two principles seem to disagree, read the corresponding Meta rule (Category 11). Pick the principle that wins, and document the call.
Reference Files
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for adding new rules |
| metadata.json | Version and reference information |
Related Skills
.experimental/clean-code— Original language-agnostic clean code (Java examples). This skill is the TS+React sibling..curated/react— React 19-specific patterns (Server Components, concurrent rendering, ref-as-prop)..curated/typescript— TS compiler performance and tsconfig tuning..curated/refactor— Mechanical refactoring workflows..curated/tdd— The TDD workflow itself.
© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 65 other files (references, assets) in skills/.experimental/clean-code-ts-react of pproenca/dot-skills.
- SKILL.md
- AGENTS.md
- assets/templates/_template.md
- metadata.json
- references/_sections.md
- references/bound-isolate-framework.md
- references/bound-learning-tests.md
- references/bound-type-assertions-at-edges.md
- references/bound-wrap-third-party-hooks.md
- references/comp-avoid-hoc-stacks.md
- references/comp-children-over-props.md
- references/comp-context-only-when-needed.md
- references/comp-render-props-vs-hooks.md
- references/comp-separate-construction-from-use.md
- references/comp-small-components.md
- references/data-branded-types.md
- references/data-demeter-prop-drilling.md
- references/data-discriminated-unions-over-flags.md
- … and 48 more
Open the folder on GitHubat commit cf93c57
Compare with similar skills
Clean Code TS React next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Clean Code TS React this skillpproenca/dot-skills | 214 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Qovery Console StandardsQovery/console | 227 | — | ~924 | Automated safety check: Pass | MIT | |
| Typescript React ReviewerSuFxGIT/scoutarr | 114 | — | ~1.7k | Automated safety check: Pass | None | |
| Typescript Best Practicesjwynia/agent-skills | 165 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Effect TStellahq/opensession | 392 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Frontend Module Standardssiteboon/claudecodeui | 14k | — | ~2.6k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Typescript React Reviewer
SuFxGIT/scoutarr
Expert code reviewer for TypeScript + React 19 applications.
Typescript Best Practices
jwynia/agent-skills
Guide AI agents through TypeScript coding best practices including type safety, error handling, code organization, and architecture patterns.
Effect TS
tellahq/opensession
Write idiomatic Effect v4 TypeScript verified against the pinned effect@4.0.0-rc.112 source.
Frontend Module Standards
siteboon/claudecodeui
Enforces one repository's React and TypeScript module layout for code under src/: source-root imports, feature barrels, deliberate exports and no deep imports.
Dignified Python Standards
docling-project/docling
Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance.
More from pproenca/dot-skills
All 182 skills in this repoAudio Voice Recovery
pproenca/dot-skills
Audio forensics and voice recovery guidelines for CSI-level audio analysis.
Codemod React Pipeline
pproenca/dot-skills
Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.
Dev Rfc
pproenca/dot-skills
Create well-structured RFCs and technical proposals for software projects.
Dx Harness
pproenca/dot-skills
Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.
Language Spec Author
pproenca/dot-skills
Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…
Python Pep Author
pproenca/dot-skills
Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…
Related
Works with
Categories
Questions about Clean Code TS React
What does Clean Code TS React do?
A skill your agent uses when writing, reviewing, or refactoring TypeScript or React code for craftsmanship — naming, function and component shape, error handling, data modeling, tests, and…. Clean Code TS React is an agent skill from pproenca/dot-skills. Use when writing, reviewing, or refactoring TypeScript or React code for craftsmanship — naming, function and component shape, error handling, data modeling, tests, and abstraction.
When should I use Clean Code TS React?
Clean Code TS React fits situations like: refactoring TypeScript; React code for craftsmanship — naming; function and component shape; refactoring for clarity.
How do I install Clean Code TS React in Claude Code?
Run `npx skills add pproenca/dot-skills --skill clean-code-ts-react -a claude-code`. Or copy the skill folder (skills/.experimental/clean-code-ts-react in pproenca/dot-skills) into .claude/skills/clean-code-ts-react in your project. Claude Code loads it when a task matches its description.
How do I install Clean Code TS React in Codex?
Run `npx skills add pproenca/dot-skills --skill clean-code-ts-react -a codex`. Or copy the skill folder (skills/.experimental/clean-code-ts-react in pproenca/dot-skills) into .agents/skills/clean-code-ts-react in your project. Codex loads it when a task matches its description.
Can I use Clean Code TS React in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill clean-code-ts-react -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clean-code-ts-react, .gemini/skills/clean-code-ts-react, .github/skills/clean-code-ts-react and .opencode/skills/clean-code-ts-react in your project.
What does Clean Code TS React need to run?
SKILL.md names no scripts, command-line tools or credentials: Clean Code TS React is instructions for the agent only.
Does Clean Code TS React access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Clean Code TS React safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Clean Code TS React use?
Clean Code TS React is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Clean Code TS React use?
About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 42k tokens, read only when the agent opens those files.
What are the alternatives to Clean Code TS React?
Skills that share tags, products or a category with Clean Code TS React: Qovery Console Standards (Qovery/console, 227 stars), Typescript React Reviewer (SuFxGIT/scoutarr, 114 stars), Typescript Best Practices (jwynia/agent-skills, 165 stars) and Effect TS (tellahq/opensession, 392 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clean Code TS React?
pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 214 GitHub stars. The repository holds 182 skills in this directory. The repository was last updated on August 15, 2026.
Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.