vercel-react-best-practices

Apply React/Next.js performance best practices to components and pages.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React/Next.js projects often suffer from performance regressions due to waterfalls, large bundles, and suboptimal data fetching strategies. This skill consolidates Vercel's performance guidelines into an accessible reference to prevent regressions and accelerate refactoring.

Core Features & Use Cases

  • 57 rules across 8 categories guiding performance improvements from server-side rendering to client rendering.
  • Use cases include writing, reviewing, or refactoring React/Next.js components and pages, optimizing data fetching, code-splitting, and bundle-size optimizations to improve metrics like TTI and LCP.

Quick Start

Apply these guidelines to your codebase to start improving performance today; identify critical patterns like async deferral, parallel data fetching, suspense boundaries, and per-request caching, and begin refactoring accordingly.

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 to reduce large bundle sizes?

Optimize React and Next.js performance by applying 57 rules across 8 categories covering dynamic imports, code-splitting, and bundle-size optimizations. This skill guides refactoring components to enforce correctness, safety, and maintainability guardrails improving metrics like TTI and LCP.

What is the best way to prevent data fetching waterfalls in Next.js?

Prevent data fetching waterfalls in Next.js by applying proven patterns like async deferral and parallel data fetching. This skill enforces category-specific guidelines to optimize data fetching strategies from server-side rendering to client rendering.

How do I use Suspense boundaries for code-splitting in a React application?

Use Suspense boundaries for code-splitting by applying this skill's patterns for dynamic imports and suspense integration. It provides guardrails for writing and refactoring components, ensuring safe and maintainable rendering optimizations.

Does this skill help with refactoring existing components or only writing new ones?

This skill helps with writing, reviewing, and refactoring existing React/Next.js components and pages. It consolidates Vercel's performance guidelines to accelerate refactoring and prevent performance regressions across your codebase.

When should I not use client-side rendering in Next.js?

You should avoid client-side rendering when server-side rendering or static generation better suits your data fetching needs. This skill enforces 8 category-specific patterns to guide rendering choices, checking for correctness, safety, and maintainability.

Why does my React app suffer from performance regressions after adding new pages?

React apps suffer performance regressions due to waterfalls, large bundles, and suboptimal data fetching. This skill applies Vercel's performance guidelines to identify critical patterns like per-request caching and suspense boundaries to prevent regressions.