better-skills / vercel-composition-patterns
AGENTS.md11 starsChanged 9 months agoMITView on GitHub
React composition guidance index for agents. Keep this file compact and pull detailed rules only when needed. Use this skill when tasks involve:
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- resources/AGENTS.mdAGENTS.md
- better-auth-best-practicesSkill
- honoSkill
- neon-postgresSkill
- next-best-practicesSkill
- next-cache-componentsSkill
- opentuiSkill
- turborepoSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Use this skill when tasks involve:
- Very specific: line 23
Start with SKILL.md for category overview.
- Very specific: line 24
Read only the relevant files in rules/.
- Very specific: line 25
Treat rules/*.md as the canonical source.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md
React composition guidance index for agents. Keep this file compact and pull detailed rules only when needed.
Scope
Use this skill when tasks involve:
- refactoring boolean-prop-heavy components
- building reusable component APIs
- designing compound components
- separating state implementation from UI composition
Priority order
architecture-*(composition over prop flags)state-*(provider-lifted, dependency-injected state)patterns-*(explicit variants, children composition)react19-*(React 19 API-specific guidance)
Progressive disclosure
- Start with
SKILL.mdfor category overview. - Read only the relevant files in
rules/. - Treat
rules/*.mdas the canonical source.
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.

