frontend-verifylisted

# Frontend Verify — Look At It, Then Fix It A frontend change that passed unit tests and was never opened in a browser is unverified. This closes that loop: **capture → review → fix → re-capture** until clean. **Use the CLI, not the MCP.** Playwright CLI writes screenshots and accessibility snapshots to disk and lets you read only what you need. The MCP streams them into context — roughly 4× the tokens for the same task. Claude Code has filesystem access, so the CLI is the right tool. See `references/setup.md` if it isn't installed. ## Step 1: Scope **URL given?** Use it. **No URL, on a feature branch?** Diff-aware mode: ```bash ~/.claude/skills/frontend-verify/scripts/changed-routes.sh ``` It reports what changed and where this project keeps its routing — **it does not map files to URLs.** That mapping is framework-specific, and a hardcoded ruleset is silently wrong for the framework nobody listed: a bad pattern yields an empty list that reads like "nothing changed". Read the routing config it points at and map it yourself. If shared code changed, route mapping cannot see its reach — a button edit touches every page that renders it. Pick the highest-traffic routes that use it and say that is what you covered. Confirm the list before capturing. Wrong routes means a clean report on pages nobody touched, which is worse than no report. **No URL, on the default branch?** Ask which page. Do not guess. ## Step 2: Get the app running ```bash ~/.claude/skills/frontend-ver