Help us improve
Share bugs, ideas, or general feedback.
Builds 15-slide all-hands decks for company-wide meetings with balanced wins and candor. Inherits deck-builder pipeline for brand-native slides, financials, and Q&A placeholders.
npx claudepluginhub fluidform-ai/fluiddocs-deck-builder --plugin fluiddocs-deck-builderHow this skill is triggered — by the user, by Claude, or both
Slash command
/fluiddocs-deck-builder:deck-all-handsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Keep your process invisible.** Do not narrate the skill architecture (the "type pack" and "core" split) or announce which files you are reading. Skip preambles like "I'll start by reading...". Gather what you need, then build the deck.
Builds launch decks for product announcements and go-to-market moments. Uses a 12-slide template with demo slot, pricing section, and CTA.
Use when asked to design a pitch deck, presentation, or slide set. Examples: "design a pitch deck", "create a sales deck", "make a conference presentation", "build an investor deck", "help me present this to the board", "create slides for X".
Composes institutional committee decks (Investment, Valuation, Quarterly, Annual) from source-grounded model outputs, warehouse exhibits, and memo narrative, following brand conventions.
Share bugs, ideas, or general feedback.
deck-builder coreKeep your process invisible. Do not narrate the skill architecture (the "type pack" and "core" split) or announce which files you are reading. Skip preambles like "I'll start by reading...". Gather what you need, then build the deck.
This skill builds 15-slide all-hands decks for company-wide team meetings. It is a thin type pack that inherits the full pipeline from the deck-builder core skill. Read deck-builder/SKILL.md first for the 5-phase pipeline, 3-reviewer gate, fixed-canvas shell, brand-tokens methodology, and learnings log. This file only declares what's all-hands-specific.
References in references/:
content-spine.md, the canonical 15-slide all-hands spinevisual-components.md, per-slide brand-native patternsdemo-patterns.md, light demo recipes for product updates (optional; single moments only)Declarations the brief locks in for all-hands builds:
deck_type: all-handsTarget slide count: 15Catalog directory ($CATALOG): declared in the build brief (a folder the user picks for shipped examples)Forbidden class-name leaks: (empty)deck-builder corePipeline: deck-builder/SKILL.md, 5-phase Plan, Build, Review, Release, Learn; 3 reviewer gates (Brand, Copy, Layout).
Phase 1 artifact: deck-builder/references/build-brief-template.md, fill in deck_type: all-hands plus the other all-hands-specific fields listed above.
Phase 2 implementation:
deck-builder/references/shell-pattern.md, chrome-free nav shell + 1440x810 canvas scale + inline-edit moduledeck-builder/references/icon-library.md, inline SVG icon set replacing every emojideck-builder/references/brand-methodology.md, source-verify brand tokens protocol + logo safety + nested-subpath ruledeck-builder/references/style-presets.md, named aesthetic presets when the user has no brandBefore writing the full 15-slide deck, generate 3 first-slide HTML previews. Do not ask the user how to choose a style. Just generate three distinct visual directions (one safe preset, one bold preset, one wildcard from deck-builder/references/style-presets.md), save them to a .skill-temp/ folder, and open all 3 in the user's browser. Then ask "Which style do you want? A, B, C, or mix elements?"
Only after the user picks does the full Phase 2 build begin. The pattern matches the UX bar of a modern deck-builder skill. Show, don't ask.
Autonomous run exception: for autonomous runs without a user browser to open previews in, skip the visual preview step. Instead, document the preset choice (palette, typography, character) as a code block in the brief and proceed directly to full build. The user can iterate on the preset post-build via the inline-edit module if needed.
Phase 3 reviewer specs (all in deck-builder/reviewers/):
brand.md, copy.md, layout.mdPhase 5 learnings: deck-builder/references/learnings-log.md (shared; filter by Deck type = all-hands).
Phase 4 deliverable:
.html file at <CATALOG_DIR><Company>-Deck.html.<Company>-Brief.md.computer://... when the agent runs in an environment that resolves it).Do not write walls of explanation. The file is the deliverable.
Maintained by FluidDocs. Source: https://github.com/FluidForm-ai/fluiddocs-deck-builder. MIT licensed.