claude-screencastlisted

# Claude screencast ## Guards - If no topic is provided, stop: `❌ No screencast topic. Describe what you are recording.` - Do not record, edit video, or generate captions. Output the script and stop. - Stack-agnostic. Never name recording software, editing software, fonts, or window managers in the draft. ## 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 - `.claude/TASKS.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 land">. Override? 4. What to cut: proposing <best guess, or "anything that is not the hero moment">. Override? ``` Wait for answers before drafting. Do not infer silence as acceptance. ## Step 3: derive the slug Build a 2-to-4-word kebab-case slug from the topic and discovery answers. Examples: `auth-flow-redesign`, `cli-onboarding`, `inline-edit-launch`. ## Step 4: write th