react-doctorlisted

# React Doctor — React/Next.js Anti-Pattern Audit ## Why this exists `typescript-nextjs.md` codifies the language + framework baseline (strict mode, no `any`, Server Components by default). It does NOT govern the *runtime component contract*: how state is owned, when effects are legitimate, why a tree re-renders, where the client/server boundary leaks, and whether the rendered DOM is operable by a keyboard or screen reader. Those failures pass `tsc`, pass lint, and ship — then surface as jank, hydration mismatches, XSS, and inaccessible flows in production. This skill is the diagnostic layer between "it compiles" and "it is correct". It runs a six-axis audit (state / effects / performance / architecture / security / accessibility) and emits findings in the standard `finding-schema.md` shape so the director or `/ulak-frontend` can fold them into `analysis-findings.md`. It is read-only — it diagnoses, it does not refactor. Attribution: audit category structure is adapted from **react-doctor** (millionco, MIT-licensed). Provenance recorded in `NOTICE.md`. No source text is reproduced; the contracts below are Ulak-native and map onto the existing anti-pattern catalogue. ## When to use - Before extending an existing React/Next.js surface (`/ulak-frontend`, EXTEND/REFACTOR mode) — diagnose before adding to the mess - During Phase 2 parallel evidence on any repo whose runtime-manifest detects `react` + (`next` | client components) - As a pre-merge gate on a frontend PR that to