deck-design-ppt
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 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add appautomaton/presentation --skill deck-design-ppt技能说明
name: deck-design-ppt description: > 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.
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
.pptxfile 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 styles are defaults, not constraints.
Storyboard intake (from consultant skill)
When the input is a storyboard artifact (from the consultant skill), the brief extraction is already done. Map directly:
| Storyboard field | deck-design-ppt step |
|---|---|
| Firm overlay | Style (Phase 1, step 2) |
| Density level | Density (Phase 1, step 3) |
| Per-slide content description | Data-shape extraction (Phase 1, step 5) + pattern routing (step 6) |
| Structured data | Build script data objects (Phase 2, step 8) |
Skip Phase 1 step 1 (the brief extraction is already done). Steps 5–6 still run here: the storyboard deliberately describes WHAT each slide must prove (the comparison, decomposition, or evaluation), never chart types or data shapes. Deriving the shape from the content description and routing it to a pattern is this skill's job.
Identity intake (from brand-system skill)
If an identity.js produced by the brand-system skill exists in the working directory, the visual identity decisions are already made. Skip Style Routing. Register the identity as a theme in the build script instead:
const { createDeck } = require('<this-skill>/masters');
const { THEMES } = require('<this-skill>/masters/theme');
const brand = require('./identity');
const hex = c => c.replace('#', ''); // themes use bare hex, identity.js uses #-prefixed
THEMES[brand.palette.name] = {
name: brand.firm?.name || brand.palette.name,
accent: hex(brand.palette.accent),
canvas: hex(brand.palette.surface),
mist: hex(brand.palette.surfaceMuted),
midnight: hex(brand.palette.surfaceDark),
text: hex(brand.palette.text),
textSec: hex(brand.palette.textMuted),
textFine: hex(brand.palette.textFine),
border: hex(brand.palette.accentLight),
positive: hex(brand.palette.positive),
caution: hex(brand.palette.warning),
negative: hex(brand.palette.negative),
font: brand.fonts.body.family,
fontDisplay: brand.fonts.heading.family,
headerBar: brand.style === 'institutional' || brand.style === 'data-forward',
darkMode: brand.style === 'dark',
};
createDeck(brand.palette.name, slides, 'deck.pptx');
Two caveats:
- Fonts: PPTX embeds no fonts. The theme font renders only if installed on the viewer's machine. For unusual identity fonts, fall back to the stack's system font rather than risking substitution.
- Style direction:
brand.styleshapes composition, not just chrome.institutional/data-forwardlean on C-series density,modern/bentoon card-heavy P-series,darkon full-bleedsequoia-like treatment,editorialon typography-led patterns over charts.
Pattern library (21 communication patterns)
| Tier | Namespace | What it answers | Use when |
|---|---|---|---|
| Tier 1 | P-series (p01 … p15) | "What communication move is this slide making?" | All decks |
| Tier 2 | C-series (c01 … c06) | "What dense consulting composition does this slide require?" | MBB-style engagement deliverables |
All patterns work across all 5 styles. The palette controls the visual identity, not the pattern.
Patterns are reference implementations, not constraints. Use them when they fit the content. When a slide needs a layout that no pattern covers, build custom using pptxgenjs directly. The grid constants, theme tokens, and slide master chrome still apply. The pattern library is a starting vocabulary, not a ceiling.
How To Generate A Deck (Algorithm)
Phase 1: Understand
- Analyze the brief. Extract signals from The brief. Research what the brief references: web search for market data, benchmarks, competitors. User-provided data is the primary source.
- Pick style:
consulting-mckinsey/consulting-bcg/consulting-bain/founder/sequoia. See Style Routing. - Pick density level. See Density Profiles.
- Load firm reference (consulting decks only). See Firm Style.
- Extract data shapes (table, timeline, bridge, grid ratings, etc.).
- Route each slide to a pattern using the [Routing Table