vercel-react-best-practices

Apply Vercel performance best practices to React and Next.js codebases.

5|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/vab1997/skillstui.sh --skill vercel-react-best-practices-vab1997
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/vab1997/skillstui.sh/tree/main/.agents/skills/vercel-react-best-practices
Command: npx skills add https://github.com/vab1997/skillstui.sh --skill vercel-react-best-practices-vab1997

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React and Next.js apps often suffer from performance pitfalls such as waterfalls, large bundles, SSR/CSR imbalances, and inefficient data fetching patterns. This skill consolidates Vercel's best practices to help developers write faster, more maintainable React/Next.js code.

Core Features & Use Cases

  • Comprehensive rules spanning sections like Eliminating Waterfalls, Bundle Size Optimization, Server-Side Performance, Client-Side Data Fetching, Re-render Optimization, Rendering Performance, JavaScript Performance, and Advanced Patterns.
  • Guidance for writing, reviewing, and refactoring React/Next.js code to improve performance in real-world projects.
  • Provides practical examples and actionable patterns for both server components and client components.

Quick Start

Analyze a React/Next.js project and apply the 69 rules and patterns from the guide to optimize 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 eliminate data fetching waterfalls in React and Next.js?▼

Eliminate React and Next.js waterfalls by applying Vercel best practices for parallel data fetching, proper server component boundaries, and optimized client-side fetching patterns to prevent sequential requests.

What is the best way to optimize bundle size in a Next.js application?▼

Optimize Next.js bundle size by applying code splitting, enforcing server-side rendering boundaries, and removing unused JavaScript to reduce client payload and improve loading performance.

How do I set safe boundaries between SSR and CSR in React components?▼

Set safe SSR and CSR boundaries in React by correctly identifying server and client components, ensuring data fetching executes server-side while interactivity remains strictly client-side.

Can I use server actions securely in my Next.js refactoring workflow?▼

You can securely use Next.js server actions during refactoring by applying specific reliability guardrails and security patterns that protect data mutations and prevent unauthorized client-side execution.

How do I optimize re-renders when refactoring React components?▼

Optimize React component re-renders during refactoring by applying JavaScript performance patterns, identifying unnecessary state updates, and structuring components to minimize client-side rendering bottlenecks.

Does this approach work for reviewing existing React codebases?▼

This approach works for reviewing existing React codebases by applying 69 consolidated Vercel performance rules to audit waterfalls, bundle size, rendering logic, and data fetching patterns.