What problem does it solve? Turning a spec, report, changelog, or thread into a slide deck usually produces a table of contents with a background — one slide per heading, bullets everywhere. This Skill forces the deck to be an argument: a stated conclusion, the claims that carry it, and one deliberate visual composition per claim, rendered on a fixed house design system. ## Core Features & Use Cases - Argument-first structure: Derives a one-sentence conclusion and 3–7 ordered claims from the source before any layout decision, with every slide title written as a declarative assertion rather than a label. - Composition routing: Maps each claim's evidence to a composition family (lane, graph, band, matrix, plot, chart, statement, table) instead of defaulting to bullet lists. - Deterministic HTML output: Scaffolds a deck from the bundled deck-chassis.html asset, fills one slide per exact-string edit, and writes a single self-contained file to decks/YYYY-MM-DD-<slug>.html. - Built-in self-QA: Ships a ?qa panel plus manual checks covering overflow, contrast, figure accessibility, title quality, and print/PDF fidelity. - Use Case: Paste a design doc and ask for a projected deck for an engineering review; the Skill reads the source, extracts the argument, chooses compositions, and emits a finished HTML deck you open in a browser. ## Quick Start Turn the attached design doc into a 10-slide projected deck for an engineering audience using the zz-deck skill.