React Best Practices

mastra-ai/mastra/.claude/skills/react-best-practices

作者 mastra-aia7a34bfcc223无许可证28K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库今天更新

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

AI 生成的概览

面向 React 的性能与代码质量指南,涵盖九大类共 27 条规则,用于编写、审查和重构 React 代码。

功能
该技能是 React 性能与质量工作的路由与优先级指南,按九大类组织,共 27 条规则。它概述了消除异步瀑布、减小打包体积等关键模式,以及数据获取、重渲染、渲染、JavaScript、组件结构、测试和类型安全方面的中等影响建议。详细的说明、示例、审查异味和影响指标存放在引用的规则文件中,可按需单独加载。
适用场景
适用于编写新的 React 组件、实现数据获取、审查 React 代码中的性能问题、重构现有 React 代码,或优化打包体积与加载时间。也适用于检查 React 代码库中的组件结构、测试约定或类型安全规则。
运行要求
无需脚本或运行时依赖,属于纯指令型技能。它依赖随附的参考目录和 references/rules/ 下的规则文件,由智能体按需读取或检索。

React Best Practices

Overview

Routing and priority guide for React performance and quality, containing 27 rules across 9 categories. Rule files hold the detailed explanations, examples, review smells, and impact metrics.

When to Apply

Reference these guidelines when:

  • Writing new React components
  • Implementing data fetching
  • Reviewing code for performance issues
  • Refactoring existing React code
  • Optimizing bundle size or load times

Priority-Ordered Guidelines

Rules are prioritized by impact:

PriorityCategoryImpact
1Eliminating WaterfallsCRITICAL
2Bundle Size OptimizationCRITICAL
3Client-Side Data FetchingMEDIUM-HIGH
4Re-render OptimizationMEDIUM
5Rendering PerformanceMEDIUM
6JavaScript PerformanceLOW-MEDIUM
7Component StructureMEDIUM-HIGH (maintainability)
8TestingMEDIUM-HIGH (correctness)
9Type SafetyHIGH

Quick Reference

Critical Patterns (Apply First)

Eliminate Waterfalls:

  • Use Promise.all() for independent async operations (async-parallel)

Reduce Bundle Size:

  • Avoid barrel file imports, import directly from source (bundle-barrel-imports)
  • Defer non-critical third-party libraries (bundle-defer-third-party)

Medium-Impact Patterns

Client-Side Data Fetching:

  • Use Tanstack Query for automatic request deduplication (client-request-dedupe)
  • Dependent query params are the value or undefined, never | null or a fake fallback; narrow at the caller so hooks stay strict, or guard with skipToken when the hook must accept an optional param (client-request-dedupe)

Re-render Optimization:

  • Use lazy state initialization for expensive values (rerender-lazy-state-init)
  • Apply startTransition for non-urgent updates (rerender-transitions)
  • Keep UI handlers plain; use Effect Events only for effect-fired logic (rerender-useeffect-function-calls)
  • Never reset state with useEffect; lift the discriminant and remount the branch (rerender-no-useeffect-state-reset)
  • Never add useMemo or useCallback; leave memoization decisions to developers with profiler evidence (rerender-no-usememo-usecallback)
  • Never call setState during render or inside useEffect; derive during render or move state ownership to an intermediate component (rerender-no-setstate-in-render-or-effect)

Component Structure:

  • One domain component/hook per file, one responsibility each — split bloated components (structure-single-responsibility)
  • Keep component, hook, function, and utility APIs narrow: split oversized props, arguments, and return objects into focused units composed at the component level; wrapping the same values in one object is not a fix (structure-narrow-apis)
  • Use PascalCase components for JSX-returning helpers; keep lowercase helpers for non-JSX values (structure-component-naming)
  • Derive props/params instead of accepting a value computable from another arg (structure-derive-dont-duplicate)
  • Extract complex derived logic into named locals plus predicates or pure helpers with early returns: oversized conditions, nested ternaries, ternaries that compute instead of picking (multi-line branches, or an as cast re-asserting what the condition tested), fallback chains, and let-based render prep are code smells, in render prep and in hook options, request builders, config maps, and reducers alike (structure-complex-derived-logic)
  • Pick the view with early if guards but keep the layout wrapper in one place — branch a body component, don't ternary or duplicate the shell (structure-early-return-render-branches)
  • For a fixed set of items, write one component per item with explicit props that owns its data and loading — don't map a config-object array onto a component shape (structure-composition-over-config)
  • When a domain component fetches data, render through a pure layout component that positions slots, and branch the slot contents between skeletons and resolved sub-domain components (structure-data-fetching-layout)

Testing:

  • BDD tests that drive the real @mastra/client-js + React Query stack and mock only the network; never vi.mock our own hooks/services/auth gating or the SDK (testing-bdd-no-mocks)
  • Avoid class-name assertions for visual behavior; prefer computed styles, user-visible behavior, or browser validation, and prefer no test over a className-only implementation mirror (testing-no-classname-assertions)

Type Safety:

  • No as type assertions anywhere — production or tests; narrow with real type guards, query generics (querySelector<T>, getByRole<T>), typed fixture factories, or implements on mocks. as const is the only allowed form. Do not replace a cast with a domain-type predicate that only checks typeof value === 'object'; call that an isRecord helper or validate the fields used (types-no-type-assertions)
  • Use undefined and optional ? for absence, not null; convert external null at boundaries, and keep leaf props strict so callers own absence and fallback rendering (types-no-null)

Rendering Patterns

  • Animate SVG wrappers, not SVG elements directly (rendering-animate-svg-wrapper)
  • Use content-visibility: auto for long lists (rendering-content-visibility)

JavaScript Patterns

  • Use Set/Map for repeated lookups (js-set-map-lookups)
  • Use toSorted() instead of sort() for immutability (js-tosorted-immutable)
  • Early length check for array comparisons (js-length-check-first)

References

Rule files are the canonical source for detailed guidance and examples:

  • references/react-best-practices-reference.md - Rule catalog with category order and rule-file paths
  • references/rules/ - Canonical individual rule files organized by category

Load only the relevant rule file when implementing or reviewing a specific pattern. Use the catalog to choose the right rule without loading every example.

To look up a specific pattern, grep the rules directory:

grep -l "Promise.all" references/rules/grep -l "barrel" references/rules/grep -l "Tanstack" references/rules/

Rule Categories in references/rules/

  • async-* - Waterfall elimination (1 rule)
  • bundle-* - Bundle size optimization (2 rules)
  • client-* - Client-side data fetching (1 rule)
  • rerender-* - Re-render optimization (6 rules)
  • rendering-* - DOM rendering performance (2 rules)
  • js-* - JavaScript micro-optimizations (3 rules)
  • types-* - Type-safety / no-as-cast and no-null rules (2 rules)
  • structure-* - Component/hook/function/utility structure (8 rules)
  • testing-* - BDD tests + mock-only-the-network policy + no className implementation-mirror assertions (2 rules)

来源与署名

来源:mastra-ai/mastra位于.claude/skills/react-best-practices提交a7a34bf

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架