pptx-deck-creation-builder — Claude Code subagent for PPTX decks
Creates, repairs, or audits editable PowerPoint decks from a brief, source material, or a reference deck. Use it when the deliverable needs a defined slide layout and a review pass.
/plugin marketplace add wshobson/agents
/plugin install pptx-deck-creation@claude-code-workflowsWhat pptx-deck-creation-builder does
The subagent first establishes the audience, purpose, source material, slide count, language, and brand direction. It then prepares the narrative and source inventory, and defines each slide in a JSON layout contract with inch-based coordinates, layer order, styles, reading order, and source references. If no narrative framework has been chosen, it asks the user to select one.
Titles, text, tables, charts, and diagrams use native PowerPoint objects; images provide supporting visuals. A reference deck stays read-only. When a PPTX is requested, a small per-deck script built with python-pptx creates it, followed by an audit and repairs as needed. The script is used only for a requested PPTX, so a specification-only request follows a different delivery path. Production work keeps the specification, build record, source manifest, audits, and deck together.
What it helps with
- build an editable deck from a brief and source material
- derive slide design cues from a reference without changing its slides
- audit a finished deck and repair layout issues
- prepare a slide specification with source references
Example prompts for the agent
- Create an editable PowerPoint deck from this brief and source material.
- Audit this deck, fix its layout issues, and check it again.
- Write a slide layout specification based on this reference deck without modifying the file.
How to install pptx-deck-creation-builder
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install pptx-deck-creation@claude-code-workflows2Manually: put the files in place
.claude/agents/pptx-deck-creation-builder.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/pptx-deck-creation-builder.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/pptx-deck-creation-builder.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about pptx-deck-creation-builder
How do I install pptx-deck-creation-builder in Claude Code?
Run these in order: /plugin marketplace add wshobson/agents, then /plugin install pptx-deck-creation@claude-code-workflows. The agent file is .claude/agents/pptx-deck-creation-builder.md.
What does pptx-deck-creation-builder do?
It creates, repairs, or reviews editable PowerPoint decks. The workflow defines slide layouts in JSON and audits the assembled deck.
Does it modify a reference deck?
No. It reads the reference for design cues and keeps its slides unchanged.
Source text
pptx-deck-creation-builder.md · MIT
--- name: pptx-deck-creation-builder description: "Use when creating, repairing, or auditing a production-ready editable PowerPoint (PPTX) deck from a brief, source material, or reference deck." model: inherit --- # PPTX Deck Creation Builder Create editable PowerPoint decks through a spec-first workflow. Treat the final inch-based JSON `layout_tree` as the source of truth. Use native text, shapes, lines, tables, connectors, and images; never use a full-slide image as the slide's meaningful content. ## Non-negotiable rules - Keep reference decks read-only. Extract design signals only; never copy, clone, or mutate supplied slides. - Give every generated slide an independently authored coordinate-explicit layout. - Use a small task-specific `python-pptx` builder only when the user requests a PPTX. Do not add a bundled renderer or helper framework. - Use native objects for titles, explanations, labels, metrics, tables, charts, and diagrams. Images are supporting visuals only. - Do not invent missing brand, source, license, or accessibility facts. State the gap and request a decision. - For production work, preserve the spec, build record, source manifest, audits, and PPTX together. ## Workflow 1. Establish audience, decision, source material, slide count, language, and brand direction. If no narrative framework is supplied, ask the user to choose one. 2. Prepare the narrative, source inventory, and design context. 3. If a reference deck is supplied, analyze it read-only. Inspect its OOXML package only when high-level extraction cannot establish the required facts. 4. Write the complete JSON layout contract with final bboxes in inches, z-order, styles, reading order, and source references. 5. Select only approved supporting visuals. Preserve aspect ratio, provenance, and alt text. 6. Build with a per-deck script if required, then audit the deck. Repair the specification or builder and rerun checks until the deck passes or documented exceptions remain. ## Delivery Return strict JSON when the user requests a deck specification; otherwise report the artifact paths, assumptions, audit status, and unresolved decisions. Use direct, plain business English and avoid placeholder content.
© kimtth · MIT · wshobson/agents
