vercel-react-best-practices

Analyze React/Next.js projects against 57 performance rules and implement refactors.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/not-ani/elevated-school-takehome --skill vercel-react-best-practices-not-ani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/not-ani/elevated-school-takehome/tree/main/.agents/skills/vercel-react-best-practices
Command: npx skills add https://github.com/not-ani/elevated-school-takehome --skill vercel-react-best-practices-not-ani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill consolidates best practices for optimizing React and Next.js apps, helping teams reduce bundle sizes, improve startup times, and deliver faster UIs.

Core Features & Use Cases

  • Performance patterns: guidelines covering server actions, Suspense, data fetching, memoization, and bundle optimization.
  • Code review aid: quick wins for re-render minimization, lazy loading, and parallel data fetch.
  • Real-world scenarios: apply to Next.js pages, API routes, server components, and client components to avoid waterfalls and bloated bundles.

Quick Start

Analyze a React/Next.js project against the 57 rules and implement the top recommended 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 optimize React and Next.js performance for faster page loads?

Optimize React and Next.js performance by applying patterns across components, data fetching, and bundling to reduce bundle sizes and improve startup times. This involves adopting server actions, Suspense, and memoization to deliver faster UIs.

What's the best way to avoid data fetching waterfalls in Next.js server components?

Avoid data fetching waterfalls in Next.js server components by implementing parallel data fetch strategies. Applying targeted performance rules helps restructure data retrieval to prevent sequential loading and bloated bundles.

How do I reduce bundle size when using React Suspense and client-side data fetching?

Reduce bundle size with React Suspense and client-side data fetching by applying lazy loading and code splitting guardrails. Incremental refactors based on established rules help safely minimize bloat while maintaining UI responsiveness.

Can I get concrete code review guidance for minimizing React re-renders?

You can get concrete code review guidance for minimizing React re-renders by checking your project against 57 optimization rules. This process identifies quick wins for memoization, lazy loading, and parallel data fetch implementation.

Does this approach support incremental performance improvements without breaking existing Next.js API routes?

This approach supports incremental performance improvements by providing concrete guardrails for safe refactoring. You can apply rules selectively to Next.js API routes, server components, and client components to achieve measurable impact safely.

When should I not use React memoization for performance optimization?

You should carefully evaluate React memoization when safe, incremental improvements are needed, as盲目 applying it can cause overhead. Using established code review rules helps identify when lazy loading or parallel data fetch patterns offer better measurable impact.