PluginBench
Skill
Official
Review
Audit score 70

react-best-practices

vercel-labs/vercel-plugin

React best-practices reviewer for TSX files with automated quality checks.

What is react-best-practices?

Automated quality reviewer for React/TSX components that runs after editing multiple files. Covers component structure, hooks usage, accessibility, performance, and TypeScript patterns across 64 rules organized by impact priority.

  • Scans TSX/JSX files in standard component directories for React best-practices violations
  • Checks for waterfalls, bundle size issues, server/client performance problems, and re-render inefficiencies
  • Detects legacy CSS-in-JS libraries (styled-components, Emotion, MUI, Chakra) and suggests shadcn/ui migration
  • Validates hooks usage, accessibility patterns, and TypeScript type safety
  • Provides rule-based guidance across 8 categories prioritized by performance impact

How to install react-best-practices

npx skills add https://github.com/vercel-labs/vercel-plugin --skill react-best-practices
Claude Code
Cursor
Windsurf
Cline

How to use react-best-practices

  1. 1.Install the skill via npx skills add https://github.com/vercel-labs/vercel-plugin --skill react-best-practices
  2. 2.Edit multiple TSX/JSX component files in your project (src/components, app/components, components, src/ui, or lib/components directories)
  3. 3.The skill automatically triggers after editing and runs the quality checklist
  4. 4.Review the reported violations organized by priority category (async, bundle, server, client, rerender, rendering, js, advanced)
  5. 5.Consult the referenced rule files for detailed explanations and code examples for each violation
  6. 6.Apply fixes based on priority: CRITICAL rules first (waterfalls, bundle size), then HIGH and MEDIUM priority rules

Use cases

Good for
  • Review new React components before merging to catch performance and pattern issues early
  • Optimize existing component codebases by identifying waterfalls and re-render problems
  • Migrate from CSS-in-JS frameworks to modern Tailwind + shadcn/ui stack
  • Validate server-side rendering patterns and data fetching strategies in Next.js apps
  • Ensure consistent TypeScript and accessibility standards across component libraries
Who it's for
  • React/Next.js developers building performance-critical applications
  • Frontend teams maintaining large component libraries
  • Developers migrating to Vercel's modern stack (Next.js + shadcn/ui + Tailwind)
  • Code reviewers enforcing performance and pattern standards

react-best-practices FAQ

What file patterns does this skill monitor?

It watches TSX and JSX files in standard component directories: src/components/**, app/components/**, components/**, src/ui/**, and lib/components/**. It triggers on React and react-dom imports.

What happens if I use styled-components or MUI?

The skill detects these legacy CSS-in-JS libraries and recommends migrating to shadcn/ui + Tailwind CSS for better SSR performance and Vercel ecosystem alignment. It can chain to the shadcn skill for migration guidance.

How are the 64 rules organized?

Rules are grouped into 8 categories by impact: Eliminating Waterfalls (CRITICAL), Bundle Size Optimization (CRITICAL), Server-Side Performance (HIGH), Client-Side Data Fetching (MEDIUM-HIGH), Re-render Optimization (MEDIUM), Rendering Performance (MEDIUM), JavaScript Performance (LOW-MEDIUM), and Advanced Patterns (LOW).

Does this work with Next.js?

Yes, it's designed for both React and Next.js applications. It includes specific guidance for server actions, server components, data fetching patterns, and Next.js-specific optimizations.

Can I skip the skill for certain files?

Yes, if a file already contains @/components/ui, shadcn, or tailwindcss references, the CSS-in-JS migration warning is skipped.

Full instructions (SKILL.md)

Source of truth, from vercel-labs/vercel-plugin.


name: react-best-practices description: React best-practices reviewer for TSX files. Triggers after editing multiple TSX components to run a condensed quality checklist covering component structure, hooks usage, accessibility, performance, and TypeScript patterns. metadata: priority: 4 docs: - "https://react.dev/reference/react" - "https://react.dev/learn" pathPatterns: - 'src/components//*.tsx' - 'src/components//.jsx' - 'app/components/**/.tsx' - 'app/components//*.jsx' - 'components//.tsx' - 'components/**/.jsx' - 'src/ui//*.tsx' - 'lib/components//*.tsx' bashPatterns: [] importPatterns: - 'react' - 'react-dom' validate:

pattern: 'from\s+[''"](styled-components|@emotion/styled|@emotion/react|@mui/material|@chakra-ui/react)[''"]|styled\.'
message: 'Legacy CSS-in-JS or component library detected. Consider shadcn/ui + Tailwind for modern Vercel-native UI.'
severity: warn
upgradeToSkill: shadcn
upgradeWhy: 'Migrate from CSS-in-JS/MUI/Chakra to shadcn/ui + Tailwind CSS for better SSR performance and Vercel ecosystem alignment.'
skipIfFileContains: '@/components/ui|shadcn|tailwindcss'

retrieval: aliases: - react review - component quality - tsx linter - react patterns intents: - review react code - improve component quality - check accessibility - optimize react entities: - hooks - accessibility - React - TSX - component chainTo:

