vercel-react-best-practices

Apply React and Next.js performance best practices to rendering, data fetching, and bundle size.

110|3|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/HorusGoul/eslint-plugin-react-render-types --skill vercel-react-best-practices-horusgoul
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/HorusGoul/eslint-plugin-react-render-types/tree/main/.claude/skills/vercel-react-best-practices
Command: npx skills add https://github.com/HorusGoul/eslint-plugin-react-render-types --skill vercel-react-best-practices-horusgoul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React and Next.js projects frequently suffer from performance regressions due to suboptimal rendering, data fetching, and bloated bundles. This skill provides a structured, battle-tested set of patterns to identify and apply performance optimizations across the codebase.

Core Features & Use Cases

  • Eliminate waterfalls in data fetching and API routes to improve time-to-interactive.
  • Optimize bundle size with direct imports, lazy loading, and deferred third-party libraries.
  • Improve server-side and client-side performance through parallel data fetching, Suspense boundaries, memoization, and careful state management.
  • Use cases include code reviews, refactors, and feature development to ensure performance is considered from the start.

Quick Start

Audit your React/Next.js code against the top-priority rules and implement the highest-impact optimizations.

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 rendering and data fetching performance?▼

Optimize React and Next.js performance by applying patterns to eliminate data fetching waterfalls, implement parallel data fetching with Suspense boundaries, and use component memoization to improve time-to-interactive across server and client contexts.

What is the best way to reduce bundle size in a Next.js application?▼

The best way to reduce bundle size is by using direct imports, lazy loading components, and deferring third-party libraries. These optimizations decrease the initial payload and improve web vitals.

How do I eliminate data fetching waterfalls in Next.js pages?▼

Eliminate data fetching waterfalls in Next.js by replacing sequential API calls with parallel data fetching strategies and applying server-side and client-side caching to streamline interactive routes.

When should I use dynamic imports and memoization in React components?▼

Use dynamic imports to lazy load non-critical components and reduce initial bundle size. Apply memoization to prevent unnecessary re-renders during state management changes, optimizing both client and server rendering contexts.

Does this approach work for both client and server contexts in Next.js?▼

Yes, these React and Next.js optimization guidelines apply across both client and server contexts. They enforce specific patterns for server-side and client-side caching, rendering, and data fetching to ensure comprehensive performance improvements.

How do I audit my React codebase for performance best practices?▼

Audit your React codebase against structured per-category optimization rules during code reviews or refactors. Check for dynamic imports, memoization, and waterfall elimination to identify and implement high-impact performance improvements.