vercel-react-best-practices

Apply React and Next.js performance best practices to code reviews and refactoring.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/meganide/claude --skill vercel-react-best-practices-meganide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/meganide/claude/tree/main/skills/vercel-react-best-practices
Command: npx skills add https://github.com/meganide/claude --skill vercel-react-best-practices-meganide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a centralized, actionable set of performance guidelines to identify and fix bottlenecks in React and Next.js projects, helping teams ship faster, more reliable apps.

Core Features & Use Cases

  • Category-driven rules covering elimination of waterfalls, bundle size, server and client data fetching, and rendering/performance patterns.
  • Actionable guidance with concrete examples, recommended refactor steps, and measurable outcomes for real-world projects.
  • Use cases include optimizing component rendering, data fetching strategies, and reducing initial load times for Next.js apps.

Quick Start

Audit a React/Next.js page with the guidelines and implement the top-priority fixes to reduce waterfalls and improve perceived performance.

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 fix React and Next.js data fetching waterfalls to improve page performance?

To fix React data fetching waterfalls, apply categorized performance rules that optimize server and client data fetching strategies. This approach eliminates sequential request waterfalls, directly improving Time to Interactive and Largest Contentful Paint metrics.

What are the best practices for optimizing React component rendering and bundle size?

Best practices for React component rendering and bundle size involve applying category-driven rules for SSR and CSR patterns alongside bundling optimizations. These actionable guidelines provide concrete examples and refactoring steps to reduce initial load times.

How do I use server actions in Next.js without creating performance bottlenecks?

Using server actions safely requires following curated performance constraints that guide their design and data fetching patterns. By applying these actionable rules, you prevent waterfalls and ensure speed and reliability during automated refactoring or code reviews.

Does this approach work for auditing existing Next.js apps or only for new component design?

This approach works for both auditing existing apps and new component design. You can audit a React or Next.js page using the categorized guidelines, identify bottlenecks, and implement top-priority fixes to optimize speed, reliability, and rendering patterns.

When should I optimize client-side data fetching versus server-side data fetching in Next.js?

You should optimize client or server data fetching based on categorized rules that target specific rendering and performance patterns. The guidelines distinguish when to use SSR or CSR strategies to eliminate waterfalls and achieve measurable outcomes for real-world projects.