react-components
Skill1 starsChanged 41 days agoMITView on GitHub
Build React components with clear state and effects. Use when creating or refactoring React UI, hooks, or client data fetching.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- delorenj/skillstheir own version, first seen Nov 7, 2026
- github/replicatheir own version, first seen Nov 1, 2026
- jorgeasaurus/agent-skillstheir own version, first seen May 11, 2026
- langchain-ai/skills-benchmarkstheir own version, first seen Mar 2, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- github/replica★ 230same name
- langchain-ai/skills-benchmarks★ 116same name
- delorenj/skills★ 17same name
- jorgeasaurus/agent-skills★ 14same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository49 other files it gives its agents.
- accessibilitySkill
- address-feedbackSkill
- agent-disciplineSkill
- agent-handoffSkill
- api-designSkill
- architecture-decisionSkill
- brainstormSkill
- browser-verifySkill
- code-reviewSkill
- containerizeSkill
- context-efficientSkill
- create-prSkill
- database-changesSkill
- debug-systematicSkill
- dependency-upgradeSkill
- docs-groundedSkill
- error-handlingSkill
- explore-codebaseSkill
- fix-ciSkill
- frontend-designSkill
- git-commitSkill
- git-worktreeSkill
- incident-triageSkill
- incremental-slicesSkill
- legacy-changeSkill
- migrate-codeSkill
- minimal-diffSkill
- observabilitySkill
- parallel-workSkill
- performance-auditSkill
- plan-before-codeSkill
- python-qualitySkill
- refactor-safeSkill
- release-notesSkill
- security-reviewSkill
- setup-ciSkill
- shell-safetySkill
- ship-checklistSkill
- simplify-codeSkill
- skill-authoringSkill
- skill-routerSkill
- spec-drivenSkill
- tddSkill
- threat-modelSkill
- triage-issuesSkill
- typescript-strictSkill
- verify-workSkill
- write-docsSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Keep components focused; extract hooks for reusable stateful logic.
- Distinctive: line 16
Prefer controlled inputs when the parent must own the value.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
React Components
Rules
- Match the project’s React style (Server Components, routers, state libs).
- Keep components focused; extract hooks for reusable stateful logic.
- Derive values during render when possible; avoid redundant state.
- List effect dependencies correctly; do not fake stability without cause.
- Colocate UI state with the nearest owner; lift only when sharing requires it.
- Handle loading, empty, and error states explicitly for async UI.
- Prefer controlled inputs when the parent must own the value.
Avoid
- Effects that sync props→state unnecessarily
- Prop drilling through many layers when project already uses a store/context pattern
- Inline huge components that bury the main render path
- Accessibility regressions (labels, keyboard, focus)
Checklist
- No broken hooks rules
- Keyed lists are stable
- User-facing errors are understandable
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.