React Refactor

作者 pproencacf93c57cac89無授權條款215 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫7 週前更新

Architectural refactoring guide for React applications covering component architecture, state architecture, hook patterns, component decomposition, coupling and cohesion, data flow, and refactoring safety. Use when refactoring React codebases, reviewing PRs for architectural issues, decomposing oversized components, or improving module boundaries. Does NOT cover React 19 API usage (see react skill) or performance optimization (see react-optimise skill).

AI 產生的概覽

針對 React 應用程式的架構重構指南,涵蓋元件、狀態、Hook 與資料模式的 40 條規則。

功能
提供 40 條依優先順序排列的 React 應用程式架構重構規則,分為七個類別,從關鍵的元件與狀態架構到重構安全性。每條規則記錄在參考檔案中,涵蓋複合元件、狀態就近放置、自訂 Hook、元件拆分、耦合、資料擷取與測試等模式。它僅為指導性文件,不會產生指令碼或產出檔案。
適用情境
適用於重構現有 React 程式碼庫、審查提取請求中的架構問題、拆分過大的元件、擷取可重用的 Hook,或改善模組邊界與可測試性。
執行需求
除代理程式外不需要任何工具、套件或憑證;不附帶指令碼,僅提供參考文件。

React Refactor Best Practices

Architectural refactoring guide for React applications. Contains 40 rules across 7 categories, prioritized by impact from critical (component and state architecture) to incremental (refactoring safety).

When to Apply

  • Refactoring existing React codebases or planning large-scale restructuring
  • Reviewing PRs for architectural issues and code smells
  • Decomposing oversized components into focused units
  • Extracting reusable hooks from component logic
  • Improving testability of React code
  • Reducing coupling between feature modules

Rule Categories

CategoryImpactRulesKey Topics
Component ArchitectureCRITICAL8Compound components, headless pattern, composition over props, client boundaries
State ArchitectureCRITICAL7Colocation, state machines, URL state, derived values
Hook PatternsHIGH6Single responsibility, naming, dependency stability, composition
Component DecompositionHIGH6Scroll test, extraction by change reason, view/logic separation
Coupling & CohesionMEDIUM4Dependency injection, circular deps, stable imports, barrel-free
Data & Side EffectsMEDIUM4Server-first fetch, TanStack Query, error boundaries
Refactoring SafetyLOW-MEDIUM5Characterization tests, behavior testing, integration tests

Quick Reference

Critical patterns — get these right first:

  • Use compound components instead of props explosion
  • Colocate state with the components that use it
  • Use state machines for complex UI workflows
  • Separate container logic from presentational components

Common mistakes — avoid these anti-patterns:

  • Lifting state to App when only one component reads it
  • Using context for rapidly-changing values
  • Monolithic hooks that fetch + transform + cache
  • Testing implementation details instead of behavior

