All skills
vercel-labs avatar

/react-best-practices

@805687f official
by Vercel Labsvercel-labs/agent-skills32k stars
2,784

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.

Use this Skill: https://skilld.dev/gh/vercel-labs/agent-skills/react-best-practices

This session only. Nothing lands on disk.

rulesrerender-functional-setstate.md

≈742 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Use Functional setState Updates

When updating state based on the current state value, use the functional update form of setState instead of directly referencing the state variable. This prevents stale closures, eliminates unnecessary dependencies, and creates stable callback references.

Incorrect (requires state as dependency):

function TodoList() {
  const [items, setItems] = useState(initialItems)
  
  // Callback must depend on items, recreated on every items change
  const addItems = useCallback((newItems: Item[]) => {
    setItems([...items, ...newItems])
  }, [items])  // ❌ items dependency causes recreations
  
  // Risk of stale closure if dependency is forgotten
  const removeItem = useCallback((id: string) => {
    setItems(items.filter(item => item.id !== id))
  }, [])  // ❌ Missing items dependency - will use stale items!
  
  return <ItemsEditor items={items} onAdd={addItems} onRemove={removeItem} />
}

The first callback is recreated every time items changes, which can cause child components to re-render unnecessarily. The second callback has a stale closure bug—it will always reference the initial items value.

Correct (stable callbacks, no stale closures):

function TodoList() {
  const [items, setItems] = useState(initialItems)
  
  // Stable callback, never recreated
  const addItems = useCallback((newItems: Item[]) => {
    setItems(curr => [...curr, ...newItems])
  }, [])  // ✅ No dependencies needed
  
  // Always uses latest state, no stale closure risk
  const removeItem = useCallback((id: string) => {
    setItems(curr => curr.filter(item => item.id !== id))
  }, [])  // ✅ Safe and stable
  
  return <ItemsEditor items={items} onAdd={addItems} onRemove={removeItem} />
}

Benefits:

  1. Stable callback references - Callbacks don't need to be recreated when state changes
  2. No stale closures - Always operates on the latest state value
  3. Fewer dependencies - Simplifies dependency arrays and reduces memory leaks
  4. Prevents bugs - Eliminates the most common source of React closure bugs

When to use functional updates:

  • Any setState that depends on the current state value
  • Inside useCallback/useMemo when state is needed
  • Event handlers that reference state
  • Async operations that update state

When direct updates are fine:

  • Setting state to a static value: setCount(0)
  • Setting state from props/arguments only: setName(newName)
  • State doesn't depend on previous value

Note: If your project has React Compiler enabled, the compiler can automatically optimize some cases, but functional updates are still recommended for correctness and to prevent stale closure bugs.

Source: SKILL.md on GitHub

No alerts16d4 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides a comprehensive set of performance optimization and best practice guidelines for React and Next.js applications. No security issues or risky patterns were detected.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    1/63 files flagged

Signed by skilld at 805687f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 6 months ago
metadata
{
  "author": "vercel",
  "version": "1.0.0"
}

README badge

README badge for vercel-labs/agent-skills/react-best-practices

Provides 70 React and Next.js performance optimization rules organized by priority, from eliminating waterfalls and bundle size optimization to re-render and rendering performance. Use this skill when writing, reviewing, or refactoring React/Next.js code to apply Vercel's performance patterns for data fetching, component structure, and bundle optimization.

Generated from the current SKILL.md.

Does this skill cover both React and Next.js?
Yes. The skill includes guidelines for React components, Next.js pages, server-side rendering, server actions, and data fetching patterns across both frameworks.
Are these rules ranked by importance?
Yes. Rules are organized into 8 categories ranked by impact, from eliminating waterfalls and bundle optimization (CRITICAL) down to advanced patterns (LOW).
Can this skill be used during code review and refactoring?
Yes. The skill is intended for writing new code, reviewing existing code for performance issues, and refactoring React/Next.js applications.
Does this skill include code examples?
Yes. Each of the 70 rules has a detailed file with incorrect and correct code examples, explanations, and additional context.

Generated from the current SKILL.md. These answers refresh after source changes.