PPT Master Guide

The Problem

When making slide decks, the usual failure is not “can pages be generated?” but weak organization: scattered material, unclear structure, inconsistent style. A prompt may only contain fragments or a keyword, while the output ends up as dense bullet lists, missing cover and agenda pages, wrong page count, or hard to deliver through WeChat or Feishu. This skill turns those upfront decisions into a workflow: clarify what to say, how to sequence it, and which visual language to use before handing the job to create-ppt.

How It Works

The skill acts as the planning layer for PPT production, coordinating with create-ppt rather than replacing image generation:

• Source analysis: If the user provides PDF, DOC, PPT, TXT, or images, it extracts concepts, frameworks, data, examples, and logic. If only a topic is given, it searches authoritative material to fill gaps.
• Structure planning: It sets page counts by deck type and requires a cover, agenda, content pages, and closing page, with one core idea per page.
• Style selection: It maps scenarios to codes such as style_A_infographic, style_D_cartoon, or style_E_handdrawn, defaulting to the generic blue-white style when uncertain.
• Copy drafting: It produces page titles, points, data, and closing lines, avoiding hollow headings and stacked bullet points.
• Delivery checks: It passes channel, style code, and page content to create-ppt, then validates pptx output, cover, agenda, page count, and style consistency.

Boundaries and Notes

This skill fits workflows where content planning and generation execution should be separated, especially enterprise reports, training decks, policy briefings, and product introductions. If the goal is a single poster, freeform layout, or highly custom visual design, the emphasis should shift to create-ppt's styling capabilities. The value here is constraining content quality, structure, and channel parameters early, reducing rework after generation.