vercel-react-best-practices

To optimize React and Next.js performance during a migration, apply 57 structured rules across eight priority categories incrementally. This process targets rendering, data fetching, and bundle optimization to prevent waterfalls and improve user experience safely.

Best practices for preventing Next.js data fetching waterfalls involve applying prioritized patterns for both client and server code. This targets sequential fetching bottlenecks directly to improve overall UI responsiveness.

Yes, you can use automated refactoring to fix React bundle optimization issues because the skill provides guardrails and testable rules. These guardrails ensure safe, automated code generation workflows for bundle and rendering improvements.

Yes, this approach fully supports both client and server rendering patterns in Next.js. It provides prioritized optimization guidance for client and server code, enforcing testable rules across both environments to prevent waterfalls.

You should apply server actions for Next.js performance optimization when addressing data fetching and rendering bottlenecks. They are part of eight prioritized categories that provide guardrails for safe, incremental refactoring to improve user experience.

The best way to review React components for performance bottlenecks is identifying high-impact rules across async, bundle, server, and client categories. Applying these testable rules incrementally during component reviews ensures safe performance improvements.