reviewlisted

# vischeck:review Tests, typecheck and code review all pass green on a misaligned row, a bar that stops 12px short, a card clipped behind a fixed player, a desktop screen nobody ever screenshotted. Every one of those is obvious the moment a capture is in front of you at full size. The failure mode is not an inability to notice — it is not capturing, and not looking. This skill is the review discipline: a matrix that guarantees coverage, a measurement pass that computes what shouldn't be eyeballed, a ledger that proves what was reviewed, and a report a fix agent can act on without asking questions. `vischeck:verify` is the fast everyday pass after one edit. Use this skill when the change is bigger than that, or when the user asks for a visual review. ## When to run Run after implementing or changing non-trivial product UI, **before** reporting it done. Also run whenever the user explicitly asks for a visual review — that request overrides every exclusion below. A change to a shared component (a card, a list row, a header) means reviewing **every screen that renders it**, not just the one that motivated the change. An implementation subagent that verified with tests has not done this. Do **not** run the full workflow for a one-line tweak, or for throwaway artefacts whose purpose is thinking rather than presentation — an architecture diagram, an internal HTML explainer, a planning page. Those get a render smoke-check: open one view, confirm it renders, check for catastrop