react-best

What problem does it solve?

React and Next.js performance issues caused by sequential data fetching, oversized bundles, and unnecessary re-renders that slow Time to Interactive and degrade UX.

Core Features & Use Cases

• Eliminate waterfalls first: parallelize independent awaits, defer work until needed, and apply Suspense boundaries to stream the UI earlier.
• Shrink bundle size: prevent heavy barrel imports, dynamically load large components, and defer non-critical third-party libraries until after hydration.
• Reduce re-renders with better patterns: hoist static JSX, avoid inline object props for memoized children, narrow effect dependencies, and use React 19 composition/compound patterns (including React 19 use() usage guidance).
• When to use: component writing, code review, and refactors where you see “too many re-renders,” waterfall fetching, slow pages, or bundle bloat in React/Next.js apps.

Quick Start

Ask the AI to “Apply the react-best rules to this React/Next.js component and rewrite the data fetching, imports, and render patterns to remove waterfalls and minimize re-renders.”