react-best-practices

Apply performance patterns to React and Next.js code across components and data flows.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/wanghaisheng/web3-scaffold-app-monorepo --skill react-best-practices-wanghaisheng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react-best-practices
Source: https://github.com/wanghaisheng/web3-scaffold-app-monorepo/tree/main/.claude/skills/react-best-practices
Command: npx skills add https://github.com/wanghaisheng/web3-scaffold-app-monorepo --skill react-best-practices-wanghaisheng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This guide helps teams optimize React and Next.js apps by applying proven performance patterns, reducing render times, and improving bundle sizes.

Core Features & Use Cases

  • Comprehensive guidance on performance optimization for React and Next.js, including data fetching, server components, suspense, code-splitting, and rendering strategies.
  • Practical rules for daily workflows: when to lazy-load, how to minimize re-renders, and how to structure components for reuse across teams.
  • Use Case: When adding new features, run the guidelines to review architecture and identify bottlenecks before coding.

Quick Start

Assess a React/Next.js project and apply the top performance patterns to cut render time and bundle size.

Frequently Asked Questions about 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 during code reviews?

Identify bottlenecks by assessing your Next.js project and applying proven React performance patterns to cut render time and bundle size. This involves reviewing component architecture and data flows before coding.

What is the best way to minimize re-renders and structure components in React?

The best way to minimize re-renders is to structure components for reuse and apply practical rules for daily workflows, such as determining exactly when to lazy-load components and data.

How does code-splitting and suspense work for Next.js data fetching?

Code-splitting and suspense work by applying specific rendering strategies and data fetching patterns to optimize Next.js applications, ensuring efficient bundle loading and improved rendering performance.

Can I use these guidelines to refactor server and client component patterns safely?

Yes, you can safely refactor server and client component patterns by applying the defined guidelines for bundling and observable refactors, ensuring performance improvements without breaking existing functionality.

When do I need to lazy-load components to improve bundle sizes?

You need to lazy-load components when adding new features that risk increasing bundle sizes, following practical rules to minimize initial load times and structure components for team reuse.