home / skills / kienhaminh / anti-chaotic / frontend-developer

frontend-developer skill

/.agent/skills/frontend-developer

This skill helps optimize React and Next.js performance by applying Vercel's best-practice guidelines across components, pages, data fetching, and bundle

npx playbooks add skill kienhaminh/anti-chaotic --skill frontend-developer

Review the files below or copy the command above to add this skill to your agents.

Files (55)
SKILL.md
4.6 KB
---
name: react-nextjs
description: React and Next.js performance optimization guidelines from Vercel Engineering. Sub-skill of frontend-developer. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
license: MIT
metadata:
  parent-skill: frontend-developer
  author: vercel
  version: "1.0.0"
  type: sub-skill
---

# Vercel React Best Practices

Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 45 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

| 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 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-cache-react` - Use React.cache() for per-request deduplication
- `server-cache-lru` - Use LRU cache for cross-request caching
- `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

### 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-dependencies` - Use primitive dependencies in effects
- `rerender-derived-state` - Subscribe to derived booleans, not raw values
- `rerender-functional-setstate` - Use functional setState for stable callbacks
- `rerender-lazy-state-init` - Pass function to useState for expensive values
- `rerender-transitions` - Use startTransition for non-urgent updates

### 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-activity` - Use Activity component for show/hide
- `rendering-conditional-render` - Use ternary, not && for conditionals

### 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

### 8. Advanced Patterns (LOW)

- `advanced-event-handler-refs` - Store event handlers in refs
- `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
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`

Overview

This skill provides Vercel Engineering–inspired performance optimization guidelines for React and Next.js apps. It prioritizes actionable rules across critical categories like eliminating waterfalls, bundle size reduction, and server/client performance. Use it to guide automated refactors, code generation, and performance reviews for frontend projects.

How this skill works

The skill inspects component structure, data fetching patterns, bundling and import usage, server-side rendering paths, and client-side state and effects. It maps issues to prioritized rules and suggests concrete changes—e.g., parallelizing independent awaits, deferring heavy imports, adding caching layers, or memoizing expensive renders. Recommendations focus on minimal, high-impact edits that improve load time, CPU use, and bundle footprint.

When to use it

  • When adding or refactoring React components and Next.js pages
  • When implementing or reviewing data fetching (SSR, SSG, client fetches)
  • When diagnosing slow page loads or large bundle sizes
  • During code reviews focused on performance and scalability
  • When implementing progressive hydration, streaming, or suspense

Best practices

  • Eliminate waterfalls: start promises early and await them together for independent work
  • Reduce bundle size: import directly, use dynamic imports for heavy components, and defer third-party scripts
  • Optimize server work: cache per-request and cross-request results and minimize serialized client payloads
  • Control re-renders: memoize expensive nodes, use primitive effect deps, and prefer functional setState
  • Improve perceived performance: preload on hover/focus, stream content with Suspense, and hide non-critical work in transitions

Example use cases

  • Convert sequential API calls in getServerSideProps to Promise.all to cut server latency
  • Replace a large third-party component with next/dynamic so it loads after hydration
  • Introduce React.cache or an LRU cache to avoid duplicate fetches across requests
  • Refactor a component to use memo and functional state to reduce repeated expensive calculations
  • Defer analytics and logging scripts until after initial render to improve TTFB and hydration

FAQ

Which optimizations deliver the biggest wins first?

Start by eliminating waterfalls and reducing critical bundle weight: parallelize independent fetches and defer or dynamically import heavy modules.

How do I choose between server-side caching and client deduplication?

Use server-side caches for cross-request duplication and heavy compute; use client-side dedup (SWR) to reduce repeated client requests and improve perceived responsiveness.