react-best-practices

To audit React components, you analyze re-renders, data fetching waterfalls, and bundle sizes. This skill applies a prioritized checklist of 57 Vercel rules to identify and remediate inefficient rendering paths across React and Next.js apps.

Unnecessary re-renders in Next.js server components often stem from inefficient data fetching, improper serialization, or bloated client-render paths. The skill's rules provide concrete examples to optimize component rendering and enforce best practices for faster interactions.

Yes, you can fix large bundle sizes by applying the skill's audit rules. It identifies bloated bundles and provides actionable, prioritized guidance to optimize component rendering and data fetching for more responsive web applications.

The best way to optimize data fetching in React is to follow prioritized performance rules that address waterfalls and serialization. This skill provides a checklist of 57 actionable rules with concrete examples to guide remediation.

Yes, the audit covers both client and server rendering paths. It enforces a prioritized checklist of 57 Vercel rules, targeting re-renders, bundle size, and server interactions across React and Next.js projects.

Your React application may be slow due to inefficient re-renders, data fetching waterfalls, or bloated bundle sizes. Auditing the codebase against 57 prioritized performance rules helps identify and remediate these specific bottlenecks.