deck-design-pdf
Create presentation decks as high-fidelity PDF files using web technology (HTML, CSS, Tailwind, Font Awesome). Use when the user wants a polished, pixel-perfect deck with responsive layouts, rich typography, icons, and modern design. For editable PPTX output, use deck-design-ppt instead.
appautomaton · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add appautomaton/presentation --skill deck-design-pdf技能说明
name: deck-design-pdf description: > Create presentation decks as high-fidelity PDF files using web technology (HTML, CSS, Tailwind, Font Awesome). Use when the user wants a polished, pixel-perfect deck with responsive layouts, rich typography, icons, and modern design. For editable PPTX output, use deck-design-ppt instead.
Deck Design PDF: Operational Playbook
What This Skill Does
- Input: a deck brief + any structured data the user provides.
- Output: a PDF file: pixel-perfect slides rendered from HTML/CSS via Playwright. Not editable in PowerPoint. This is the high-fidelity, print-ready format.
When to use this vs deck-design-ppt
| Need | Skill |
|---|---|
| Editable slides (PowerPoint/Keynote/Slides) | deck-design-ppt |
| Pixel-perfect PDF: web typography, icons, gradients, CSS layouts | deck-design-pdf (this) |
What the web stack unlocks (beyond pptx)
- CSS Grid and Flexbox: responsive layouts instead of coordinate math
- Google Fonts with optical sizing and variable weights
- Font Awesome 6 icons inline with text
- Gradient backgrounds, box shadows, rounded corners, opacity
- ECharts 6 (SVG renderer): 21 chart types, including bar, line, pie, scatter, waterfall, gauge, sankey, treemap, radar, funnel, and heatmap
- Tailwind utility classes: rapid, consistent styling
Phase 1: Understand and Route
1. Read the room
Before asking the user anything, scan the working directory for artifacts that establish context: briefs, consultant storyboards (*-ghost.md, *-outline.md), data files, brand specs, existing build scripts. Read what's there and form a working hypothesis about what this deck needs: objective, audience, tone, density, and data.
Then ask only for what's genuinely ambiguous and would change the deck's argument or audience calibration. Frame questions as choices, not open fields: "The data suggests a Bain decision-first structure. Does that fit, or is this more of an internal working session?" One sharp question beats five vague ones. Maximum 1–3 questions, and zero is fine if the artifacts are clear.
2. Classify the deck
This determines how deep the planning phase goes. Two paths:
| Signal | Path | What happens next |
|---|---|---|
| MBB engagement, strategy consulting, due diligence, cost transformation, M&A, pricing, org restructuring | Consulting | Load the full consulting reference library (ghost-deck.md, engagement-archetypes.md, skeletons/, firm-dna.md, evidence-recipes.md, density-adaptation.md). Build a rigorous ghost deck with archetype classification, pillar architecture, transitions, and firm overlay. |
| Startup pitch, board update, product narrative, conference talk, investor roadshow, internal update | General | Stay in this playbook. Build a ghost deck using the universal quality gates below: governing thought, action titles, helicopter test, exhibit assignment. No archetype classification or skeleton required. |
Consultant handoff: if a storyboard from the consultant skill already exists (governing thought, pillars, action titles, content descriptions), the argument layer is done. Skip ghost deck construction entirely. Validate the argument (run the helicopter test on the titles), then proceed to the production outline.
3. Pick style and density
Style:
| If the deck is… | Palette | Surface | Font |
|---|---|---|---|
| Consulting / board / engagement deliverable | consulting-mckinsey | Light | Inter |
| Framework evaluation, process-transparent | consulting-bcg | Light | DM Sans |
| Diagnostic, decision support, facts-vs-perspectives | consulting-bain | Light | Source Sans 3 |
| Startup pitch / product narrative / growth story | founder | Light | Plus Jakarta Sans |
| Crisis / urgency / downturn memo / high-stakes | sequoia | Dark | Georgia + Inter |
| Warm, rigorous-but-human strategy work (Anthropic-adjacent ivory + clay) | anthropic-consulting | Light | Manrope (not vendored, load via headExtra) |
| Google-ecosystem client engagement (muted Google Blue) | meridian-google | Light | Inter |
The vendored font families are Inter, DM Sans, Plus Jakarta Sans, and Source Sans 3. The agent is not limited to these. Any Google Font can be loaded via a <link> tag in headExtra when the brief calls for a different typeface.
Brand identity intake (from brand-system skill): if an identity.js produced by the brand-system skill exists in the working directory, the style decision is already made. Do not route through the table above:
-
Palette:
identity.jsemits engine-compatible palette CSS. Write it into this skill's palette directory, then pass its name tocreateDeck:const fs = require('fs'); const brand = require('./identity'); fs.writeFileSync('<this-skill>/palettes/' + brand.palette.name + '.css', brand.toCSS()); // then: createDeck({ palette: brand.palette.name, ... }) -
Fonts: if
brand.fontsnames a family outside the vendored four, load it via a Google Fonts<link>inheadExtra(network required at build time) or accept the stack's system fallback. -
Style direction:
brand.styleroutes composition treatment, not colors:identity.jsstyleCompose like Treatment institutionalconsulting-mckinseyRestrained chrome, sharp corners, rules over boxes modernfounderCards, rounded corners, confident accent use darksequoiaDark surfaces as default, high-contrast accents bentofounderCard-grid compositions dominate, surface-muted tiles editorialnone Typography-led: oversized headings, fewer panels, whitespace as structure data-forwardconsulting-bcgChart-dense, panel mini-headers, minimal decoration
The identity's colors and fonts are authoritative. Layout and composition belong to this skill.
Density:
| Context | Level | What changes |
|---|---|---|
| Star |