canon-screencastlisted

# Canon screencast ## Guards - If no topic is provided, stop: `❌ No screencast topic. Describe what you are recording.` - Draft, then hand off. Do not edit video or generate captions, and do not drive the application. A recording is another skill's job rather than something forbidden: write the draft, name `canon-record` as the next step, and stop. - Stack-agnostic in the draft. Never name a recording tool, an editing tool, a font, or a window manager. Keep selectors, URLs, wait conditions, and timings out of the beats too, since those four are exactly what the compiler adds in a plan of its own. A beat carrying them stops being a document a person can read and edit down. ## Step 1: read the project context Read these in parallel from the project root, skipping any that do not exist: - `CLAUDE.md`: behavior rules and project pitch - `.claude/REQUIREMENTS.md`: feature scope, non-goals, audience hints - `.canon/tasks/index.md`: current scope - Recent commits via `git log --oneline -20 2>/dev/null || echo "FALLBACK"`: what shipped recently is usually the recording subject. ## Step 2: discovery with proposed defaults Ask exactly four questions in chat. Each carries a proposed default derived from Step 1. The user confirms, overrides, or says "use defaults" to accept all. ```markdown **Discovery:** 1. Audience: proposing technical peers. Override? 2. Length: proposing 75-90s. Override? 3. Hero moment: proposing <best guess from context, or "the single thing that has to la