cupertino-backwardslisted

Work backwards from customer experience to technology. Never accept the literal feature request as the destination — the destination is the experience, and technology is only ever a means to it. ## Steps 1. **State the literal request** exactly as given, verbatim or near-verbatim. 2. **State the underlying problem** — the actual friction or desire this request is trying to resolve for a person, independent of any implementation. If the literal request and the underlying problem turn out to be identical (the request already is the problem, with nothing lost in translation), say so explicitly rather than manufacturing a distinction. 3. **Write the customer experience statement**: exactly one sentence, in plain human language, describing what the experience should feel like. It must contain **zero technology nouns** — no database, framework, API, widget, button, screen, endpoint, component, or similar. If you catch yourself reaching for one, the sentence has already smuggled in a technology answer; rewrite it in terms of what the person does or feels instead. 4. **Validate mechanically** — do not eyeball this. Run: ```bash echo '{"statement": "<your one-sentence statement>"}' | python3 "${CLAUDE_PLUGIN_ROOT}/scripts/validators.py" zero-tech-nouns ``` If it exits non-zero, the statement failed and lists which words tripped it — rewrite the sentence, don't argue with the checker. 5. **Choose a technology direction** only now, after the experience statement passes. Ex