vercel-react-best-practices

Enforce React and Next.js performance and maintainability best practices during code reviews and refactors.

4|2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/PeterFile/my-common-skills --skill vercel-react-best-practices-peterfile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/PeterFile/my-common-skills/tree/main/vercel-react-best-practices
Command: npx skills add https://github.com/PeterFile/my-common-skills --skill vercel-react-best-practices-peterfile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies React and Next.js performance best practices to help teams write, review, and refactor code that loads faster, scales better, and remains maintainable.

Core Features & Use Cases

  • Provides guidelines for eliminating waterfalls, reducing bundle size, and enabling parallel data fetching across server and client boundaries.
  • Applies to tasks involving React components, Next.js pages, data fetching, and performance optimization reviews.
  • Use case: during code reviews, you can reference these practices to identify bottlenecks and suggest refactors that improve Time to Interactive (TTI) and startup time.

Quick Start

To apply these practices, run a quick audit of a component or page, then apply recommended patterns such as splitting bundles, using Suspense boundaries, and avoiding barrel imports.

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 during code reviews?

To optimize React and Next.js performance during code reviews, reference established best practices to identify bottlenecks and suggest refactors that improve Time to Interactive and startup time.

What is the best way to reduce bundle size and eliminate data fetching waterfalls in Next.js?

The best way to reduce bundle size and eliminate waterfalls is by splitting bundles, avoiding barrel imports, and enabling parallel data fetching across server and client boundaries.

How do Suspense boundaries and server components improve Next.js data fetching?

Suspense boundaries and server components improve Next.js data fetching by enforcing patterns that enable parallel data retrieval and reduce waterfalls across server and client boundaries.

When should I apply React bundle optimization patterns in my project?

You should apply React bundle optimization patterns when writing, reviewing, or refactoring components and pages to ensure your codebase loads faster, scales better, and remains maintainable.

Does this approach work for both client and server-side data fetching in Next.js?

Yes, these performance patterns apply to data fetching across both server and client boundaries, ensuring parallel retrieval and eliminating waterfalls in Next.js applications.

Why should I avoid barrel imports when optimizing React bundle size?

You should avoid barrel imports when optimizing React bundle size because they can prevent effective bundle splitting, increasing startup time and degrading overall application performance.