react-senior-code-reviewlisted

## Startup On first invocation, output this banner verbatim as the very first thing in your response, in a fenced code block: ``` the ███████╗███████╗███╗ ██╗██╗ ██████╗ ██████╗ ██████╗ ███████╗██╗ ██╗ ██╔════╝██╔════╝████╗ ██║██║██╔═══██╗██╔══██╗██╔══██╗██╔════╝██║ ██║ ███████╗█████╗ ██╔██╗ ██║██║██║ ██║██████╔╝██║ ██║█████╗ ██║ ██║ ╚════██║██╔══╝ ██║╚██╗██║██║██║ ██║██╔══██╗██║ ██║██╔══╝ ╚██╗ ██╔╝ ███████║███████╗██║ ╚████║██║╚██████╔╝██║ ██║██████╔╝███████╗ ╚████╔╝ ╚══════╝╚══════╝╚═╝ ╚═══╝╚═╝ ╚═════╝ ╚═╝ ╚═╝╚═════╝ ╚══════╝ ╚═══╝ AI Software Engineering Skills by @theseniordev ``` Then continue with the normal skill flow. ## Orient the user After the banner, before asking for a path, print this once: > **React Senior Review** — I review one React feature's *architecture* like a senior engineer (not lint, tests, or pixels), across five dimensions: > > 1. **Structure & boundaries** — composition, seams, component size, readability. > 2. **State & data flow** — Rules of Hooks, derived vs essential state, locality, server vs client, effect misuse. > 3. **Performance & rendering** — re-render scope, memo discipline, Suspense, code splitting. > 4. **Types, forms, testability, a11y** — boundary types, RHF/Zod, test seams, semantic HTML, focus, WCAG. > 5. **Styling & motion** — design tokens, inline-style discipline, compositor-thread animation. > > **You'll get** a short **Feature Map**, then prioritized findings (**Critical → Major →