Pick the right slide workflow before your agent starts making slides.
Quick Start • Why • Routes • Screenshots • Docs
Important
Most AI slide failures are workflow failures.
Agents often jump straight to "make a PPTX." That is too early. Real slide work moves through story, evidence, visual direction, editable source, render QA, and final delivery.
ai-native-slides is a small meta-skill that tells the agent which representation to use at each stage.
Tell your coding agent:
Install AI Native Slides from https://github.com/OpenClaudex/ai-native-slides and use it whenever I ask for slide creation, migration, route selection, image-first visual drafts, editable rebuilds, or render QA.
The agent entry point is SKILL.md.
Use this when you need a deck that survives real iteration, not just a one-shot export.
- 🧭 Choose the route before overcommitting to PPTX.
- 🧱 Shape messy material into a claim spine and talk track.
- 🖼️ Separate preview from source so image-first slides are not called editable.
- ✅ Check the render before calling the deck done.
Without this skill: "generate slides"
With this skill: "choose the right representation for this stage"
| Route | Use When | Watch Out |
|---|---|---|
Feishu Docs + lark-cli |
Story, notes, evidence, assets are still moving | Not ideal as the live deck |
Slidev |
Technical deck, web preview, Git-friendly editing | Needs layout tuning |
Beamer |
Academic / PDF-first talk | Weak fit for visual-heavy pitches |
GPT-image -> image-first |
Fast visual direction and moodboards | Text is baked into pixels |
editable PPTX rebuild |
Final PowerPoint handoff | Slower, but maintainable |
PPTX / OpenXML |
Final compatibility | Heavy for early iteration |
Real route outputs generated for this repo. Source examples live in docs/examples/real.
The Feishu Docs + lark-cli panel is a real Feishu document page created through lark-cli; the redacted CLI transcript is kept as reproduction evidence. The other panels are real exports from Slidev, Beamer, GPT-image, PPTX, and OpenXML tooling.
- One-shot deck hallucination before the argument is clear.
- Calling image slides "editable."
- Choosing PPTX too early and fighting XML/layout mechanics.
- Turning an interview pitch into a dense project inventory.
- Shipping without render QA.