vercel-react-best-practices
Skill2 starsChanged 7 months agoMITView on GitHub
Comprehensive performance and architecture optimization for React and Next.js. Use this for code reviews, refactoring, or building new components.
176 other projects use a version of this.
Adopted by
Most recently taken up by
- linx-systems/clamuitheir own version, first seen Nov 9, 2026
- CherryHQ/cherry-studiotheir own version, first seen Nov 8, 2026
- open-slide/open-slidetheir own version, first seen Nov 8, 2026
- JustinWangJP/cc-agent-teams-action-monitortheir own version, first seen Nov 8, 2026
- figueroaignacio/ignaciofigueroa.devtheir own version, first seen Nov 8, 2026
- dazeb/ClaudePlaybooktheir own version, first seen Nov 8, 2026
Used with
Projects 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
betacatslingSkillfeature-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
VercelSkillnext-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods
Also in 12 projects that use this
SentrySkillvercel-composition-patterns
Also in 124 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
VercelSkillnext-cache-components
Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag
Also in 17 projects that use this
- +3 more from vercel-labs
Other versions176 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 176
- Significant-Gravitas/AutoGPT★ 188ksame name
- calesthio/OpenMontage★ 78ksame name
- OpenMontageInc/OpenMontage★ 78ksame name
- CherryHQ/cherry-studio★ 53ksame name
- QuantumNous/new-api★ 52ksame name
- vercel-labs/agent-skills★ 33ksame name
- udecode/plate★ 17ksame name
- open-metadata/OpenMetadata★ 16ksame name
- Arize-ai/phoenix★ 12ksame name
- trycompai/crm★ 12ksame name
166 more not listed
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 repository32 other files it gives its agents.
- skills/coding/redis-agent-skills/AGENTS.mdAGENTS.md
- skills/coding/redis-agent-skills/CLAUDE.mdCLAUDE.md
- agent-browserSkill
- autopilotSkill
- book-studySkill
- brainstormingSkill
- browser-useSkill
- cavemanSkill
- androidSkill
- brand-guidelinesSkill
- canvas-designSkill
- frontend-designSkill
- supabase-postgres-best-practicesSkill
- theme-factorySkill
- web-design-guidelinesSkill
- context7-aware-codingSkill
- document-intakeSkill
- explore-codebaseSkill
- find-skillsSkill
- finishing-a-branchSkill
- ohc-coding-disciplineSkill
- pdfSkill
- ralphSkill
- requesting-code-reviewSkill
- retrospectiveSkill
- seo-auditSkill
- skill-creatorSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- writing-plansSkill
- writing-skillsSkill
The file
Files
vercel-react-best-practices
Optimizes React and Next.js applications using Vercel Engineering's 70+ rules across 8 categories.
Phase 1: Audit & Identify
Scan the codebase for common performance bottlenecks and anti-patterns.
- Tools:
grep_searchorrgfor specific hooks (useEffect,useState), Server Components, and Layout patterns. - Focus: RSC vs. Client Component boundaries, hydration mismatches, and waterfall fetches.
Phase 2: Category Analysis
Evaluate the code against these 8 core categories:
- Performance: Bundle size, re-renders, and memoization.
- RSC Optimization: Minimizing Client Component usage, data fetching patterns.
- Hydration: Preventing mismatches, using
Suspensecorrectly. - Data Fetching: Using
fetchin RSC, cache tags, and revalidation. - State Management: Avoiding prop drilling, choosing the right hook.
- Form Handling: Server Actions vs. traditional forms.
- Routing: Layout vs. Page structure, segment config.
- Security: Sanitizing inputs, CSRF protection in Server Actions.
Phase 3: Severity Ranking
Assign a priority to each finding:
- P0 (Critical): Hydration errors, security gaps (missing auth in Server Actions).
- P1 (High): Large bundle size regressions, blocking waterfalls.
- P2 (Medium): Suboptimal hook usage, minor re-render issues.
- P3 (Low): Style improvements, naming conventions.
Phase 4: Recommendation
Propose specific code changes using the "Fix it" or "Refactor it" pattern. Explain the "Why" behind each change (e.g., "Moving this to an RSC reduces client bundle by 20KB").
References
| File | Purpose |
| rsc-checklist.md | Server Component best practices |
| performance-rules.md | Specific React performance rules |
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.

