vercel-react-best-practices

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps frontend teams optimize React and Next.js performance by providing a structured, battle-tested set of guidelines and patterns that guide development, code reviews, and refactoring for high-performance apps.

Core Features & Use Cases

  • Structured guidelines for eliminating waterfalls, bundle size optimization, server-side performance, and client-side data fetching, with explicit rules and real-world examples.
  • Actionable patterns such as Promise.all(), dynamic imports, Suspense boundaries, after() side effects, and server actions authentication to improve initial load and runtime performance.
  • Use Case: When refactoring a slow Next.js page, apply these patterns to reduce TTI, improve LCP, and ensure resilient data fetching.

Quick Start

Read the SKILL.md and AGENTS.md in this skill directory and begin auditing a React/Next.js project for perf issues; implement parallel data fetching, lazy-loading of heavy components, and non-blocking analytics as you go.

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 when refactoring a slow page?

Optimize React and Next.js performance by applying structured guidelines like parallel data fetching with Promise.all, dynamic imports for heavy components, and Suspense boundaries to improve initial load times and reduce Time to Interactive.

What is the best way to eliminate data fetching waterfalls in Next.js?

Eliminate data fetching waterfalls in Next.js by replacing sequential awaits with parallel data fetching using Promise.all, which allows multiple requests to resolve concurrently and significantly reduces overall page load latency.

How do I reduce bundle size in a React application?

Reduce bundle size in a React application by implementing dynamic imports to lazy-load heavy components, ensuring only necessary JavaScript is shipped to the client during initial page load and rendering.

Does this Next.js performance best-practices approach work with server actions and Suspense?

Yes, this Next.js performance approach explicitly works with server actions authentication and Suspense boundaries, providing actionable patterns to secure backend calls and stream UI components asynchronously.

When should I use dynamic imports versus standard imports in React?

Use dynamic imports instead of standard imports in React when dealing with heavy components or non-critical UI elements, deferring their JavaScript payload until needed to prevent blocking the initial render.

Why does my Next.js page have a slow Time to Interactive and how do I fix it?

A slow Time to Interactive in Next.js is often caused by large JavaScript bundles and sequential data fetching; fix it by applying parallel fetching, lazy-loading components, and non-blocking side effects.

Related Skills