vercel-react-best-practices

Diagnose React and Next.js performance bottlenecks with 69 prioritized rules.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Fabianrzs/car-wash --skill vercel-react-best-practices-fabianrzs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/Fabianrzs/car-wash/tree/main/.agents/skills/vercel-react-best-practices
Command: npx skills add https://github.com/Fabianrzs/car-wash --skill vercel-react-best-practices-fabianrzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React and Next.js performance can degrade as projects scale, leading to slower renders, bloated bundles, and inefficient data fetching. This Skill provides a curated, category-driven set of proven patterns to diagnose and fix performance bottlenecks across modern React apps.

Core Features & Use Cases

  • 69 rules across 8 priority-driven categories with concrete examples and guardrails, designed to guide automated refactoring and code generation.
  • Guidance for writing, reviewing, and refactoring React/Next.js code to improve load times, memory usage, and SSR/CSR performance.
  • Real-world scenarios covering data fetching, code-splitting, and server-rendered pages to ensure scalable improvements.

Quick Start

Analyze a current React/Next.js project and begin applying the top-priority rules to reduce waterfalls, trim bundle size, and optimize server rendering.

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 large scaling projects?

To optimize React and Next.js performance, apply category-driven rules to diagnose and fix bottlenecks like slow renders and bloated bundles. This provides concrete examples and guardrails to guide automated refactoring for scalable improvements across load times and memory usage.

What are the best practices for reducing bundle size in React applications?

Best practices for reducing bundle size involve applying priority-driven rules for code-splitting and efficient data fetching. This approach trims unnecessary code and ensures scalable improvements in application load times.

How do I fix inefficient data fetching waterfalls in server-rendered React pages?

Fixing inefficient data fetching waterfalls in server-rendered React pages requires applying curated patterns that reduce sequential fetching. This ensures optimized server-side rendering and improved data loading performance.

Can I use these best practices to guide automated refactoring of existing React code?

Yes, you can use these best practices to guide automated refactoring of existing React code. The 69 rules across 8 categories provide concrete examples and guardrails specifically designed to direct code generation and automated refactoring tasks.

When should I refactor React code to improve SSR and CSR performance?

You should refactor React code to improve SSR and CSR performance when projects scale and experience slower renders or bloated bundles. Applying these patterns during code review and refactoring ensures optimized load times and memory usage.