vercel-react-best-practices

Identify and apply React/Next.js performance best practices to optimize frontend code.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/Bigtablet/bigtablet-frontend-template --skill vercel-react-best-practices-bigtablet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/Bigtablet/bigtablet-frontend-template/tree/main/template/.agents/skills/vercel-react-best-practices
Command: npx skills add https://github.com/Bigtablet/bigtablet-frontend-template --skill vercel-react-best-practices-bigtablet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React/Next.js performance best practices help engineers identify and apply proven patterns to optimize frontend apps, reduce bundle sizes, and improve user experience.

Core Features & Use Cases

  • 57 rules across 8 priority categories to guide automated refactoring and code generation.
  • Patterns for eliminating waterfalls, optimizing bundle size, server-side performance, client-side data fetching, rendering, and advanced patterns.
  • Real-world scenarios include optimizing data fetching, SSR/CSR boundaries, and reducing TTFB/LCP.

Quick Start

Review and apply the Vercel React Best Practices to improve 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 optimize React and Next.js performance for data fetching and bundle size?

To optimize React and Next.js performance, apply 57 deterministic rules across eight priority categories covering data fetching, bundle optimization, and automated refactoring to reduce TTFB and LCP.

What are the best practices for eliminating data fetching waterfalls in Next.js?

Eliminating data fetching waterfalls in Next.js involves applying specific server-side and client-side performance patterns that enforce parallel data fetching and optimize server actions to prevent blocking.

Can I use this to refactor React components and establish SSR and CSR boundaries?

Yes, you can refactor React components to establish SSR and CSR boundaries using deterministic guidance that optimizes server-side rendering and client-side data fetching scenarios.

Does this provide automated guidance for server-side rendering and advanced React patterns?

This provides automated refactoring and code generation guidance for server-side rendering performance and advanced React patterns, enforcing best practices across client and server contexts.

What are the limitations when applying Next.js optimization rules to existing client-side code?

When applying Next.js optimization rules to existing client-side code, limitations depend on the deterministic nature of the 57 rules, meaning complex dynamic patterns may require manual review beyond automated refactoring.