vercel-react-best-practices

Applies 57 prioritized React and Next.js performance optimization rules during code writing and review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? React and Next.js codebases often ship with performance issues like request waterfalls, bloated bundles, unnecessary re-renders, and hydration mismatches that are hard to catch during development. This Skill provides a structured, impact-prioritized rule set from Vercel Engineering so these issues are caught and fixed while writing, reviewing, or refactoring code. ## Core Features & Use Cases - 57 Rules Across 8 Categories: Covers eliminating waterfalls, bundle size optimization, server-side performance, client-side data fetching, re-render optimization, rendering performance, JavaScript performance, and advanced patterns, each prioritized by impact from CRITICAL to LOW. - Incorrect vs Correct Code Examples: Every rule file includes a brief explanation plus concrete incorrect and correct TypeScript/TSX code samples for direct application during refactoring. - Use Case: When reviewing a Next.js page that fetches user, posts, and comments sequentially, apply the async-parallel rule to rewrite the fetches with Promise.all(), cutting three round trips down to one. ## Quick Start Ask the assistant to review your React component or Next.js page against the Vercel performance rules and refactor any violations it finds.

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 optimize React and Next.js performance?▼

Apply impact-prioritized rules starting with eliminating async waterfalls using Promise.all() and reducing bundle size via direct imports and next/dynamic. Then address server-side caching, re-render optimization, and rendering performance based on each rule's impact rating.

How to fix request waterfalls in Next.js API routes?▼

Start independent promises immediately and await them later, or use Promise.all() for operations with no interdependencies. For partial dependency chains, the better-all library starts each task at the earliest possible moment.

Why are barrel file imports slow in Next.js?▼

Barrel files from libraries like lucide-react or @mui/material can re-export thousands of modules, adding 200-800ms import cost per cold start. Import directly from source files or enable optimizePackageImports in next.config.js for Next.js 13.5+.

Does React Compiler replace manual memoization rules?▼

Yes, for some rules. With React Compiler enabled, manual memo() and useMemo() optimization and static JSX hoisting become unnecessary, though functional setState updates are still recommended to prevent stale closure bugs.

When should I not use Suspense boundaries for data fetching?▼

Avoid Suspense for critical data needed for layout decisions, SEO-critical above-the-fold content, and small fast queries where the overhead is not worth it. The trade-off is faster initial paint versus potential layout shift.