visual-verificationlisted
Install: claude install-skill tomerhayundev/skills
# Visual Verification
## Overview
**Confirming the code is not confirming the output. And looking the part is not working.**
You may NOT call work done, correct, good, or ready, or approve / hand it off, until you have observed the **actual end-user-facing result** as the user experiences it, **exercised its behavior**, and judged it good against the goal. Reading the source never counts. A screenshot proves layout; only *using* the feature proves it works: a flawless-looking button with a dead handler is pixel-identical to a working one.
**Violating the letter of this rule violates its spirit.** "I can tell from the code" and "it looks right, so it works" are the exact judgments this skill exists to override.
## When to Use
Every time you are about to call an output done/good/ready, approve it, or hand it off, whenever it has a surface distinct from its source: a page, running program, opened document, generated media, command output, or delivered text. Not for a plain chat answer (already visible); yes for every artifact you produce or modify.
## What Actually Counts (this turn)
| Output | Required |
|---|---|
| UI / web page / component | A **screenshot** of the rendered result, **and if it does anything, use it** (next row). |
| Interactive feature / button / form / link / flow | **Perform the real user action end-to-end and watch the result occur**: click fires, form submits, data changes, right state shows. Check console/network for errors. "Wired up" ≠ works. |