| name | vercel-react-best-practices |
| description | 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. |
| license | MIT |
| metadata | {"author":"vercel","version":"1.0.0"} |
On-demand loading: Read individual rule files from rules/ only when the specific category is relevant to the current task. Do not load AGENTS.md unless a full compiled reference is explicitly needed.
When to use
- React and Next.js performance optimization guidelines from Vercel Engineering.
Vercel React Best Practices
Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 57 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- |
How to Use
For detailed explanations and code examples, read the specific rule file:
rules/<prefix>-<rule>.md # e.g. rules/async-parallel.md
Each rule file contains: why it matters, incorrect vs correct examples, references.
Full compiled guide (57 rules): AGENTS.md — load only on demand.