Modèles React 19.2 modernes

VérifiéSûr

Principes pour construire des applications React prêtes pour la production, couvrant les composants serveur, hooks, gestion d'état, performances et tests.

Spar Skills Guide Bot
DeveloppementAvancé
1027/07/2026
Claude Code
#react#component-design#hooks#state-management#performance

Recommandé pour

Notre avis

Fournit des modèles modernes pour React 19.2 couvrant la conception de composants, les hooks, la gestion d'état et l'optimisation des performances.

Points forts

  • Couvre un large éventail de concepts React, des types de composants aux anti-patrons
  • Inclut des tableaux pratiques pour la prise de décision
  • Se concentre sur la composition et les bonnes pratiques

Limites

  • Manque d'exemples de code concrets
  • Peut être trop général pour les débutants
  • Suppose une familiarité avec TypeScript et les tests
Quand l'utiliser

Utilisez cette compétence lors de la conception de nouveaux composants React ou de la refactorisation de composants existants pour suivre les meilleures pratiques modernes.

Quand l'éviter

N'utilisez pas cette compétence si vous avez besoin de tutoriels étape par étape ou d'extraits de code fonctionnels.

Analyse de sécurité

Sûr
Score qualité85/100

The skill provides React design pattern guidance without any executable code or instructions that could compromise security. It only uses safe file and search tools for development assistance.

Aucun point d'attention détecté

Exemples

Component design advice
I'm building a new React component. What design principles should I follow?
State management selection
How should I choose between useState, Context, React Query, and Zustand for my app?
Performance optimization
My React app is slow. How should I approach performance optimization?

name: react-patterns description: "Mẫu thiết kế React 19.2 hiện đại: Compiler, Hooks, Server Components và tối ưu re-render." allowed-tools: Read, Write, Edit, Glob, Grep

React Patterns

Principles for building production-ready React applications.


1. Component Design Principles

Component Types

| Type | Use | State | |------|-----|-------| | Server | Data fetching, static | None | | Client | Interactivity | useState, effects | | Presentational | UI display | Props only | | Container | Logic/state | Heavy state |

Design Rules

  • One responsibility per component
  • Props down, events up
  • Composition over inheritance
  • Prefer small, focused components

2. Hook Patterns

When to Extract Hooks

| Pattern | Extract When | |---------|-------------| | useLocalStorage | Same storage logic needed | | useDebounce | Multiple debounced values | | useFetch | Repeated fetch patterns | | useForm | Complex form state |

Hook Rules

  • Hooks at top level only
  • Same order every render
  • Custom hooks start with "use"
  • Clean up effects on unmount

3. State Management Selection

| Complexity | Solution | |------------|----------| | Simple | useState, useReducer | | Shared local | Context | | Server state | React Query, SWR | | Complex global | Zustand, Redux Toolkit |

State Placement

| Scope | Where | |-------|-------| | Single component | useState |

  • Parent provides context
  • Children consume context
  • Flexible slot-based composition
  • Example: Tabs, Accordion, Dropdown

Render Props vs Hooks

| Use Case | Prefer | |----------|--------| | Reusable logic | Custom hook | | Render flexibility | Render props | | Cross-cutting | Higher-order component |


6. Performance Principles

When to Optimize

| Signal | Action | |--------|--------| | Slow renders | Profile first | | Large lists | Virtualize | | Expensive calc | useMemo | | Stable callbacks | useCallback |

Optimization Order

  1. Check if actually slow
  2. Profile with DevTools
  3. Identify bottleneck
  4. Apply targeted fix

7. Error Handling

Error Boundary Usage

| Scope | Placement | |-------|-----------| | App-wide | Root level | | Feature | Route/feature level | | Component | Around risky component |

Error Recovery

  • Show fallback UI
  • Log error
  • Offer retry option
  • Preserve user data

8. TypeScript Patterns

Props Typing

| Pattern | Use | |---------|-----| | Interface | Component props | | Type | Unions, complex | | Generic | Reusable components |

Common Types

| Need | Type | |------|------| | Children | ReactNode | | Event handler | MouseEventHandler | | Ref | RefObject<Element> |


9. Testing Principles

| Level | Focus | |-------|-------| | Unit | Pure functions, hooks | | Integration | Component behavior | | E2E | User flows |

Test Priorities

  • User-visible behavior
  • Edge cases
  • Error states
  • Accessibility

10. Anti-Patterns

| ❌ Don't | ✅ Do | |----------|-------| | Prop drilling deep | Use context | | Giant components | Split smaller | | useEffect for everything | Server components | | Premature optimization | Profile first | | Index as key | Stable unique ID |


Remember: React is about composition. Build small, combine thoughtfully.

Skills similaires