All skills
vercel-labs avatar

/vercel-react-best-practices

@805687f
by Vercel Labsvercel-labs/openreview1.7k stars
118

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/openreview/vercel-react-best-practices

This session only. Nothing lands on disk.

rulesjs-length-check-first.md

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

Early Length Check for Array Comparisons

When comparing arrays with expensive operations (sorting, deep equality, serialization), check lengths first. If lengths differ, the arrays cannot be equal.

In real-world applications, this optimization is especially valuable when the comparison runs in hot paths (event handlers, render loops).

Incorrect (always runs expensive comparison):

function hasChanges(current: string[], original: string[]) {
  // Always sorts and joins, even when lengths differ
  return current.sort().join() !== original.sort().join();
}

Two O(n log n) sorts run even when current.length is 5 and original.length is 100. There is also overhead of joining the arrays and comparing the strings.

Correct (O(1) length check first):

function hasChanges(current: string[], original: string[]) {
  // Early return if lengths differ
  if (current.length !== original.length) {
    return true;
  }
  // Only sort when lengths match
  const currentSorted = current.toSorted();
  const originalSorted = original.toSorted();
  for (let i = 0; i < currentSorted.length; i++) {
    if (currentSorted[i] !== originalSorted[i]) {
      return true;
    }
  }
  return false;
}

This new approach is more efficient because:

  • It avoids the overhead of sorting and joining the arrays when lengths differ
  • It avoids consuming memory for the joined strings (especially important for large arrays)
  • It avoids mutating the original arrays
  • It returns early when a difference is found

Source: SKILL.md on GitHub

No alerts17d4 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    This skill provides rules, tools, and scripts intended for compiling and managing React and Next.js performance optimization guidelines. No high-severity security considerations or anomalous patterns were discovered.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer6mo

    1/61 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 2 months ago.

Dormantupdated 7 months ago
metadata
{
  "author": "vercel",
  "version": "1.0.0"
}
  • React
  • Performance
  • next.js
  • optimization
  • bundle-size
  • server-components
  • data-fetching
  • rendering
  • javascript

README badge

README badge for vercel-labs/openreview/vercel-react-best-practices

Provides 58 prioritized React and Next.js performance rules from Vercel Engineering, organized across waterfalls, bundle size, server/client data fetching, re-renders, and rendering patterns. Use when writing or refactoring React components and Next.js pages to apply production-grade optimization practices.

Generated from the current SKILL.md.

Does this skill apply to both React and Next.js?
Yes. The skill covers React components, Next.js pages, server components, server actions, and data fetching patterns for both frameworks.
Can I use this skill to review existing code for performance issues?
Yes. The skill is designed for reviewing and refactoring React/Next.js code against 58 prioritized rules organized by impact (critical, high, medium, low).
Does this skill cover bundle size optimization?
Yes. Bundle size optimization is marked as a critical priority category with 5 rules, including barrel imports, dynamic imports, and third-party script deferral.
What about server-side performance and data fetching?
The skill covers both. It includes rules for server components, React.cache(), LRU caching, parallel fetching, and client-side patterns like SWR deduplication and event listener optimization.

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