vercel-react-best-practices

Identify React and Next.js performance best practices for automated refactoring and code generation.

2|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/hotriluan/alkana-dashboard --skill vercel-react-best-practices-hotriluan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/hotriluan/alkana-dashboard/tree/main/.opencode/skill/react-best-practices
Command: npx skills add https://github.com/hotriluan/alkana-dashboard --skill vercel-react-best-practices-hotriluan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill consolidates authoritative React and Next.js performance guidelines to help teams build faster, more reliable UIs by addressing rendering bottlenecks, data-fetching inefficiencies, and bloated bundles.

Core Features & Use Cases

  • Provides a curated set of performance patterns for React components, Next.js pages, and data-fetching flows used to improve TTI, LCP, and overall UX.
  • Includes guidance on server components vs client components, caching, and bundle optimization with practical examples and guardrails for safe refactoring.
  • Real-world scenario: refactoring a dashboard with many data sources to reduce waterfalls and improve responsiveness.

Quick Start

Analyze a React/Next.js project and apply the recommended performance patterns to optimize rendering, data fetching, and bundle size.

Frequently Asked Questions about vercel-react-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are React and Next.js performance best practices for reducing data fetching waterfalls?

React and Next.js performance best practices reduce data fetching waterfalls by applying server components and parallel data fetching patterns. This minimizes serialization and client-side requests to improve dashboard responsiveness and overall LCP.

How do I optimize React bundle size when refactoring a complex codebase?

To optimize React bundle size during refactoring, apply curated performance patterns to components and pages. This shrinks the overall bundle footprint and enforces safe guardrails to prevent rendering bottlenecks during automated code generation.

When should I use Next.js server components vs client components for performance optimization?

Use Next.js server components vs client components based on performance optimization needs to reduce serialization and shrink bundle size. Server components handle data fetching efficiently, while client components manage interactive UI rendering.

Can I automate Next.js performance refactoring for pages with multiple data sources?

You can automate Next.js performance refactoring for pages with multiple data sources by applying actionable patterns. This guides code generation to reduce waterfalls, minimize serialization, and improve end-to-end responsiveness with traceable outcomes.

What is the best way to improve TTI and LCP in a React and Next.js application?

The best way to improve TTI and LCP in React and Next.js applications is applying performance patterns across components, pages, and data fetching. This reduces rendering bottlenecks and shrinks bundle size for faster UI reliability.

Are there guardrails for safely refactoring React data fetching flows to prevent breaking changes?

Guardrails for safely refactoring React data fetching flows enforce safe boundaries during automated code generation. These prevent breaking changes while applying performance patterns to reduce waterfalls and minimize serialization across components.