Agent skill

Vercel React Best Practices Skill: 70 Performance Rules

The vercel-react-best-practices skill gives an AI coding agent 70 React and Next.js performance rules from Vercel Engineering, ranked by impact from waterfalls to micro-optimizations.

Install
git clone https://github.com/vercel-labs/agent-skills.git
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the vercel-react-best-practices skill?

vercel-react-best-practices is a skill in Vercel's agent-skills repository with 70 React and Next.js performance rules across 8 categories, prioritized by impact. Your agent applies it when writing, reviewing or refactoring components, data fetching and bundles. Each rule has an incorrect and a correct code example.

vercel-react-best-practices is a skill in the vercel-labs/agent-skills repository. Its folder is skills/react-best-practices, and its SKILL.md describes React and Next.js performance guidelines from Vercel Engineering: 70 rules across 8 categories, prioritized by impact.

The description says to use it when writing, reviewing or refactoring React and Next.js code, covering components, pages, data fetching, bundle optimization and performance work. Each rule is its own file, and a compiled AGENTS.md holds the full guide.

The eight rule categories

PriorityCategoryImpact
1Eliminating waterfallsCritical
2Bundle size optimizationCritical
3Server-side performanceHigh
4Client-side data fetchingMedium-high
5Re-render optimizationMedium
6Rendering performanceMedium
7JavaScript performanceLow-medium
8Advanced patternsLow

What changes in your agent's output

  • Independent awaits go through Promise.all, and awaits move into the branch that uses them instead of blocking the whole function.
  • Imports go directly to the module instead of through barrel files, and heavy components load with next/dynamic.
  • Server actions are authenticated like API routes, and only the data a client component needs is passed to it.
  • Derived state is computed during render, not in effects, and interaction logic lives in event handlers.
  • Conditional rendering uses a ternary instead of &&.

Who the skill is for

Best for

  • React and Next.js projects where agents write components, pages or data fetching.
  • Performance reviews of existing code, from bundle size to re-renders.
  • Teams that want one ranked rule set instead of ad hoc performance advice.

Not for

  • Visual design or accessibility review. web-design-guidelines audits UI code against interface rules.
  • Animation work. Use emil-design-eng for motion and feel.
  • Non-React stacks, since every rule is written for React and Next.js.

Use it with UiChemy

This skill tunes React code you ship yourself. If your site is on WordPress, UiChemy covers that path: AI to WordPress imports an AI-built page and Composer edits it in Elementor or Gutenberg. Click Get Started on uichemy.com. For page speed beyond React code, see the web performance skill.