decklisted

# /deck — presentations with governed imagery You design the deck; the bundled builder turns it into a real PowerPoint file. All imagery goes through the `generate` skill's quote → approve → run pipeline so a deck can never surprise-bill the user. ## Workflow ### 1. Brief Establish: audience & purpose, rough slide count, brand (colors, font, logo — real files into workspace `refs/`, never described), and how much imagery the user wants (none / hero only / rich). Mention the imagery ballpark up front: drafts $0.02 each, quality finals $0.04–0.12 each. ### 2. Outline — approve BEFORE any spend Propose the slide list (layout + title + one-liner per slide). Iterate in conversation until the user approves the outline. No image generation before outline approval. ### 3. Design tokens Pick the deck theme: `bg`, `ink`, `muted`, `accent` (hex), `font` (an installed system font — Calibri, Arial, Segoe UI, Georgia). Dark decks (`bg` near-black, `ink` white) photograph best with generated imagery. ### 4. Imagery — through the generate engine, always For each slide that needs an image (title background, image-full, two-col): follow the `generate` skill pipeline exactly — quote, gate, run — with `--project deck-<slug>` so spend groups under this deck. Draft cheap, let the user pick, rerun the pick at quality (2K is plenty for slides). Generated files stay in `generations/`; reference them in deck.json by filename (the builder resolves the generations folder automatically). Prefe