react-best-practices

Enforce React and Next.js performance patterns to reduce waterfalls and bundle bloat.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/jordanhindo/meridian --skill react-best-practices-jordanhindo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react-best-practices
Source: https://github.com/jordanhindo/meridian/tree/main/.claude/skills/create-beads-orchestration/templates/skills/react-best-practices
Command: npx skills add https://github.com/jordanhindo/meridian --skill react-best-practices-jordanhindo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reduces slow loads, bundle bloat, and unnecessary re-renders in React and Next.js codebases by enforcing high-impact performance patterns from the start.

Core Features & Use Cases

  • Eliminates request waterfalls using parallelism strategies like Promise.all and correct Suspense boundaries.
  • Cuts bundle size and TTI with direct imports, dynamic imports for heavy components, and deferred non-critical libraries.
  • Prevents expensive client and rendering work by minimizing RSC serialization, narrowing effect dependencies, and using modern state update patterns.
  • Use case: Improve a Next.js dashboard that currently has slow page loads, large initial bundles, and duplicated data fetching across components.

Quick Start

Apply the rules in this skill before writing or refactoring any React or Next.js code for your feature, starting with eliminating waterfalls and then optimizing bundle size.

Frequently Asked Questions about react-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I eliminate request waterfalls in React and Next.js data fetching?

Eliminate request waterfalls in React by using parallelism strategies like Promise.all and correct Suspense boundaries to fetch data concurrently. This architectural pattern prevents sequential fetching delays and significantly improves Next.js runtime performance.

How do I reduce bundle size and Time to Interactive (TTI) in Next.js?

Reduce bundle size and TTI in Next.js by using direct imports, applying dynamic imports for heavy components, and deferring non-critical libraries. This optimization pattern minimizes the initial JavaScript payload shipped to the client.

How do I minimize React Server Component (RSC) serialization for expensive rendering work?

Minimize RSC serialization by enforcing architectural patterns that narrow effect dependencies and use modern state update patterns. This prevents expensive client rendering work and reduces unnecessary serialization overhead across the RSC boundary.

How do I use Suspense boundaries correctly for parallel data fetching in Next.js?

Use Suspense boundaries correctly by wrapping parallel data fetching streams so the UI renders progressively as data arrives. Combining Suspense with Promise.all ensures concurrent fetching without blocking the entire page load.

What is the best way to optimize a slow Next.js dashboard with large initial bundles?

Optimize a slow Next.js dashboard by prioritizing waterfall elimination, using dynamic imports for heavy modules, and minimizing RSC serialization. Apply these implementation patterns during development or refactoring to cut bundle bloat.