# vision + customer pass

Any verification of UI is incomplete until it includes looking at the render AND walking the flow as the bound target customer.

## What it is
A structural rule about verification itself: any check of something that renders UI is incomplete until it includes two passes — eyes on the rendered surface, and a walkthrough as the project's bound target customer. Tests and DOM checks verify the implementation; these two verify what a person actually experiences.

## Why
Tests verify the implementation; neither of them experiences the page. An element can pass every check and still be occluded, illegible, or confusing — failures only visible to eyes on the render and a walk-through as the person it's for.

## How Andrew uses it
The rule binds at authoring time — a verification plan, a workflow verify stage, or a QA gate that omits either pass is malformed and gets fixed before it runs. The customer pass runs as the specific persona recorded at kickoff: their device, their patience, their vocabulary.

## How to get it
The whole method is downloadable and adaptable — `rules/vision-plus-customer-pass.md` inside the zip.

_Distilled from: ~/.claude/CLAUDE.md § Vision + customer pass on every verification_
