presentation

Presentation skill

Build evolving-scene presentations: one shared diagrammatic canvas where entities morph across steps while captions and navigation guide the audience. Each presentation is a self-contained folder under src/presentations/<slug>/ that composes the reusable scene kit at src/presentation-kit/.

When to use

• User asks to create, build, or generate a presentation or talk
• User asks to modify, update, or add steps to an existing presentation
• Project lacks the scene kit or presentation infrastructure and needs bootstrapping
• User asks to update, resync, or pull the latest scene kit into a project whose vendored src/presentation-kit/ has fallen behind the skill (see Updating the vendored kit)

Procedure

Work through these phases in order. Do not skip self-verify.

1. Gather requirements

Ask one question at a time. Cover:

1. Topic — what the presentation is about
2. Visual style — accents, mood, density (sparse diagram vs. rich layout)
3. High-level sections — the major parts of the story, in order
4. Each step — after the sections are agreed, flesh them out one by one. A "step" means one navigable beat in the presentation: the caption/title plus the scene state shown for that moment.
5. Per-step visuals — which entities appear, how they relate, and what morphs between steps

Rules:

• Do not assume details the user can still provide
• Allow the user to proceed with partial detail and iterate later — no hard completeness gate
• Do not start by asking how long the talk should be or how many steps it should have. First establish the high-level sections, then expand each section into steps. Ask about length/count only after that structure exists, or when the user explicitly asks the agent to decide or fill in details.
• If the user says the length/count is TBD, accept that and continue by shaping the high-level sections before implementing any steps.
• Define skill-specific terms the first time they are used in user-facing conversation. For example: a "step" is one navigable beat of the talk; a "hero" entity is the main visual object that carries continuity across the scene. Do not front-load a glossary; define terms just before they matter.
• If the prompt already contains topic, style, and all step details, proceed to scaffold/generate without further questions
• For key or complex steps, optionally draw an ASCII mockup of the layout and ask the user to confirm before building. Use mockups selectively, not for every step