home / skills / benchflow-ai / skillsbench / react-best-practices

This skill helps you apply Vercel React best practices to React and Next.js code to reduce CLS, hydration issues, and improve performance.

npx playbooks add skill benchflow-ai/skillsbench --skill react-best-practices

Review the files below or copy the command above to add this skill to your agents.

Files (50)
SKILL.md
5.2 KB
---
name: react-best-practices
description: "**IMPORTANT**: Any change to React or Next.js code must read through this skill first. React and Next.js guidelines from Vercel Engineering covering visual instability, layout shifts, CLS, flickering, hydration issues, and font loading."
license: MIT
metadata:
  author: vercel
  version: "1.0.0"
---

# Vercel React Best Practices

Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 45 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

## When to Apply

Reference these guidelines when:

- Refactoring existing React/Next.js code
- Writing new React components or Next.js pages
- Fixing visual instability or layout shift (CLS) issues
- Preventing flickering when reading from localStorage or cookies
- Handling hydration mismatches with client-only data
- Optimizing font loading (FOIT/FOUT prevention)
- Adding proper dimensions to images and dynamic content

## 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 used
- `async-parallel` - Use Promise.all() for independent operations
- `async-dependencies` - Use better-all for partial dependencies
- `async-api-routes` - Start promises early, await late in API routes
- `async-suspense-boundaries` - Use Suspense to stream content

### 2. Bundle Size Optimization (CRITICAL)

- `bundle-barrel-imports` - Import directly, avoid barrel files
- `bundle-dynamic-imports` - Use next/dynamic for heavy components
- `bundle-defer-third-party` - Load analytics/logging after hydration
- `bundle-conditional` - Load modules only when feature is activated
- `bundle-preload` - Preload on hover/focus for perceived speed

### 3. Server-Side Performance (HIGH)

- `server-cache-react` - Use React.cache() for per-request deduplication
- `server-cache-lru` - Use LRU cache for cross-request caching
- `server-serialization` - Minimize data passed to client components
- `server-parallel-fetching` - Restructure components to parallelize fetches
- `server-after-nonblocking` - Use after() for non-blocking operations

### 4. Client-Side Data Fetching (MEDIUM-HIGH)

- `client-swr-dedup` - Use SWR for automatic request deduplication
- `client-event-listeners` - Deduplicate global event listeners

### 5. Re-render Optimization (MEDIUM)

- `rerender-defer-reads` - Don't subscribe to state only used in callbacks
- `rerender-memo` - Extract expensive work into memoized components
- `rerender-dependencies` - Use primitive dependencies in effects
- `rerender-derived-state` - Subscribe to derived booleans, not raw values
- `rerender-functional-setstate` - Use functional setState for stable callbacks
- `rerender-lazy-state-init` - Pass function to useState for expensive values
- `rerender-transitions` - Use startTransition for non-urgent updates

### 6. Rendering Performance (MEDIUM)

- `rendering-animate-svg-wrapper` - Animate div wrapper, not SVG element
- `rendering-content-visibility` - Use content-visibility for long lists
- `rendering-hoist-jsx` - Extract static JSX outside components
- `rendering-svg-precision` - Reduce SVG coordinate precision
- `rendering-hydration-no-flicker` - Use inline script for client-only data
- `rendering-activity` - Use Activity component for show/hide
- `rendering-conditional-render` - Use ternary, not && for conditionals

### 7. JavaScript Performance (LOW-MEDIUM)

- `js-batch-dom-css` - Group CSS changes via classes or cssText
- `js-index-maps` - Build Map for repeated lookups
- `js-cache-property-access` - Cache object properties in loops
- `js-cache-function-results` - Cache function results in module-level Map
- `js-cache-storage` - Cache localStorage/sessionStorage reads
- `js-combine-iterations` - Combine multiple filter/map into one loop
- `js-length-check-first` - Check array length before expensive comparison
- `js-early-exit` - Return early from functions
- `js-hoist-regexp` - Hoist RegExp creation outside loops
- `js-min-max-loop` - Use loop for min/max instead of sort
- `js-set-map-lookups` - Use Set/Map for O(1) lookups
- `js-tosorted-immutable` - Use toSorted() for immutability

### 8. Advanced Patterns (LOW)

- `advanced-event-handler-refs` - Store event handlers in refs
- `advanced-use-latest` - useLatest for stable callback refs

## How to Use

Read individual rule files for detailed explanations and code examples:

```
rules/async-parallel.md
rules/bundle-barrel-imports.md
rules/_sections.md
```

Each rule file contains:
- Brief explanation of why it matters
- Incorrect code example with explanation
- Correct code example with explanation
- Additional context and references

Overview

This skill enforces Vercel React and Next.js best practices to prevent visual instability, layout shifts (CLS), flickering, hydration mismatches, and font-loading issues. It prioritizes 45 concrete rules across eight categories so any change to React or Next.js code is checked and refactored for performance and stability. Use it as a gatekeeper before committing or deploying UI and server-rendered changes.

How this skill works

The skill inspects code for pattern-based anti-patterns and missing optimizations across categories like eliminating waterfalls, bundle size, server performance, client data fetching, render optimizations, and JavaScript micro-optimizations. For each detected issue it returns the relevant rule ID, a short rationale, and suggested corrective changes or refactor snippets to apply. It focuses on outcomes that reduce CLS, eliminate flicker, improve hydration consistency, and cut unnecessary work on the client.

When to use it

  • Before committing or reviewing any React or Next.js changes
  • When refactoring components, pages, or API routes
  • When addressing CLS, flicker, or hydration mismatch reports
  • When optimizing initial load, bundle size, or server-render costs
  • When implementing or fixing font loading and dynamic content sizing

Best practices

  • Run this skill as a mandatory pre-merge check for all React/Next.js code changes
  • Prioritize rules by impact: eliminate waterfalls and reduce bundle size first
  • Prefer parallel fetches and early promise starts for server/API code
  • Defer heavy or third-party modules until after hydration
  • Add explicit dimensions and placeholders to dynamic images and content to prevent layout shifts
  • Use Suspense, startTransition, and memoization to reduce visible re-renders

Example use cases

  • Refactor a page to use Promise.all and Suspense to avoid waterfall rendering
  • Replace barrel imports with direct imports to shrink client bundles
  • Add React.cache or LRU server caching to reduce per-request work
  • Switch client-only localStorage reads to inline script patterns to avoid hydration flicker
  • Defer analytics and heavy third-party widgets until after user interaction

FAQ

Does the skill rewrite code automatically?

It recommends concrete refactors and snippets; automatic application depends on the agent or tooling you run alongside the skill.

Which rules should I fix first?

Start with CRITICAL categories: eliminate waterfalls (async-*) and bundle-size optimizations (bundle-*), then address server-side and client-side performance.