vercel-react-best-practices

Enforce Vercel best practices for React and Next.js performance optimization.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React and Next.js projects often struggle with performance due to waterfalls, large bundles, and suboptimal rendering patterns. This skill codifies Vercel's practical guidelines to help engineers consistently apply best practices during development, reviews, and refactoring.

Core Features & Use Cases

  • 45+ rules across 8 categories prioritize critical improvements such as eliminating waterfalls and bundle-size optimization, plus server/client performance patterns.
  • Guidance for code reviews and automated refactoring to improve load times, interactivity, and maintainability in React and Next.js apps.
  • Real-world use case: when optimizing a Next.js app, apply dynamic imports, Suspense boundaries, and per-route data-fetching patterns to reduce TTI and LCP while preserving UX.

Quick Start

Review top-priority rules and instruct tooling to implement them across components, pages, and data-fetching layers.

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 by eliminating data fetching waterfalls?

To optimize React performance, apply Vercel best practices like per-route data fetching and parallel requests to eliminate waterfalls. This structured rule set provides practical guidance for refactoring client and server components to improve load times and interactivity.

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

Reducing bundle size in Next.js involves applying dynamic imports and code-splitting patterns. This Skill codifies 45+ rules across 8 categories, prioritizing bundle-size optimization and rendering improvements to enable automated refactoring and lower TTI.

How do I use Suspense boundaries correctly in React server and client components?

Suspense boundaries in React components isolate loading states and prevent waterfall rendering. This Skill enforces proven Vercel engineering patterns for applying Suspense and code-splitting across server and client components to preserve UX while reducing LCP.

Can I automate code reviews for React performance issues using these best practices?

Yes, you can automate code reviews for React performance issues using this structured rule set. It provides guardrails and examples that enable tooling to automatically identify suboptimal rendering patterns and generate refactored code for Next.js apps.

Does this React optimization guidance apply to both client and server components?

Yes, this React optimization guidance applies directly to both client and server components. It covers data fetching, code-splitting, and rendering optimizations across React apps and Next.js pages to consistently enforce Vercel best practices during development.

When should I use dynamic imports instead of static imports in Next.js?

Use dynamic imports in Next.js when optimizing initial load times and reducing large bundle sizes. This Skill provides guardrails to identify suboptimal rendering patterns and instructs tooling to implement dynamic imports and Suspense boundaries for better interactivity.