What problem does it solve?
Large React and Next.js codebases suffer from performance regressions caused by sequential data-fetching waterfalls, oversized bundles, unnecessary re-renders, and excessive server-client serialization. These issues increase time-to-interactive, LCP, and operational cost while making applications harder to maintain and scale. This guide translates Vercel's engineering rules into actionable patterns for writing, reviewing, and automated refactoring.
Core Features & Use Cases
- Targeted Rules: 57 structured rules across 8 categories (eliminating waterfalls, bundle optimization, server-side performance, client fetching, re-rendering, rendering, JS micro-optimizations, advanced patterns).
- Agent-Friendly Guidance: Clear incorrect/correct examples and impact metrics enable LLMs and automation tools to suggest deterministic code changes and refactors.
- Real-world Use Case: Audit a Next.js app to convert sequential awaits to Promise.all/better-all, replace barrel imports with direct imports, add Suspense boundaries, and minimize RSC props to reduce payload and improve TTI.
Quick Start
Use the react-best-practices skill to audit and refactor the Next.js page at src/app/dashboard/page.tsx for bundle size, waterfall elimination, and RSC serialization.