frontend-code-review

Check that hooks are never called inside conditions or loops, useEffect dependency arrays are complete, cleanup functions are returned where needed, and useState uses lazy initialization for expensive initial values. Custom hooks should start with 'use' and have independent tests.

A thorough checklist covers correctness, type safety, component design, hook usage, performance, state management, accessibility, styling, and security. Prioritize findings as P0 (blocking), P1 (should fix), and P2 (nice to have) so reviewers know what blocks a merge.

Verify list items have stable unique keys, large lists over 100 items use virtual scrolling, expensive computations are wrapped in useMemo, callbacks passed to children use useCallback, and routes use React.lazy for code splitting.

Yes, the checklist includes Zustand-specific checks: stores split by domain, selective subscriptions via useStore(selector) to avoid global re-renders, derived state computed in selectors rather than synced with useEffect, and separation of server and client state.

Checklist review catches known pattern violations but cannot verify runtime behavior, business logic correctness, or visual regressions. Combine it with automated tests, type checking via tsc --noEmit, and manual exploratory testing for full coverage.