oh-my-ppt-layout

Oh My PPT Layout

This skill is the decision backbone for slide structure. Deep examples live in the references:

• references/catalog.md — canonical 1600×900 zone skeletons and named layout patterns (the structure-choice layer you pick from before writing HTML).
• references/layout.md — collision-avoidance code comparison and height-budget walkthroughs.
• references/checklist.md — P0/P1/P2 structural self-check.

When to use

• Creating a new slide or rewriting a whole slide
• Choosing a slide composition or layout intent (cover, data-focus, comparison, etc.)
• Repairing overflow, collision, or content exceeding the canvas

When not to use

• Tiny text/style edits that do not affect layout (color, wording, single element)

1. The per-page decision path

Before writing HTML, answer these in order. The first three decide the role and density; the rest decide structure and budget.

1. PPT message — what is the one sentence this page should make the audience remember within 3 seconds? Source material is evidence; the slide is an edited message.
2. Role — what is this slide? (cover / data exhibit / comparison / timeline / concept / process / summary / quote / image-focus)
3. Reading path — what does the audience see first → understand second → remember last?
4. Content shape — which source facts support the message, which can be grouped, and which becomes compact secondary detail? A slide is a designed argument, not a document dump.
   • If the page feels over-dense or would exceed 1600×900, pause before writing HTML and self-summarize: one message + a content-appropriate set of support groups/evidence rails. Only place that distilled structure on the slide; merge minor facts into labels, notes, annotations, or omitted speaker-context.
5. Density — low (one hero or primary visual with limited support), medium (main + 1–2 support), or high (grid/table/matrix only when the content truly demands it)?
6. Pattern + skeleton — use a named layout pattern from references/catalog.md when it clarifies the reading path or solves a known density risk; if the page risks becoming top-heavy, a canonical 1600×900 zone skeleton is a useful starting point. These are references, not a closed menu: create a fresh composition when the page thesis or style calls for it, while keeping the same semantic anchor and readable budget.
7. Height budget — calculate the height budget so the chart and modules fit within 900px while preserving actual gaps between independent modules (see §4).
8. Self-check width/height: Before calling the write tool, estimate the final layout. Width must fit 1600px and height must fit 900px, including padding, title/subtitle, rows, gaps, chart frames, footnotes, and likely text wrapping. If either dimension exceeds the canvas, redesign the composition and check again.