vercel-react-best-practices

Identify and fix React and Next.js performance bottlenecks in application code.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/darkmatter/skills --skill vercel-react-best-practices-darkmatter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/darkmatter/skills/tree/main/skills/vercel-react-best-practices
Command: npx skills add https://github.com/darkmatter/skills --skill vercel-react-best-practices-darkmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify and fix React and Next.js performance issues that slow down rendering, inflate bundles, and create unnecessary re-renders or data-fetching waterfalls.

Core Features & Use Cases

  • Performance review guidance: Evaluate component code, server actions, and routing patterns for common bottlenecks.
  • Refactoring recommendations: Improve bundle loading, parallelize async work, reduce serialization, and tighten re-render scope.
  • Production-ready best practices: Apply safe patterns for hydration, caching, Suspense, resource hints, and non-blocking server work.
  • Use case: Use it when reviewing a Next.js page that feels slow, when modernizing a React codebase, or when rewriting a feature to render faster and ship less JavaScript.

Quick Start

Ask the skill to review your React or Next.js code for performance bottlenecks and recommend concrete refactors.

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 identify and fix React performance bottlenecks in my application code?

To fix React performance bottlenecks, evaluate component code, server actions, and routing patterns to reduce unnecessary re-renders, parallelize async work, and tighten rendering scope. Apply memoization and dynamic imports to ship less JavaScript.

What's the best way to optimize Next.js server-components and data fetching waterfalls?

Optimize Next.js server-components by applying safe patterns for hydration, caching, and Suspense. Refactor data fetching waterfalls by parallelizing async work and using non-blocking server actions to improve rendering speed.

How do I reduce bundle size and improve hydration in a Next.js app?

Reduce bundle size and improve hydration by applying dynamic imports, resource hints, and Suspense. Refactoring component design to tighten re-render scope and reduce serialization also minimizes the JavaScript shipped to the client.

Can I use this approach to review and refactor an existing React codebase for rendering speed?

Yes, you can review and refactor existing React codebases for rendering speed. The process identifies performance issues like inflated bundles and unnecessary re-renders, then recommends concrete refactors like parallelization and caching during modernization.

Why does my Next.js page feel slow and how do I apply production-ready best practices?

A Next.js page feels slow due to data-fetching waterfalls, unnecessary re-renders, and inflated bundles. Apply production-ready best practices by using Suspense, caching, resource hints, and safe server-side patterns to render faster.