
Vercel React Best Practices
- 88 installs
- 8 repo stars
- Updated February 11, 2026
- vercel-labs/cursor-plugin
A curated set of 57 performance rules for React/Next.js categorized by impact (critical, high, medium, low), each with code examples, rationale, and GitHub-fetched detailed guidance.
About
Comprehensive performance optimization skill maintained by Vercel Engineering containing 57 rules across 8 prioritized categories. Guides developers writing, reviewing, or refactoring React and Next.js code to eliminate waterfalls, reduce bundle size, optimize server-side rendering, and improve client-side data fetching. Rules span from critical patterns like Promise.all() parallelization and dynamic imports to advanced techniques like useLatest and event handler refs. Each rule includes incorrect/correct code examples and detailed rationale for impact.
- 57 rules prioritized by performance impact across 8 categories
- Critical rules: waterfall elimination and bundle optimization patterns
- Server-side performance guidance: React.cache(), LRU caching, parallel fetching
- Re-render optimization: memoization, dependency management, useTransition
- Maintained by Vercel Engineering with fetched rule examples from GitHub
Vercel React Best Practices by the numbers
- 88 all-time installs (skills.sh)
- Ranked #1,093 of 2,245 Frontend Development skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 20, 2026 (Skillselion catalog sync)
vercel-react-best-practices capabilities & compatibility
- Capabilities
- identify performance anti patterns in react/next · recommend rule based refactoring with priority l · provide correct code examples for each optimizat · guide server component vs client component trade · suggest bundle splitting and code splitting stra
- Works with
- github
- Use cases
- code review · refactoring · frontend · documentation
What vercel-react-best-practices says it does
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 patter
Contains 57 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
npx skills add https://github.com/vercel-labs/cursor-plugin --skill vercel-react-best-practicesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 88 |
|---|---|
| repo stars | ★ 8 |
| Security audit | 2 / 3 scanners passed |
| Last updated | February 11, 2026 |
| Repository | vercel-labs/cursor-plugin ↗ |
What it does
Optimize React/Next.js performance via 57 prioritized rules for bundle size, waterfalls, and rendering efficiency.
Who is it for?
Development teams building production React/Next.js applications requiring systematic performance reviews, refactoring guidance, and code generation alignment with Vercel best practices.
Skip if: Static site generators, non-React frameworks, or teams without strict performance targets; not for Vue, Angular, or Svelte projects.
When should I use this skill?
Writing new React components, implementing data fetching, reviewing code for performance, refactoring legacy React/Next.js codebases, or optimizing bundle size and load times.
What you get
Engineers apply rules to eliminate sequential data dependencies, reduce JavaScript payload, optimize server rendering, deduplicate requests, and implement efficient re-render strategies, improving Core Web Vitals and per
- Prioritized list of applicable optimization rules
- Incorrect-to-correct code refactoring examples
- Performance impact rationale for each rule
By the numbers
- 57 total optimization rules
- 8 categories by priority (1=critical to 8=advanced)
- ~80KB full guide with all code examples
Files
Vercel React Best Practices
Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel Engineering. Contains 57 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
Loading the Full Guide
The complete rules document with all code examples is maintained at:
https://raw.githubusercontent.com/vercel-labs/agent-skills/main/skills/react-best-practices/AGENTS.mdWhen you need detailed rule guidance, fetch the full document from the URL above using your web fetch tool. The document is ~80KB and contains all 57 rules with incorrect/correct code examples.
For individual rules, fetch:
https://raw.githubusercontent.com/vercel-labs/agent-skills/main/skills/react-best-practices/rules/{rule-name}.mdWhen 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-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-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-serialization— Minimize data passed to client componentsserver-parallel-fetching— Restructure components to parallelize fetchesserver-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, not raw valuesrerender-derived-state-no-effect— Derive state during render, not effectsrerender-functional-setstate— Use functional setState for stable callbacksrerender-lazy-state-init— Pass function to useState for expensive valuesrerender-simple-expression-in-memo— Avoid memo for simple primitivesrerender-move-effect-to-event— Put interaction logic in event handlersrerender-transitions— Use startTransition for non-urgent updatesrerender-use-ref-transient-values— Use refs for transient frequent values
6. Rendering Performance (MEDIUM)
rendering-animate-svg-wrapper— Animate div wrapper, not SVG elementrendering-content-visibility— Use content-visibility for long listsrendering-hoist-jsx— Extract static JSX outside componentsrendering-svg-precision— Reduce SVG coordinate precisionrendering-hydration-no-flicker— Use inline script for client-only datarendering-hydration-suppress-warning— Suppress expected mismatchesrendering-activity— Use Activity component for show/hiderendering-conditional-render— Use ternary, not && for conditionalsrendering-usetransition-loading— Prefer useTransition for loading state
7. JavaScript Performance (LOW-MEDIUM)
js-batch-dom-css— Group CSS changes via classes or cssTextjs-index-maps— Build Map for repeated lookupsjs-cache-property-access— Cache object properties in loopsjs-cache-function-results— Cache function results in module-level Mapjs-cache-storage— Cache localStorage/sessionStorage readsjs-combine-iterations— Combine multiple filter/map into one loopjs-length-check-first— Check array length before expensive comparisonjs-early-exit— Return early from functionsjs-hoist-regexp— Hoist RegExp creation outside loopsjs-min-max-loop— Use loop for min/max instead of sortjs-set-map-lookups— Use Set/Map for O(1) lookupsjs-tosorted-immutable— Use toSorted() for immutability
8. Advanced Patterns (LOW)
advanced-event-handler-refs— Store event handlers in refsadvanced-init-once— Initialize app once per app loadadvanced-use-latest— useLatest for stable callback refs
How to Use
When a user asks about React/Next.js performance, or when writing/reviewing React code:
1. Identify the relevant category from the priority table above 2. Fetch the specific rule from GitHub for detailed guidance:
https://raw.githubusercontent.com/vercel-labs/agent-skills/main/skills/react-best-practices/rules/{rule-name}.md3. Or fetch the full guide for comprehensive review:
https://raw.githubusercontent.com/vercel-labs/agent-skills/main/skills/react-best-practices/AGENTS.md4. Apply the rule's correct pattern, explaining why it matters
Each rule file contains:
- Brief explanation of why it matters
- Incorrect code example with explanation
- Correct code example with explanation
- Additional context and references
Source
Maintained by Vercel Engineering at github.com/vercel-labs/agent-skills.
Related skills
FAQ
Is Vercel React Best Practices safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.