vercel-react-best-practices

Review React and Next.js code against performance best practices.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/apostolos-geyer/StoliStack --skill vercel-react-best-practices-apostolos-geyer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/apostolos-geyer/StoliStack/tree/main/.agents/skills/vercel-react-best-practices
Command: npx skills add https://github.com/apostolos-geyer/StoliStack --skill vercel-react-best-practices-apostolos-geyer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Vercel React Best Practices skill provides a centralized, prescriptive guide to optimize React and Next.js apps, helping teams avoid common performance pitfalls and accelerate UX.

Core Features & Use Cases

  • Comprehensive rules across 8 categories (waterfalls, bundle size, server-side performance, client data fetching, re-render optimization, rendering performance, JavaScript performance, and advanced patterns).
  • Practical examples and code snippets that demonstrate correct vs incorrect implementations.
  • Ideal for reviews, refactors, and architecture decisions to improve load times, TTI, and UX.

Quick Start

Review this guide and start applying the best-practice patterns to your React/Next.js projects today.

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 load times?

Optimize React and Next.js performance by applying proven best practices for server-side data fetching, bundle size reduction, and rendering pattern refactoring to eliminate waterfalls and improve UX.

What are the best practices for reducing bundle size in a Next.js application?

Reduce Next.js bundle size by following structured optimization rules that demonstrate correct versus incorrect code implementations, helping you refactor imports and eliminate unnecessary client-side JavaScript.

How do I eliminate data fetching waterfalls in server-side React components?

Eliminate server-side data fetching waterfalls by implementing structured performance patterns that refactor sequential fetches into parallel operations, significantly improving load times and Time to Interactive.

Does this React performance guide cover both client-side and server-side rendering optimization?

Yes, this React performance guide covers both server-side and client-side data fetching, re-render optimization, and advanced rendering patterns across typical Next.js projects to accelerate overall UX.

Can I use these Next.js best practices for reviewing and refactoring existing UI code?

Yes, you can use these Next.js best practices for code reviews and refactoring existing UI components, leveraging practical examples to identify and correct common performance pitfalls in your architecture.

Why does my Next.js app have slow Time to Interactive and poor web performance?

Slow Next.js Time to Interactive often stems from unoptimized client-side data fetching, large bundle sizes, and rendering waterfalls, which structured best-practice rules help identify and resolve through targeted refactoring.