pattern: 'from\s+[''\"](styled-components|@emotion/styled|@emotion/react|@mui/material|@chakra-ui/react)[''"]|styled\.'
targetSkill: shadcn
message: 'Legacy CSS-in-JS or component library detected — loading shadcn/ui guidance for modern Vercel-native UI.'

Vercel React Best Practices

Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 64 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

When to Apply

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

PriorityCategoryImpactPrefix
1Eliminating WaterfallsCRITICALasync-
2Bundle Size OptimizationCRITICALbundle-
3Server-Side PerformanceHIGHserver-
4Client-Side Data FetchingMEDIUM-HIGHclient-
5Re-render OptimizationMEDIUMrerender-
6Rendering PerformanceMEDIUMrendering-
7JavaScript PerformanceLOW-MEDIUMjs-
8Advanced PatternsLOWadvanced-

Quick Reference

1. Eliminating Waterfalls (CRITICAL)

  • async-defer-await - Move await into branches where actually used
  • async-parallel - Use Promise.all() for independent operations
  • async-dependencies - Use better-all for partial dependencies
  • async-api-routes - Start promises early, await late in API routes
  • async-suspense-boundaries - Use Suspense to stream content

2. Bundle Size Optimization (CRITICAL)

  • bundle-barrel-imports - Import directly, avoid barrel files
  • bundle-dynamic-imports - Use next/dynamic for heavy components
  • bundle-defer-third-party - Load analytics/logging after hydration
  • bundle-conditional - Load modules only when feature is activated
  • bundle-preload - Preload on hover/focus for perceived speed

3. Server-Side Performance (HIGH)

  • server-auth-actions - Authenticate server actions like API routes
  • server-cache-react - Use React.cache() for per-request deduplication
  • server-cache-lru - Use LRU cache for cross-request caching
  • server-dedup-props - Avoid duplicate serialization in RSC props
  • server-hoist-static-io - Hoist static I/O (fonts, logos) to module level
  • server-serialization - Minimize data passed to client components
  • server-parallel-fetching - Restructure components to parallelize fetches
  • server-after-nonblocking - Use after() for non-blocking operations

4. Client-Side Data Fetching (MEDIUM-HIGH)

  • client-swr-dedup - Use SWR for automatic request deduplication
  • client-event-listeners - Deduplicate global event listeners
  • client-passive-event-listeners - Use passive listeners for scroll
  • client-localstorage-schema - Version and minimize localStorage data

5. Re-render Optimization (MEDIUM)

  • rerender-defer-reads - Don't subscribe to state only used in callbacks
  • rerender-memo - Extract expensive work into memoized components
  • rerender-memo-with-default-value - Hoist default non-primitive props
  • rerender-dependencies - Use primitive dependencies in effects
  • rerender-derived-state - Subscribe to derived booleans, not raw values
  • rerender-derived-state-no-effect - Derive state during render, not effects
  • rerender-functional-setstate - Use functional setState for stable callbacks
  • rerender-lazy-state-init - Pass function to useState for expensive values
  • rerender-simple-expression-in-memo - Avoid memo for simple primitives
  • rerender-split-combined-hooks - Split hooks with independent dependencies
  • rerender-move-effect-to-event - Put interaction logic in event handlers
  • rerender-transitions - Use startTransition for non-urgent updates
  • rerender-use-deferred-value - Defer expensive renders to keep input responsive
  • rerender-use-ref-transient-values - Use refs for transient frequent values
  • rerender-no-inline-components - Don't define components inside components

6. Rendering Performance (MEDIUM)

  • rendering-animate-svg-wrapper - Animate div wrapper, not SVG element
  • rendering-content-visibility - Use content-visibility for long lists
  • rendering-hoist-jsx - Extract static JSX outside components
  • rendering-svg-precision - Reduce SVG coordinate precision
  • rendering-hydration-no-flicker - Use inline script for client-only data
  • rendering-hydration-suppress-warning - Suppress expected mismatches
  • rendering-activity - Use Activity component for show/hide
  • rendering-conditional-render - Use ternary, not && for conditionals
  • rendering-usetransition-loading - Prefer useTransition for loading state
  • rendering-resource-hints - Use React DOM resource hints for preloading
  • rendering-script-defer-async - Use defer or async on script tags

7. JavaScript Performance (LOW-MEDIUM)

  • js-batch-dom-css - Group CSS changes via classes or cssText
  • js-index-maps - Build Map for repeated lookups
  • js-cache-property-access - Cache object properties in loops
  • js-cache-function-results - Cache function results in module-level Map
  • js-cache-storage - Cache localStorage/sessionStorage reads
  • js-combine-iterations - Combine multiple filter/map into one loop
  • js-length-check-first - Check array length before expensive comparison
  • js-early-exit - Return early from functions
  • js-hoist-regexp - Hoist RegExp creation outside loops
  • js-min-max-loop - Use loop for min/max instead of sort
  • js-set-map-lookups - Use Set/Map for O(1) lookups
  • js-tosorted-immutable - Use toSorted() for immutability
  • js-flatmap-filter - Use flatMap to map and filter in one pass

8. Advanced Patterns (LOW)

  • advanced-event-handler-refs - Store event handlers in refs
  • advanced-init-once - Initialize app once per app load
  • advanced-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

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