Reviewing Web Interfaces
Use evidence from a rendered interface. This is a review skill, not permission to redesign a product without the Designing Interfaces reference lock.
Workflow
- For a React shadcn app, run the deterministic shadscan audit first per shadscan-audit.md — it produces the missing UI fundamentals report from static evidence before anything renders.
- Capture the affected route and viewport(s) with rendering-chromium-to-png.
- For a material UI change, get a fresh-context critique when an independent reviewer is available. Keep its evidence separate from the implementation rationale.
- Review semantics, keyboard flow, focus, overflow, contrast, responsive states, production states, and user-facing copy using review-checklist.md and interface-copy.md.
- Re-render after each material correction. Report the remaining risks with evidence.
Design Cluster
Review preserves the direction set by designing-interfaces. Route implementation fixes to improving-web-interfaces, performance findings to optimizing-react-interfaces, repeated patterns to extracting-design-systems, and behavior or visual regressions to testing-web-interfaces.
References
- Review checklist
- Shadscan audit