All skills
vercel-labs avatar

/react-best-practices

@805687f official
by Vercel Labsvercel-labs/agent-skills32k stars
2,784

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Use this Skill: https://skilld.dev/gh/vercel-labs/agent-skills/react-best-practices

This session only. Nothing lands on disk.

rulesbundle-barrel-imports.md

≈699 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Avoid Barrel File Imports

Import directly from source files instead of barrel files to avoid loading thousands of unused modules. Barrel files are entry points that re-export multiple modules (e.g., index.js that does export * from './module').

Popular icon and component libraries can have up to 10,000 re-exports in their entry file. For many React packages, it takes 200-800ms just to import them, affecting both development speed and production cold starts.

Why tree-shaking doesn't help: When a library is marked as external (not bundled), the bundler can't optimize it. If you bundle it to enable tree-shaking, builds become substantially slower analyzing the entire module graph.

Incorrect (imports entire library):

import { Check, X, Menu } from 'lucide-react'
// Loads 1,583 modules, takes ~2.8s extra in dev
// Runtime cost: 200-800ms on every cold start

import { Button, TextField } from '@mui/material'
// Loads 2,225 modules, takes ~4.2s extra in dev

Correct - Next.js 13.5+ (recommended):

// next.config.js - automatically optimizes barrel imports at build time
module.exports = {
  experimental: {
    optimizePackageImports: ['lucide-react', '@mui/material']
  }
}
// Keep the standard imports - Next.js transforms them to direct imports
import { Check, X, Menu } from 'lucide-react'
// Full TypeScript support, no manual path wrangling

This is the recommended approach because it preserves TypeScript type safety and editor autocompletion while still eliminating the barrel import cost.

Correct - Direct imports (non-Next.js projects):

import Button from '@mui/material/Button'
import TextField from '@mui/material/TextField'
// Loads only what you use

TypeScript warning: Some libraries (notably lucide-react) don't ship .d.ts files for their deep import paths. Importing from lucide-react/dist/esm/icons/check resolves to an implicit any type, causing errors under strict or noImplicitAny. Prefer optimizePackageImports when available, or verify the library exports types for its subpaths before using direct imports.

These optimizations provide 15-70% faster dev boot, 28% faster builds, 40% faster cold starts, and significantly faster HMR.

Libraries commonly affected: lucide-react, @mui/material, @mui/icons-material, @tabler/icons-react, react-icons, @headlessui/react, @radix-ui/react-*, lodash, ramda, date-fns, rxjs, react-use.

Reference: How we optimized package imports in Next.js

Source: SKILL.md on GitHub

No alerts16d4 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides a comprehensive set of performance optimization and best practice guidelines for React and Next.js applications. No security issues or risky patterns were detected.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    1/63 files flagged

Signed by skilld at 805687f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 6 months ago
metadata
{
  "author": "vercel",
  "version": "1.0.0"
}

README badge

README badge for vercel-labs/agent-skills/react-best-practices

Provides 70 React and Next.js performance optimization rules organized by priority, from eliminating waterfalls and bundle size optimization to re-render and rendering performance. Use this skill when writing, reviewing, or refactoring React/Next.js code to apply Vercel's performance patterns for data fetching, component structure, and bundle optimization.

Generated from the current SKILL.md.

Does this skill cover both React and Next.js?
Yes. The skill includes guidelines for React components, Next.js pages, server-side rendering, server actions, and data fetching patterns across both frameworks.
Are these rules ranked by importance?
Yes. Rules are organized into 8 categories ranked by impact, from eliminating waterfalls and bundle optimization (CRITICAL) down to advanced patterns (LOW).
Can this skill be used during code review and refactoring?
Yes. The skill is intended for writing new code, reviewing existing code for performance issues, and refactoring React/Next.js applications.
Does this skill include code examples?
Yes. Each of the 70 rules has a detailed file with incorrect and correct code examples, explanations, and additional context.

Generated from the current SKILL.md. These answers refresh after source changes.