vercel-react-best-practices

Apply React and Next.js performance best practices across component design, data fetching, and code reviews.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/Trio-Blockchain-Labs/whitepaperiq-pro-landing-page --skill vercel-react-best-practices-trio-blockchain-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/Trio-Blockchain-Labs/whitepaperiq-pro-landing-page/tree/main/.agents/skills/vercel-react-best-practices
Command: npx skills add https://github.com/Trio-Blockchain-Labs/whitepaperiq-pro-landing-page --skill vercel-react-best-practices-trio-blockchain-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a comprehensive set of performance optimization guidelines for React and Next.js projects, helping teams craft faster, more efficient UI code.

Core Features & Use Cases

  • A structured catalog of 57 rules across 8 categories covering eliminating waterfalls, bundle size, server-side performance, client data fetching, rendering, and JavaScript performance.
  • Practical code examples and patterns for common scenarios like parallel data fetching, suspense boundaries, dynamic imports, server actions, and RSC/CSR data flow.
  • Use this skill during component/page creation, code reviews, refactors, and performance audits to enforce best practices and measure improvements.

Quick Start

Try applying the guidelines to a current Next.js React page to identify top performance bottlenecks and iteratively refactor for faster TTI and LCP.

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 faster hydration and reduced bundle size?

To optimize React and Next.js performance, apply engineering best practices across component design, data fetching, and bundling. This reduces bundle size, accelerates hydration, and improves TTI and LCP metrics in production applications.

What are the best practices for managing server and client boundaries in React Server Components?

Managing server and client boundaries requires enforcing safer RSC and CSR data flows. Applying structured rules for server-side rendering performance and client data fetching ensures secure boundaries and eliminates data fetching waterfalls.

How do I eliminate data fetching waterfalls in Next.js applications?

Eliminating data fetching waterfalls involves using parallel data fetching patterns and suspense boundaries. Applying these React optimization rules during page creation prevents sequential requests and improves server-side performance.

Can I use these React performance rules during code reviews and refactoring?

These React performance rules are designed for code reviews, refactors, and performance audits. Applying the catalog of 57 rules across 8 categories helps identify bottlenecks and enforce best practices iteratively.

What's the best way to reduce JavaScript bundle size in a production Next.js app?

The best way to reduce JavaScript bundle size is applying dynamic imports and optimized bundling patterns. These best practices eliminate unnecessary code and improve overall application loading metrics.

Why does my Next.js page have a slow Time to Interactive, and how do I fix it?

Slow Time to Interactive often results from heavy hydration and large bundles. Fixing it requires applying performance optimization guidelines for rendering and JavaScript performance to iteratively refactor pages for faster TTI.