vercel-react-best-practices
Skill0 starsChanged 3 months agoNo licenceView on GitHub
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
We split this skill into the rules it gives an agent
1 rule. 1 is common, 0 are distinctive, and 0 are very specific to this project.
1
Common
Most of the 117 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 117 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.
Trending
Rising: 20 new projects took it in the last 4 weeks, 1.3× the 4 weeks before.
Other versions265 projects use a version of this.
Word for word · 143
- vercel-labs/agent-skills★ 33k100% same
- udecode/plate★ 17k100% same
- open-metadata/OpenMetadata★ 16k100% same
- Arize-ai/phoenix★ 12k100% same
- trycompai/crm★ 11k100% same
- mengxi-ream/read-frog★ 10k100% same
- 1weiho/open-slide★ 9.3k100% same
- zai-org/ZCode★ 7.9k100% same
- basketikun/infinite-canvas★ 7.7k100% same
- zhukunpenglinyutong/idea-claude-code-gui★ 7.4k100% same
133 more not listed
Edited · 118
- Significant-Gravitas/AutoGPT★ 188k91% same
- calesthio/OpenMontage★ 74k92% same
- CherryHQ/cherry-studio★ 53k97% same
- polarsource/polar★ 10k91% same
- caorushizi/mediago★ 9.3k98% same
- mfts/papermark★ 9.2k95% same
- papermark/papermark★ 9.2k95% same
- midudev/preguntas-entrevista-react★ 7.8k99% same
- Kiranism/next-shadcn-dashboard-starter★ 7.1k97% same
- dinerojs/dinero.js★ 6.8k95% same
108 more not listed
Wrote their own version · 4
- QuantumNous/new-api★ 51ksame name
- coco-research/coco★ 797same name
- extra-org/extra★ 118same name
- composio-community/opencode-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.
Used alongsideProjects with it also use dep-refs, feature-boundary-planner and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
betacatslingSkilldep-refs
Use when needs to inspect TypeScript export references in the z-code workspace, list exports from a file, verify whether an export is unused before deletion, investigate who imports a symbol during refactors, or combine pnpm knip unused-export results with pnpm dep:refs symbol-level reference tracing.
Also in 5 projects that use this
- betacatslingSkill
feature-boundary-planner
Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Use for impact analysis, product-boundary planning, or an implementation handoff grounded in the checked-out source.
Also in 5 projects that use this
SentrySkillvercel-composition-patterns
Also in 113 projects that use this
VercelSkillnext-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods
Also in 10 projects that use this
Cartograf666Skillarchitecture-governance
Bootstrap, document, enforce, and review a project's architecture through layer responsibilities, dependency direction, architecture manifests, legacy baselines, Change Envelopes, cross-layer approval policy, and deterministic architecture checks. Use when starting a project, auditing an existing codebase, planning cross-layer work, preventing architecture erosion, reviewing structural changes, or deciding whether implementation may expand into another layer.
Also in 5 projects that use this
- VercelSkill
next-cache-components
Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag
Also in 15 projects that use this
- +3 more from vercel-labs
In this repository31 other files it gives its agents.
- kami/AGENTS.mdAGENTS.md
- vercel-react-best-practices/AGENTS.mdAGENTS.md
- kami/CLAUDE.mdCLAUDE.md
- kami/llms.txtllms.txt
- agent-browserSkill
- ai-elementsSkill
- ai-sdkSkill
- better-auth-best-practicesSkill
- better-auth-security-best-practicesSkill
- building-componentsSkill
- create-authSkill
- create-auth-skillSkill
- edaSkill
- emil-design-engSkill
- find-skillsSkill
- gcp-monitoringSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- kamiSkill
- project-memorySkill
- prototypeSkill
- schoger-ui-craftSkill
- setup-matt-pocock-skillsSkill
- shadcnSkill
- shutongSkill
- splashSkill
- tddSkill
- tldraw-canvasSkill
- vercel-cliSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.