react-patterns

To review React components for hooks discipline and state placement, audit effect boundaries, keep derived values correct, and choose between local state, context, or external stores based on justified performance heuristics.

The best way to structure Server Components and Client Components is to enforce clear server-client boundaries by ensuring serializable server-client props and correctly routing data fetching and Suspense boundaries across your React architecture.

Handling Suspense and error boundaries when fetching data in React requires wrapping asynchronous data fetching operations in Suspense boundaries and pairing them with error boundaries to gracefully manage loading states and rendering failures.

React components fail accessibility reviews when lacking semantic markup; fix this by building keyboard-friendly UI structures with proper labels, correct focus handling, and accessible composition throughout your component architecture.

Yes, you can audit React form actions and custom hooks by reviewing render purity, validating effect boundaries, and ensuring your custom hooks follow disciplined patterns for subscriptions and derived state.

You should not use memoization in React state management when performance heuristics do not justify it; instead, rely on predictable rendering behavior and choose local state or context only when clearly needed for your component architecture.