vercel-react-best-practices

Analyze React and Next.js code for performance pitfalls and actionable fixes.

31|1|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/quan0715/QJudge --skill vercel-react-best-practices-quan0715
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/quan0715/QJudge/tree/main/.cursor/skills/vercel-react-best-practices
Command: npx skills add https://github.com/quan0715/QJudge --skill vercel-react-best-practices-quan0715

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide addresses common performance regressions and anti-patterns in React and Next.js codebases by providing concrete, prioritized rules to eliminate waterfalls, reduce bundle size, and improve server/client data fetching behavior.

Core Features & Use Cases

  • Eliminate Waterfalls: Patterns and examples to parallelize async work and avoid sequential awaits that increase latency.
  • Bundle Size & Loading: Recommendations for direct imports, dynamic loading, and deferring non-critical libraries to shrink initial bundles.
  • Server & Client Patterns: Advice for per-request deduplication, cross-request LRU caching, Suspense boundaries, and SWR-based deduplication for client fetching.
  • Use Case: Use this guidance when reviewing a Next.js page or refactoring a React component to improve TTI, LCP, and reduce unnecessary renders.

Quick Start

Use the vercel-react-best-practices skill to analyze a React or Next.js code snippet and produce prioritized, actionable fixes for waterfalls, bundle imports, and data-fetching patterns.

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 Next.js and React Server Components?

To eliminate data fetching waterfalls in React Server Components, apply parallelization patterns for async work and avoid sequential awaits to reduce latency. This approach provides actionable code-level changes to optimize component rendering.

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

The best way to reduce bundle size in a React application is to use direct imports, dynamic loading, and defer non-critical libraries. This shrinks initial bundles and improves loading metrics like TTI and LCP.

How do I optimize server-side and client-side data fetching in modern React?

Optimize React data fetching by applying per-request deduplication, cross-request LRU caching for servers, and SWR-based deduplication for clients. Suspense boundaries also guide these server and client caching behaviors.

Can I use this guidance to refactor existing React components for better rendering performance?

Yes, you can use this guidance to refactor React components and reduce unnecessary renders. It provides prioritized rules and actionable fixes for code review workflows to improve TTI and LCP metrics.

Why does my Next.js page have poor LCP and TTI despite using React Server Components?

Poor LCP and TTI in Next.js often stems from sequential awaits, large initial bundles, or unnecessary renders. Analyzing the code for waterfall patterns and import optimizations yields actionable fixes to improve performance.