demo-presentation-architectlisted

# Demo Presentation Architect Design and refine **slide-deck specifications** as a markdown document. Each slide is described by its layout (from a fixed catalog) and its exact text content. This skill never produces HTML, PDF, or PPTX — only the `.md` source another tool (or designer) will consume. Layout catalog in [LAYOUTS.md](LAYOUTS.md); slide-spec template, anti-patterns, and review checklist in [RECIPES.md](RECIPES.md). ## 1. Scope boundaries - **Output is always one `.md` file.** No HTML, PDF, PPTX, image generation, or styling code. If the user asks for a rendered deck, refuse and offer the `.md` instead. - **Pairs with — but is distinct from — [[demo-script-architect]].** This skill defines what the audience *sees on each slide*; the script skill defines what the presenter *says*. Both can be produced for the same demo, but they are separate deliverables. - **Visual exemplar.** A reference HTML deck in this skill folder demonstrates how the layouts look when rendered. The skill never reproduces or regenerates that HTML — it only mines layout *shapes* from it. The full layout catalog and design conventions live in [LAYOUTS.md](LAYOUTS.md). ## 2. Interview-first protocol **Never start writing the deck without finishing the interview.** Ask in order; wait for each answer: 1. **Language.** "Which language should the deck be written in?" Every piece of slide text — titles, bullets, captions, speaker notes — must be in this language. Do not mix languages unless the