Skip to content

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

docs(authoring): align image and native-shape selection

hugohe371d4bf11222c
diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.md
index ab443e24..e99841f1 100644
--- a/skills/ppt-master/references/executor-base.md
+++ b/skills/ppt-master/references/executor-base.md
@@ -176,30 +176,30 @@ Before drawing each page, look up its entry in `page_rhythm` (key format `P<NN>`
### 3.0 Native Shape Selection
-**Use the highest-level native construction that faithfully expresses the
-page and each atom.** Basic primitives and exact Office presets already export
-as editable PowerPoint shapes; compose them independently when one contour is
-unnecessary. Materialize a Merge Shapes Boolean result only for contour
-semantics that independent atoms cannot express. Hand-authored freeform is the final
-fallback, not the first drawing convenience. Block arrows, chevrons, banners /
-ribbons, callouts, flowchart nodes, stars, and other Office symbols should be
-**authored as presets** via `preset_shape_svg.py`, not redrawn as plain
-`<path>`s or faked with rectangles. Apply the decision gate in
-[`native-shape-authoring.md`](./native-shape-authoring.md) before drawing the
-object.
+**Hard rule — contour before encoding**: choose the page-fit contour from the
+full native vocabulary before its authoring form. Rectangle, rounded-rectangle,
+circle, and ellipse are preset contours even when authored with short SVG
+primitive syntax; never select them because that syntax is easier. After
+selection, use [`native-shape-authoring.md`](./native-shape-authoring.md) §1's
+simplest exact form, keep atoms independent unless one contour is required,
+materialize that contour with Boolean semantics, and use freeform last. Block
+arrows, chevrons, banners / ribbons, callouts, flowchart nodes, stars, and other
+Office symbols use `preset_shape_svg.py`, not plain paths or fake rectangles.
§IX `Native shape suggestion` records a semantic opportunity, not a literal
-tool command. Decide from the actual page construction whether a basic
-primitive, preset, independent compound construction, Boolean result, or necessary freeform best realizes it; a
-different implementation is valid when it preserves the intended object and
-content.
-
-**Compound-shape check (automatic, not a quota)**: after structure resolves and
-before drawing, test whether a page-level native geometry system would organize
-the background, zones, hierarchy, or reading path better than a uniform card
-grid. If yes, build it through [`native-shape-authoring.md`](./native-shape-authoring.md)
-§2.1; otherwise keep the simpler composition. There is no per-page or per-deck
-coverage target and no required explanation for declining it.
+tool command. Decide from the actual page construction which page-fit native
+contour and simplest exact authoring form, independent compound construction,
+Boolean result, or necessary freeform best realizes it; a different
+implementation is valid when it preserves the intended object and content.
+
+**Mandatory — independent per-page compound-shape decision**: after the
+Structure result and any applicable topology resolve, decide whether two or more
+native shapes would organize the background, zones, hierarchy, or reading path
+better than a simpler composition. This applies to both `Structure=no` and
+`Structure=yes`, stays in active context, and never changes that result. If yes,
+use [`native-shape-authoring.md`](./native-shape-authoring.md) §2.1; otherwise
+keep the simpler composition. There is no coverage target or required
+explanation for declining it.
**Default — do not use rectangles as the universal carrier (may use when a
neutral field is the best fit)**: before drawing another `<rect>` / rounded
@@ -219,13 +219,12 @@ Keep these as independently editable siblings in the ordinary semantic group;
visual containment never authorizes placing content inside an atomic preset
fragment or merging shapes that do not require one contour.
-| Decision | Action |
+| Selected result | Authoring form |
|---|---|
-| Plain rect / symmetric round rect / circle / ellipse | Keep the ordinary SVG primitive; it is already natively editable. |
+| Selected exact non-Connector stock contour | Use ordinary SVG only when the exporter maps it to that same contour; otherwise call `preset_shape_svg.py render` and paste its complete stdout fragment. |
| Straight relationship / divider / leader | Use `<line>`; add a registered marker only when direction is meaningful. |
-| Exact single-preset match | Call `preset_shape_svg.py render` and paste its complete stdout fragment into the current hand-authored SVG. |
| Bent / curved relationship exactly expressed by a stock Connector contour, with no required endpoint attachment | Use the matching `bentConnector*` / `curvedConnector*` preset through the helper as an unconnected native Connector shape. |
-| Text/content zone needs containment or emphasis without a filled surface | Use a faithful primitive or exact preset with `fill="none"` and a visible stroke; keep text and other content independent. |
+| Selected text/content boundary needs no filled surface | Use its exact authoring form with `fill="none"` and a visible stroke; keep text and other content independent. |
| Two or more native shapes should form one page-level geometry system | Follow [`native-shape-authoring.md`](./native-shape-authoring.md) §2.1: compose faithful primitives and presets as independent siblings first, then materialize only contours that require Boolean semantics. |
| Supported closed-shape / resolvable-text operands need union, cutout, overlap, symmetric difference, or fragmentation | Use `shape_boolean_svg.py` when Boolean materialization is the clearest faithful construction; follow [`native-shape-authoring.md`](./native-shape-authoring.md) §6. |
| Stock shape that needs a gradient fill/stroke or a pattern fill | Keep ordinary SVG — the helper paints `none` or a solid HEX on both fill and stroke only ([`native-shape-authoring.md`](./native-shape-authoring.md) §5). |
@@ -233,12 +232,12 @@ fragment or merging shapes that do not require one contour.
| Similar-looking contour only | Never infer a preset; continue to the Boolean gate, then use freeform only if no faithful construction exists. |
**Hard rule — freeform is the last construction tier**: before hand-authoring a
-stock-looking `<path>` / `<polygon>`, complete the primitive / exact-preset atom
-→ independent composition → required Boolean-result decision order above. A freeform is permitted only when those
-tiers cannot faithfully express the object; avoiding a helper or drawing the
-browser-visible contour faster is not a valid exception. Data-defined geometry
-and a genuinely locked organic / hand-drawn contour satisfy the exception by
-semantics, not by convenience.
+stock-looking `<path>` / `<polygon>`, complete contour selection, simplest exact
+materialization, independent composition, and the required Boolean-result gate.
+A freeform is permitted only when those routes cannot faithfully express the
+object; avoiding a helper or drawing the browser-visible contour faster is not
+a valid exception. Data-defined geometry and a genuinely locked organic /
+hand-drawn contour satisfy the exception by semantics, not by convenience.
This decision applies only while drawing a new object. A suggestion never
triggers retrospective scanning, contour classification, or automatic
diff --git a/skills/ppt-master/references/executor-structure.md b/skills/ppt-master/references/executor-structure.md
index 6b358995..a89b7e97 100644
--- a/skills/ppt-master/references/executor-structure.md
+++ b/skills/ppt-master/references/executor-structure.md
@@ -49,10 +49,9 @@ Combine atoms as needed; never force a named business model. Numbers used only a
**Hard rule — realization enters the construction gate**: Decide whether each
role is implicit/direct content or drawn geometry. Every drawn field, spine,
-node carrier, or edge uses the first faithful tier under
-[`native-shape-authoring.md`](./native-shape-authoring.md) §§1–2.1: primitive /
-exact-preset atoms → independent compound system → required Boolean result →
-necessary freeform. Text styling/rules cannot replace
+node carrier, or edge follows [`native-shape-authoring.md`](./native-shape-authoring.md)
+§§1–2.1: contour before encoding → simplest exact native form → independent
+compound → required Boolean → necessary freeform. Text styling cannot replace
required geometry; implicit/direct roles need no container. Decoration cannot
invent a relationship.
@@ -94,7 +93,7 @@ inapplicable operations; implicit/direct roles remain container-free.
| Attachment | Labels/evidence belong to the correct node, edge, or region |
| Removal | Without color/effects/icons/garnish, placement still communicates |
| Fidelity | All required units, qualifiers, values, and caveats remain |
-| Construction | Drawn fields/spines/node carriers/edges pass §2; implicit/direct roles need no carrier; freeform follows failed primitive/preset/independent-compound/Boolean tiers |
+| Construction | Drawn roles pass §2; implicit/direct roles need no carrier; freeform follows failed exact-native/independent-compound/Boolean routes |
| Composition | Every used contact, void, overlap, cutout, occlusion, or canvas-edge crossing maps to an atom/role or remains removable garnish; none obscures ownership or reading path |
Load Chart/Table branches independently for embedded objects. Keep one dominant reading path while allowing secondary atoms whose ownership stays clear.
diff --git a/skills/ppt-master/references/image-generator.md b/skills/ppt-master/references/image-generator.md
index 761f22cd..df614f98 100644
--- a/skills/ppt-master/references/image-generator.md
+++ b/skills/ppt-master/references/image-generator.md
@@ -260,6 +260,14 @@ stable Layer 1 artwork, not page copy converted to an image.
**Hard rule**: a sheet is a generation source, not a slide asset. In Default Generate, keep the sheet row out of `spec_lock.md images`; in Quick Generate, retain its generation-only status in active context and the operational manifest. The sheet is never referenced from SVG. Only sliced element rows are placed.
+**Hard rule — separable treatment before keying**: when the intended slice
+excludes a supporting surface, choose a treatment whose complete visible
+geometry can stand alone against the key field. Engraved, etched, debossed,
+inlaid, bas-relief, or other surface-dependent treatments are valid only when
+that carrier belongs in the intended slice; otherwise choose a genuinely
+freestanding treatment. Never define a carrier as necessary to the treatment
+and ask the same prompt to remove it.
+
**Sheet prompt convention** — one `page_role: local` manifest item; choose
`image_size` from final placement size. Spot sheets use `text_policy: none`;
lettering sheets use `text_policy: embedded`:
@@ -463,7 +471,7 @@ Defaulting an entire `ai` resource list to `none` because "SVG can always overla
**Forbidden — text that may be reworded**: any word that may later change belongs in Layer 2, not Layer 1. Layer 1 is for stable visual identifiers and designed lettering that is part of the image itself.
-**Default — controlled, deck-aligned artistic authorship (may override when the user explicitly requests high expression or confirms a strongly expressive direction)**: For decorative lettering, give the model the exact intended string, communication role, placement/background relationship, deck identity, relative visual weight, and desired energy. The resolved rendering, semantic colors, mood, and page hierarchy define the envelope. Without the stated override, keep expression controlled and glyph-native: carry identity through the glyph silhouette, stroke construction, internal material/texture, contour-bound depth/light, and letterform composition; do not translate the topic into literal illustrations or detached decoration around the word. A lettering-plus-illustration lockup is a separate treatment and requires an explicit user request or confirmed design direction. Within the chosen treatment, let the model decide and combine—or omit—the calligraphic gesture, material, dimensionality, texture, lighting, internal hierarchy, and composition; such terms are possibility space, not an effect recipe. Do not flatten the art merely to simplify extraction: §4.3's key field, clear padding, and cell isolation protect delivery without raising the chosen intensity. When fit is uncertain, use the lower effect density; never infer high expression or external motifs from the topic, place, or wording alone. Keep a multi-line lockup as one element when its hierarchy is part of the art.
+**Default — controlled, deck-aligned artistic authorship (may override when the user explicitly requests high expression or confirms a strongly expressive direction)**: For decorative lettering, give the model the exact intended string, communication role, placement/background relationship, deck identity, relative visual weight, and desired energy. The resolved rendering, semantic colors, mood, and page hierarchy define the envelope. Without the stated override, keep expression controlled and glyph-native: carry identity through the glyph silhouette, stroke construction, internal material/texture, contour-bound depth/light, and letterform composition; do not translate the topic into literal illustrations or detached decoration around the word. A lettering-plus-illustration lockup is a separate treatment and requires an explicit user request or confirmed design direction. Within the chosen treatment, let the model decide and combine—or omit—the calligraphic gesture, material, dimensionality, texture, lighting, internal hierarchy, and composition; such terms are possibility space, not an effect recipe. Do not flatten the art merely to simplify extraction: §4.3's separable-treatment gate, key field, clear padding, and cell isolation protect delivery without raising the chosen intensity. When fit is uncertain, use the lower effect density; never infer high expression or external motifs from the topic, place, or wording alone. Keep a multi-line lockup as one element when its hierarchy is part of the art.
**Font choice for in-image text — free description, with the deck typography as one optional reference**
diff --git a/skills/ppt-master/references/native-shape-authoring.md b/skills/ppt-master/references/native-shape-authoring.md
index 10bee060..1d24657b 100644
--- a/skills/ppt-master/references/native-shape-authoring.md
+++ b/skills/ppt-master/references/native-shape-authoring.md
@@ -3,34 +3,38 @@
# Native Shape Authoring Reference
Use this reference during Executor SVG construction or project-owned canonical
-template maintenance when basic primitives, one standard PowerPoint shape, or
-supported shape/text operands can express the intended object. Prefer, in order:
-editable basic primitives, one exact Office preset per atom, an independent
-composition of those faithful atoms, then a PowerPoint-style Boolean result
-only for contours that must become one object. Hand-authored freeform geometry
-is allowed only when those constructions cannot faithfully express the object.
-Neither helper writes a page. The preset helper does not create the shape's own
-`p:txBody`; keep visible text outside the atomic fragment.
-
-## 1. Selection Gate
-
-Apply this decision order before drawing any new geometric contour.
-
-> This gate is for picking the **highest-level faithful native construction**.
-> Do not hand-author a freeform merely because an SVG path is convenient.
-
-| Condition | Action |
+template maintenance when native contours or supported shape/text operands can
+express the intended object. Choose each contour from its page job before
+deciding how to encode it, then use the simplest exact authoring form. Keep
+faithful atoms independent unless one contour is required; materialize that
+contour with a PowerPoint-style Boolean result, and use hand-authored freeform
+only when those constructions fail. Neither helper writes a page. The preset
+helper does not create the shape's own `p:txBody`; keep visible text outside the
+atomic fragment.
+
+## 1. Contour Selection and Materialization Gate
+
+**Hard rule — contour before encoding**: choose the page-fit contour from the
+intended job and active visual system across the full native vocabulary before
+considering authoring syntax. Rectangle, rounded-rectangle, circle, and ellipse
+contours are not an earlier visual tier merely because SVG has short primitive
+syntax for them. A neutral contour is valid when neutrality is the job; easier
+syntax is never the reason to select it.
+
+After contour selection, use the simplest exact materialization below. Do not
+hand-author a freeform merely because an SVG path is convenient.
+
+| Selected result | Authoring form |
|---|---|
-| Plain rectangle, symmetric rounded rectangle, circle, or ellipse | Write the ordinary SVG primitive; the exporter already emits an editable native shape. |
-| A text/content zone needs a visible boundary but not a filled surface | Use a faithful primitive or exact preset with `fill="none"` and a visible stroke; keep its content as independent siblings. |
-| Straight relationship, divider, or leader | Write `<line>`; use a registered marker only when direction is meaningful. |
-| One DrawingML preset exactly expresses the intended object | Run `preset_shape_svg.py render`, then insert its complete stdout fragment into the hand-authored page or canonical template. |
+| Mirror/preserve input already owns native-shape metadata | Keep the existing object and metadata; never reselect its preset. |
+| One exact non-Connector stock contour | Use an ordinary SVG primitive only when the exporter maps it to that same contour; otherwise run `preset_shape_svg.py render` and insert its complete stdout fragment. |
| A stock `bentConnector*` / `curvedConnector*` contour exactly expresses a bent or curved relationship and endpoint attachment is not required | Run `preset_shape_svg.py render --object-kind connector`; the result is an unconnected native Connector shape. |
-| Two or more faithful primitives / presets form the page construction but do not need one contour | Keep them as independently editable siblings in one ordinary semantic group; use §2.1 to compose the page-level geometry system. |
+| A straight relationship, divider, or leader | Write `<line>`; use a registered marker only when direction is meaningful. |
+| A selected text/content boundary needs no filled surface | Use its exact authoring form with `fill="none"` and a visible stroke; keep its content as independent siblings. |
+| Two or more selected native contours form the page construction but do not need one contour | Keep them as independently editable siblings in one ordinary semantic group; use §2.1 to compose the page-level geometry system. |
| Two or more supported closed-shape / resolvable-text operands require Union, Combine, Fragment, Intersect, or Subtract | Run `shape_boolean_svg.py render`, then replace the operands with every stdout path; the result remains ordinary editable custom geometry. |
-| Basic primitives, exact presets, their independent composition, and Boolean materialization cannot faithfully express the visual meaning or contour | Write ordinary `<path>` / `<polygon>` geometry; export keeps it as editable custom geometry. |
+| Exact native contours, their independent composition, and Boolean materialization cannot faithfully express the visual meaning or contour | Write ordinary `<path>` / `<polygon>` geometry; export keeps it as editable custom geometry. |
| The shape only resembles a preset | Never infer a preset; continue to the Boolean gate, then use freeform only if no faithful construction exists. |
-| Mirror/preserve input already owns native-shape metadata | Keep the existing object and metadata; never reselect its preset. |
**Hard rule**: `preset_shape_svg.py` is the only authoring entry for
`data-pptx-authoring="preset"`. Never add `data-pptx-prst`, frame, adjustment,
@@ -42,9 +46,9 @@ rerun the helper whenever its geometry, paint, or filter reference changes.
## 2. Semantic Preset Candidate Guide
Use the table below as a high-frequency entry, not a whitelist: match the
-page's visual intent to a candidate preset *before* defaulting to a plain rect
-or path. A neutral rect remains valid when neutrality is the job; otherwise
-search the registry rather than forgetting the broader preset vocabulary.
+page's visual intent to a candidate contour before settling on a neutral
+rectangle / ellipse or a freeform path. Search the registry when the job calls
+for a more specific contour rather than letting authoring convenience decide.
"Automatic" means the Executor independently applies this semantic decision
gate before drawing a new object. It does not scan existing SVG, classify
@@ -86,16 +90,19 @@ owned by the preserve/mirror round-trip contract.
### 2.1 Compound page geometry
-**Trigger**: after [`executor-structure.md`](./executor-structure.md) resolves the
-page topology, use this method when two or more native shapes can strengthen its
-background field, content zoning, focal hierarchy, or reading path. This is a
-construction method, not a requirement to decorate every page.
+**Trigger**: after the page or prototype's communication / slot job, composition
+anchors, and any applicable topology under
+[`executor-structure.md`](./executor-structure.md) are resolved, use this method
+when two or more native shapes can strengthen its background field, content
+zoning, focal hierarchy, or reading path. This method applies whether the
+per-page Structure result is `no` or `yes`; it never creates a decoration
+requirement.
| Pass | Action | Result |
|---|---|---|
| Page job | Name the geometric jobs already implied by the resolved page: surface, boundary, direction, reveal, focal mark, shared region, or counterweight. | A small set of functional zones; no shape names yet. |
| Decompose | Separate visible content from geometric atoms. Identify which atoms need independent movement, paint, or reuse and which contour must become one object. | Editable siblings plus any explicit Boolean operand set. |
-| Select | Apply §1 to every atom: primitive first, then one exact preset; use freeform only after faithful preset and Boolean routes fail. | The highest-level faithful native construction per atom. |
+| Select | Choose each atom's contour from its job and the full native vocabulary, then apply §1's simplest exact materialization. | Page-fit native atoms without syntax bias. |
| Compose | Establish page frame, scale, z-order, and negative space with independent atoms. Keep text, images, icons, data marks, and non-merged accents outside Boolean operands. | One page-level geometry system, not a collection of unrelated decorations. |
| Materialize | Run the preset helper for each adopted preset. Run the Boolean helper only for contours that require Merge Shapes semantics, then replace those operands with its stdout paths. | Valid authoring SVG ready for native export. |
@@ -114,7 +121,7 @@ construction method, not a requirement to decorate every page.
| Required result | Construction |
|---|---|
-| Stock contour already expresses the job | One exact preset; do not rebuild it from primitives or Boolean operands. |
+| Stock contour already expresses the job | Keep that exact contour and materialize it through §1; do not rebuild it from other shapes or Boolean operands. |
| Shapes overlap or layer but must remain independently editable | Keep separate primitives / presets in one ordinary semantic group; do not merge them. |
| One continuous outer silhouette | `union`; use `combine` only for intentional symmetric negative regions. |
| A true hole, edge cut, or reveal | `subtract`, with the visible body first and cutout operands after it. |
@@ -125,7 +132,7 @@ construction method, not a requirement to decorate every page.
| SVG authoring form | Native PPTX result |
|---|---|
-| Ordinary `<rect>`, rounded `<rect>`, `<circle>`, `<ellipse>`, or `<line>` | Editable primitive / line shape. |
+| Ordinary `<rect>`, rounded `<rect>`, `<circle>`, `<ellipse>`, or `<line>` | Matching editable preset geometry / line shape. |
| Complete `preset_shape_svg.py` fragment | One exact `a:prstGeom` shape, or `p:cxnSp` for an authored connector preset. |
| `shape_boolean_svg.py` result path | Editable `a:custGeom`; the final contour is retained, not replayable Merge Shapes history. |
| Parent semantic group containing independent atoms and content | A grouped page construction whose child shapes remain separately editable. |
diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.md
index 7391e48a..33001a74 100644
--- a/skills/ppt-master/references/strategist.md
+++ b/skills/ppt-master/references/strategist.md
@@ -435,9 +435,10 @@ an exact preset key, endpoint/site metadata, or attachment promises. Only when
one contour, cutout, common region, or meaningful fragmentation is intended,
name the candidate Union / Combine / Fragment / Intersect / Subtract operation,
semantic operands, and result.
-Executor still decides the exact basic primitive, preset, independent compound
-construction, Boolean result, or necessary freeform under its native-shape branch; the recommendation never
-creates a §VII row or lock field.
+Executor still decides the exact page-fit native contour and authoring form,
+independent compound construction, Boolean result, or necessary freeform under
+its native-shape branch; the recommendation never creates a §VII row or lock
+field.
### Speaker Notes Requirements
diff --git a/skills/ppt-master/references/template-designer.md b/skills/ppt-master/references/template-designer.md
index b3f5be7b..30807f2b 100644
--- a/skills/ppt-master/references/template-designer.md
+++ b/skills/ppt-master/references/template-designer.md
@@ -64,7 +64,7 @@ ownership.
| Mode | Output structure contract |
|---|---|
-| `standard` / `fidelity` | Author project-canonical SVG prototypes and an intentional new Master/Layout/slot system. Source visual language and assets may guide the design, but source ownership, keys, picker names, parent relationships, placeholders, and repeated Slide-local elements do not define or seed the output topology. Build new geometry from editable primitives and exact compact presets as independent atoms; materialize a Boolean result only where one contour requires it, and use freeform last. |
+| `standard` / `fidelity` | Author project-canonical SVG prototypes and an intentional new Master/Layout/slot system. Source visual language and assets may guide the design, but source ownership, keys, picker names, parent relationships, placeholders, and repeated Slide-local elements do not define or seed the output topology. Choose page-fit contours from the full native vocabulary before their authoring forms; keep exact native atoms independent, materialize a Boolean result only where one contour requires it, and use freeform last. |
| `mirror` | Materialize a new workspace from the validated source graph one-to-one: keep the Master/Layout identities and parentage, slide assignments, placeholder type/index/bounds, and supported visual/native-object facts that are actually present. Edit the authoring IR; materialization may rehydrate converter-supported native payload only for unchanged source refs. Mechanical normalization maps fixed-layer source groups into the direct atoms required by the current explicit SVG contract while preserving ownership, paint order, and appearance; it must not invent missing facts or semantically redesign the graph. |
Every page remains a complete standalone SVG preview.
diff --git a/skills/ppt-master/templates/design_spec_reference.md b/skills/ppt-master/templates/design_spec_reference.md
index 98aa9174..5bc82d2e 100644
--- a/skills/ppt-master/templates/design_spec_reference.md
+++ b/skills/ppt-master/templates/design_spec_reference.md
@@ -228,7 +228,7 @@ never write an empty or `none` placeholder:
- **Motion suggestion**: <communication job plus desired page-entry or reveal relationship/order>
```
-Add `Mathematical content` whenever a Slide needs a mathematical expression preserved exactly. Store the expression body as valid LaTeX without `$...$`, `$$...$$`, `\(...\)`, or `\[...\]` source delimiters; the field does not classify inline versus structural use. This is content authority for [`native-formula.md`](../references/native-formula.md), not a formula policy, marker, or implementation request; Executor chooses ordinary text, inline native math, or block native math. Add `Visualization` / `Images` when a Slide consumes §VII/§VIII or uses a page-local visual model. Name every value-driven geometry, qualitative relationship, cell grid, and child visual here; only independent Chart/Table entries use object keys. Describe qualitative order, linkage, hierarchy, grouping, contrast, overlap, and reading path freely—not as a model name or grammar enum. §IX may choose a custom Chart/Table fallback. Add `Native shape suggestion` only when a page-level shape system, preset, stock Connector, or compound silhouette/cutout/intersection/fragment may help; name semantic geometry jobs and relationships plus independent atom roles, a candidate family, or Boolean operands as applicable, never implementation geometry or keys. Executor chooses the primitive, preset, independent compound construction, Boolean result, or necessary freeform. Add `Motion suggestion` whenever transition/reveal advice strengthens communication, regardless of the Custom Animations outcome; state purpose and semantic order/relationship, not registry keys, options, timing, ids, or coverage. The suggestion never activates animation execution by itself, creates content, or binds implementation. Describe required visible image states in `Layout` / `Images` only for an explicit motion requirement or an enabled Custom Animations outcome. Add keyed `Native-ready` only for independent data charts or pure text-grid tables, `Fact IDs` for sourced claims, and `Data class: scenario` for invented demo values. Except on preservation paths, `Cover impact` carries a binding hook and adaptable composition; apply the same split to `Closing impact` only when the deck genuinely resolves. Roster/order/content stay authoritative. §VIII image layout is non-empty free prose with optional library ids; §VII Chart/Table rows are references. Executor owns geometry, hierarchy, treatment, and sparse local garnish.
+Add `Mathematical content` whenever a Slide needs a mathematical expression preserved exactly. Store the expression body as valid LaTeX without `$...$`, `$$...$$`, `\(...\)`, or `\[...\]` source delimiters; the field does not classify inline versus structural use. This is content authority for [`native-formula.md`](../references/native-formula.md), not a formula policy, marker, or implementation request; Executor chooses ordinary text, inline native math, or block native math. Add `Visualization` / `Images` when a Slide consumes §VII/§VIII or uses a page-local visual model. Name every value-driven geometry, qualitative relationship, cell grid, and child visual here; only independent Chart/Table entries use object keys. Describe qualitative order, linkage, hierarchy, grouping, contrast, overlap, and reading path freely—not as a model name or grammar enum. §IX may choose a custom Chart/Table fallback. Add `Native shape suggestion` only when a page-level shape system, preset, stock Connector, or compound silhouette/cutout/intersection/fragment may help; name semantic geometry jobs and relationships plus independent atom roles, a candidate family, or Boolean operands as applicable, never implementation geometry or keys. Executor chooses the page-fit native contour and exact authoring form, independent compound construction, Boolean result, or necessary freeform. Add `Motion suggestion` whenever transition/reveal advice strengthens communication, regardless of the Custom Animations outcome; state purpose and semantic order/relationship, not registry keys, options, timing, ids, or coverage. The suggestion never activates animation execution by itself, creates content, or binds implementation. Describe required visible image states in `Layout` / `Images` only for an explicit motion requirement or an enabled Custom Animations outcome. Add keyed `Native-ready` only for independent data charts or pure text-grid tables, `Fact IDs` for sourced claims, and `Data class: scenario` for invented demo values. Except on preservation paths, `Cover impact` carries a binding hook and adaptable composition; apply the same split to `Closing impact` only when the deck genuinely resolves. Roster/order/content stay authoritative. §VIII image layout is non-empty free prose with optional library ids; §VII Chart/Table rows are references. Executor owns geometry, hierarchy, treatment, and sparse local garnish.
For free-design pages, describe `Layout` through relationships, hierarchy, regions, and column spans; do not prescribe element-level `x`, `y`, `width`, or `height` or duplicate the global geometry in §II/§V. Exact coordinates belong to Executor SVG authoring. Preserve literal geometry only when the user explicitly requires it or a mirror/template preservation contract owns it.
diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.md
index 872a173c..7dc74d52 100644
--- a/skills/ppt-master/workflows/generate-pptx.md
+++ b/skills/ppt-master/workflows/generate-pptx.md
@@ -652,7 +652,7 @@ sidecars, or guessed family paths.
**Visual Construction Phase**: generate SVG pages sequentially, one at a time, in one continuous pass → `<project_path>/svg_output/`
-Each completed SVG MUST be a standalone, complete representation of that slide's visible design. Template SVGs and locked planning artifacts may guide construction, but export must not reach back to them to add visible objects omitted from `svg_output/`. Speaker notes, animation, narration, transitions, and direct native-PPTX workflows remain separately owned artifacts/capabilities. Treat §IX `Native shape suggestion` as a candidate, not a command: inspect the actual page construction, then follow [`native-shape-authoring.md`](../references/native-shape-authoring.md) — compose editable primitives and exact Office presets as independent atoms when possible, materialize a Merge Shapes Boolean result only where contour semantics require it, and use necessary freeform last. Diagram relationships follow the same Shape-first gate; do not infer a preset from contour similarity.
+Each completed SVG MUST be a standalone, complete representation of that slide's visible design. Template SVGs and locked planning artifacts may guide construction, but export must not reach back to them to add visible objects omitted from `svg_output/`. Speaker notes, animation, narration, transitions, and direct native-PPTX workflows remain separately owned artifacts/capabilities. Treat §IX `Native shape suggestion` as a candidate, not a command: inspect the actual page construction, then follow [`native-shape-authoring.md`](../references/native-shape-authoring.md) — choose page-fit contours from the full native vocabulary before their authoring forms, keep exact native atoms independent when possible, materialize a Merge Shapes Boolean result only where contour semantics require it, and use necessary freeform last. Diagram relationships follow the same Shape-first gate; do not infer a preset from contour similarity.
**Motion-ready image composition**: Only when an explicit user motion
instruction, the effective Custom Animations outcome in `design_spec.md §I` is
diff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.md
index 35843b01..97a63b52 100644
--- a/skills/ppt-master/workflows/profiles/quick-generate.md
+++ b/skills/ppt-master/workflows/profiles/quick-generate.md
@@ -381,7 +381,7 @@ generation capability is resolved during resource preparation, not eligibility.
| Reusable title/corner decoration, a dominant illustrated anchor, supporting figure, or accent strengthens one or more page compositions | A coherent AI illustration family prepared as transparent `slice` assets and combined freely with other carriers |
| A compact semantic cue clarifies a category, process, KPI, state, or navigation item | Prepared project-local SVG/emoji icon, an illustrated-icon `slice`, or a coherent combination |
| A real company, product, service, or social brand must appear as itself | Prepare the exact brand mark from `simple-icons` or supplied project assets as needed; it is not a user-facing library choice |
-| Editable geometry can express a relationship, flow, emphasis, callout, symbol, or diagram | Basic primitives and exact Office presets, independently composed when possible; Boolean only for required contour semantics; necessary freeform last |
+| Editable geometry can express a relationship, flow, emphasis, callout, symbol, or diagram | Page-fit contours from the full native vocabulary, then their simplest exact authoring forms; independent composition when possible, required Boolean next, necessary freeform last |
| Values, categories, time, weights, or duration determine mark geometry | Value-driven chart |
| Sequence, hierarchy, role, region, or relationship determines page-local topology | Qualitative structure |
| Rows, columns, cells, headers, merges, and alignment form the information model | Cell-grid table |
@@ -503,9 +503,11 @@ page and reuse throughout the valid execution context:
`Status: Sourced` image or filename recorded in `image_sources.json`.
Reread only after a known file change or context invalidation.
-`executor-structure.md` is loaded once before all SVG authoring so Quick cannot
-omit shape-composition reasoning. Reuse it throughout the valid execution
-context; reread only after a known file change or context invalidation.
+`executor-structure.md` is loaded once before all SVG authoring so every
+`Structure=yes` result can apply its qualitative topology grammar.
+`native-shape-authoring.md` independently owns contour selection and compound
+page geometry for both Structure results. Reuse both throughout the valid
+execution context; reread only after a known file change or context invalidation.
**Mandatory — per-image-page composition decision**: For every page with one
or more images, after its content and communication move are
@@ -528,12 +530,12 @@ whole-object carrier, and author canonical SVG `<a href>` under
[`native-hyperlinks.md`](../../references/native-hyperlinks.md). Never guess an
unknown destination.
-Image to PPTX replaces this open composition decision for its canonical page
-frame: preserve the source geometry, restore text natively, preserve
-source-graphic identity through the prepared exact or reconstructed asset, and
-use the active-context registered layer/plate stack for scene imagery. Run the
-ordinary decision only for an additional non-source image whose placement is
-not already fixed by that surface.
+Image to PPTX replaces the open image-composition and compound-shape decisions
+for its canonical page frame: preserve the source geometry, restore text
+natively, preserve source-graphic identity through the prepared exact or
+reconstructed asset, and use the active-context registered layer/plate stack
+for scene imagery. Run either ordinary decision only for additional non-source
+content whose placement or geometry is not already fixed by that surface.
**Mandatory — per-page Structure decision**: after the current page's content
and communication move are determined, but before choosing any geometry or
@@ -548,6 +550,15 @@ artifact, spec, lock, manifest, or extra pass.
This decision is mandatory on every page and cannot be satisfied by the
capability menu, visualization recall, template geometry, or a later check.
+**Mandatory — independent per-page compound-shape decision**: after the
+Structure result and any applicable topology resolve, decide whether two or more
+native shapes would organize the background, zones, hierarchy, or reading path
+better than a simpler composition. This applies to both `no` and `yes`, stays in
+active context, and never changes the Structure result. If yes, use
+[`native-shape-authoring.md`](../../references/native-shape-authoring.md) §2.1;
+otherwise keep the simpler composition. There is no coverage target or required
+explanation for declining it.
+
| Deterministic trigger | Additional authority |
|---|---|
| A selected primary Chart/Table `family/key` | [`executor-visualization.md`](../../references/executor-visualization.md), then the matching Chart/Table authority |