vercel-react-best-practices

Apply React and Next.js performance patterns to optimize rendering and data fetching.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/createdbysalt/nextjs-starter-template --skill vercel-react-best-practices-createdbysalt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/createdbysalt/nextjs-starter-template/tree/main/.claude/skills/react-best-practices
Command: npx skills add https://github.com/createdbysalt/nextjs-starter-template --skill vercel-react-best-practices-createdbysalt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates battle-tested React and Next.js performance guidelines to help teams write fast, maintainable code and avoid common bottlenecks.

Core Features & Use Cases

  • Guidelines for server and client rendering, data fetching, and bundling to improve TTI, LCP, and bundle weight.
  • Automation-friendly patterns that can be applied during code reviews, refactoring, and scaffolding new projects.
  • Use Case: When optimizing a large Next.js app, apply these patterns to reduce waterfalls, parallelize fetches, and cut unnecessary bundle weight.

Quick Start

Scan a React project to surface core performance patterns and generate actionable 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 to reduce render waterfalls and bundle size?

Optimize React and Next.js performance by applying codified rules for avoiding data fetch waterfalls, parallelizing requests, and cutting unnecessary bundle weight. These patterns improve rendering, data fetching, and client-server boundaries to drive faster builds and automated refactoring.

What are the best practices for React server components and client-server boundaries in Next.js?

React server components and client-server boundaries best practices focus on guidelines for server and client rendering, data fetching, and bundling. Applying these patterns improves TTI, LCP, and bundle weight while maintaining maintainable code across component design and routes.

Can I use these Next.js performance patterns during automated code reviews and refactoring?

You can use these Next.js performance patterns during automated code reviews and refactoring because they are automation-friendly. Scan a React project to surface core performance patterns and generate actionable refactors for component design, routes, and build pipelines.

What is the best way to parallelize data fetches and improve LCP in a large Next.js app?

The best way to parallelize data fetches and improve LCP in a large Next.js app is to apply battle-tested performance guidelines that reduce waterfalls. Consolidating these patterns during refactoring helps teams write fast, maintainable code and avoid common bottlenecks.

When should I refactor React component design to improve TTI and bundle weight?

Refactor React component design to improve TTI and bundle weight when optimizing a large Next.js app. Apply these performance patterns to reduce waterfalls, parallelize fetches, and cut unnecessary bundle weight across server and client rendering boundaries.