verifylisted

# vischeck:verify Use the `screenshot` CLI to visually verify UI changes against a running dev server. Always Read the saved image after taking a screenshot — then **review it like a critical designer, not a rubber stamp.** This is the fast pass for one edit. When the change touches several screens, crosses a breakpoint, or lands in a shared component that renders in many places, invoke `Skill(vischeck:review)` instead — it builds a proper coverage matrix and a ledger to prove it. ## When to use After editing any view, template, component, or layout file: 1. Take a screenshot **with `--sweep`**, and Read the image 2. **Judge it against the rubric below — this is the point of the skill, not an afterthought** 3. For interactive elements (forms, buttons, inputs), also test the interaction with playwright-cli ## Measure first, then look Half of what goes wrong is arithmetic, and arithmetic done by eye is where a 12px error survives a confident "looks good". `--sweep` measures the rendered layout and hands you a short list of numbers, so your attention goes to what code can't judge: ```bash screenshot /signup --sweep # zero-config checks screenshot /signup --sweep --sweep-rows ".user-list" --sweep-align ".label" \ --sweep-content ".signup-form" # named intent → verdicts ``` It catches what a screenshot cannot show you: sub-44px tap targets, `overflow: hidden` swallowing text, a row that indents because it lacks an icon, a b