
Vercel React Best Practices
- 584k installs
- 29.5k repo stars
- Updated July 24, 2026
- vercel-labs/agent-skills
vercel-react-best-practices is a skill containing 70 Vercel-maintained React and Next.js performance rules for writing, reviewing, and refactoring code.
About
vercel-react-best-practices is a Vercel-maintained skill that embeds 70 React and Next.js performance rules across 8 impact-prioritized categories. It applies when an agent writes, reviews, or refactors components, pages, data fetching, or bundle configuration and steers toward patterns Vercel Engineering uses. Rules cover eliminating network waterfalls, bundle size, server-side performance, client fetching, re-render and rendering optimization, JavaScript hot paths, and advanced patterns. A developer uses it during performance audits, PR reviews, and refactors where generic React advice is not specific enough.
- 70 performance rules across 8 impact-prioritized categories
- Covers waterfalls, bundle size, server and client fetching, and re-renders
- Maintained by Vercel Engineering for React and Next.js
- Rules are prefixed and ranked by measured impact for automated refactoring
Vercel React Best Practices by the numbers
- 584,435 all-time installs (skills.sh)
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
vercel-react-best-practices capabilities & compatibility
Free (MIT); the docs describe only guideline rules, no API key required.
- Capabilities
- react performance · nextjs optimization · bundle optimization · code review · refactoring
- Use cases
- refactoring · code review · frontend
- Runs
- Runs locally
- Pricing
- Free
What vercel-react-best-practices says it does
Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel.
Contains 70 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
npx skills add https://github.com/vercel-labs/agent-skills --skill vercel-react-best-practicesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 584k |
|---|---|
| repo stars | ★ 29.5k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 24, 2026 |
| Repository | vercel-labs/agent-skills ↗ |
How do I make my React or Next.js app faster and catch performance anti-patterns in review?
refactoring
Who is it for?
Developers auditing or refactoring React/Next.js code who want performance patterns Vercel Engineering uses in production.
Skip if: Non-React projects or teams that only need general React advice rather than performance-specific rules.
When should I use this skill?
Writing, reviewing, or refactoring React/Next.js components, pages, data fetching, or bundle optimization.
What you get
Code refactored toward Vercel's prioritized performance rules for waterfalls, bundles, rendering, and fetching.
- React/Next.js code refactored to prioritized performance rules
- A performance review checklist by category
By the numbers
- 70 rules across 8 categories
- 8 rule categories prioritized by impact
Files
Vercel React Best Practices
Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 70 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
When to Apply
Reference these guidelines when:
- Writing new React components or Next.js pages
- Implementing data fetching (client or server-side)
- Reviewing code for performance issues
- Refactoring existing React/Next.js code
- Optimizing bundle size or load times
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Eliminating Waterfalls | CRITICAL | async- |
| 2 | Bundle Size Optimization | CRITICAL | bundle- |
| 3 | Server-Side Performance | HIGH | server- |
| 4 | Client-Side Data Fetching | MEDIUM-HIGH | client- |
| 5 | Re-render Optimization | MEDIUM | rerender- |
| 6 | Rendering Performance | MEDIUM | rendering- |
| 7 | JavaScript Performance | LOW-MEDIUM | js- |
| 8 | Advanced Patterns | LOW | advanced- |
Quick Reference
1. Eliminating Waterfalls (CRITICAL)
async-cheap-condition-before-await- Check cheap sync conditions before awaiting flags or remote valuesasync-defer-await- Move await into branches where actually usedasync-parallel- Use Promise.all() for independent operationsasync-dependencies- Use better-all for partial dependenciesasync-api-routes- Start promises early, await late in API routesasync-suspense-boundaries- Use Suspense to stream content
2. Bundle Size Optimization (CRITICAL)
bundle-barrel-imports- Import directly, avoid barrel filesbundle-analyzable-paths- Prefer statically analyzable import and file-system paths to avoid broad bundles and tracesbundle-dynamic-imports- Use next/dynamic for heavy componentsbundle-defer-third-party- Load analytics/logging after hydrationbundle-conditional- Load modules only when feature is activatedbundle-preload- Preload on hover/focus for perceived speed
3. Server-Side Performance (HIGH)
server-auth-actions- Authenticate server actions like API routesserver-cache-react- Use React.cache() for per-request deduplicationserver-cache-lru- Use LRU cache for cross-request cachingserver-dedup-props- Avoid duplicate serialization in RSC propsserver-hoist-static-io- Hoist static I/O (fonts, logos) to module levelserver-no-shared-module-state- Avoid module-level mutable request state in RSC/SSRserver-serialization- Minimize data passed to client componentsserver-parallel-fetching- Restructure components to parallelize fetchesserver-parallel-nested-fetching- Chain nested fetches per item in Promise.allserver-after-nonblocking- Use after() for non-blocking operations
4. Client-Side Data Fetching (MEDIUM-HIGH)
client-swr-dedup- Use SWR for automatic request deduplicationclient-event-listeners- Deduplicate global event listenersclient-passive-event-listeners- Use passive listeners for scrollclient-localstorage-schema- Version and minimize localStorage data
5. Re-render Optimization (MEDIUM)
rerender-defer-reads- Don't subscribe to state only used in callbacksrerender-memo- Extract expensive work into memoized componentsrerender-memo-with-default-value- Hoist default non-primitive propsrerender-dependencies- Use primitive dependencies in effectsrerender-derived-state- Subscribe to derived booleans, no
Guides
- Claude Code Skills Examples: 7 Real Skills and What Their SKILL.md Files Actually Do
Claude Code skills are markdown instruction files that teach the agent one job. This guide walks through 7 real examples spanning discovery, UI generation, plan review, TDD, framework rules, browser automation, and Postgres tuning - led by find-skills at 2,438,642 installs (skills.sh registry, July 2026) - plus the SKILL.md anatomy and a minimal skeleton.
Related skills
How it compares
Use vercel-react-best-practices for Vercel-official React/Next.js perf rules; use general linting for syntax and style only.
FAQ
How many rules does this skill contain?
It contains 70 rules across 8 categories, prioritized by impact.
What categories do the rules cover?
Eliminating waterfalls, bundle size, server-side performance, client-side fetching, re-render, rendering, JavaScript, and advanced patterns.
Who maintains it?
It is maintained by Vercel and reflects patterns Vercel Engineering uses.
Is Vercel React Best Practices safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.