# customer lens

A second kickoff interview: who is this actually for? Verification then runs as that specific person, never a generic user.

## What it is
Alongside the taste interview, a second interview at kickoff pins down the target customer — their device, patience, vocabulary, and what makes them bounce. The answers live in the project's agent instructions as a persona block.

## Why
A walkthrough as “some user” passes things the real audience would bounce off. Every time I skipped this, verification checked the spec instead of the person — and the spec is not who shows up. Naming the customer once makes every later check concrete.

## How Andrew uses it
Every check of user-facing work runs as that persona: can they find the thing, does the copy read in their register, would anything confuse or lose them. A verification that judges as 'some user' passes work the real customer would bounce off — so the persona block gets pasted into every review prompt, including the adversarial ones.

## How to get it
The whole method is downloadable and adaptable — `skills/customer-lens-kickoff/SKILL.md` and `method/steps/customer-lens.md` inside the zip. Drop the skill into `~/.claude/skills/` and it fires at project and feature kickoffs.

_Distilled from: ~/.claude/skills/customer-lens-kickoff/SKILL.md_
