vercel-react-best-practices

Apply React and Next.js performance rules to components, pages, and data fetching.

2|Updated May 13, 2026
One-click install
npx skills add https://github.com/danger-English/claude-code-intro --skill vercel-react-best-practices-danger-english
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/danger-English/claude-code-intro/tree/main/skills/vercel-react-best-practices
Command: npx skills add https://github.com/danger-English/claude-code-intro --skill vercel-react-best-practices-danger-english

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates React and Next.js performance guidelines authored by Vercel Engineering to help teams write, review, and refactor code with performance in mind, reducing common bottlenecks and inefficiencies.

Core Features & Use Cases

  • 70 rules across 8 priority-driven categories, designed to guide automated refactoring and code generation.
  • Clear category prefixes (async-, bundle-, server-, client-, rerender-, rendering-, js-, advanced-) to organize patterns by impact and domain.
  • Practical guidance for React components, Next.js pages, data fetching strategies, and bundle optimization in real-world projects.

Quick Start

Review the 70 rules and apply the most impactful patterns during React/Next.js optimizations.

Frequently Asked Questions about vercel-react-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize React and Next.js performance during code refactoring?

Apply a structured taxonomy of 70 rules across 8 priority-driven categories covering bundling, SSR, and server actions to guide automated React and Next.js refactoring workflows and eliminate common UI bottlenecks.

What are the best practices for Next.js data fetching and bundle optimization?

Best practices for Next.js data fetching and bundle optimization involve applying category-prefixed rules (async-, bundle-, server-) that organize performance patterns by domain impact to streamline data-fetch strategies and reduce bundle size.

How does a rule-based taxonomy help with React component code generation?

A rule-based taxonomy drives automated code generation by using clear category prefixes (client-, rerender-, rendering-, js-) to systematically enforce performance guidelines when writing or refactoring React components and Next.js pages.

Can I use these performance guidelines for reviewing existing React applications?

Yes, you can use these Vercel engineering performance guidelines to review existing React applications by evaluating components and pages against 70 rules to identify and refactor performance inefficiencies across the codebase.

When should I apply server-side rendering optimization rules in Next.js?

Apply server-side rendering optimization rules in Next.js when refactoring pages and data-fetch patterns, utilizing the server- and advanced- category prefixes to enforce SSR performance guidelines and reduce rendering bottlenecks.