Imagegen PPT Workflow

Problem

Generating .pptx decks directly with a model often produces unstable text boxes, shapes, and layouts. The result can feel like a document rather than a presentation. imagegen-ppt-workflow defines the final deliverable as image-based slides: each final slide is a complete PNG, while the .pptx file is only an ordered container for those rendered images.

How It Works And Where It Fits

The skill follows four phases:

• Planning: extract the deck goal, audience, page count, and layout anchors from papers, reports, outlines, or speaker notes, then write slides_plan.md.
• Preview and confirmation: use $imagegen to create a cover, chapter divider, or body-slide style preview, then generate a low-fidelity whole-deck overview to check rhythm, density, and visual consistency.
• Final generation: produce full-page slide images in order, such as final_slides/slide-01.png, keeping typography, spacing, color, and chart style consistent.
• Packaging: place the approved PNG slides onto full-slide blank layouts with scripts/images_to_pptx.py, producing *-images-only.pptx.

It fits scenarios that need strong visual cohesion, such as thesis defenses, research reports, product pitches, and class talks. Note that it does not prioritize editable text boxes, nor does it rely on HTML screenshots or code-drawn layouts as the main output path. Dense Chinese copy should be compressed into titles, cards, or short phrases to preserve generation fidelity.