About this skill

Problem

Enterprise solution decks often fail less on single-slide aesthetics and more on process control: context is not fully gathered before design, page plans drift, bulk generation produces inconsistent title bars, visible slide text leaks prompt fields or draft notes, 2K output is mistaken for 4K finals, and PPTX files retain text boxes, placeholders, or page numbers.

How It Works

The skill turns PPT production into a checkable workflow:
- Intake: confirm project name, root directory, topic, audience, version, deliverables, and source materials; ask when fields are missing
- Storyline: draft background, positioning, architecture, capabilities, scenarios, value, and implementation path, then convert it into a page plan
- Sample Gate: generate 3-5 sample pages before bulk work to lock the title bar, typography, layout, and visual style
- Batch Control: use gpt-image-2 to produce full-page PNGs, with 2K/4K failure handling that avoids hollowed-out slides or blind retries
- Repair & Packaging: repair local issues with image edits, composite only the affected region, and build PPTX only after confirmation, checking slide count, order, and full-image pages

Boundaries

It fits engineers or presales teams with clear business materials who need stable solution-page output; it does not invent key business facts and does not replace brand rules, legal review, or final human acceptance.

Screenshots

Use Cases

Presales engineers turn meeting notes and old decks into enterprise PPT pages with a consistent title bar.
Solution architects convert background, architecture, and value into a storyline, then batch 16:9 PNG finals.
Delivery consultants sync scheme MD, PNG pages, and confirmed styles after customer material changes.
Engineers repair residual text or page numbers with image edits before packaging a reviewed PPTX.