Skip to content

zebbern/claude-code-guide / skills/react-best-practices

vercel-react-best-practices

Verified

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.

FileKindSize
AGENTS.mdmarkdown79.4 KB
README.mdmarkdown3.3 KB
SKILL.mdskill md6.2 KB
metadata.jsonconfig921 B
rules/_sections.mdmarkdown1.5 KB
rules/_template.mdmarkdown631 B
rules/advanced-event-handler-refs.mdmarkdown1.4 KB
rules/advanced-init-once.mdmarkdown958 B
rules/advanced-use-latest.mdmarkdown1.0 KB
rules/async-api-routes.mdmarkdown1.1 KB
rules/async-defer-await.mdmarkdown2.0 KB
rules/async-dependencies.mdmarkdown1.3 KB
rules/async-parallel.mdmarkdown646 B
rules/async-suspense-boundaries.mdmarkdown2.4 KB
rules/bundle-barrel-imports.mdmarkdown2.3 KB
rules/bundle-conditional.mdmarkdown959 B
rules/bundle-defer-third-party.mdmarkdown919 B
rules/bundle-dynamic-imports.mdmarkdown790 B
rules/bundle-preload.mdmarkdown1.1 KB
rules/client-event-listeners.mdmarkdown1.9 KB
rules/client-localstorage-schema.mdmarkdown1.9 KB
rules/client-passive-event-listeners.mdmarkdown1.6 KB
rules/client-swr-dedup.mdmarkdown1.1 KB
rules/js-batch-dom-css.mdmarkdown3.2 KB
rules/js-cache-function-results.mdmarkdown1.9 KB
rules/js-cache-property-access.mdmarkdown532 B
rules/js-cache-storage.mdmarkdown1.6 KB
rules/js-combine-iterations.mdmarkdown759 B
rules/js-early-exit.mdmarkdown1.1 KB
rules/js-hoist-regexp.mdmarkdown1.0 KB
rules/js-index-maps.mdmarkdown847 B
rules/js-length-check-first.mdmarkdown1.7 KB
rules/js-min-max-loop.mdmarkdown2.2 KB
rules/js-set-map-lookups.mdmarkdown532 B
rules/js-tosorted-immutable.mdmarkdown1.7 KB
rules/rendering-activity.mdmarkdown564 B
rules/rendering-animate-svg-wrapper.mdmarkdown1.1 KB
rules/rendering-conditional-render.mdmarkdown936 B
rules/rendering-content-visibility.mdmarkdown817 B
rules/rendering-hoist-jsx.mdmarkdown989 B
rules/rendering-hydration-no-flicker.mdmarkdown2.2 KB
rules/rendering-hydration-suppress-warning.mdmarkdown850 B
rules/rendering-svg-precision.mdmarkdown588 B
rules/rendering-usetransition-loading.mdmarkdown2.0 KB
rules/rerender-defer-reads.mdmarkdown973 B
rules/rerender-dependencies.mdmarkdown824 B
rules/rerender-derived-state-no-effect.mdmarkdown1.2 KB
rules/rerender-derived-state.mdmarkdown727 B
rules/rerender-functional-setstate.mdmarkdown2.9 KB
rules/rerender-lazy-state-init.mdmarkdown2.0 KB
rules/rerender-memo-with-default-value.mdmarkdown1.1 KB
rules/rerender-memo.mdmarkdown1.1 KB
rules/rerender-move-effect-to-event.mdmarkdown1.2 KB
rules/rerender-simple-expression-in-memo.mdmarkdown1018 B
rules/rerender-transitions.mdmarkdown1.0 KB
rules/rerender-use-ref-transient-values.mdmarkdown1.7 KB
rules/server-after-nonblocking.mdmarkdown2.0 KB
rules/server-auth-actions.mdmarkdown2.6 KB
rules/server-cache-lru.mdmarkdown1.3 KB
rules/server-cache-react.mdmarkdown2.2 KB
rules/server-dedup-props.mdmarkdown2.0 KB
rules/server-parallel-fetching.mdmarkdown1.5 KB
rules/server-serialization.mdmarkdown1000 B

rules/js-batch-dom-css.md

View on GitHub
---
title: Avoid Layout Thrashing
impact: MEDIUM
impactDescription: prevents forced synchronous layouts and reduces performance bottlenecks
tags: javascript, dom, css, performance, reflow, layout-thrashing
---

## Avoid Layout Thrashing

Avoid interleaving style writes with layout reads. When you read a layout property (like `offsetWidth`, `getBoundingClientRect()`, or `getComputedStyle()`) between style changes, the browser is forced to trigger a synchronous reflow.

**This is OK (browser batches style changes):**

```typescript
function updateElementStyles(element: HTMLElement) {
  // Each line invalidates style, but browser batches the recalculation
  element.style.width = "100px"
  element.style.height = "200px"
  element.style.backgroundColor = "blue"
  element.style.border = "1px solid black"
}
```

**Incorrect (interleaved reads and writes force reflows):**

```typescript
function layoutThrashing(element: HTMLElement) {
  element.style.width = "100px"
  const width = element.offsetWidth // Forces reflow
  element.style.height = "200px"
  const height = element.offsetHeight // Forces another reflow
}
```

**Correct (batch writes, then read once):**

```typescript
function updateElementStyles(element: HTMLElement) {
  // Batch all writes together
  element.style.width = "100px"
  element.style.height = "200px"
  element.style.backgroundColor = "blue"
  element.style.border = "1px solid black"

  // Read after all writes are done (single reflow)
  const { width, height } = element.getBoundingClientRect()
}
```

**Correct (batch reads, then writes):**

```typescript
function avoidThrashing(element: HTMLElement) {
  // Read phase - all layout queries first
  const rect1 = element.getBoundingClientRect()
  const offsetWidth = element.offsetWidth
  const offsetHeight = element.offsetHeight

  // Write phase - all style changes after
  element.style.width = "100px"
  element.style.height = "200px"
}
```

**Better: use CSS classes**

```css
.highlighted-box {
  width: 100px;
  height: 200px;
  background-color: blue;
  border: 1px solid black;
}
```

```typescript
function updateElementStyles(element: HTMLElement) {
  element.classList.add("highlighted-box")

  const { width, height } = element.getBoundingClientRect()
}
```

**React example:**

```tsx
// Incorrect: interleaving style changes with layout queries
function Box({ isHighlighted }: { isHighlighted: boolean }) {
  const ref = useRef<HTMLDivElement>(null)

  useEffect(() => {
    if (ref.current && isHighlighted) {
      ref.current.style.width = "100px"
      const width = ref.current.offsetWidth // Forces layout
      ref.current.style.height = "200px"
    }
  }, [isHighlighted])

  return <div ref={ref}>Content</div>
}

// Correct: toggle class
function Box({ isHighlighted }: { isHighlighted: boolean }) {
  return <div className={isHighlighted ? "highlighted-box" : ""}>Content</div>
}
```

Prefer CSS classes over inline styles when possible. CSS files are cached by the browser, and classes provide better separation of concerns and are easier to maintain.

See [this gist](https://gist.github.com/paulirish/5d52fb081b3570c81e3a) and [CSS Triggers](https://csstriggers.com/) for more information on layout-forcing operations.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 319kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 196kUpdated Claude CodeCodexVerifiedInstall