vercel-react-best-practices

Guide React/Next.js refactoring and reviews with Vercel performance best practices.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SatohaCC/nextjs-mdx-blog --skill vercel-react-best-practices-satohacc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/SatohaCC/nextjs-mdx-blog/tree/main/.agents/skills/vercel-react-best-practices
Command: npx skills add https://github.com/SatohaCC/nextjs-mdx-blog --skill vercel-react-best-practices-satohacc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a comprehensive, AI-friendly guide to applying Vercel's React and Next.js performance best practices across codebases, enabling teams to accelerate delivery while maintaining quality.

Core Features & Use Cases

  • Offers a structured set of rules spanning 8 categories (async improvements, bundle size, server-side performance, client-side fetching, re-render optimization, rendering performance, JavaScript tricks, and advanced patterns).
  • Serves as a reference during writing, reviewing, or refactoring React/Next.js components, pages, and data-fetching logic to maximize efficiency and accessibility.
  • Real-world scenarios include optimizing API routes, server actions, dynamic imports, Suspense usage, and per-request caching strategies, with concrete examples.

Quick Start

Review a React/Next.js codebase and output a prioritized refactor plan following Vercel React Best Practices.

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 using Vercel best practices?

Optimize React and Next.js performance by applying Vercel best practices across eight categories including async improvements, bundle size reduction, and rendering performance. You get a structured set of rules for reviewing and refactoring components, API routes, and data-fetching logic.

What is the best way to refactor Next.js server actions and API routes for performance?

Refactor Next.js server actions and API routes by following concrete patterns for per-request caching, security, and immutability. This approach provides testable steps and modular design patterns to maximize efficiency across your Next.js project.

How does dynamic imports and Suspense usage improve Next.js client-side fetching?

Dynamic imports and Suspense usage improve Next.js client-side fetching by optimizing rendering performance and reducing initial bundle size. Applying these patterns ensures efficient data fetching and component loading strategies.

Can I use these React best practices for AI-assisted code reviews and refactoring?

Yes, you can use these React best practices for AI-assisted code reviews and refactoring. The guide provides an AI-friendly reference that outputs a prioritized refactor plan adhering to security, immutability, and modularization requirements.

When should I not use server-side rendering optimizations in my Next.js project?

You should evaluate server-side rendering limitations when client-side fetching and re-rendering optimizations better suit your component design. The guide helps distinguish when to apply server-side versus client-side patterns based on specific performance bottlenecks.

Why does my Next.js bundle size increase when adding new React components?

Your Next.js bundle size increases when components are not properly modularized or dynamically imported. Applying Vercel best practices for bundle size reduction and advanced patterns ensures efficient code splitting and modular component design.