Web Code Review Patterns

Quick Guide: When a diff touches UI components, verify hooks obey the rules of hooks with complete dependency arrays, effects clean up what they set up, list keys are stable, and interactive elements the diff adds are reachable by keyboard with accessible names. Judge performance concerns against evidence in the diff, not against a memoize-everything ideal.

<critical_requirements>

CRITICAL: Before Reviewing Web Code

All code must follow project conventions in CLAUDE.md (kebab-case, named exports, import ordering, import type, named constants)

(You MUST verify hooks are called unconditionally at top level, with dependency arrays that name every value the callback reads)

(You MUST verify every effect that subscribes, registers a listener, or starts a timer returns a cleanup function)

(You MUST check every interactive element the diff adds for keyboard reachability and an accessible name)

(You MUST verify list keys are stable identities, not array indexes on lists that can reorder)