vercel-react-best-practices

Apply React and Next.js performance rules to components and pages.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents common performance regressions in React and Next.js by replacing waterfall data fetching, oversized bundles, and avoidable re-renders with proven patterns.

Core Features & Use Cases

  • Eliminates waterfalls by parallelizing independent async work and using Suspense boundaries to stream UI sooner.
  • Reduces bundle size and cold starts through direct imports, dynamic imports for heavy components, conditional loading, and intent-based preloading.
  • Improves rendering performance and correctness by minimizing unnecessary effect dependencies, avoiding state/prop mutations, preventing hydration flicker, and using memoization patterns appropriately.

Quick Start

Use this skill when reviewing or refactoring React/Next.js components to align with Vercel’s performance rules, ensuring faster initial paint, reduced client work, and cleaner server-side execution.

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 fix slow React component rendering and avoidable re-renders?

Improve React component rendering by minimizing effect dependencies, preventing state mutations, and applying appropriate memoization patterns to stop unnecessary re-renders and optimize UI performance.

What's the best way to prevent Next.js server and client data fetching waterfalls?

Prevent Next.js data fetching waterfalls by parallelizing independent async execution and using Suspense boundaries to stream UI components sooner, reducing sequential server and client bottleneck delays.

How do I reduce React bundle size and improve Next.js cold starts?

Reduce React bundle size and Next.js cold starts by using direct imports, applying dynamic imports for heavy components, implementing conditional loading, and configuring intent-based preloading strategies.

Why does my Next.js UI flicker during hydration and how do I fix it?

Fix Next.js hydration flicker by enforcing hydration-safe patterns that ensure server-rendered HTML matches the client's initial render, preventing visual layout shifts and state mismatches during page load.

Can I use Suspense streaming boundaries to speed up my Next.js initial paint?

Yes, you can use Suspense streaming boundaries in Next.js to wrap slow asynchronous components, allowing the server to stream HTML progressively and significantly speed up initial page paint.

When should I use dynamic import and code splitting in my React application?

Use dynamic import and code splitting in React when loading heavy components conditionally or on demand, minimizing the initial JavaScript payload and improving overall application load times.