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.

rulesjs-batch-dom-css.md

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

Avoid Layout Thrashing

Avoid interleaving style writes with layout reads. When you read a layout property (like offsetWidth, getBoundingClientRect(), or getComputedStyle()) between style changes, the browser is forced to trigger a synchronous reflow.

This is OK (browser batches style changes):

function updateElementStyles(element: HTMLElement) {
  // Each line invalidates style, but browser batches the recalculation
  element.style.width = '100px'
  element.style.height = '200px'
  element.style.backgroundColor = 'blue'
  element.style.border = '1px solid black'
}

Incorrect (interleaved reads and writes force reflows):

function layoutThrashing(element: HTMLElement) {
  element.style.width = '100px'
  const width = element.offsetWidth  // Forces reflow
  element.style.height = '200px'
  const height = element.offsetHeight  // Forces another reflow
}

Correct (batch writes, then read once):

function updateElementStyles(element: HTMLElement) {
  // Batch all writes together
  element.style.width = '100px'
  element.style.height = '200px'
  element.style.backgroundColor = 'blue'
  element.style.border = '1px solid black'
  
  // Read after all writes are done (single reflow)
  const { width, height } = element.getBoundingClientRect()
}

Correct (batch reads, then writes):

function avoidThrashing(element: HTMLElement) {
  // Read phase - all layout queries first
  const rect1 = element.getBoundingClientRect()
  const offsetWidth = element.offsetWidth
  const offsetHeight = element.offsetHeight
  
  // Write phase - all style changes after
  element.style.width = '100px'
  element.style.height = '200px'
}

Better: use CSS classes

.highlighted-box {
  width: 100px;
  height: 200px;
  background-color: blue;
  border: 1px solid black;
}
function updateElementStyles(element: HTMLElement) {
  element.classList.add('highlighted-box')
  
  const { width, height } = element.getBoundingClientRect()
}

React example:

// Incorrect: interleaving style changes with layout queries
function Box({ isHighlighted }: { isHighlighted: boolean }) {
  const ref = useRef<HTMLDivElement>(null)
  
  useEffect(() => {
    if (ref.current && isHighlighted) {
      ref.current.style.width = '100px'
      const width = ref.current.offsetWidth // Forces layout
      ref.current.style.height = '200px'
    }
  }, [isHighlighted])
  
  return <div ref={ref}>Content</div>
}

// Correct: toggle class
function Box({ isHighlighted }: { isHighlighted: boolean }) {
  return (
    <div className={isHighlighted ? 'highlighted-box' : ''}>
      Content
    </div>
  )
}

Prefer CSS classes over inline styles when possible. CSS files are cached by the browser, and classes provide better separation of concerns and are easier to maintain.

See this gist and CSS Triggers for more information on layout-forcing operations.

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.