What problem does it solve? After building or modifying a frontend surface, it is hard to systematically catch visual regressions, accessibility gaps, broken responsive layouts, and missing interaction states before users do. This Skill provides a structured review process that inspects the rendered application in the browser rather than relying on code reading alone. ## Core Features & Use Cases - Visual Evidence Capture: Runs the app and captures screenshots at desktop (1280px), tablet (768px), and mobile (375px) widths, plus key interaction states, stored under .local/artifacts/. - Structured Review Checklist: Covers visual hierarchy, layout and responsiveness, accessibility and keyboard interaction, design-system consistency, content states, and performance-sensitive UI patterns. - Severity-Ranked Reporting: Reports findings as Must fix, Should fix, or Could improve, each with code paths, screenshot references, and concrete fix directions. - Use Case: After implementing a new settings page, ask for a UI review to get screenshots across breakpoints, an audit of form error and loading states, and a prioritized list of issues such as missing focus indicators or mobile overflow. ## Quick Start Review the UI of the page I just built and give me a prioritized list of design, accessibility, and responsiveness issues with screenshots.
