deck-design-pptlisted

Create new presentation decks as native editable PPTX files with consulting-quality design. Use when the user wants to build a new slide deck, presentation, or pitch deck from a brief or topic. For editing existing .pptx files, use the pptx skill instead.
appautomaton/presentation · ★ 53 · Web & Frontend · score 73

Install: claude install-skill appautomaton/presentation

# Deck Design: Operational Playbook ## What This Skill Does - **Input:** a deck brief + any structured data the user has (tables, time series, bridges, evaluation criteria, etc.). - **Output:** a native **editable `.pptx`** file with slide masters, theme colors, and all content as PowerPoint-native objects (text boxes, shapes, charts). Every element is individually editable in PowerPoint. ### The brief The **brief** is everything the user provides about what they want. Before generating anything, extract these signals: | Signal | Examples | Defaults if absent | |---|---|---| | **Objective** | "pitch to Series A investors", "board strategy update", "SBIR Phase II proposal deck" | General presentation | | **Audience** | "DoD program managers", "VC partners", "internal team" | General professional | | **Brand identity** | Logo colors, company name, client palette | Palette defaults | | **Tone / firm style** | "McKinsey-style", "clean and modern", "urgent/high-stakes" | Infer from audience + objective | | **Density** | "dense and evidence-heavy", "keep it simple", specific L1/L2/L3 | Infer from audience + objective | | **Data** | Tables, metrics, timelines, comparisons, evaluations | None. Build from research or request more | Not every brief contains all signals. Extract what's there, infer what you can, and use defaults for the rest. Do not ask the user to fill out a checklist. If the user provides a custom palette, brand guide, or design spec, follow it. The built-in sty