PPT Master Document Assistant

Problem

When a user already has a document, web page, or long text but wants ppt-master to generate a deck, the raw material is often noisy: inconsistent headings, navigation or disclaimer text, scattered conclusions, weak page boundaries, and unclear chart intent. ppt-master must spend extra effort on decomposition, page splitting, and style inference, so unstable input leads to unstable output.

How It Works

PPT Master Document Assistant does not create the final presentation. It converts arbitrary input into a cleaner Markdown draft that ppt-master can consume more directly:

• Denoise: remove headers, footers, navigation, ads, and disclaimers while preserving headings, paragraphs, tables, and key numbers.
• Structure: normalize headings into H1–H3, using --- plus H2 as candidate slide boundaries.
• Extract conclusions: add one > blockquote core takeaway after each H2 to reduce later scanning for the bottom line.
• Compress bullets: condense paragraphs into 3–5 short bullets, preferably under 20 characters each.
• Surface tables and visual hints: convert comparisons, metrics, and workflows into Markdown tables, and add chart suggestions at the end of relevant sections.
• Prefill YAML: infer fields such as ppt-audience, ppt-goal, ppt-mode, ppt-style, and ppt-palette to form a design contract for ppt-master.

The workflow is ordered: read input, denoise, refine, generate YAML, assemble output, then present the YAML inference and wait for user confirmation before writing slide-source.md.

Boundaries

It is best for turning existing material into a PPT source draft. It does not invent business viewpoints, add missing evidence, or change the original meaning. If the source lacks a clear audience, goal, or conclusion, the user should correct the YAML and page-level claims during the confirmation step.