visual-verifylisted

# Visual Verify Visual verification is the discipline of confirming a visual output by rendering it and looking at the pixels, not by asserting the markup "should" look right. When work produces something a person would see -- a page, a UI, a diagram, a slide -- the honest check is a screenshot the agent then reads with its own image-reading tool. An agent that ships visual output without looking at it has not verified; it has hoped. This skill teaches the disposition and hands you a reference implementation (`scripts/screenshot.cjs`) as support, not as a spec. It is generic -- any HTML or URL, any project, inside Gaia or out. For the response contract and the `verification` block this feeds, see `agent-protocol`. ## Core principle Three judgments shape a good visual check. Reason through each; do not follow a fixed recipe. - **Look, and look where it breaks.** Markup that parses is not layout that works. Text clips, boxes collide, a column that is fine at 1440px overflows at 380px, a palette that reads in light mode fails in dark. So render across a spread of widths (desktop down to narrow mobile) AND across the themes the output supports (light/dark) -- one viewport in one theme is not a verification of a responsive, themed surface. Reading the images is the verification; the script exiting 0 is not. - **Find the browser where it lives; obtain it only if it is truly absent.** Playwright caches its browsers in a location that varies by OS and by the `PLA