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

refactor(prompts): rewrite formula, chart, semantic-svg, structure references concise

hugohe3a7fdcab8b5b3
diff --git a/skills/ppt-master/references/executor-chart.md b/skills/ppt-master/references/executor-chart.md
index f09f73e6..2c36e423 100644
--- a/skills/ppt-master/references/executor-chart.md
+++ b/skills/ppt-master/references/executor-chart.md
@@ -1,12 +1,10 @@
-> Default Generate also loads [`executor-base.md`](./executor-base.md); a selected chart-family SVG is adapted through [`executor-visualization.md`](./executor-visualization.md), while independent native readiness and metadata remain exclusively in [`native-data-interface.md`](./native-data-interface.md).
+> Default Generate also loads [`executor-base.md`](./executor-base.md); a selected chart-family SVG is adapted through [`executor-visualization.md`](./executor-visualization.md), while native readiness and metadata remain exclusively in [`native-data-interface.md`](./native-data-interface.md).
# Executor Chart Branch
Conditional Executor authority for value-driven SVG geometry, plot-area markers, and the [`verify-charts`](../workflows/stages/verify-charts.md) handoff.
-**Trigger**: load whenever source values determine visible geometry, including bar length/height, point position, arc angle, polygon vertex, connector or flow width/path, bubble center/radius, duration position, area, or another quantitative visual variable. Mini charts, sparklines, insets, and small multiples count even without a catalog reference.
-
-**Boundary**:
+**Trigger**: source values determine visible geometry — bar length/height, point position, arc angle, polygon vertex, connector or flow width/path, bubble center/radius, duration position, area, or another quantitative visual variable. Mini charts, sparklines, insets, and small multiples count even without a catalog reference.
| Information model | Route |
|---|---|
@@ -18,40 +16,15 @@ Conditional Executor authority for value-driven SVG geometry, plot-area markers,
## 1. Value-driven Geometry
-**Hard rule — data owns the marks**: derive every quantitative mark from the authoritative values and one explicit scale/encoding. Do not eyeball positions, preserve sample values from a catalog preview, or alter data to improve composition.
-
-Construct the chart in this order:
-
-1. Resolve the data domain, categories, units, baseline, scale, and any radius/color/bin mapping.
-2. Establish the plot frame, axes/grid or radial frame, and legend needed to decode those mappings.
-3. Calculate marks from the values, including cumulative, derived, or hierarchical geometry where the chosen chart requires it.
-4. Add data labels, axis/category labels, annotations, units, source notes, and visible exceptions from the active page contract.
-5. Apply project typography, palette, effects, and container treatment without changing the encoding.
-
-**Perceptual reading**: choose the least ambiguous presentation of the same
-authoritative data. Preserve source or semantic order when it carries meaning;
-otherwise sort categories for the page's comparison task. Prefer direct series
-labels when they remain legible, and keep legends, grid lines, ticks, and other
-decoding aids only when they materially reduce lookup or comparison effort.
-Comparable panels and small multiples use the same domain, scale, and category
-order unless a visibly disclosed difference is itself the message. Bars and
-columns whose length compares magnitude start from zero; schedule spans and
-other true interval marks retain their authoritative domain. Any non-zero
-baseline or axis break must be explicit and must not exaggerate the comparison.
-A dual-axis chart is valid only when both series share the exact time/category
-domain and the units and visual identities stay unambiguous; otherwise separate
-the views.
+**Hard rule — data owns the marks**: derive every quantitative mark from the authoritative values and one explicit scale/encoding. Do not eyeball positions, preserve sample values from a catalog preview, or alter data to improve composition. A schedule is a Gantt chart when dates or durations determine each task bar's `x` and `width`, even if the source was a PowerPoint table; a qualitative stage × lane placement belongs to `executor-structure.md`.
-**Per-object completeness**: preserve every authoritative series, category, point, label, unit, qualifier, source, and scale cue needed to read the chart. For a `<object-key>=yes` chart, the JSON mirrors the drawn fallback item by item in the same edit: legend labels verbatim, point-level exception colors as `point_colors`, the axis scale, the classic `plot_area` taken from the plot-area marker, visible data labels or summary figures as `data_labels` or companion text, and the actual label / axis / grid colors — omit `text_color` and its siblings rather than guess them. When the source cannot determine a required scale or derived value, return the ambiguity upstream in Default or resolve it from explicit source facts in Quick; never fabricate it at draw time.
+Construct in this order: (1) resolve data domain, categories, units, baseline, scale, and any radius/color/bin mapping; (2) establish the plot frame, axes/grid or radial frame, and legend needed to decode them; (3) calculate marks from the values, including cumulative, derived, or hierarchical geometry; (4) add data labels, axis/category labels, annotations, units, source notes, and visible exceptions from the page contract; (5) apply project typography, palette, effects, and container treatment without changing the encoding.
-**Hard rule — schedule geometry**: A schedule is a Gantt chart when dates or
-durations determine each task bar's `x` and `width`, even if the source was a
-PowerPoint table object. A qualitative stage × lane placement without that
-mapping belongs to [`executor-structure.md`](./executor-structure.md).
+**Perceptual reading**: choose the least ambiguous presentation of the same data. Preserve source or semantic order when it carries meaning; otherwise sort for the page's comparison task. Prefer direct series labels when legible; keep legends, grid lines, and ticks only when they materially reduce lookup effort. Comparable panels share domain, scale, and category order unless a disclosed difference is the message. Magnitude bars and columns start from zero; interval marks keep their authoritative domain; any non-zero baseline or axis break is explicit and never exaggerates. A dual-axis chart is valid only when both series share the exact time/category domain and units and identities stay unambiguous.
-**Selected reference**: when the page has a `chart/<key>` primary reference, [`executor-visualization.md`](./executor-visualization.md) owns its resolution and flexible adaptation. This branch still owns the actual value-to-geometry calculation. A chart authored from scratch follows the same geometry contract without loading a catalog SVG.
+**Per-object completeness**: preserve every authoritative series, category, point, label, unit, qualifier, source, and scale cue. For a `<object-key>=yes` chart, the JSON mirrors the drawn fallback item by item in the same edit — legend labels verbatim, point-level exception colors as `point_colors`, the axis scale, `plot_area` from the plot-area marker, visible data labels or summary figures as `data_labels` or companion text, actual label/axis/grid colors (omit `text_color` and siblings rather than guess). When the source cannot determine a required scale or derived value, return the ambiguity upstream in Default or resolve it from explicit source facts in Quick; never fabricate at draw time.
-**Incidental microvisual**: draw a small value-driven trend or indicator accurately. It enters §2 and the verification handoff only when Default §IX or the Quick active-context decision promotes it to a coordinate-verified data object; do not infer that promotion from its appearance after drawing.
+**Selected reference**: with a `chart/<key>` primary reference, [`executor-visualization.md`](./executor-visualization.md) owns resolution and adaptation; this branch still owns the value-to-geometry calculation. A chart authored from scratch follows the same contract. An incidental microvisual (small trend or indicator) is drawn accurately but enters §2 and verification only when Default §IX or the Quick active-context decision promotes it to a coordinate-verified object.
---
@@ -59,19 +32,7 @@ mapping belongs to [`executor-structure.md`](./executor-structure.md).
### 2.1 Chart Plot-Area Marker (Mandatory per verified chart object)
-> [`verify-charts`](../workflows/stages/verify-charts.md) enumerates Default pages from Design Spec §IX and Quick pages from the still-active authoring decisions. A missing marker invokes that stage's declared fallback and adds avoidable derivation work.
-
-**Hard rule — object-scoped marker**: every Default chart object given a
-semantic key in §IX `Visualization`, and every Quick chart object promoted for
-coordinate verification, has one page-local `kebab-case` object key. Wrap that
-object in `<g id="<object-key>">`; put exactly one marker inside its plot-area
-group after the axes and before the first data mark. Use
-`id="<object-key>-chartArea"` so several charts can coexist without duplicate
-IDs. New pages prefix the marker payload with `object=<object-key> |`. A legacy
-unscoped marker and `<g id="chartArea">` are accepted only when the page has
-exactly one verified chart object.
-
-**Rectangular plot area**:
+**Hard rule — object-scoped marker**: every Default chart object keyed in §IX `Visualization`, and every Quick chart object promoted for coordinate verification, has one page-local `kebab-case` object key. Wrap it in `<g id="<object-key>">`; place exactly one marker inside its plot-area group `id="<object-key>-chartArea"`, after the axes and before the first data mark, with payload prefix `object=<object-key> |`. A legacy unscoped marker with `<g id="chartArea">` is accepted only when the page has exactly one verified chart object.
```xml
<g id="revenue-trend">
@@ -83,8 +44,6 @@ exactly one verified chart object.
</g>
```
-**Radial plot area**:
-
```xml
<!-- chart-plot-area: object=share-pie | pie | center: cx,cy | radius: r -->
<!-- chart-plot-area: object=share-donut | donut | center: cx,cy | outer-radius: r1 | inner-radius: r2 -->
@@ -93,48 +52,21 @@ exactly one verified chart object.
| Value | Derivation |
|---|---|
-| `x_min` | X coordinate of the Y-axis line or leftmost data boundary |
-| `y_min` | Y coordinate of the topmost grid line or data boundary |
-| `x_max` | X coordinate of the rightmost axis endpoint or data boundary |
-| `y_max` | Y coordinate of the X-axis baseline or bottom data boundary |
-| `cx, cy` | Absolute center after accounting for containing translate transforms |
-| `r`, `r1`, `r2` | Visible outer/inner radii used by the authored radial geometry |
-
-Calculator-supported SVGs in `templates/charts/` carry the same comment, and
-single-object previews may retain the legacy unscoped payload and
-`id="chartArea"`. A qualitative structure or cell-grid table does not gain a
-marker merely because it contains numbers.
+| `x_min` / `x_max` | X of the Y-axis line or leftmost data boundary / rightmost axis endpoint or data boundary |
+| `y_min` / `y_max` | Y of the topmost grid line or data boundary / X-axis baseline or bottom data boundary |
+| `cx, cy` | Absolute center after containing translate transforms |
+| `r`, `r1`, `r2` | Visible outer/inner radii of the authored radial geometry |
-### 2.2 Authoring-time Check
+Calculator-supported SVGs in `templates/charts/` carry the same comment. A qualitative structure or cell-grid table gains no marker merely because it contains numbers. A missing marker invokes the verify stage's declared fallback and adds avoidable derivation work.
-After writing each page containing verified charts, confirm marker count and
-object ownership before continuing:
-
-```bash
-rg -n "chart-plot-area" <project_path>/svg_output/<current_page>.svg
-```
-
-The number of markers must equal the number of promoted chart objects, and each
-marker must sit under its matching object wrapper. One marker somewhere on a
-multi-chart page is insufficient.
+### 2.2 Authoring-time Check
-**Native layout handoff**: for a native-ready classic chart whose authored plot
-rectangle must remain fixed, copy that final absolute slide rectangle into
-metadata `plot_area`; omit it only for PowerPoint automatic layout. The marker
-comment alone does not affect export; the closed schema stays in
-[`native-data-interface.md`](./native-data-interface.md) §2.
+After each page containing verified charts: `rg -n "chart-plot-area" <project_path>/svg_output/<current_page>.svg` — marker count equals promoted chart objects and each marker sits under its object wrapper.
-Technical SVG/PPT constraints remain in [`shared-standards-core.md`](./shared-standards-core.md).
+**Native layout handoff**: for a native-ready classic chart whose authored plot rectangle must stay fixed, copy that absolute rectangle into metadata `plot_area`; omit it for PowerPoint automatic layout. The comment alone does not affect export; the closed schema is [`native-data-interface.md`](./native-data-interface.md) §2.
---
## 3. Verification Handoff
-Coordinate calibration is a conditional post-generation stage, not part of the page-authoring loop. After all SVG pages exist, run [`verify-charts`](../workflows/stages/verify-charts.md) whenever the active profile declares at least one page with value-driven chart geometry.
-
-| Active profile | Verification page list |
-|---|---|
-| Default Generate | Design Spec §IX, with the stage's explicit legacy §VII fallback |
-| Quick Generate | Still-active page decisions cross-checked one-for-one against plot-area markers |
-
-Do not run `svg_position_calculator.py` during the initial draft. The stage calibrates completed SVG geometry against the declared plot area, handles direct/decomposable/formula/manual modes, repairs genuine coordinate mismatches, and then returns to the active profile's checker order.
+Coordinate calibration is a conditional post-generation stage. After all SVG pages exist, run [`verify-charts`](../workflows/stages/verify-charts.md) whenever the active profile declares at least one page with value-driven chart geometry: Default enumerates Design Spec §IX (with the stage's legacy §VII fallback); Quick cross-checks still-active page decisions one-for-one against plot-area markers. Do not run `svg_position_calculator.py` during the initial draft; the stage calibrates completed geometry against the declared plot area, repairs genuine mismatches, and returns to the profile's checker order.
diff --git a/skills/ppt-master/references/executor-structure.md b/skills/ppt-master/references/executor-structure.md
index 0bf901d2..f15ca091 100644
--- a/skills/ppt-master/references/executor-structure.md
+++ b/skills/ppt-master/references/executor-structure.md
@@ -2,60 +2,34 @@
# Executor Shape Composition Grammar
-Runtime grammar for Slide-local qualitative relationships built from editable shapes; it is not a diagram/template catalog.
+Runtime grammar for Slide-local qualitative relationships built from editable shapes; not a diagram catalog. Default and Quick read it once with their fixed construction bundle and reuse it for every per-page decision; loading it selects no `Structure=yes` and creates no geometry quota.
-**Load**: Default and Quick read this grammar once with their fixed construction
-bundle before all SVG authoring and reuse it for every per-page decision. Loading
-the grammar does not select `Structure=yes` or create a geometry quota.
+**Hard rule — no Structure catalog**: never recall or resolve `structure/<key>`; compose from authoritative content, §IX relationships, the communication move, and the active visual system.
-**Hard rule — no Structure catalog**: never recall or resolve `structure/<key>`. Compose from authoritative content, §IX relationships, the communication move, and the active visual system.
+**Hard rule — not structured PPTX**: this branch owns Slide-local geometry. [`executor-structured.md`](./executor-structured.md) independently owns reusable Master/Layout/placeholders under `pptx_structure.mode: structured`.
-**Hard rule — not structured PPTX**: this branch owns Slide-local geometry. [`executor-structured.md`](./executor-structured.md) independently owns reusable Master/Layout/placeholders under `pptx_structure.mode: structured`; neither implies the other.
+Numbers used only as labels do not create a chart; value-derived position, length, angle, area, radius, width, or color routes to [`executor-chart.md`](./executor-chart.md), row-header × column-header facts to [`executor-table.md`](./executor-table.md). Qualitative lanes use this grammar; date/duration-driven task-bar `x` / `width` is Gantt geometry.
---
## 1. Relationship Atoms
-**Mandatory — relationship → topology before contour**: For each active atom,
-resolve only the path, junctions, enclosure, field partition, shared region,
-scale change, and entry / endpoint that carry meaning. Adapt that topology to
-the actual units, text load, page role, and active visual system before
-selecting contours.
+**Mandatory — relationship → topology before contour**: for each active atom resolve only the path, junctions, enclosure, field partition, shared region, scale change, and entry/endpoint that carry meaning, adapted to the actual units, text load, page role, and visual system, before selecting contours.
| Atom | Meaning | Encode with | Generate topology from |
|---|---|---|---|
-| `order` | Sequence, progression, or rank | Position, numbering, direction, shared path | One reading path: open / closed; straight / bent / stepped / switchback / coiled; level / rising / falling; constant / expanding / contracting; turns, milestones, endpoint |
-| `link` | Dependency, exchange, influence, transition | Proximity / alignment when unmistakable; otherwise an edge | Sources, targets, and junctions: direct, hub, chain, split, merge, exchange, or feedback; let the relationship determine the fewest necessary edges |
-| `parent` | One unit governs or decomposes into children | Branching, indentation, nesting, scale | Root, depth, and sibling groups: branch, indent, nest, radiate, or scale; let child roles set fan-out and weight |
-| `membership` | Units belong to a group, stage, lane, or region | Containment, shared field, band, repetition | Owning fields: enclose, band, lane, cluster, repeat, or nest; let content set field shape and occupancy |
-| `contrast` | Peers, states, options, or positions compare | Shared baseline, opposing regions, parallel framing | Shared invariants plus separation: one or more semantic axes / baselines, opposing or parallel fields, counterweight, divergence, or a before / after boundary |
-| `overlap` | Units share a meaningful subset or duty | Intersecting regions plus a clear common area | Exact exclusive / shared regions: paired, chained, or layered intersections; keep every owner and common area legible |
-
-**Reference — not a constraint**: `Generate topology from` names common
-transform axes rather than an exhaustive set. Combine, deform, or invent
-page-fit topologies from the active atoms; never recall a named diagram or
-reproduce a listed form by default.
-
-**Mandatory — combined-atom spatial relation before contour**: Combine atoms as
-needed; never force a named business model. When multiple atoms share one
-construct, resolve whether their topologies share a field, nest, run in
-parallel, cross orthogonally, or intersect. Orthogonal overlay applies when
-independent dimensions occupy one field, including but not limited to an
-`order` path across `membership` lanes and two independent `contrast`
-dimensions; preserve each atom's ownership and reading direction. The overlay
-never implies equal partitions.
-
-**Hard rule — no topology from balance alone**: Node count and text fit may
-change spacing, route, or wrap. They never justify equal shapes, gaps, or
-partitions, mirroring, radial symmetry, or closure that invents peer weight,
-centrality, reciprocity, or recurrence.
-
-Numbers used only as labels do not create a chart. Value-derived position,
-length, angle, area, radius, width, or color routes to
-[`executor-chart.md`](./executor-chart.md); row-header × column-header facts
-route to [`executor-table.md`](./executor-table.md). Qualitative lanes use this
-grammar, but date / duration-driven task-bar `x` / `width` is Gantt Chart
-geometry.
+| `order` | Sequence, progression, rank | Position, numbering, direction, shared path | One reading path: open / closed; straight / bent / stepped / switchback / coiled; level / rising / falling; constant / expanding / contracting; turns, milestones, endpoint |
+| `link` | Dependency, exchange, influence, transition | Proximity / alignment when unmistakable; otherwise an edge | Sources, targets, junctions: direct, hub, chain, split, merge, exchange, feedback; the fewest necessary edges |
+| `parent` | One unit governs or decomposes into children | Branching, indentation, nesting, scale | Root, depth, sibling groups: branch, indent, nest, radiate, scale; child roles set fan-out and weight |
+| `membership` | Units belong to a group, stage, lane, region | Containment, shared field, band, repetition | Owning fields: enclose, band, lane, cluster, repeat, nest; content sets field shape and occupancy |
+| `contrast` | Peers, states, options, positions compare | Shared baseline, opposing regions, parallel framing | Shared invariants plus separation: semantic axes / baselines, opposing or parallel fields, counterweight, divergence, before / after boundary |
+| `overlap` | Units share a subset or duty | Intersecting regions plus a clear common area | Exact exclusive / shared regions: paired, chained, layered intersections; every owner and common area legible |
+
+The last column names common transform axes, not an exhaustive set: combine, deform, or invent page-fit topologies; never recall a named diagram or reproduce a listed form by default.
+
+**Mandatory — combined-atom spatial relation before contour**: when several atoms share one construct, resolve whether their topologies share a field, nest, run in parallel, cross orthogonally, or intersect. Orthogonal overlay applies when independent dimensions occupy one field (an `order` path across `membership` lanes, two independent `contrast` dimensions); preserve each atom's ownership and reading direction. Never force a named business model; the overlay never implies equal partitions.
+
+**Hard rule — no topology from balance alone**: node count and text fit may change spacing, route, or wrap. They never justify equal shapes, gaps, or partitions, mirroring, radial symmetry, or closure that invents peer weight, centrality, reciprocity, or recurrence.
---
@@ -67,50 +41,37 @@ geometry.
| `node` | Semantic unit, state, actor, item, or group; may punctuate a drawn carrier as a stop, turn, junction, or bridge |
| `spine` | Explicit/implied scaffold or continuous carrier establishing reading direction |
| `edge` | Necessary semantic connection, branch, dependency, or transition |
-| `label` | Text/evidence attached directly or by a non-relational leader/tether to a node, edge, region, or relationship |
+| `label` | Text/evidence attached directly or by a non-relational leader/tether to its owner |
| `garnish` | Non-semantic accent added after the relationship works |
| Operation | Job |
|---|---|
-| `repeat` | Create peers from one visual family; clone the full contour only when their structural states match |
-| `arrange` | Establish order, alignment, rhythm, rank, comparison |
+| `repeat` | Peers from one visual family; clone the full contour only when structural states match |
+| `arrange` | Order, alignment, rhythm, rank, comparison |
| `transform` | Vary scale, rotation, crop, fill, emphasis, or entry/continuation/turn/terminal port state meaningfully |
| `connect` | Add an edge when layout/containment is insufficient |
| `region` | Partition, contain, intersect, band, or layer fields |
| `attach` | Bind labels, badges, annotations, or evidence to an owner |
-**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 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.
+**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 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.
---
## 3. Construction Order
-Choose the field and map required atoms, then follow:
-
-**Mandatory — spine/topology → nodes → connectors → labels → garnish**:
+**Mandatory — spine/topology → nodes → connectors → labels → garnish**, after choosing the field and mapping required atoms:
| Layer | Completion evidence |
|---|---|
| `spine` | Entry, direction, and organizing path are clear; reversal, cycle, split/merge, or stage change reshapes a continuous carrier before node placement |
-| `nodes` | Every required unit has one home and intentional weight; each is direct content or a §2-approved carrier; carrier-crossing nodes intentionally continue, stop, turn, join, or bridge its visible path |
-| `connectors` (`edge`) | Only unresolved semantic links become edges; route/source/target is clear; every drawn edge passes §2 |
-| `labels` | Copy and caveats visibly attach directly or by leader/tether to what they explain; when a node has multiple text roles, cue → claim/value → support → note remains perceptibly descending and absent roles stay absent |
+| `nodes` | Every unit has one home and intentional weight as direct content or a §2-approved carrier; carrier-crossing nodes intentionally continue, stop, turn, join, or bridge its path |
+| `connectors` | Only unresolved semantic links become edges; route/source/target is clear |
+| `labels` | Copy and caveats visibly attach to what they explain; with several text roles on a node, cue → claim/value → support → note stays perceptibly descending and absent roles stay absent |
| `garnish` | Removing accents leaves all meaning intact |
**Hard rule — relationship before styling**: establish atoms, field, spine, nodes, and necessary edges before palette, type, effects, or containers. Containment, alignment, baselines, and proximity express relationships without edges; lines/Connectors express real edges.
-**Structural carriers**: a relationship-bearing field, spine, node carrier, or
-directional shape can be the page-scale move; Structure `yes` by itself adds no
-geometry. When drawn roles interact, resolve relationship-bearing
-parent contour/direction → contact → joint or intentional void →
-z-order/occlusion → canvas-edge behavior before labels/garnish. Skip
-inapplicable operations; implicit/direct roles remain container-free.
+**Structural carriers**: a relationship-bearing field, spine, node carrier, or directional shape can be the page-scale move; Structure `yes` by itself adds no geometry. When drawn roles interact, resolve parent contour/direction → contact → joint or intentional void → z-order/occlusion → canvas-edge behavior before labels/garnish; skip inapplicable operations.
---
@@ -118,13 +79,13 @@ inapplicable operations; implicit/direct roles remain container-free.
| Check | Pass condition |
|---|---|
-| Coverage | Every authoritative atom is visible; none was invented |
-| Reading path | Entry, progression, hierarchy, and endpoint are unambiguous |
+| Coverage | Every authoritative atom is visible; none invented |
+| Reading path | Entry, progression, hierarchy, and endpoint unambiguous |
| Roles | Nodes/edges have one duty; garnish carries no meaning |
| 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 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 |
+| Construction | Drawn roles pass §2; implicit/direct roles need no carrier; freeform follows failed exact-native/compound/Boolean routes |
+| Composition | Every contact, void, overlap, cutout, occlusion, or canvas-edge crossing maps to an atom/role or stays removable garnish |
-Load Chart/Table branches independently for embedded objects. Keep one dominant reading path while allowing secondary atoms whose ownership stays clear.
+Load Chart/Table branches independently for embedded objects. Keep one dominant reading path while secondary atoms keep clear ownership.
diff --git a/skills/ppt-master/references/native-formula.md b/skills/ppt-master/references/native-formula.md
index e10986c5..1c9cbd17 100644
--- a/skills/ppt-master/references/native-formula.md
+++ b/skills/ppt-master/references/native-formula.md
@@ -1,30 +1,25 @@
# Native Formula Specification
-Shared authoring contract for editable PowerPoint math generated from exact
-LaTeX, either inline in Slide-local prose or as a standalone block.
+Authoring contract for editable PowerPoint math generated from exact LaTeX, inline in Slide-local prose or as a standalone block. Compiler profile, normalization, reverse import, and compatibility live in [`svg-pipeline.md`](../scripts/docs/svg-pipeline.md#native-formula-compiler).
## 1. Trigger and Ownership
-**Trigger**: A page contains structural mathematical notation such as a
-fraction, radical, integral, n-ary expression, limit, matrix, delimiter
-construction, accent, or complex script.
+**Trigger**: a page contains structural mathematical notation — fraction, radical, integral, n-ary expression, limit, matrix, delimiter construction, accent, or complex script.
| Layer | Ownership |
|---|---|
| Default Strategist | Record exact mathematical content as a canonical delimiter-free LaTeX expression body; do not classify its implementation |
-| Default Executor | Decide ordinary text versus inline native math versus block native math, then author the selected marker and SVG preview |
-| Active Quick context | Perform both content and authoring responsibilities directly |
+| Default Executor | Decide ordinary text versus inline versus block native math, then author the marker and SVG preview |
+| Active Quick context | Both responsibilities directly |
| SVG-to-PPTX exporter | Compile marker LaTeX to editable Office Math and replace only the registered preview |
| Content form | Authoring choice |
|---|---|
-| Short variables, percentages, simple assignments, or notation such as `O(n log n)` | Ordinary editable SVG text |
-| One-line structural math embedded in prose whose native-height envelope fits the reserved row/module space | Inline native marker |
-| Matrix, `cases`, `aligned`, multiline derivation, standalone high-structure expression, or vertically expanding math that cannot fit its prose row | Block native marker |
+| Short variables, percentages, simple assignments, notation such as `O(n log n)` | Ordinary editable SVG text |
+| One-line structural math in prose whose native-height envelope fits the reserved row/module space | Inline marker |
+| Matrix, `cases`, `aligned`, multiline derivation, standalone high-structure expression, or vertically expanding math that cannot fit its prose row | Block marker |
-The Strategist's `Mathematical content` field does not pre-decide this choice.
-Formula handling is not a user-confirmed policy, image resource, manifest, or
-`spec_lock.md images` entry.
+Formula handling is not a user-confirmed policy, image resource, manifest, or `spec_lock.md images` entry.
---
@@ -38,32 +33,11 @@ Formula handling is not a user-confirmed policy, image resource, manifest, or
</text>
```
-**Hard rule — one leaf run**: Put non-empty LaTeX directly in
-`data-pptx-inline-formula` on a leaf `<tspan>`. Canonical authoring omits outer
-`$...$`, `$$...$$`, `\(...\)`, and `\[...\]` delimiters, though the compiler
-accepts and removes one complete outer pair. Give that `<tspan>` one non-empty
-direct preview string with no leading/trailing whitespace, no child element,
-and no `x`, `y`, `dx`, `dy`, or paragraph-layout metadata; spacing belongs to
-the surrounding text. The marker inherits its computed size and visible solid
-fill; exported math uses the project text language and Cambria Math. Local
-`\color` / `\textcolor` scopes override the marker fill on both selectable
-formula runs and non-selectable structural controls. `\boldsymbol` / `\bm`
-also applies its bold-italic style to structural control glyphs. Neither form
-changes unrelated marker defaults.
-
-**Hard rule — Slide-local ordinary text only**: Do not place an inline marker
-inside a structured Layout placeholder, a Master/Layout layer, imported
-preserved `txBody`, geometry transport subtree, another inline marker, or any
-`data-pptx-replace-with` subtree. Export keeps the surrounding text runs in the
-same `a:p` and replaces only the marker run with `a14:m > m:oMath`.
-
-**Hard rule — reserve native height**: Treat the parsed formula structure, not
-its flat SVG preview, as vertical layout truth. Keep adjacent content outside
-the native ascent/descent required by fractions, radicals, nested scripts,
-n-ary limits, accents, and other stacked structures. The exporter and SVG
-checker use the same structural envelope. If the prose row or root module
-cannot reserve that space without overlap, isolate the formula line or use the
-block marker.
+**Hard rule — one leaf run**: non-empty delimiter-free LaTeX in `data-pptx-inline-formula` on a leaf `<tspan>` (the compiler strips one complete outer `$…$` / `$$…$$` / `\(…\)` / `\[…\]` pair) with one non-empty direct preview string, no surrounding whitespace, no child element, and no `x`, `y`, `dx`, `dy`, or paragraph-layout metadata — spacing belongs to the surrounding text. The marker inherits its computed size and visible solid fill; local `\color` / `\textcolor` and `\boldsymbol` / `\bm` scopes apply to formula runs and structural control glyphs. Exported math uses the project text language and Cambria Math.
+
+**Hard rule — Slide-local ordinary text only**: never inside a structured Layout placeholder, Master/Layout layer, imported preserved `txBody`, geometry transport subtree, another inline marker, or a `data-pptx-replace-with` subtree. Export keeps the surrounding runs in the same `a:p` and replaces only the marker run with `a14:m > m:oMath`.
+
+**Hard rule — reserve native height**: the parsed formula structure, not its flat preview, is vertical layout truth. Keep adjacent content outside the native ascent/descent of fractions, radicals, nested scripts, n-ary limits, and accents; exporter and checker use the same envelope. If the prose row or module cannot reserve that space, isolate the formula line or use the block marker.
### 2.2 Block formula
@@ -81,95 +55,16 @@ block marker.
</g>
```
-**Hard rule — block metadata is truth**: Write one direct
-`<metadata type="application/json">` child with non-empty `latex`, `display:
-block`, `font_size` in `(0, 400]`, a visible `color`, and `align:
-left|center|right`. Use the same canonical delimiter-free form described above.
-Give the group finite `data-pptx-x/y`, positive `data-pptx-width/height`, and
-matching root-coordinate `data-pptx-bounds`. Export replaces the complete group
-with `a14:m > m:oMathPara > m:oMath`.
+**Hard rule — block metadata is truth**: one direct `<metadata type="application/json">` child with non-empty `latex`, `display: block`, `font_size` in `(0, 400]`, a visible `color`, and `align: left|center|right`; finite `data-pptx-x/y`, positive `data-pptx-width/height`, and matching root-coordinate `data-pptx-bounds`. Export replaces the whole group with `a14:m > m:oMathPara > m:oMath`.
-**Hard rule — preview is SVG, never fallback**: Make every marker preview
-semantically equivalent with ordinary SVG text/shapes/lines/paths. Do not use
-`<image>`, `<foreignObject>`, visible raw LaTeX, or another runtime renderer.
-The exporter discards the registered preview and emits no picture branch.
+**Hard rule — preview is SVG, never fallback**: every preview is semantically equivalent ordinary SVG text/shapes/lines/paths — no `<image>`, `<foreignObject>`, visible raw LaTeX, or runtime renderer. The exporter discards the preview and emits no picture branch.
---
## 3. Source, Failure, and Validation
-**Forward input profile**: The compiler implements every explicitly named
-LaTeX-to-OMML input and behavior in Microsoft's documented
-[Microsoft 365 LaTeX profile](https://learn.microsoft.com/en-us/office/math/latex)
-(Windows 2606 / Mac 16.110) and
-[mhchem profile](https://learn.microsoft.com/en-us/office/math/latex.mhchem)
-(Windows 2605 / Mac 16.109). This includes outer delimiters, all listed symbols
-and relations, fractions and binomials, roots, right and left scripts,
-delimiters and `\middle`, accents, bars and group characters, limits, all 21
-listed n-ary operators, standard/custom functions, matrices and equation-array
-environments, CD diagrams, fonts and local colors, boxes and phantoms, spacing,
-global 0–9 argument macros, and the documented `\ce` chemistry grammar. The
-closed command tables in `scripts/svg_to_pptx/native_objects/formula_profile.py`
-are the executable vocabulary; the public compiler facade and OMML structure
-gate live in `scripts/svg_to_pptx/native_objects/formula_compiler.py` and
-`scripts/svg_to_pptx/native_objects/formula_omml.py`. Microsoft's open-ended
-“etc.” wording for additional relation aliases does not define undisclosed
-names; only explicitly named commands and retained project aliases are
-contractual.
-
-Implementations:
-[`formula.py`](../scripts/svg_to_pptx/native_objects/formula.py),
-[`formula_ast.py`](../scripts/svg_to_pptx/native_objects/formula_ast.py),
-[`formula_parser.py`](../scripts/svg_to_pptx/native_objects/formula_parser.py),
-[`formula_run_properties.py`](../scripts/svg_to_pptx/native_objects/formula_run_properties.py),
-[`inline_formula.py`](../scripts/svg_to_pptx/native_objects/inline_formula.py).
-
-**Native normalization**: `\dfrac` / `\tfrac`, `\dbinom` / `\tbinom`, and
-continued-fraction alignment normalize to the corresponding OMML structure;
-explicit big-delimiter grades become auto-sizing delimiters; `\mathscr`
-normalizes to `\mathcal`; `smallmatrix` normalizes to `matrix`; PowerPoint array
-columns become centered; style/size commands and equation tags are accepted but
-not stored. Color is stored in generated formula runs and structural control
-properties.
-
-**Narrow reverse import**: `pptx_to_svg.py` rebuilds a block formula marker or
-same-paragraph inline marker only when one `a14:m` root passes this compiler's
-closed OMML validator and its normalized structure can be serialized back to
-LaTeX accepted by the same compiler. The reconstructed LaTeX is canonicalized;
-it is not the original spelling. A formula-only `m:oMathPara` text shape becomes
-one bounded block marker when its carrier also fits the unstyled rectangular
-native-formula contract; carrier grouping, paint, effects, rotation, hyperlink,
-or placeholder ownership force fallback instead of being silently discarded.
-Supported `m:oMath` zones remain inline among their surrounding text runs. Both
-forms receive a dependency-free linear SVG preview. This contract covers PPT
-Master-emitted vocabulary, not arbitrary third-party OMML. Tolerant import
-reports `formula-not-reconstructed`, renders readable formula text, and retains
-a relationship-free unchanged source `txBody` as opaque metadata; strict import
-stops instead.
-
-**Fail-closed boundary**: Input containing unknown commands or environments,
-Microsoft's explicitly unsupported commands, unsupported mhchem arrows,
-unescaped `%` comments, invalid macros, or any resource-limit overflow blocks
-conversion. This is stricter than Microsoft 365's literal-text passthrough and
-macro-limit behavior: PPT Master never leaks unresolved LaTeX into a released
-slide.
-
-**Hard rule — repair LaTeX upstream**: Unsupported source or an invalid marker
-blocks the page. Rewrite within the documented profile without changing the
-planned mathematics; otherwise return it to the content owner. Never substitute
-a PNG, flatten structural math into ordinary text, hand-write OMML, or leave raw
-LaTeX visible.
-
-**Compatibility boundary**: The generated package uses standard editable Office
-Math and retains the PowerPoint 2010+ package target. The executable profile is
-pinned to the Microsoft documentation versions above. Repository verification
-covers compilation, OMML structure, and PPTX packaging; it is not a complete
-Microsoft 365 UI rendering/editability certification. Earlier PowerPoint
-versions are not the source-profile baseline. WPS, Keynote, LibreOffice, and
-other clients receive no embedded formula fallback and are outside the
-rendering/editability contract.
-
-**Validation**: The first-page/final SVG checker validates every marker,
-compiles its LaTeX, and applies the shared native-height envelope to page/module
-text bounds before release; native export repeats validation and uses that
-envelope for the generated text frame.
+**Accepted input**: every explicitly named command in Microsoft's documented [Microsoft 365 LaTeX profile](https://learn.microsoft.com/en-us/office/math/latex) and [mhchem profile](https://learn.microsoft.com/en-us/office/math/latex.mhchem) — symbols, fractions and binomials, roots, scripts, delimiters and `\middle`, accents, limits, n-ary operators, functions, matrix and equation-array environments, CD diagrams, fonts and local colors, boxes and phantoms, spacing, 0–9 argument macros, `\ce` chemistry. Unknown commands or environments, Microsoft's explicitly unsupported commands, unsupported mhchem arrows, unescaped `%` comments, invalid macros, and resource-limit overflow block conversion: PPT Master never leaks unresolved LaTeX into a released slide.
+
+**Hard rule — repair LaTeX upstream**: unsupported source or an invalid marker blocks the page. Rewrite within the profile without changing the planned mathematics, or return it to the content owner. Never substitute a PNG, flatten structural math into ordinary text, hand-write OMML, or leave raw LaTeX visible.
+
+**Validation**: the first-page/final SVG checker validates every marker, compiles its LaTeX, and applies the shared native-height envelope to page/module text bounds; native export repeats validation and uses that envelope for the generated text frame. Output is standard editable Office Math for PowerPoint 2010+; WPS, Keynote, and LibreOffice receive no embedded fallback and are outside the rendering/editability contract.
diff --git a/skills/ppt-master/references/semantic-svg.md b/skills/ppt-master/references/semantic-svg.md
index 79229ac7..0e8f494e 100644
--- a/skills/ppt-master/references/semantic-svg.md
+++ b/skills/ppt-master/references/semantic-svg.md
@@ -1,102 +1,57 @@
# Minimal Semantic SVG Markers
-PPT Master uses rendering-neutral compiler hints only where ordinary SVG cannot express PowerPoint Master, Layout, placeholder, native-object, or package behavior.
+Rendering-neutral compiler hints, used only where ordinary SVG cannot express PowerPoint Master, Layout, placeholder, native-object, or package behavior. The completed SVG remains the full visible page: removing the metadata must not change browser rendering, and metadata never copies visible text, geometry, style, or asset values.
## 1. Boundary
| Marker | Placement | Purpose |
|---|---|---|
-| `data-pptx-page-role` | Root `<svg>` on flat pages only | Classify a free-design/brand-only page as `cover`, `toc`, `section`, `content`, or `ending`. |
-| `data-pptx-master` / `data-pptx-master-name` | Root `<svg>` | Bind the page to one named PowerPoint Slide Master. |
-| `data-pptx-layout` / `data-pptx-layout-name` | Root `<svg>` | Bind the page to one named Layout under that Master. |
-| `data-pptx-layer="master"` | Direct atomic child of root | Promote one fixed visual object to the named Master. |
-| `data-pptx-layer="layout"` | Direct atomic child of root | Promote one fixed visual object to the named Layout. |
-| `data-pptx-placeholder` | Direct child `<g id>` of root | Declare one reusable Layout slot whose visible content remains Slide-local. |
-| `data-pptx-role` | Structural page-frame element | Supply package, page-number, or animation behavior not already expressed by specialized metadata. |
+| `data-pptx-page-role` | Root `<svg>` on flat pages only | Classify a free-design/brand-only page as `cover`, `toc`, `section`, `content`, or `ending` |
+| `data-pptx-master` / `-master-name`, `data-pptx-layout` / `-layout-name` | Root `<svg>` on structured pages | Bind the page to one named Master and one Layout under it |
+| `data-pptx-layer="master\|layout"` | Direct atomic child of root | Promote one fixed visual object to the Master or Layout |
+| `data-pptx-placeholder` | Direct child `<g id>` of root | Declare one reusable Layout slot whose visible content stays Slide-local |
+| `data-pptx-role` | Structural page-frame element | Package, page-number, or animation behavior no specialized metadata already expresses |
-The completed SVG remains the full visible page. Removing the metadata must not change browser rendering. Do not copy visible text, geometry, style, or asset values into metadata.
+**Hard rule — route boundary**: free-design, brand-only, and `template_reuse_scope: style` pages use `pptx_structure.mode: flat`, declare one root `data-pptx-page-role`, and omit every Master/Layout/layer/placeholder marker. Only Default `template_reuse_scope: mirror|layout` pages or Quick pages authoring an installed Layout/Deck owner's structure declare Master and Layout before drawing and omit `data-pptx-page-role`; the exporter compiles that contract and never selects, clusters, distills, or infers it.
-**Hard rule — route boundary**: Free-design, brand-only, and `template_reuse_scope: style` pages use `pptx_structure.mode: flat`, declare one canonical root `data-pptx-page-role`, and omit every Master/Layout/layer/placeholder marker in this document. Only Default `template_reuse_scope: mirror|layout` pages or Quick pages authoring an installed Layout/Deck owner's structure declare their final Master and Layout before drawing begins and omit `data-pptx-page-role`; the structured exporter compiles that contract and never selects, clusters, distills, or visually infers it.
-
-**Hard rule — specialized metadata wins**: Use Master/Layout/placeholder metadata for native structure, `data-pptx-replace-with` for optional PowerPoint-native Chart/Table replacement, and the imported/authored shape metadata defined in [`shared-standards-core.md`](./shared-standards-core.md) §§1.4–1.5. Do not duplicate those facts with `data-pptx-role`.
+**Hard rule — specialized metadata wins**: Master/Layout/placeholder metadata for native structure, `data-pptx-replace-with` for native Chart/Table/Formula replacement, and the shape metadata of [`shared-standards-core.md`](./shared-standards-core.md) §§1.4–1.5 are never duplicated with `data-pptx-role`.
---
## 2. Master and Layout Atoms
-On structured `template_reuse_scope: mirror|layout` routes, Master and fixed Layout visuals are atomic root children:
+Structured routes only — attribute table, layer order, and consistency rules in [`pptx-structure-interface.md`](./pptx-structure-interface.md) §2. Canonical form:
```xml
-<svg xmlns="http://www.w3.org/2000/svg"
- viewBox="0 0 1280 720"
- data-pptx-master="master-default"
- data-pptx-master-name="Default Master"
- data-pptx-layout="content-two-column"
- data-pptx-layout-name="Two Column">
- <rect id="master-bg" data-pptx-layer="master"
- x="0" y="0" width="1280" height="720" fill="#F8FAFC"/>
- <path id="layout-rule" data-pptx-layer="layout"
- d="M72 132H1208" stroke="#CBD5E1"/>
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1280 720"
+ data-pptx-master="master-default" data-pptx-master-name="Default Master"
+ data-pptx-layout="content-two-column" data-pptx-layout-name="Two Column">
+ <rect id="master-bg" data-pptx-layer="master" x="0" y="0" width="1280" height="720" fill="#F8FAFC"/>
+ <path id="layout-rule" data-pptx-layer="layout" d="M72 132H1208" stroke="#CBD5E1"/>
</svg>
```
-| Requirement | Rule |
-|---|---|
-| Placement | Every Master/Layout atom is a direct child of the root SVG and has a stable unique `id`. |
-| Grouping | A `<g>` may not carry `data-pptx-layer="master|layout"`. The sole exception is one validated compact authored-preset `<g>` ([`shared-standards-core.md`](./shared-standards-core.md) §1.5), which compiles to one native object. Imported PowerPoint groups flatten recursively into atomic children with their transform/style/opacity/z-order semantics. |
-| Atomicity | One marked child must compile to one DrawingML object. A nested crop `<svg>` is allowed only when it is the supported single-picture carrier, not an arbitrary container. |
-| Consistency | Pages sharing one Master key repeat the identical ordered Master atom contract. Pages sharing one `(master, layout)` pair repeat the identical ordered Layout atom contract. |
-| Ownership | Concrete titles, body text, metrics, charts, tables, images, and page-specific decoration stay Slide-local or inside a declared slot. |
-
-> Note: Flattening a source PPTX group preserves supported appearance and native-layer ownership, but intentionally does not preserve the source group-editing hierarchy.
+Every atom is a direct root child with a stable unique `id` that compiles to one DrawingML object; a `<g>` may not carry the layer attribute except the one validated compact authored-preset group. Concrete titles, body text, metrics, charts, tables, images, and page-specific decoration stay Slide-local or inside a declared slot.
---
## 3. Layout Slots
-### 3.1 Carrier-bound slot
-
-Use one direct root group as the authoring boundary and one compatible direct child as the visible PowerPoint placeholder carrier:
+Structured routes only — placeholder values, carrier compatibility, and bounds derivation in [`pptx-structure-interface.md`](./pptx-structure-interface.md) §2. Canonical forms:
```xml
-<g id="title-slot"
- data-pptx-placeholder="title"
- data-pptx-bounds="72 48 1136 72">
- <text id="title-carrier"
- data-pptx-carrier="true"
- x="72" y="100">Actual title</text>
+<g id="title-slot" data-pptx-placeholder="title" data-pptx-bounds="72 48 1136 72">
+ <text id="title-carrier" data-pptx-carrier="true" x="72" y="100">Actual title</text>
</g>
-```
-
-| Requirement | Rule |
-|---|---|
-| Placement | The slot `<g id>` is a direct root child. Structural metadata may not be nested below it. |
-| Bounds | `data-pptx-bounds="x y width height"` is mandatory, finite, and positive. It describes the reusable design zone, not the current glyph/content tight bounds. |
-| Carrier | The group contains exactly one compatible direct drawable child marked `data-pptx-carrier="true"`. Export unwraps that child into the real Slide placeholder binding. |
-| Identity | `data-pptx-idx` is optional; effective indices must be unique within one Layout. Preserve a source index when reconstructing an existing PPTX. |
-| Fixed decoration | Reusable decoration does not belong in the slot. Author it as a root Layout atom. Page-specific labels/captions use another slot or remain Slide-local. |
-
-Canonical placeholder values are `title`, `subtitle`, `body`, `picture`, `chart`, `table`, `object`, `media`, `date`, `footer`, and `slide-number`. Carrier compatibility is defined in [`pptx-structure-interface.md`](./pptx-structure-interface.md) §2.
-### 3.2 Explicit composite proxy
-
-When one reusable region is a composite object that cannot bind to one real PowerPoint placeholder, declare the downgrade explicitly:
-
-```xml
-<g id="hero-composite-slot"
- data-pptx-placeholder="object"
- data-pptx-binding="proxy"
+<g id="hero-composite-slot" data-pptx-placeholder="object" data-pptx-binding="proxy"
data-pptx-bounds="544 160 664 472">
<rect x="544" y="160" width="664" height="472" fill="#E2E8F0"/>
<text x="576" y="214">Visible composite content</text>
</g>
```
-The visible group stays Slide-local. Export creates one hidden transparent matching placeholder proxy. Proxy binding is valid only for `object`; it is an explicit fallback, not the default slot form.
-
-### 3.3 Zero-slot Layout
-
-A Layout may contain no slot groups. Cover, poster, full-visual, or other fixed-composition pages still declare their Master/Layout root identity and any fixed atoms; do not manufacture a full-page `object` placeholder merely to make the Layout non-empty.
+A carrier-bound slot holds exactly one compatible direct child marked `data-pptx-carrier="true"`; reusable decoration is a root Layout atom, not slot content. The proxy form is the explicit `object`-only downgrade for a composite region: the visible group stays Slide-local and export adds one hidden transparent placeholder. A Layout may have zero slots.
---
@@ -106,27 +61,15 @@ Use `data-pptx-role` only when no specialized marker owns the behavior:
| Value | Compiler behavior |
|---|---|
-| `background` | Treat an otherwise unmarked background as static page framing for animation. |
-| `decoration` | Exclude decorative framing from automatic entrance animation. |
-| `header`, `footer`, `logo`, `watermark`, `chrome` | Identify Slide-local static framing without claiming Master/Layout ownership. |
-| `page-number` | Identify a Slide-local number when no `slide-number` placeholder exists. |
-
-On flat pages, a direct root background image or full-canvas scrim/decoration
-rectangle may carry the matching role and remain a primitive. Give the marked
-element a stable unique `id`; do not add a `<g>` solely to avoid an
-ungrouped-element advisory.
+| `background` | Treat an otherwise unmarked background as static page framing for animation |
+| `decoration` | Exclude decorative framing from automatic entrance animation |
+| `header`, `footer`, `logo`, `watermark`, `chrome` | Slide-local static framing without Master/Layout ownership |
+| `page-number` | Slide-local number when no `slide-number` placeholder exists |
-Do not add structural roles to ordinary titles, body copy, cards, KPIs, diagrams, charts, icons, or images.
+On flat pages a direct root background image or full-canvas scrim/decoration rectangle may carry the role and remain a primitive with a stable unique `id`; do not add a `<g>` solely to avoid an ungrouped-element advisory. Never add structural roles to ordinary titles, body copy, cards, KPIs, diagrams, charts, icons, or images.
---
## 5. Validation and Migration
-For structured `template_reuse_scope: mirror|layout` projects, validation rejects:
-
-- a missing root Master/Layout identity or a page-to-lock mismatch;
-- an ordinary Master/Layout `<g>` (the compact authored-preset atom is the sole exception), nested structure marker, missing/stale id, or inconsistent shared atom contract;
-- a slot without positive bounds, a carrier-bound slot without exactly one compatible carrier, or a proxy binding on a non-`object` slot;
-- incomplete page mappings, cross-Master Layout-key reuse, or conflicting same-key Layout contracts.
-
-Legacy structured/template SVGs using unmapped `baseline`, `preserve`, `layout_strategy: distill`, `data-pptx-layout-kind`, `distilled`, `utility`, direct atomic placeholders, or an incomplete Master identity are not a second supported structured contract. Create a new workspace through [`create-template`](../workflows/create-template.md) before generation or export. An explicit `mode: flat` free-design/brand-only project is current and intentionally has no Master identity. Original PPTX Type A may preserve native identities that still exist in the package; legacy SVG-only Type B may guide `standard` / `fidelity` visually but does not authorize topology recovery. Export never derives, repairs, or migrates structure.
+Structured validation rejects a missing or lock-mismatched root identity, an ordinary Master/Layout `<g>`, nested structure markers, missing/stale ids, inconsistent shared atom contracts, slots without positive bounds or exactly one compatible carrier, proxy binding on a non-`object` slot, incomplete page mappings, cross-Master key reuse, and conflicting same-key contracts. Legacy metadata and the input boundary are in [`pptx-structure-interface.md`](./pptx-structure-interface.md) §3; export never derives, repairs, or migrates structure.
diff --git a/skills/ppt-master/scripts/docs/svg-pipeline.md b/skills/ppt-master/scripts/docs/svg-pipeline.md
index 7abb06d5..8bc2fa61 100644
--- a/skills/ppt-master/scripts/docs/svg-pipeline.md
+++ b/skills/ppt-master/scripts/docs/svg-pipeline.md
@@ -963,6 +963,16 @@ Checker and exporter behavior behind [`pptx-structure-interface.md`](../../refer
**Final-package read-back gate**: before publishing, export reopens the temporary structured PPTX and verifies that each Slide targets exactly one Layout, one Layout key resolves to one part, distinct keys do not collapse, and every declared Layout—including unused ones—is registered through its Master and the Presentation; that physical Slide/Layout/Master part rosters, content-type overrides, and registrations are exact; the Layout picker name, Master picker identity, placeholder type and effective index, `p:hf` flags, design-zone frame, prompt size, and level-one default size; every owned `p:bg` as an exact zero-or-one payload against the pre-promotion result (preserving the base Master background when none replaces it); the exact top-level shape-name roster and order of every Slide, Layout, and Master; carrier-bound slot bindings, ordinary composite visible carriers, hidden composite proxies, and zero-slot Layouts with no placeholder. Later Slides may keep different Slide-local geometry; only the reusable Layout frame is checked. Any mismatch fails export without replacing the requested output.
+### Native formula compiler
+
+Behind [`native-formula.md`](../../references/native-formula.md) §3. The compiler implements every explicitly named LaTeX-to-OMML input in Microsoft's documented [Microsoft 365 LaTeX profile](https://learn.microsoft.com/en-us/office/math/latex) (Windows 2606 / Mac 16.110) and [mhchem profile](https://learn.microsoft.com/en-us/office/math/latex.mhchem) (Windows 2605 / Mac 16.109): outer delimiters, listed symbols and relations, fractions and binomials, roots, right and left scripts, delimiters and `\middle`, accents, bars and group characters, limits, all 21 listed n-ary operators, standard/custom functions, matrices and equation-array environments, CD diagrams, fonts and local colors, boxes and phantoms, spacing, global 0–9 argument macros, and the documented `\ce` chemistry grammar. Microsoft's open-ended "etc." wording defines no undisclosed names; only explicitly named commands and retained project aliases are contractual. The closed command tables in `svg_to_pptx/native_objects/formula_profile.py` are the executable vocabulary; the compiler facade and OMML structure gate are `formula_compiler.py` and `formula_omml.py`, with `formula.py`, `formula_ast.py`, `formula_parser.py`, `formula_run_properties.py`, and `inline_formula.py` alongside.
+
+**Normalization**: `\dfrac` / `\tfrac`, `\dbinom` / `\tbinom`, and continued-fraction alignment normalize to the corresponding OMML structure; explicit big-delimiter grades become auto-sizing delimiters; `\mathscr` → `\mathcal`; `smallmatrix` → `matrix`; array columns become centered; style/size commands and equation tags are accepted but not stored. Color is stored in generated formula runs and structural control properties; `\boldsymbol` / `\bm` applies bold-italic to structural control glyphs.
+
+**Fail-closed**: unknown commands or environments, Microsoft's explicitly unsupported commands, unsupported mhchem arrows, unescaped `%` comments, invalid macros, and resource-limit overflow block conversion — stricter than Microsoft 365's literal-text passthrough and macro-limit behavior.
+
+**Compatibility**: the package uses standard editable Office Math and keeps the PowerPoint 2010+ target; the executable profile is pinned to the documentation versions above. Repository verification covers compilation, OMML structure, and PPTX packaging, not a Microsoft 365 UI rendering/editability certification. Earlier PowerPoint versions are not the source-profile baseline; WPS, Keynote, LibreOffice, and other clients receive no embedded fallback. Reverse import is described in [`conversion.md`](conversion.md#native-formula-reverse-import).
+
## `total_md_split.py`
Split `total.md` into per-slide note files.
diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.json
index e9b8b1df..58273d66 100644
--- a/skills/ppt-master/scripts/prompt_audit_manifest.json
+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json
@@ -20,9 +20,9 @@
"skills/ppt-master/SKILL.md": 1750,
"skills/ppt-master/references/executor-base.md": 8000,
"skills/ppt-master/references/executor-structured.md": 5500,
- "skills/ppt-master/references/executor-chart.md": 3500,
+ "skills/ppt-master/references/executor-chart.md": 1750,
"skills/ppt-master/references/executor-visualization.md": 1250,
- "skills/ppt-master/references/executor-structure.md": 2250,
+ "skills/ppt-master/references/executor-structure.md": 1750,
"skills/ppt-master/references/topology-assembly.md": 3750,
"skills/ppt-master/references/executor-table.md": 1250,
"skills/ppt-master/references/executor-image.md": 2000,
@@ -45,7 +45,9 @@
"skills/ppt-master/workflows/generate-pptx.md": 10000,
"skills/ppt-master/workflows/stages/apply-template-workspace.md": 3500,
"skills/ppt-master/references/confirm-surface.md": 3000,
- "skills/ppt-master/references/video-design.md": 2500
+ "skills/ppt-master/references/video-design.md": 2500,
+ "skills/ppt-master/references/native-formula.md": 1500,
+ "skills/ppt-master/references/semantic-svg.md": 1500
},
"load_sets": {
"bootstrap.routing": {