Table of Contents

  1. Component Architecture [blocked] — CRITICAL
    • 1.1 Apply Interface Segregation to Component Props [blocked] — CRITICAL (prevents 30-50% of unnecessary re-renders)
    • 1.2 Colocate Files by Feature Instead of Type [blocked] — CRITICAL (reduces cross-directory navigation by 70%)
    • 1.3 Convert Render Props to Custom Hooks [blocked] — CRITICAL (eliminates 2-4 levels of nesting)
    • 1.4 Extract Headless Components for Logic Reuse [blocked] — CRITICAL (5x more reuse scenarios)
    • 1.5 Prefer Composition Over Props Explosion [blocked] — CRITICAL (reduces prop count by 50-70%)
    • 1.6 Separate Container Logic from Presentational Components [blocked] — CRITICAL (enables independent testing)
    • 1.7 Use Compound Components for Implicit State Sharing [blocked] — CRITICAL (reduces API surface by 60%)
    • 1.8 Push Client Boundaries to Leaf Components [blocked] — HIGH (keeps 60-80% server-rendered)
  2. State Architecture [blocked] — CRITICAL
    • 2.1 Colocate State with Components That Use It [blocked] — CRITICAL (reduces prop passing by 60%)
    • 2.2 Derive Values Instead of Syncing State [blocked] — CRITICAL (eliminates double-render cycle)
    • 2.3 Lift State Only When Multiple Components Read It [blocked] — CRITICAL (eliminates unnecessary parent re-renders)
    • 2.4 Use Context for Rarely-Changing Values Only [blocked] — CRITICAL (5-50x fewer re-renders)
    • 2.5 Use State Machines for Complex UI Workflows [blocked] — CRITICAL (reduces valid states from 2^n to N)
    • 2.6 Use URL Parameters as State for Shareable Views [blocked] — CRITICAL (enables deep linking and sharing)
    • 2.7 Use useReducer for Multi-Field State Transitions [blocked] — CRITICAL (eliminates impossible states)
  3. Hook Patterns [blocked] — HIGH
    • 3.1 Avoid Object and Array Dependencies in Custom Hooks [blocked] — HIGH (prevents effect re-execution every render)
    • 3.2 Compose Hooks Instead of Nesting Them [blocked] — HIGH (flattens dependency graph)
    • 3.3 Extract Logic into Custom Hooks When Behavior Is Nameable [blocked] — HIGH (40-60% shorter components)
    • 3.4 Follow Hook Naming Conventions for Discoverability [blocked] — HIGH (reduces navigation time by 40%)
    • 3.5 Keep Custom Hooks to a Single Responsibility [blocked] — HIGH (3x easier to test)
    • 3.6 Stabilize Hook Dependencies with Refs and Callbacks [blocked] — HIGH (prevents infinite loops)
  4. Component Decomposition [blocked] — HIGH
    • 4.1 Apply the Scroll Test to Identify Oversized Components [blocked] — HIGH (3x faster code review)
    • 4.2 Complete Component Extraction Without Half-Measures [blocked] — HIGH (enables independent testing and reuse)
    • 4.3 Extract Components by Independent Change Reasons [blocked] — HIGH (70% fewer files touched per change)
    • 4.4 Extract Pure Functions from Component Bodies [blocked] — HIGH (10x faster unit tests)
    • 4.5 Inline Premature Abstractions Before Re-Extracting [blocked] — HIGH (40-60% simpler code)
    • 4.6 Separate View Layer from Business Logic [blocked] — HIGH (5x faster test suite)
  5. Coupling & Cohesion [blocked] — MEDIUM
    • 5.1 Break Circular Dependencies with Intermediate Modules [blocked] — MEDIUM (eliminates undefined-at-import-time bugs)
    • 5.2 Import from Stable Public API Surfaces Only [blocked] — MEDIUM (enables internal refactoring)
    • 5.3 Use Barrel-Free Feature Modules for Clean Dependencies [blocked] — MEDIUM (200-800ms build reduction)
    • 5.4 Use Dependency Injection for External Services [blocked] — MEDIUM (3x faster test setup)
  6. Data & Side Effects [blocked] — MEDIUM
    • 6.1 Fetch Data on the Server by Default [blocked] — MEDIUM (reduces client JS by 30-60%)
    • 6.2 Place Error Boundaries at Data Fetch Granularity [blocked] — MEDIUM (errors isolated to affected section)
    • 6.3 Use Context Module Pattern for Action Colocation [blocked] — MEDIUM (centralizes data mutations)
    • 6.4 Use TanStack Query for Client-Side Server State [blocked] — MEDIUM (eliminates 80% of fetch boilerplate)
  7. Refactoring Safety [blocked] — LOW-MEDIUM
    • 7.1 Avoid Snapshot Tests for Refactored Components [blocked] — LOW-MEDIUM (eliminates false test failures)
    • 7.2 Extract Pure Functions to Increase Testability [blocked] — LOW-MEDIUM (10x faster test execution)
    • 7.3 Prefer Integration Tests for Component Verification [blocked] — LOW-MEDIUM (catches 40% more bugs)
    • 7.4 Test Component Behavior Not Implementation Details [blocked] — LOW-MEDIUM (5x fewer test updates)
    • 7.5 Write Characterization Tests Before Refactoring [blocked] — LOW-MEDIUM (catches 90% of unintended changes)

References

  1. https://react.dev
  2. https://react.dev/learn/thinking-in-react
  3. https://kentcdodds.com/blog/application-state-management-with-react
  4. https://testing-library.com/docs/guiding-principles
  5. https://patterns.dev

Related Skills

  • For React 19 API best practices, see react skill
  • For application performance optimization, see react-optimise skill
  • For client-side form handling, see react-hook-form skill

來源與署名

來源:pproenca/dot-skills位於skills/.experimental/react-refactor提交cf93c57

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架