AI turns documents or topics into real, native PowerPoint decks—with native shapes, transitions and animations, data-backed charts and tables on demand, audio narration from speaker notes, and support for your own .pptx templates. · by Hugo He
feat(prompts): surface expression capability ahead of constraints
hugohe3bf81f3ece547
diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.mdindex c9354c58..f7e2e75b 100644--- a/skills/ppt-master/SKILL.md+++ b/skills/ppt-master/SKILL.md@@ -57,6 +57,19 @@ never compete with it.---+## Authored Expression Range++**Reference — not a constraint**: what a generated page can carry. Text — inline+emphasis runs, lead-in, kicker, pull quote, hero number, takeaway line. Geometry+— 187 Office presets, Boolean merge, connectors, freeform, page-field and+outline-carrier composition. Image — full-bleed field, editorial crop, shaped+picture, registered layers, scrim and spotlight, cross-page continuity. Paint —+gradients, channel alpha, native shadow and glow, halftone, faceted form.+Recurrence — one cross-page motif varied by page role. Each form's syntax lives+in the selected runtime authority's construction references.++---+## Global Execution Discipline1. **Serial execution** — Follow the selected authority's steps in order. A completed non-blocking step may continue directly to the next eligible step.diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.mdindex 0af69e22..37591765 100644--- a/skills/ppt-master/references/executor-base.md+++ b/skills/ppt-master/references/executor-base.md@@ -31,6 +31,51 @@ Evaluate branches from each object's actual information model, not only from a C---+## Page Expression Core++Read this before §1. It is the expression vocabulary every page draws from; the+technical contracts below bound how it is written, not whether it is available.++**Capability — typographic feature elements**: beyond the structural roles fixed+by `typography` anchors, a page may carry deliberate typographic hierarchy — a+lead-in sentence, an inline emphasis run, a pull quote, a kicker, a hero number,+a takeaway line. Each is its own feature element with its own size and treatment;+a recurring one becomes a named role.++**Capability — inline emphasis is one editable frame**: a `<text>` paragraph may+nest non-positional `<tspan>` runs carrying their own `fill`, `font-weight`, or+`font-size`. Export walks those nested runs and emits one DrawingML run per+styled segment, so a coloured or bold phrase inside a sentence stays inside the+same editable PowerPoint text frame. Positioned line-break `<tspan>` children may+themselves contain inline runs.++```xml+<text x="72" y="300" font-size="24" fill="#2E3230">腐朽但仍可加固接续的<tspan fill="#9E2B25" font-weight="bold">千年木梁,不做整体更换</tspan>;风化的古墙,只做防风化微创处理。</text>+```++**Reference — everyday device menu (not a constraint, not a quota)**: the pieces most slides are built from.++| Device | Typical job | Realization |+|---|---|---|+| Gradient block or band | Cover / chapter field, title backing, zone separation | `<linearGradient>` / `<radialGradient>` in 2–3 stops of the deck hue |+| Rounded card | One content module among peers, a feature or option block | `<rect rx>` in `secondary_bg`; a shadow only when it floats over a photo or colored panel |+| Icon with label | Feature markers, list prefixes, step or category cues | `<use data-icon>` at 32–48 px in an accent or primary role |+| Numbered circle or badge | Ordered steps, ranked items, chapter marks | `<circle>` + centered number; oversized numeral for a chapter |+| Color swatch | A color, material, or sample that the content names | `<circle>` / `<rect>` filled with the subject's own value, labeled with its name and HEX |+| KPI card | Metric name + hero number + trend or comparison | Card + number at the hero size + small annotation; icon optional |+| Takeaway box | One-sentence conclusion under a title | Tinted band (`fill-opacity` 0.06–0.10) with the sentence in lead size |+| Divider or rule | Separate sections, columns, header from body | Hairline `<line>` in `divider`, or a 2 px accent bar |+| Full-bleed image + scrim | Cover, chapter divider, mood page | Image `slice` + directional gradient scrim + floating title |+| Framed or shaped picture | Portrait, product, place, evidence photo | Circle / rounded clip on `<image>`, hairline frame, caption |+| Quote block | Pull quote, testimonial, source sentence | Oversized quotation mark or accent rule + text at lead size + attribution |+| Timeline or step strip | Ordered events or stages | Baseline `<line>` with ticks/nodes, or chevron presets, labels above/below |++**Reference — page-level recipes**: [`svg-effects.md`](./svg-effects.md) §6.13+carries a back-to-front layer stack for cover, divider, text-led, process,+evidence, comparison, closing, and cross-page-motif pages.++---+## 1. Effect Capability Discovery**Reference — effects vocabulary**: [`svg-effects.md`](./svg-effects.md) §6.1@@ -171,22 +216,7 @@ Before drawing each page, look up its entry in `page_rhythm` (key format `P<NN>`- **Default — stage each page with the style's composition geometry (may override when another page-fit move is stronger)**: an SVG page is a canvas, not a DOM. Resolve the page-scale move from `spec_lock.md`: a preset uses that selected style's §1 `Composition geometry`; `custom` executes `visual_style_behavior` first, then uses §1 geometry only from exact `visual_style_references` that the behavior assigns a shape or composition job. Other bases contribute only their assigned job, and an unreferenced novel custom follows its behavior alone. Treat every listed move as generative vocabulary rather than a finite menu, then apply [`native-shape-authoring.md`](./native-shape-authoring.md) §2.1's shared exact-fit geometry gate.- **Default — consider the planned motif direction (may override when another coherent expression better serves the deck)**: when §III `Theme` recommends a cross-page motif or element family, decide whether it earns a continuity job. If adopted, keep its reuse coherent while varying scale, crop, density, position, and content interaction by page role; otherwise adapt or decline it and establish a more fitting style-consistent expression. An explicit user/template motif remains binding.- **Ordinary carriers stay ordinary**: cards, icon-and-label rows, color swatches, soft shadows, and gradient fields are everyday slide carriers. Use them whenever content groups, compares, enumerates, or names a color, material, or sample, and give peers one shared treatment. When the subject itself is a color or material, draw it: a swatch is content, its value comes from the source, and it needs no lock row.-- **Reference — everyday device menu (not a constraint, not a quota)**: the pieces most slides are built from; reach for them by page job and let the locked style set their treatment.--| Device | Typical job | Realization |-|---|---|---|-| Gradient block or band | Cover / chapter field, title backing, zone separation | `<linearGradient>` / `<radialGradient>` in 2–3 stops of the deck hue |-| Rounded card | One content module among peers, a feature or option block | `<rect rx>` in `secondary_bg`; a shadow only when it floats over a photo or colored panel |-| Icon with label | Feature markers, list prefixes, step or category cues | `<use data-icon>` at 32–48 px in an accent or primary role |-| Numbered circle or badge | Ordered steps, ranked items, chapter marks | `<circle>` + centered number; oversized numeral for a chapter |-| Color swatch | A color, material, or sample that the content names | `<circle>` / `<rect>` filled with the subject's own value, labeled with its name and HEX |-| KPI card | Metric name + hero number + trend or comparison | Card + number at the hero size + small annotation; icon optional |-| Takeaway box | One-sentence conclusion under a title | Tinted band (`fill-opacity` 0.06–0.10) with the sentence in lead size |-| Divider or rule | Separate sections, columns, header from body | Hairline `<line>` in `divider`, or a 2 px accent bar |-| Full-bleed image + scrim | Cover, chapter divider, mood page | Image `slice` + directional gradient scrim + floating title |-| Framed or shaped picture | Portrait, product, place, evidence photo | Circle / rounded clip on `<image>`, hairline frame, caption |-| Quote block | Pull quote, testimonial, source sentence | Oversized quotation mark or accent rule + text at lead size + attribution |-| Timeline or step strip | Ordered events or stages | Baseline `<line>` with ticks/nodes, or chevron presets, labels above/below |+- **Everyday devices**: the device menu in `Page Expression Core` above is the recall list; reach for a device by page job and let the locked style set its treatment.- **Inherited containers**: preserve meaningful template frames; restyle radius, fill, stroke, and depth from the active Design Spec and `spec_lock.md`. Selected Chart/Table reference adaptation is owned by [`executor-visualization.md`](./executor-visualization.md); preview effects never override project styling or structural roles.- **Reference — prefer semantic geometry over preset stacks**: for relationships such as ascending, converging, breaking through, or stacking, first compose faithful primitives and exact presets as one page geometry system; use a Boolean only when the contour itself must merge, open, or fragment. Only when neither construction works should one page-specific polygon/path replace a stack of generic arrows.diff --git a/skills/ppt-master/references/shared-standards-core.md b/skills/ppt-master/references/shared-standards-core.mdindex eb029220..862e9c36 100644--- a/skills/ppt-master/references/shared-standards-core.md+++ b/skills/ppt-master/references/shared-standards-core.md@@ -28,6 +28,10 @@ Mandatory reference for every route that authors or regenerates slide visuals th**Reference — effects vocabulary**: Default and Quick Generate load [`svg-effects.md`](./svg-effects.md); its §6.1 Visual Job Router lists the visual jobs an effect can serve. Whether any compatible technique is added is the author's call.+**Reference — where expression lives**: §4.2 owns editable text form, including+per-run inline emphasis and leading; §4.3 owns grouping. §1.4's imported-PowerPoint+metadata applies only to import, mirror, and round-trip routes.+**Fidelity labels**:| Label | Meaning |@@ -645,7 +649,7 @@ These forms are needed only when the stated PPT behavior matters:| Desired behavior | Required form ||---|---|-| One editable PPT text frame with mixed formatting or multiline prose | Use one `<text>` per logical paragraph and non-positional `<tspan>` children for inline runs. Keep the first line as direct text; later lines use direct positioned `<tspan>` children that repeat parent `x` with positive relative `dy`; an all-`<tspan>` form may start at `dy="0"`. Default retains these breaks without PowerPoint wrapping; `--reflow-text` may join eligible lines. A font-size change, list marker, or larger accepted gap starts another paragraph. Sibling `<text>` elements are forbidden as one paragraph's line breaks; they remain valid for independent frames. |+| One editable PPT text frame with mixed formatting or multiline prose | Use one `<text>` per logical paragraph and non-positional `<tspan>` children for inline runs. Per-run `fill` / `font-weight` / `font-size` is retained: export walks nested runs and emits one DrawingML run per styled segment, so an emphasised phrase stays inside the same editable frame, and a positioned line-break `<tspan>` may itself contain inline runs. Keep the first line as direct text; later lines use direct positioned `<tspan>` children that repeat parent `x` with positive relative `dy`; an all-`<tspan>` form may start at `dy="0"`. Default retains these breaks without PowerPoint wrapping; `--reflow-text` may join eligible lines. A font-size change, list marker, or larger accepted gap starts another paragraph. Sibling `<text>` elements are forbidden as one paragraph's line breaks; they remain valid for independent frames. || Stable object grouping or object-level animation anchor | Wrap the intended object in `<g id="...">`. Content grouping is **mandatory** per §4.3 — a top-level `<g id>` is also the animation anchor; it is not an optional convenience. || Native PowerPoint background promotion | Outside structured mode, the first eligible visual layer may be a direct full-canvas `<rect>` or one inside a simple single-child group. Its fill must have a registered native mapping (solid, linear/radial gradient, or preset pattern), and it must have no transform, filter, clip, rounding, or visible stroke. Export writes the fill as Slide `p:bg`; image elements remain pictures. Structured routes use the narrower explicit solid-background ownership contract in [`pptx-structure-interface.md`](./pptx-structure-interface.md). || Free-design / brand-only PowerPoint structure | Use `pptx_structure.mode: flat`. Keep represented objects Slide-local; export emits one clean Master plus Blank Layout, removes stock content placeholders/Layout inventory, and retains the standard date/footer/slide-number hooks. Do not author Master/Layout identities, layers, or slots. Without a Layout/Deck owner, Quick uses the same ownership with converter-default theme scaffolding. |diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.mdindex 723a3aef..52dd41a0 100644--- a/skills/ppt-master/references/strategist.md+++ b/skills/ppt-master/references/strategist.md@@ -600,7 +600,7 @@ includes transitions.- **page_rhythm is mandatory**: Based on the page list in §IX Content Outline, assign each page one of `anchor` / `dense` / `breathing`. This is what breaks the uniform "every page is a card grid" feel. New locks may not omit the section; consumer omission behavior is owned by [`executor-base.md`](executor-base.md) §2.1.- **Fact IDs and scenario labels are mandatory when applicable**: Read any `sources/*.facts.json`. For each §IX page, list the stable IDs actually used; never cite an ID whose claim is absent from the page. Mark invented KPIs/targets/internal ratios as `Data class: scenario` and state which values are scenario data. Executor carries external sources into notes/footnotes and renders a visible scenario label for scenario figures.- **Mandatory — whole-roster rhythm check**: During the same §IX composition, compare neighbors and section arcs to judge whether chapter entries visibly reset, extended same-density runs are intentional, extended same-carrier or same-topology runs form an intentional semantic sub-arc, repeated dominant geometry carries a continuity job, any qualifying §6.1 visible-state sequence preserves a recognizable mental map while making its next semantic change legible, each section follows a mode-fitting progression—including framework → explanation/evidence → judgment/action when it serves the objective—and the final arc resolves the communication objective before a genuine ending lowers information load. Same section, equal weight or density, one style, and prior-page precedent do not establish a semantic sub-arc. Repair the existing roster, `Layout` recommendations, and `page_rhythm` choices in place. This is judgment, not quota; preserve intentional continuity, legitimately all-`dense` material, and 1:1/literal order. Do not invent filler pages to manufacture rhythm; a `breathing` page marks a meaningful pause—chapter transition, standalone emphasis, or SCQA bridge—and must stand alone. Create no field, lock row, artifact, or second review/execution pass.- - **Cover impact is mandatory**: In `design_spec.md §IX`, give `P01` one concrete hook from the source's strongest claim, metaphor, number, moment, or conflict plus a recommended composition. The hook binds; Executor may adopt, adapt, or decline the composition while preserving the hook and explicit constraints. With no suitable image, recommend a native-SVG hook instead of a generic title treatment. Beautify preservation paths are exempt.+ - **Cover impact is mandatory**: In `design_spec.md §IX`, give `P01` one concrete hook from the source's strongest claim, metaphor, number, moment, or conflict plus a recommended composition. **Reference — not a constraint**: composition starting points include full-bleed image with floating title, typographic poster, hero object, data hook, editorial scene, and high-contrast abstract geometry; a fresh composition the subject suggests is equally valid — these are starting points rather than the allowed set. A distilled display phrase taken from the deck's own subject may carry the cover as the dominant mark while the complete title stays as a native subtitle. The hook binds; Executor may adopt, adapt, or decline the composition while preserving the hook and explicit constraints. With no suitable image, recommend a native-SVG hook instead of a generic title treatment. Beautify preservation paths are exempt.- **Cover rhythm lock**: `P01` remains `anchor`. Default away from generic content-page templates; a card grid, agenda, or equal-weight columns remains valid when content, user direction, or the template makes it the clearest cover.- **Closing impact (only when the deck closes)**: For a genuine conclusion / CTA / final takeaway, name the binding takeaway plus a recommended composition; Executor may adopt, adapt, or decline the latter while preserving the takeaway and explicit constraints. Do not default to an information-empty "Thank you", contact-only slide, or cover reprise; an explicit contact/event CTA may serve the purpose. **Do NOT invent a closing page to satisfy this**. Preservation paths are exempt.- **pptx_structure is mandatory**: Free-design, brand-only, and `template_reuse_scope: style` routes write `mode: flat`; a style-reference route may also record `template_reuse_scope: style` but omits every structure mapping and `template_adherence`. `template_reuse_scope: mirror|layout` writes `mode: structured` plus `template_adherence: strict|adaptive`. Do not write legacy `baseline`, `template`, `preserve`, `layout_strategy`, or Layout-kind rows into a new project.diff --git a/skills/ppt-master/references/svg-effects.md b/skills/ppt-master/references/svg-effects.mdindex 7cd2ae24..4e56de99 100644--- a/skills/ppt-master/references/svg-effects.md+++ b/skills/ppt-master/references/svg-effects.md@@ -38,6 +38,11 @@ serve.| Surface / select | Name the target, confirm its owning subsection and fidelity, and let the Router recall candidates. Choose a compatible technique that fully performs the job; prefer simpler/native-stable alternatives only when communication is equal. `Approximate` requires review, not automatic rejection. || Integrate / stop | Align paint, contour, light, hierarchy, and z-order; combine only techniques with different jobs. Check legibility, editability, density, fidelity, and style; simplify failures, use legal alternatives, and bake only the smallest pixel-dependent layer. Keep authoritative text/data native. |+**Reference — page-level recipes**: §6.13 carries a back-to-front layer stack for+cover, divider, text-led explanation, process, evidence, comparison, closing, and+cross-page motif pages. Read it with this router rather than after the page is+already composed.+**Default — one dominant composition scaffold (may override when a secondscaffold performs an independent communication job)**: Integrate the page-scalemove and every active Structure / Image / Chart / Table branch into one dominant@@ -62,6 +67,7 @@ contracts are the boundary; membership in this table is not.| Picture/card/overlay elevation or boundary is unclear | Object or picture/carrier shadow, restrained glow, or hairline | §6.4; one light direction || Native copy and image do not integrate | Scrim, fade, wash, vignette, off-center spotlight, or faux glass | §6.5 and the Image-Treatment Implementation Map; verify contrast; no backdrop blur || Relationship state, direction, continuity, or boundary is unclear | Draft/optional/future → dash; direction → marker; undirected → solid; continuous flow → gradient stroke; repeated boundary → frame/contour/crop edge; exact grid → multi-subpath | §6.6 / §6.3; every line needs a job |+| Body copy carries a load-bearing figure, contrast, or noun that does not survive a scan | Inline emphasis run — a nested `<tspan>` with its own fill or weight inside the same paragraph | §6.7; the frame stays one editable text object || Short display text needs notation, silhouette, or material/image emphasis | Removed/former → strike; eyebrow distinction → tracking; display silhouette → outline/gradient; justified material/image emphasis → native picture/texture fill; luminous metric → glow; semantic list → native bullet | §6.7 / §6.3 / §6.4; no decorative body-copy treatment || Tilt, repetition, or reversible asset direction helps composition | Rotate, translate/mirror, or local `<use>` | §6.8; never mirror text, logos, or directional evidence || Resolved style needs hand, print, pixel, facets, layers, ribbon, or line-plus-area | Matching constructed recipe | §6.11; no generic decorative freeform |diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex f0eadb5c..6c2b50fb 100644--- a/skills/ppt-master/scripts/prompt_audit_manifest.json+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json@@ -17,7 +17,7 @@},"file_budgets": {"AGENTS.md": 3250,- "skills/ppt-master/SKILL.md": 1250,+ "skills/ppt-master/SKILL.md": 1500,"skills/ppt-master/references/executor-base.md": 12000,"skills/ppt-master/references/executor-structured.md": 5500,"skills/ppt-master/references/executor-chart.md": 3500,@@ -29,7 +29,7 @@"skills/ppt-master/references/executor-web-image.md": 750,"skills/ppt-master/references/executor-notes.md": 1000,"skills/ppt-master/references/shared-standards.md": 500,- "skills/ppt-master/references/shared-standards-core.md": 13000,+ "skills/ppt-master/references/shared-standards-core.md": 14000,"skills/ppt-master/references/svg-effects.md": 16000,"skills/ppt-master/references/native-data-interface.md": 7750,"skills/ppt-master/references/pptx-structure-interface.md": 4750,@@ -54,7 +54,7 @@"skills/ppt-master/SKILL.md","skills/ppt-master/workflows/routing.md"],- "max_tokens": 7750+ "max_tokens": 8000},"support.sponsor-recommendation.en": {"description": "English sponsor context for explicit user requests for model, AI image model, API/provider, or hosted-service recommendations.",