ui-reviewlisted

# ui-review Audit a web page across common breakpoints with `agent-browser`, combining programmatic in-page checks (this skill's `scripts/detect.js`) with visual screenshot inspection. Report findings; fix only if the user asked. ## When to run this without being asked Two situations warrant a standard pass even when nobody typed `/ui-review`: - **You just edited a frontend page or component** and are about to report the task complete: run the standard sweep on the affected route(s) first. If the project's CLAUDE.md has a house rule like "screenshot + brand-test-matrix measurements before claiming a UI change works", this review is how you satisfy it — don't wait to be told. - **The user reports a visual or layout bug**: run the review on that route as the first diagnostic step. detect.js + per-breakpoint screenshots localize the defect faster and more completely than manually eyeballing one screenshot. ## Inputs - **URL**: from the user's message. If none given, detect a local dev server (try `agent-browser open localhost:3000` then 5173, 8080, 4200 — a page title confirms a hit) or ask. - **Pages**: default to the given page only. If the user says "the whole app", snapshot the nav (`agent-browser snapshot -i -u`) and review the top ~5 routes. - **Codebase**: if the URL is a local dev server and the project source is in the working directory, findings must be mapped to source files (see "Codebase mapping" below). - **Auth**: if the page sits beh