open-claude-ui-reviewlisted

# UI Design Review Judge the rendered product, not the source in isolation. A design review distinguishes standards failures, product-quality problems, and subjective preferences so the user can trust the verdict. ## Mutation boundary **Review and audit requests are report-only.** Inspect, execute read-only checks, and return evidence-backed findings without editing files. **Change files only when the user asks to fix, polish, redesign, or implement**, or when a parent workflow explicitly carries that authorized fix scope. ## Establish the baseline Read the affected UI, its tokens/components, supported themes, product context, and user-stated constraints. Capture the current rendered state before proposing a correction. Existing brand and system choices outrank generic taste; accessibility requirements do not. When Impeccable is installed, reuse current hook findings and named refinement evidence. Do not run its detector again unless no current hook evidence exists or a specific fix needs rechecking. ## Select review lanes Read only the relevant references, resolved relative to this skill: | Lane | Required reference | |---|---| | Contrast, semantics, keyboard, forms, motion, target size, or WCAG review | `references/accessibility.md` | | Brand fidelity, content discipline, hierarchy, rhythm, system consistency, or generic-template review | `references/visual-quality.md` | | Interactive states, responsive/theme coverage, runtime verification, or final polish | `refer