vercel-react-best-practices

Apply 57 prioritized rules to optimize React and Next.js performance.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/EdwinFermin/innvox --skill vercel-react-best-practices-edwinfermin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/EdwinFermin/innvox/tree/main/.agents/skills/vercel-react-best-practices
Command: npx skills add https://github.com/EdwinFermin/innvox --skill vercel-react-best-practices-edwinfermin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React and Next.js performance optimization guidelines from Vercel Engineering help teams write, review, and refactor code to ensure optimal performance patterns. They address common patterns that cause waterfalls, large bundle sizes, and server/client inefficiencies, providing a structured playbook for frontend optimization.

Core Features & Use Cases

  • 57 rules across 8 categories prioritized by impact to guide automated refactoring and code generation.
  • Clear guidance for eliminating waterfalls, bundle optimization, server-side performance, and client-side data fetching strategies.
  • Use cases include writing new components, reviewing code, and refactoring existing projects to improve TTI, LCP, and bundle size.

Quick Start

Start by reviewing the guidelines and apply the 57 rules across the eight categories to your React/Next.js codebase.

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 component refactoring?

Optimize React and Next.js performance by applying a structured playbook of 57 rules across 8 impact-prioritized categories to guide automated refactoring, eliminating waterfalls, large bundle sizes, and server/client inefficiencies.

What causes large bundle sizes and data fetching waterfalls in Next.js?

Large bundle sizes and data fetching waterfalls in Next.js are caused by common inefficient server/client patterns, which can be resolved using structured guidelines targeting client-side data fetching strategies and bundle optimization.

Does this React performance guide work for both new components and existing projects?

Yes, this React performance guide applies to writing new components, reviewing code, and refactoring existing projects to improve TTI, LCP, and bundle size using Vercel Engineering guidelines.

What is the best way to eliminate server-side performance inefficiencies in Next.js?

The best way to eliminate server-side performance inefficiencies in Next.js is to apply impact-prioritized optimization rules that specifically address server/client boundaries and rendering strategies.

How do I improve LCP and TTI metrics in a React frontend application?

Improve LCP and TTI metrics in a React frontend by applying structured performance optimization guidelines that address bundle optimization, eliminate data waterfalls, and refine client-side data fetching strategies.

When should I not use client-side data fetching in React applications?

You should avoid client-side data fetching in React applications when it causes data waterfalls or server/client inefficiencies, applying the guidelines to identify when server-side performance patterns are more optimal.