I’d rather write slides in Markdown. Text in Git, diffs I can read, no fiddling with text boxes. In a corporate environment, that rarely works. Marketing ships a PowerPoint template, the brand guidelines say every deck uses it, and the next person who edits my slides expects a .pptx they can click into. PPT Master closes that gap.
The Problem With Slides as Code in Corporate#
Tools like Marp, Slidev, and reveal.js are great as long as I’m the only one who touches the deck. They render HTML or PDF. Some can export to PowerPoint, but Marp, for example, renders each slide as an image by default. That’s a dead end in a company:
- A colleague wants to fix a typo and can’t, because the text is part of a picture.
- The deck doesn’t use the official slide master, so it fails the brand review.
- Charts are screenshots, so nobody can update the numbers before the board meeting.
What PPT Master Does Differently#
PPT Master is an open-source workflow (MIT) that runs inside an AI agent like Claude Code, Codex CLI, or Cursor. I hand it a source, for example a Markdown file or pasted text, and it produces a real PowerPoint file on my machine. Real means native objects: text boxes, shapes, connectors, tables, and data-backed charts. Click any element in PowerPoint and it behaves like something a human built. No flattened images.
The part that matters for corporate users: it works with existing templates. There are three routes.
Generate
Edit native PPTX
.pptx, such as the marketing template, with new content and keeps its design.Create template
This saves me hours of manual PowerPoint editing every month.
How I Use It#
PPT Master needs Python 3.10 or newer. Install it as a plugin in Claude Code:
# Inside Claude Code
/plugin marketplace add hugohe3/ppt-master
/plugin install ppt-master@ppt-masterThe plugin only ships the skill files. Install the Python dependencies from the installed location, or clone the repository instead:
git clone https://github.com/hugohe3/ppt-master.git
cd ppt-master
pip install -r requirements.txtThen I ask for a deck in plain language and point it at the corporate template:
Fill projects/brand/corporate-template.pptx with the content of talk.md.
Keep the slide master, 10 slides max.By default, the agent first confirms a design spec with me: template, format, page count. After that it analyzes the content, lays out each page, and exports the .pptx. If I want to skip the confirmation round trip, I ask for quick generation.
Limitations#
PPT Master is not a wishing well, and the README says so itself.
- The model sets the ceiling. The project recommends a large-context model plus AI image generation. A cheap model produces noticeably weaker decks.
- It costs tokens. Page-by-page design is expensive. The tool is free, the model usage is not.
- It’s not deterministic. Marp renders the same Markdown into the same slides every time. PPT Master is an agent, so two runs give two slightly different decks. The Markdown is under version control, the
.pptxis not really “as code.” - Expect polishing. The result is a strong first version, not a finished deck. Since everything is editable, the polishing happens in PowerPoint, where it belongs in a corporate setting anyway.




