vercel-react-best-practices

Apply prioritized React/Next.js performance rules to components, routing, and data fetching.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/badass-courses/course-builder --skill vercel-react-best-practices-badass-courses
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-react-best-practices
Source: https://github.com/badass-courses/course-builder/tree/main/.opencode/skill/react-best-practices
Command: npx skills add https://github.com/badass-courses/course-builder --skill vercel-react-best-practices-badass-courses

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React performance optimization guidelines for React and Next.js applications, aimed at reducing waterfalls, optimizing SSR/CSR, and trimming bundle sizes to deliver faster, more reliable user experiences.

Core Features & Use Cases

  • Comprehensive rules across 8 priority areas to guide automated refactoring, code generation, and review processes.
  • Practical examples demonstrating common anti-patterns and their performant alternatives in React/Next.js codebases.
  • Real-world scenarios for engineers auditing components, pages, and data-fetching strategies to improve load times and stability.

Quick Start

Use the React Best Practices skill to audit a React component or Next.js page and apply the 8 category rules to optimize performance.

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 performance and reduce waterfalls in Next.js?

To optimize React performance, you must reduce data fetching waterfalls by enabling parallel data fetching and using React.cache(). This skill enforces concrete engineering rules across component authoring and routing to improve load times.

What is the best way to trim bundle size in a Next.js application?

Trimming bundle size requires avoiding barrel imports to prevent unused code from entering the build. Applying prioritized best practices audits your component structure and enforces concrete requirements for smaller, more efficient bundles.

How do I audit a React component for performance anti-patterns?

Auditing a React component involves applying a prioritized set of 8 category rules to identify common anti-patterns. You evaluate component authoring, data fetching, and server-side rendering to find and replace inefficient code.

Does this React performance approach work for both server and client rendering?

Yes, these performance best practices apply to both server and client rendering in Next.js. The rules guide optimizations across SSR and CSR strategies, ensuring faster load times and reliable user experiences across environments.

When should I use React.cache() for data fetching in Next.js?

You should use React.cache() when aiming to minimize data fetching waterfalls and optimize server-side rendering. It enables parallel data fetching strategies, which reduces sequential waits and improves application stability.

What are the limitations of relying on default Next.js data fetching?

Default Next.js data fetching can create sequential waterfalls and bloated bundles if not carefully managed. Without enforcing parallel fetching and avoiding barrel imports, applications suffer from slower load times and unstable performance.