About react-best-practices
react-best-practices is a reference skill for performance-focused work on React and Next.js applications. Its prioritized rules cover data fetching, bundles, server and client performance, rendering, and JavaScript, with examples in individual rule files.
Key features
- 0145 rules across eight categories
- 02Prioritized performance guidance
- 03React and Next.js examples
- 04Individual rule files with code examples
- 05Compiled guide in AGENTS.md
Use cases
- 01Reviewing React code for performance issues
- 02Optimizing data-fetching patterns
- 03Reducing bundle size and load times
- 04Guiding React and Next.js refactoring
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill react-best-practicesAfter installing, type/react-best-practicesin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
metadata.jsonREADME.mdAGENTS.mdrules/advanced-event-handler-refs.md_template.mdasync-api-routes.mdasync-defer-await.md_sections.mdadvanced-use-latest.mdasync-dependencies.mdbundle-preload.mdbundle-defer-third-party.mdbundle-dynamic-imports.mdasync-parallel.mdbundle-barrel-imports.mdasync-suspense-boundaries.mdbundle-conditional.mdclient-swr-dedup.mdjs-batch-dom-css.mdclient-event-listeners.mdjs-cache-function-results.mdjs-combine-iterations.mdjs-cache-storage.mdjs-index-maps.mdjs-set-map-lookups.mdjs-min-max-loop.mdjs-early-exit.mdjs-hoist-regexp.mdjs-cache-property-access.mdjs-length-check-first.mdDetails
From the project READMEReact Best Practices (catalog adaptation)
Comprehensive performance optimization guide for React and Next.js applications, adapted from Vercel’s published guidance. Contains 45 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
When to Use
Reference these guidelines when:
- Writing new React components or Next.js pages
- Implementing data fetching (client or server-side)
- Reviewing code for performance issues
- Refactoring existing React/Next.js code
- Optimizing bundle size or load times
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Eliminating Waterfalls | CRITICAL | async- |
| 2 | Bundle Size Optimization | CRITICAL | bundle- |
| 3 | Server-Side Performance | HIGH | server- |
| 4 | Client-Side Data Fetching | MEDIUM-HIGH | client- |
| 5 | Re-render Optimization | MEDIUM | rerender- |
| 6 | Rendering Performance | MEDIUM | rendering- |
| 7 | JavaScript Performance | LOW-MEDIUM | js- |
| 8 | Advanced Patterns | LOW | advanced- |
Quick Reference
1. Eliminating Waterfalls (CRITICAL)
async-defer-await- Move await into branches where actually usedasync-parallel- Use Promise.all() for independent operationsasync-dependencies- Use better-all for partial dependenciesasync-api-routes- Start promises early, await late in API routesasync-suspense-boundaries- Use Suspense to stream content
2. Bundle Size Optimization (CRITICAL)
bundle-barrel-imports- Import directly, avoid barrel filesbundle-dynamic-imports- Use next/dynamic for heavy componentsbundle-defer-third-party- Load analytics/logging after hydrationbundle-conditional- Load modules only when feature is activatedbundle-preload- Preload on hover/focus for perceived speed
3. Server-Side Performance (HIGH)
server-cache-react- Use React.cache() for per-request deduplicationserver-cache-lru- Use LRU cache for cross-request cachingserver-serialization- Minimize data passed to client componentsserver-parallel-fetching- Restructure components to parallelize fetchesserver-after-nonblocking- Use after() for non-blocking operations
4. Client-Side Data Fetching (MEDIUM-HIGH)
client-swr-dedup- Use SWR for automatic request deduplicationclient-event-listeners- Deduplicate global event listeners
5. Re-render Optimization (MEDIUM)
rerender-defer-reads- Don't subscribe to state only used in callbacksrerender-memo- Extract expensive work into memoized componentsrerender-dependencies- Use primitive dependencies in effectsrerender-derived-state- Subscribe to derived booleans, not raw valuesrerender-functional-setstate- Use functional setState for stable callbacksrerender-lazy-state-init- Pass function to useState for expensive valuesrerender-transitions- Use startTransition for non-urgent updates
6. Rendering Performance (MEDIUM)
rendering-animate-svg-wrapper- Animate div wrapper, not SVG elementrendering-content-visibility- Use content-visibility for long listsrendering-hoist-jsx- Extract static JSX outside componentsrendering-svg-precision- Reduce SVG coordinate precisionrendering-hydration-no-flicker- Keep server and first client theme consistentrendering-activity- Use Activity component for show/hiderendering-conditional-render- Use ternary, not && for conditionals
7. JavaScript Performance (LOW-MEDIUM)
js-batch-dom-css- Group CSS changes via classes or cssTextjs-index-maps- Build Map for repeated lookupsjs-cache-property-access- Cache object properties in loopsjs-cache-function-results- Cache function results in module-level Mapjs-cache-storage- Cache localStorage/sessionStorage readsjs-combine-iterations- Combine multiple filter/map into one loopjs-length-check-first- Check array length before expensive comparisonjs-early-exit- Return early from functionsjs-hoist-regexp- Hoist RegExp creation outside loopsjs-min-max-loop- Use loop for min/max instead of sortjs-set-map-lookups- Use Set/Map for O(1) lookupsjs-tosorted-immutable- Use toSorted() for immutability
8. Advanced Patterns (LOW)
advanced-event-handler-refs- Store event handlers in refsadvanced-use-latest- useLatest for stable callback refs
How to Use
Read individual rule files for detailed explanations and code examples:
rules/async-parallel.md
rules/bundle-barrel-imports.md
rules/_sections.md
Each rule file contains:
- Brief explanation of why it matters
- Incorrect code example with explanation
- Correct code example with explanation
- Additional context and references
Full Compiled Document
For the complete guide with all rules expanded: AGENTS.md
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Examples are sketches, not complete applications. Identify installed React/Next/SWR versions, public package exports and Server/Client module boundaries before editing. Profile a concrete bottleneck and preserve authorization, privacy, accessibility and behavior; impact levels and historical timing numbers are priorities, not guaranteed measurements. Validate one change with the application’s checks before broad refactoring. No deployments or analytics transmission are authorized by this guide.