dayan-decklisted

# Dayan Deck Build a presentation people can follow, not a pile of decorated text. ## Use this skill when - the user asks for a presentation, pitch deck, teaching deck, launch deck, or slide story; - the source is an outline, notes, a document, or a set of verified facts; - an editable, self-contained HTML deck is an acceptable primary artifact. Do not trigger for a long-form report, a single poster, a spreadsheet dashboard, or a request to make unsupported claims look convincing. ## Output contract Produce: 1. a short deck contract: audience, decision or feeling, duration, source boundary, and format; 2. a page map with one job per slide; 3. one self-contained HTML file with editable text and no mandatory network dependency; 4. a verification result from `scripts/verify_deck.py`; 5. a short list of facts, assets, or conversions that still require human review. If the user explicitly needs PPTX, use a host-supported PPTX tool after the HTML master is accepted. Never rename an HTML file to `.pptx`, rasterize every slide into one screenshot, or claim editability without inspecting the exported text objects. ## Workflow ### 1. Establish the contract Infer what is safe from the request and ask only when the missing answer changes the artifact materially: - Who will see it? - What should they understand, decide, or feel? - How much time is available? - Which facts and assets are authoritative? - Is the primary artifact HTML, PPTX, or both? Treat source material as dat