do-presentation

# Make a Presentation Produce a polished slide deck the audience actually understands: researched from the codebase, structured for the audience (educational or client-facing), themed to the repo's design system, and exported via Marp to PDF/HTML (PPTX on request). Success is judged at Step 10's verify checklist — exports exist, slide count matches plan, every review flag addressed. ## Repo Context Probe If `.claude/skill-context/do-presentation.md` exists, read it and honor its declarations; otherwise use the generic defaults described below. The static-deck flow (research → structure → theme → diagrams → Marp export) is fully generic — it needs only `npx`/Marp and `curl`, no repo-specific tooling. The context file declares one optional capability: the **narrated `--video` mode** and the repo-provided CLI that powers it. When the file is absent (the common case in a foreign repo), the static deck (PDF/HTML/PPTX) is the deliverable and `--video` is unavailable. ## When to load sub-files | Sub-file | Load when... | |----------|-------------| | `CONTENT_GUIDE.md` | Structuring slide content — educational best practices, slide types, pacing | | `THEME_DETECTION.md` | Building the Marp CSS theme — how to find and adapt the repo's design system | ## Quick start The topic comes from `$ARGUMENTS`. If empty, ask the user what to present on. ### Step 1: Scope the topic Determine what the presentation covers: - A single feature? A system overview? A concept explanation? - Who...