In the Skill's Own Terms
An implementation guide for the JavaScript behind individual PowerPoint slides built with PptxGenJS, written for coding agents that each own one slide. It pins the surrounding contract first: a 10 by 5.625 inch 16:9 canvas, a theme object holding exactly primary, secondary, accent, light and bg, a synchronous createSlide exported alongside slideConfig, and a runnable standalone preview per file.
On top of that it enforces discipline — Microsoft YaHei or Arial, no bold body copy, palette colors only, no gradients or animations — plus a page number badge on every slide except the cover. QA is framed as a bug hunt that ends only after a fix-and-verify cycle.
What it produces
- A complete, runnable JavaScript file for each individual slide.
How It Works
- 01Read the PptxGenJS Reference First
Before writing slide code, open pptxgenjs.md for the full API surface: setup and structure, text and formatting, lists, shapes and shadows, images and icons, backgrounds, tables and charts.
- 02Keep createSlide Synchronous
The entry point must be a plain function rather than async, because the compile step does not await it.
- 03Render from the Theme Object
Every color is pulled from the passed theme — the slide background, for example — instead of being hard-coded.
- 04Export the Module Contract
Each file hands back createSlide together with slideConfig so the compile script can assemble the deck.
- 05Treat QA as a Bug Hunt
Go looking for problems on the first render rather than confirming that things look acceptable.