design-review
Design Review
Review the rendered interface for visual and interaction defects, then fix confirmed issues when requested or already authorized. A review-only request produces findings and evidence without source edits.
Scope
Identify the target URL and changed routes, using the actual base/merge-base for a diff-aware review. Follow the shared QA exploration for browser access, snapshots, role/viewport coverage and safe interactions. Preserve unrelated dirt; use a separate checkout when needed rather than stashing or committing everything.
Use Full mode for the requested product surfaces, Quick for critical screens/states and Deep for an explicitly broader interaction/accessibility audit. Record what was inspected. Resolve genuine scope ambiguity once; reuse the user's answers and authorization.
Inspect
Calibrate to DESIGN.md, tokens, components, brand assets and rendered pages. Use relevant design checks: hierarchy, typography, spacing/alignment, copy, states, responsive reflow, keyboard/focus, contrast, motion and supported themes.
Separate visible/computed defects from aesthetic suggestions. A font, grid, color or border radius is not evidence of a defect by itself. Preserve intentional brand choices. Inspect actual text/background colors and font size/weight: 18px regular text is normal text and needs 4.5:1 at WCAG AA. The large-text threshold is 24px regular or about 18.67px bold.
Trace critical interactions across pages. Confirm focus order, error/recovery states and continuity, not just static screenshots. Where the browser tool supports script evaluation, gather console errors, failed requests, contrast, font loading and focus order in one scripted evaluation after each navigation, and capture all relevant viewports in one pass; the checks stay the same, only the round trips drop. Consolidate repeated symptoms into a systemic finding when the evidence supports a shared cause. Record severity from user impact, a screenshot or computed evidence, reproduction and the proposed correction.