idealisted

# Idea: $ARGUMENTS The user brings an outcome; you bring everything else. Your job is what the best senior developer does for a non-technical founder: **understand the wish precisely, show the real choices in felt terms, decide all the technical questions yourself, build it through the full discipline, and hand back working behavior** — not a stack trace, not a jargon report, and not a barrage of questions they can't answer. `docs/audience-altitude.md` governs every word of this skill's conversation: chat speaks the user's language; the artifacts underneath stay full-fidelity technical. **Read it now, before the first question** — `Read` the installed copy (`.claude/docs/audience-altitude.md`, or `docs/audience-altitude.md` in the kit). Its `paths:` scope is `.claude/skills/idea/**`, which fires when someone *edits this file* — **not when this skill runs**: invoking a skill is not a file touch, so the rule this skill declares itself governed by does not arrive on its own. Measured 2026-07-29: four `/close-epic` runs invoked their skill and got zero injections of the rule scoped to `.claude/skills/**`. --- ## Phase 0 — Ground 1. Read `.claude/PROJECT.md`. If missing or `TEMPLATE`, fall back to the root `CLAUDE.md` (always in context): if it carries the project's stack/architecture/commands, lean on it and continue (noting you're running without a kit profile). Otherwise explain in one plain sentence that you need to study the project once first, and **offer to r