In the Skill's Own Terms
Covers the whole PowerPoint surface for coding agents: reading an existing deck's text with markitdown, editing template-based decks through XML workflows, and building decks from scratch with PptxGenJS.
The from-scratch path is a seven-step workflow — gather requirements, pick a palette and font pairing, choose a Sharp, Soft, Rounded or Pill style, classify every slide as one of five page types, generate one synchronous JS module per slide, compile through slides/compile.js, then run the required QA pass. A mandatory theme contract of five exact keys keeps slides consistent, the canvas is 10 by 5.625 inches, and every slide except the cover carries a page number badge.
What it produces
- One complete, runnable JS file per slide, each exporting createSlide and slideConfig.
- A slides/compile.js script that requires every slide module and writes the assembled presentation.
- The finished deck at slides/output/.
- A per-slide preview PPTX, written under a slide-specific file name when a module is run on its own.
How It Works
- 01Read the Source Deck First
When a presentation already exists, extract its text before touching layout, so the agent is working from real content rather than guesses.
- 02Choose Palette, Fonts and Design Style
The design-system reference supplies color palettes, font pairings, style recipes (Sharp, Soft, Rounded, Pill) and typography spacing, all chosen to match the topic and audience.
- 03Plan the Outline by Page Type
Every slide must be classified as exactly one of the five page types, with content and layout planned per slide so layouts do not repeat.
- 04Write One JS Module per Slide
Slide files live in the slides directory, each exporting a synchronous createSlide(pres, theme) function; up to five can be farmed out to subagents.
- 05Compile the Modules into One Deck
A compile script requires every slide module, applies the shared theme object, and writes the finished file.
- 06Run the Required QA Pass
Step 7 of the workflow is mandatory and points at the QA process and PptxGenJS pitfalls checklist.