vercel-react-best-practices

Apply React and Next.js performance best practices to optimize code.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Division6066/tempo-rhythm --skill vercel-react-best-practices-division6066
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/Division6066/tempo-rhythm/tree/main/.agents/skills/vercel-react-best-practices
Command: npx skills add https://github.com/Division6066/tempo-rhythm --skill vercel-react-best-practices-division6066

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React and Next.js projects often struggle with performance pitfalls such as waterfalls, large bundles, slow SSR, and unnecessary re-renders. This Skill provides a structured collection of proven best practices to identify and apply performance patterns across components, pages, and data-fetching strategies.

Core Features & Use Cases

  • A categorized catalog of guidelines covering Eliminating Waterfalls, Bundle Size Optimization, Server-Side Performance, Client-Side Data Fetching, Re-render Optimization, Rendering Performance, JavaScript Performance, and Advanced Patterns.
  • Practical use cases like parallelizing fetches in API routes, using dynamic imports and Suspense boundaries, and applying per-request caching and safe data serialization.
  • Guidance for automated refactoring and code-generation tasks to improve load times and user-perceived performance.

Quick Start

Review a React/Next.js codebase and rewrite it to follow the Vercel React Best Practices for performance optimization.

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 for slow server-side rendering and large bundle sizes?

To optimize React and Next.js performance, apply best practices covering bundle size reduction, server-side rendering improvements, and re-render optimization. These guidelines help refactor components and data-fetching strategies to resolve slow SSR and large bundles.

What is the best way to eliminate data-fetching waterfalls in Next.js API routes?

Eliminate data-fetching waterfalls in Next.js by parallelizing fetches within API routes. This technique avoids sequential blocking and pairs with per-request caching and safe data serialization to improve overall server-side performance.

How do I reduce bundle size in a React application using dynamic imports and Suspense boundaries?

Reduce React bundle size by using dynamic imports alongside Suspense boundaries. This combination defers loading non-critical JavaScript until required, minimizing the initial payload and improving user-perceived performance.

Can I use these React performance best practices when reviewing and refactoring existing Next.js pages?

Yes, these React performance best practices are explicitly applicable when writing, reviewing, or refactoring Next.js pages. The guidelines provide guardrails and examples suitable for automated refactoring tasks across existing project codebases.

Why does my React component re-render unnecessarily and how do I apply rendering optimization patterns?

React components re-render unnecessarily due to improper state management or prop changes. Apply re-render optimization patterns from this catalog to identify bottlenecks, restructure components, and improve client-side data fetching and rendering performance.

When should I not use dynamic imports for JavaScript performance optimization in Next.js?

Avoid dynamic imports when the module is critical for above-the-fold rendering or initial server-side load. Overusing Suspense boundaries for immediately needed content degrades user-perceived performance, so apply these patterns selectively for non-critical bundle size reduction.