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): tighten hyperlinks, table, visualization, notes, canvas references

hugohe3d15265307487
diff --git a/skills/ppt-master/references/canvas-formats.md b/skills/ppt-master/references/canvas-formats.md
index eab34629..ee6b88dc 100644
--- a/skills/ppt-master/references/canvas-formats.md
+++ b/skills/ppt-master/references/canvas-formats.md
@@ -1,13 +1,12 @@
# Canvas Format Specification
-> See [`shared-standards-core.md`](./shared-standards-core.md) §4.1 for the normative root
-> `viewBox` grammar, compatibility spellings, and fail-closed validation rules.
+> See [`shared-standards-core.md`](./shared-standards-core.md) §4.1 for the normative root `viewBox` grammar, compatibility spellings, and fail-closed validation rules.
## Format Quick Reference
| ID | Format | Size | viewBox | Ratio | Use Case |
|----|--------|------|---------|-------|----------|
-| `ppt169` | PPT 16:9 | `1280x720` | `0 0 1280 720` | 16:9 | Business presentations, meetings |
+| `ppt169` | PPT 16:9 | `1280x720` | `0 0 1280 720` | 16:9 | Business presentations, meetings, modern devices |
| `ppt43` | PPT 4:3 | `1024x768` | `0 0 1024 768` | 4:3 | Traditional projectors, academic talks |
| `xiaohongshu` | Xiaohongshu (RED) | `1242x1660` | `0 0 1242 1660` | 3:4 | Image-text sharing, knowledge posts |
| `moments` | WeChat Moments / IG | `1080x1080` | `0 0 1080 1080` | 1:1 | Square posters, brand showcases |
@@ -16,49 +15,20 @@
| `banner` | Landscape Banner | `1920x1080` | `0 0 1920 1080` | 16:9 | Web banners, digital screens |
| `a4` | A4 Print | `1240x1754` | `0 0 1240 1754` | 1:sqrt(2) | Print posters, flyers |
-The table lists canonical root spellings. New custom canvases likewise use
-`0 0 W H` with positive integer pixels. A fractional positive canvas is accepted
-only as compatible input for an imported custom PowerPoint slide size; it is not
-the default authoring form. All pages and internal Layout prototypes in one
-export use the same numeric canvas and stay within PowerPoint's supported slide
-range (914,400–51,206,400 EMU per side, approximately 96–5,376 SVG px).
+Custom canvases likewise use `0 0 W H` with positive integer pixels; a fractional positive canvas is accepted only as compatible input for an imported custom PowerPoint slide size. All pages and internal Layout prototypes in one export share the same numeric canvas within PowerPoint's supported slide range (914,400–51,206,400 EMU per side, about 96–5,376 SVG px). `ppt169` is exactly `1280x720`; same-ratio canvases such as `banner` are different coordinate systems.
-`ppt169` is the canonical PPT wide-screen canvas in this repo: `1280x720`, not any arbitrary 16:9 size. Same-ratio canvases such as `banner` (`1920x1080`) must be treated as different coordinate systems.
-
-## Format Selection Decision Tree
-
-```
-Content purpose?
-├── Presentation
-│ ├── Modern devices → PPT 16:9 (1280x720)
-│ └── Traditional devices → PPT 4:3 (1024x768)
-├── Social sharing
-│ ├── Xiaohongshu (RED) → 1242x1660
-│ ├── WeChat Moments / IG → 1080x1080
-│ └── Story / TikTok → 1080x1920
-└── Marketing materials
- ├── WeChat Article Header → 900x383
- ├── Banner → 1920x1080
- └── Print → 1240x1754
+```xml
+<svg viewBox="0 0 1280 720"> <!-- PPT 16:9 -->
+<svg viewBox="0 0 1080 1920"> <!-- Story -->
```
## Platform Keep-clear
-Canvas dimensions do not imply a title band, content topology, or recurring
-chrome. Reserve space only for a real output obstruction. For `story`, keep
-meaning-bearing text, identity, and calls to action within `y=120..1740` by
-default because common mobile story controls occupy the top and bottom; images,
-backgrounds, and nonessential texture may remain full bleed. An exact target-
-platform overlay guide or installed template overrides this advisory band.
+Canvas dimensions imply no title band, content topology, or recurring chrome; reserve space only for a real output obstruction. For `story`, keep meaning-bearing text, identity, and calls to action within `y=120..1740` by default because mobile story controls occupy the top and bottom; images, backgrounds, and texture may stay full bleed. An exact target-platform overlay guide or installed template overrides this advisory band.
## Typography Scale Start
-**Hard rule — normative owner**: This section owns the initial body-size anchor
-and sanity band for every registered or custom canvas. Strategist and Quick
-consume it directly. Confirm UI maintains an exact executable mirror and must
-not infer alternate canvas classes or values. All values are unitless SVG px.
-
-**PPT reading modes**:
+**Hard rule — normative owner**: this section owns the initial body-size anchor and sanity band for every registered or custom canvas. Strategist and Quick consume it directly; Confirm UI maintains an exact executable mirror and must not infer alternate canvas classes or values. Values are unitless SVG px.
| Canvas | Reading mode | Advisory body band | Initial body |
|---|---|---:|---:|
@@ -66,17 +36,11 @@ not infer alternate canvas classes or values. All values are unitless SVG px.
| `ppt169` / `ppt43` | `balanced` | 22–25 | 24 |
| `ppt169` / `ppt43` | `presentation` | 28–32 | 32 |
-**Non-PPT registered and custom canvases**: derive one effective canvas span
-from the canonical or custom `W x H`, then calculate the advisory band and
-initial body anchor:
+Non-PPT registered and custom canvases derive one effective span from `W x H`:
```text
-short = min(W, H)
-long = max(W, H)
-span = min(long, 3 * short)
-low = round(span * 0.025)
-start = round(span * 0.029)
-high = round(span * 0.033)
+short = min(W, H); long = max(W, H); span = min(long, 3 * short)
+low = round(span * 0.025); start = round(span * 0.029); high = round(span * 0.033)
```
| Canvas | Effective span | Advisory body band | Initial body |
@@ -84,25 +48,7 @@ high = round(span * 0.033)
| `wechat` | 900 | 23–30 | 26 |
| `moments` | 1080 | 27–36 | 31 |
| `xiaohongshu` | 1660 | 42–55 | 48 |
-| `story` | 1920 | 48–63 | 56 |
-| `banner` | 1920 | 48–63 | 56 |
+| `story` / `banner` | 1920 | 48–63 | 56 |
| `a4` | 1754 | 44–58 | 51 |
-**Default — starting anchor, not a floor (may override when confirmed identity,
-source fidelity, or target viewing conditions require it)**: Start from the
-table or formula, then resolve the complete role ramp and page density from the
-active content and delivery context. The advisory band only surfaces unusual
-values; falling outside it is not a validation failure. Apply the
-viewing-distance baseline in
-[`shared-standards-core.md`](./shared-standards-core.md) instead of silently
-shrinking a recurring role to make content fit.
-
-## ViewBox Examples
-
-```xml
-<svg width="1280" height="720" viewBox="0 0 1280 720"> <!-- PPT 16:9 -->
-<svg width="1242" height="1660" viewBox="0 0 1242 1660"> <!-- Xiaohongshu -->
-<svg width="1080" height="1080" viewBox="0 0 1080 1080"> <!-- WeChat Moments -->
-<svg width="1080" height="1920" viewBox="0 0 1080 1920"> <!-- Story -->
-<svg width="900" height="383" viewBox="0 0 900 383"> <!-- WeChat Article Header -->
-```
+**Default — starting anchor, not a floor (may override when confirmed identity, source fidelity, or target viewing conditions require it)**: start from the table or formula, then resolve the complete role ramp and page density from the content and delivery context. The band only surfaces unusual values; falling outside it is not a validation failure. Apply the viewing-distance baseline in [`shared-standards-core.md`](./shared-standards-core.md) instead of silently shrinking a recurring role to make content fit.
diff --git a/skills/ppt-master/references/executor-notes.md b/skills/ppt-master/references/executor-notes.md
index a4dd5ee5..3b4ee041 100644
--- a/skills/ppt-master/references/executor-notes.md
+++ b/skills/ppt-master/references/executor-notes.md
@@ -4,56 +4,35 @@
Conditional late-stage authority for generating or validating the complete speaker-notes document.
-**Trigger**: Default Generate loads this after the final quality check when the
-effective Speaker Notes outcome in `design_spec.md §I` is enabled. Quick
-Generate loads it after its final check when the current agent selected notes
-or narration in active context. A missing legacy outcome defaults to enabled.
-Narration requires notes; when notes are disabled, do not load this branch or
-create `notes/total.md`.
+**Trigger**: Default loads this after the final quality check when the effective Speaker Notes outcome in `design_spec.md §I` is enabled (a missing legacy outcome defaults to enabled); Quick loads it after its final check when the agent selected notes or narration. Narration requires notes; with notes disabled, do not load this branch or create `notes/total.md`.
## 1. Complete Speaker-notes Document
-Write the complete deck to `notes/total.md` in one batch for coherent transitions. Use `# <number>_<page_title>` per page and `---` between pages; only the heading is stripped before TTS.
+Write the whole deck to `notes/total.md` in one batch: `# <number>_<page_title>` per page, `---` between pages; only the heading is stripped before TTS. `notes_to_audio.py` reads the body verbatim, so write prose only — no list/bullet markup, stage markers, key-point labels, duration lines, or other metadata. Keep one language; spell out digits or symbols when literal TTS would sound wrong (Chinese "百分之六十八" rather than "68%").
-**Pre-SVG narration branch**: when `notes/total.md` already exists because the
-user supplied a final/literal script or Quick is directly delivering narrated
-video, validate it instead of regenerating it. Retain every word and segment of
-a final/literal script. Agent-authored Quick narration may be repaired only for
-final-SVG inconsistency and before audio generation. A `# Slide <number>`
-heading remains valid until Generate Step 7.1 resolves the authored roster.
+**Pre-SVG narration branch**: when `notes/total.md` already exists from a final/literal script or Quick direct narrated video, validate it instead of regenerating. Retain every word and segment of a final/literal script; agent-authored Quick narration may be repaired only for final-SVG inconsistency and before audio. A `# Slide <number>` heading remains valid until Generate Step 7.1 resolves the roster.
-**Pure spoken narration**: `notes_to_audio.py` reads the body verbatim. Write prose only; never add Markdown list/bullet markup, stage markers, key-point labels, duration lines, or other metadata.
-
-**Length follows content**: size natural sentences to semantic burden. Two to five is typical, not a cap; anchor pages may use less and dense pages more. Honor the active Design Spec or Quick context plus source rules. Duration is pacing guidance only: never pad, repeat, compress, or omit meaning to hit it.
+**Length follows content**: size natural sentences to semantic burden — two to five is typical, not a cap; anchor pages may use less and dense pages more. Duration is pacing guidance only: never pad, repeat, compress, or omit meaning to hit it.
## 2. Final-SVG Grounding and Coverage
-**Hard rule — the final SVG is the visible page authority**: read every finalized `svg_output/<slide>.svg` in slide order. Use the active plan/context and approved sources; never write from the outline or core message alone.
-
-Before drafting, internally inventory the visible title/subtitle and every information-bearing direct-root `<g id>`; structured placeholder content still counts. Coverage requires its unique claim, evidence, example, relationship, qualifier, or implication—not merely its label—to enter the narration.
+**Hard rule — the final SVG is the visible page authority**: read every finalized `svg_output/<slide>.svg` in slide order with the active plan/context and approved sources; never write from the outline or core message alone.
-For a pre-SVG narration branch, apply the same inventory in reverse: every
-independent visible claim or relationship must be supported by its script
-segment. Repair the visual page or return to planning for final/literal input;
-for agent-authored Quick narration, repair the narration before audio without
-inventing unsupported claims. Every spoken idea that requires orientation must
-likewise have a visible state or an explicit speech-only role in the active plan.
+Before drafting, internally inventory the visible title/subtitle and every information-bearing direct-root `<g id>` (structured placeholder content counts). Coverage means its unique claim, evidence, example, relationship, qualifier, or implication — not merely its label — enters the narration. For a pre-SVG script, apply the inventory in reverse: every independent visible claim is supported by its script segment; repair the visual page or return to planning for final/literal input, repair the narration before audio for agent-authored Quick narration, and give every spoken idea needing orientation a visible state or explicit speech-only role.
-- Text blocks, comparisons, and processes retain every independent fact or relationship; combine related short groups causally or comparatively.
-- Charts, tables, and KPIs state the takeaway, decisive values or trend, comparison basis, implication, and material uncertainty—not every axis, row, or cell.
-- Quotes retain the decisive clause, material attribution, and relevance. Explain semantic images or text-free diagrams only from the SVG plus locked plan/source; never infer facts from appearance.
-- Speak a source or page-local footer only when attribution, uncertainty, or qualification changes the argument. Omit backgrounds, decoration, repeated chrome, page numbers, and fixed Master/Layout atoms.
+- Text blocks, comparisons, and processes keep every independent fact or relationship; combine related short groups causally or comparatively.
+- Charts, tables, and KPIs state the takeaway, decisive values or trend, comparison basis, implication, and material uncertainty — not every axis, row, or cell.
+- Quotes keep the decisive clause, material attribution, and relevance. Explain semantic images or text-free diagrams only from the SVG plus plan/source; never infer facts from appearance.
+- Speak a source or footer only when attribution, uncertainty, or qualification changes the argument. Omit backgrounds, decoration, chrome, page numbers, and fixed Master/Layout atoms.
-Form one coherent argument in intended reading/reveal order: proposition → evidence or mechanism → implication or bridge. DOM order need not be speaking order. A sentence may cover related groups and a complex group may need several sentences, but no independent group may disappear to meet a sentence count. Keep the inventory internal: never vocalize IDs, positions, colors, icons, repetitive "this card shows" descriptions, or coverage markers.
+Form one coherent argument in intended reading/reveal order — proposition → evidence or mechanism → implication or bridge; DOM order need not be speaking order. A sentence may cover related groups and a complex group may need several sentences, but no independent group disappears to meet a count. Never vocalize IDs, positions, colors, icons, "this card shows" descriptions, or coverage markers.
## 3. Reading Mode and TTS
| `consumption_mode` | Notes emphasis |
|---|---|
-| `text` | Interpret and connect a self-contained page; synthesize every independent SVG information group rather than omitting it. |
-| `balanced` | Connect visible claim and evidence, explain the trade-off, and bridge forward. |
-| `presentation` | Carry reasoning, context, and supporting detail intentionally omitted from the sparse page. |
-
-Put transitions naturally in the opening sentence when useful; never label them. Keep one language. Spell out digits or symbols when literal TTS would sound wrong (for example, Chinese "百分之六十八" rather than "68%").
+| `text` | Interpret and connect a self-contained page; synthesize every independent information group rather than omitting it |
+| `balanced` | Connect visible claim and evidence, explain the trade-off, bridge forward |
+| `presentation` | Carry reasoning, context, and supporting detail intentionally omitted from the sparse page |
-After `notes/total.md` is complete, return to Generate Step 7.1 (Default) or `quick-generate.md` §4 (Quick); each route owns splitting and its success criterion.
+Put transitions naturally in the opening sentence; never label them. When `notes/total.md` is complete, return to Generate Step 7.1 (Default) or `quick-generate.md` §4 (Quick); each route owns splitting and its success criterion.
diff --git a/skills/ppt-master/references/executor-table.md b/skills/ppt-master/references/executor-table.md
index ffce2070..9245620e 100644
--- a/skills/ppt-master/references/executor-table.md
+++ b/skills/ppt-master/references/executor-table.md
@@ -4,7 +4,7 @@
Conditional Executor authority for semantic cell grids whose row/column intersections carry the information.
-**Trigger**: load when the page contains an actual cell-grid table or its primary reference uses `table/<key>`.
+**Trigger**: the page contains an actual cell-grid table or its primary reference uses `table/<key>`.
---
@@ -16,51 +16,22 @@ Conditional Executor authority for semantic cell grids whose row/column intersec
| Independent visual zones compare categories without a shared row/column grid | [`executor-structure.md`](./executor-structure.md) |
| Values determine marks, positions, lengths, areas, angles, radii, or color bins | [`executor-chart.md`](./executor-chart.md) |
-Graphical indicators may appear inside cells without changing the table family, provided the row/column grid still carries their meaning. A row of metric cards or two prose columns is a qualitative structure, not a table.
+**Hard rule — physical grid is insufficient**: a PowerPoint table object or rectangular drawing grid does not establish Table semantics. Dates or durations driving task-bar position and length route to `executor-chart.md`; qualitative stage/lane placement routes to `executor-structure.md`. Graphical indicators may sit inside cells while the grid still carries their meaning; a row of metric cards or two prose columns is a qualitative structure, not a table.
-**Hard rule — physical grid is insufficient**: A PowerPoint table object or a
-rectangular drawing grid does not establish Table semantics. Exact dates or
-durations that drive task-bar position and length route to
-[`executor-chart.md`](./executor-chart.md); qualitative stage/lane placement
-routes to [`executor-structure.md`](./executor-structure.md).
-
-When a `table/<key>` primary reference exists, [`executor-visualization.md`](./executor-visualization.md) owns resolution and flexible adaptation. A custom cell grid follows this branch without loading a catalog SVG.
-
-**Reference — not a constraint**: `record_table` covers heterogeneous record ×
-field grids; `metric_table` covers entity × KPI scanning;
-`comparison_matrix` covers heterogeneous criterion × alternative facts;
-`feature_matrix` covers capability states; `rating_matrix` covers one repeated
-ordinal scale; and `hierarchical_table` covers grouped/indented rows with detail
-and totals. These keys separate recurring cell grammars without changing the
-shared row/column information-model boundary.
+With a `table/<key>` primary reference, [`executor-visualization.md`](./executor-visualization.md) owns resolution and adaptation; a custom grid follows this branch without a catalog SVG. Catalog keys (`record_table` record × field, `metric_table` entity × KPI, `comparison_matrix` criterion × alternative, `feature_matrix` capability states, `rating_matrix` one repeated ordinal scale, `hierarchical_table` grouped rows with detail and totals) separate recurring cell grammars without changing this boundary.
---
## 2. Grid Construction
-**Hard rule — grid before decoration**: establish the complete logical grid before drawing fills, borders, badges, or other cell treatment.
-
-1. Resolve column count, row count, header rows, row labels, summaries, and any rectangular visual spans from the authoritative content.
-2. Allocate column widths and row heights from semantic weight and real text/data fit; do not default to equal columns when labels or values differ materially.
-3. Place every cell value, unit, qualifier, status, and source-bearing note in its correct intersection.
-4. Apply alignment consistently by content role, including comparable numeric alignment and stable header/body hierarchy.
-5. Add rules, fills, banding, highlights, and in-cell indicators only after the grid reads correctly in plain form.
-6. For a `<object-key>=yes` table, project the finished grid into the JSON in the same edit: `row_heights`, header fill / text / bold / alignment, whole-row or whole-column fills, first-column emphasis, padding, and per-side `borders` mirroring the drawn rules; a font size plus a uniform border is not a projection. A graphical cell (inset badge, colored chip, mini bar) cannot be expressed by `a:tbl`: return that object to `Native-ready=no`.
+**Hard rule — grid before decoration**: establish the complete logical grid before fills, borders, badges, or other cell treatment: (1) resolve column/row counts, header rows, row labels, summaries, and rectangular spans from the content; (2) allocate widths and heights from semantic weight and real text/data fit — no default equal columns when labels or values differ materially; (3) place every value, unit, qualifier, status, and source note in its intersection; (4) align by content role with comparable numeric alignment and stable header/body hierarchy; (5) add rules, fills, banding, highlights, and in-cell indicators only after the grid reads correctly plain; (6) for a `<object-key>=yes` table, project the finished grid into the JSON in the same edit — `row_heights`, header fill/text/bold/alignment, whole-row or whole-column fills, first-column emphasis, padding, and per-side `borders` mirroring the drawn rules; a font size plus a uniform border is not a projection, and a graphical cell (inset badge, colored chip, mini bar) cannot be expressed by `a:tbl`, so return that object to `Native-ready=no`.
-**Per-cell completeness**: never drop a row, column, summary, footnote, unit, or qualifier to imitate a lighter catalog preview. Reflow text, widen the affected column, rebalance adjacent columns, or increase row height while preserving the active page's information contract and [`executor-base.md`](./executor-base.md) typography bounds.
+**Per-cell completeness**: never drop a row, column, summary, footnote, unit, or qualifier to imitate a lighter catalog preview; reflow text, widen the column, rebalance neighbors, or increase row height within the page's information contract and [`executor-base.md`](./executor-base.md) typography bounds.
-**Visual span discipline**: merge only rectangular regions whose repeated boundaries would obscure an intended shared heading or group. Covered areas must not carry competing visible content. This branch owns the visible SVG geometry only; any native merge fields or payload topology belong exclusively to [`native-data-interface.md`](./native-data-interface.md).
-
-**Table chrome**: make header/body/summary roles distinguishable with the lightest sufficient combination of weight, fill, rule, and whitespace. Keep comparison scanning stable across the grid; decorative card treatment must not break row or column continuity.
+**Spans and chrome**: merge only rectangular regions whose repeated boundaries would obscure an intended shared heading or group, with no competing visible content in covered areas; native merge fields belong exclusively to [`native-data-interface.md`](./native-data-interface.md). Distinguish header/body/summary with the lightest sufficient weight, fill, rule, and whitespace; decorative card treatment must not break row or column continuity.
---
## 3. Object Boundary
-Treat each semantic table as one independently bounded page object even when it contains nested cell groups. Captions, source notes, and explanatory callouts may sit outside the grid when their ownership is visually explicit.
-
-Native readiness is decided per independent table object, not by the `table`
-family or numeric cells. Reuse its §IX/Quick semantic object key in the
-`Native-ready` map; only `<object-key>=yes` loads and follows
-[`native-data-interface.md`](./native-data-interface.md). All others remain
-ordinary Shape-first SVG geometry under [`executor-base.md`](./executor-base.md).
+Each semantic table is one independently bounded page object even with nested cell groups; captions, source notes, and callouts may sit outside the grid when ownership is visually explicit. Native readiness is decided per table object, not by family or numeric cells: reuse its §IX/Quick semantic object key in the `Native-ready` map; only `<object-key>=yes` loads [`native-data-interface.md`](./native-data-interface.md), everything else remains Shape-first SVG geometry.
diff --git a/skills/ppt-master/references/executor-visualization.md b/skills/ppt-master/references/executor-visualization.md
index 5b900be6..7d45b9e1 100644
--- a/skills/ppt-master/references/executor-visualization.md
+++ b/skills/ppt-master/references/executor-visualization.md
@@ -4,7 +4,7 @@
Conditional Executor authority for resolving one page-local Chart/Table `family/key` SVG reference and adapting it without turning the catalog preview into a page specification.
-**Trigger**: load only when Default `spec_lock.md page_visualizations` maps the current page to a canonical Chart/Table reference, a legacy `page_charts` row resolves to a live Chart/Table SVG, or Quick already selected one canonical Chart/Table reference in active context.
+**Trigger**: Default `spec_lock.md page_visualizations` maps the current page to a canonical Chart/Table reference, a legacy `page_charts` row resolves to a live Chart/Table SVG, or Quick already selected one canonical reference in active context.
---
@@ -17,30 +17,27 @@ Conditional Executor authority for resolving one page-local Chart/Table `family/
| Active profile | Resolve from |
|---|---|
-| Default Generate | Prefer the current `P<NN>: family/key` row from retained `spec_lock.md page_visualizations`, then read that page's `Page | Family | Template | Usage` row in Design Spec §VII; use a legacy `page_charts` row and its legacy §VII Usage only when the canonical row is absent |
-| Quick Generate | Use the canonical Chart/Table `family/key` and page-local purpose already selected in active context before SVG authoring |
+| Default Generate | The current `P<NN>: family/key` row in retained `spec_lock.md page_visualizations`, then that page's `Page \| Family \| Template \| Usage` row in Design Spec §VII; a legacy `page_charts` row and its §VII Usage only when the canonical row is absent |
+| Quick Generate | The canonical `family/key` and page-local purpose already selected in active context before SVG authoring |
-**Hard rule — one primary reference per page**: one page resolves at most one catalog SVG. The reference guides one dominant reusable Chart/Table information structure; secondary objects are authored from their actual content through the applicable branch without loading another catalog SVG. Independent Chart/Table children retain their §IX or Quick semantic object keys for scoped native/verification contracts.
-
-**Mandatory — shared resolution**: resolve the selected value through `visualization_recall.py validate`; consume its canonical `reference` and `path` instead of guessing a family or constructing a path from the input string. Add `--legacy-bare` only for a value read from legacy `page_charts`.
+**Mandatory — shared resolution**: resolve through `visualization_recall.py validate` and consume its canonical `reference` and `path`; never guess a family or build a path from the input string. Add `--legacy-bare` only for a value read from legacy `page_charts`.
```bash
python3 ${SKILL_DIR}/scripts/visualization_recall.py validate <family/key>
-python3 ${SKILL_DIR}/scripts/visualization_recall.py validate \
- --legacy-bare <legacy-key>
+python3 ${SKILL_DIR}/scripts/visualization_recall.py validate --legacy-bare <legacy-key>
```
-New `page_visualizations` and Quick selections accept only canonical `chart/<key>` or `table/<key>`. A bare key is read-compatible only from legacy `page_charts`: it must resolve unambiguously to one live Chart/Table entry, otherwise stop for upstream correction. If canonical and legacy rows both exist for one page, stop on the duplicate contract even when both resolve to the same SVG.
+**Hard rule — one primary reference per page**: one page resolves at most one catalog SVG, guiding one dominant reusable Chart/Table structure; secondary objects are authored from their content through the applicable branch without another catalog SVG, keeping their §IX or Quick object keys for native/verification contracts. New `page_visualizations` and Quick selections accept only canonical `chart/<key>` or `table/<key>`; a bare key is read-compatible only from legacy `page_charts` and must resolve unambiguously, otherwise stop for upstream correction. Canonical and legacy rows for one page stop on the duplicate contract even when both resolve to the same SVG.
-**Legacy Structure boundary**: a retired Structure bare key is semantic intent, not a live visualization reference. Do not resolve it to an SVG or load this branch; recover the qualitative relationship from §IX and apply [`executor-structure.md`](./executor-structure.md) when the mandatory per-page Structure decision is yes. If §IX lacks enough meaning, return upstream for Design Spec repair.
+**Legacy Structure boundary**: a retired Structure bare key is semantic intent, not a reference — do not resolve it or load this branch; recover the relationship from §IX and apply [`executor-structure.md`](./executor-structure.md) when the per-page Structure decision is yes, or return upstream when §IX lacks meaning.
-Read the resolver-returned SVG once before its first use in the valid active context and reuse that reading until a known file change or context invalidation. Do not manually reopen indexes or scan family directories during Executor realization; the planning owner already reviewed the complete live registries, and the shared resolver owns canonical path resolution here.
+Read the resolver-returned SVG once before first use and reuse that reading until a known file change; do not reopen indexes or scan family directories during realization — the planning owner already reviewed the live registries.
---
## 2. Flexible Page-local Adaptation
-**Hard rule — reference, not lock**: the selected SVG is a page-local construction reference. The current §IX page block or Quick page decision plus authoritative source content owns the final information structure; the preview does not lock visualization type, geometry, styling, or native replacement.
+**Hard rule — reference, not lock**: the selected SVG is a page-local construction reference. The §IX page block or Quick page decision plus authoritative content owns the final information structure; the preview locks no visualization type, geometry, styling, or native replacement.
| Preserve | Adapt freely |
|---|---|
@@ -48,10 +45,6 @@ Read the resolver-returned SVG once before its first use in the valid active con
| Selected Usage and valid information encoding | Borrow, recombine, simplify, extend, or depart when another realization preserves the information more faithfully |
| Complete page content obligations | Palette, typography, container treatment, effects, background, and page chrome from project authorities |
-**Forbidden — preview substitution**:
-
-- Do not copy sample labels/data as content.
-- Do not omit authoritative content to fit lighter preview density.
-- Do not spread one page's reference to another page without its own mapping.
+**Forbidden — preview substitution**: copying sample labels/data as content; omitting authoritative content to fit lighter preview density; spreading one page's reference to another page without its own mapping.
-The namespace selects a reference registry and construction authority only; it does not assert native readiness or mirror a source PowerPoint object type. An imported table used to place duration-driven bars remains Chart semantics. Native eligibility is an independent per-object decision owned by [`native-data-interface.md`](./native-data-interface.md).
+The namespace selects a registry and construction authority only; it asserts no native readiness and mirrors no source PowerPoint object type — an imported table used to place duration-driven bars remains Chart semantics. Native eligibility is an independent per-object decision owned by [`native-data-interface.md`](./native-data-interface.md).
diff --git a/skills/ppt-master/references/native-hyperlinks.md b/skills/ppt-master/references/native-hyperlinks.md
index dc638f90..ec4fd807 100644
--- a/skills/ppt-master/references/native-hyperlinks.md
+++ b/skills/ppt-master/references/native-hyperlinks.md
@@ -1,23 +1,19 @@
# Native Hyperlink Specification
-Shared authoring contract for PowerPoint-native click hyperlinks on complete
-objects and inline text runs.
+Authoring contract for PowerPoint-native click hyperlinks on complete objects and inline text runs.
## 1. Trigger and Ownership
-**Trigger**: A user instruction, source fact, or page plan requires an external
-destination or a jump to another slide in the same deck.
+**Trigger**: a user instruction, source fact, or page plan requires an external destination or a jump to another slide in the same deck.
| Layer | Ownership |
|---|---|
-| Default Strategist | Record the linked text/object intent and exact target in the applicable §IX page block; never invent or normalize an unknown destination |
+| Default Strategist | Record the linked text/object intent and exact target in the §IX page block; never invent or normalize an unknown destination |
| Default Executor | Choose the whole-object or inline carrier and author the canonical SVG anchor |
-| Active Quick context | Perform both content and authoring responsibilities directly |
+| Active Quick context | Both responsibilities directly |
| SVG-to-PPTX exporter | Validate the target, create the native relationship, and attach the click action |
-**Hard rule — page content only**: Hyperlinks are not a confirmation field,
-resource, manifest, or `spec_lock.md` entry. Missing or ambiguous targets return
-upstream; do not substitute a search result or guessed URL.
+**Hard rule — page content only**: hyperlinks are not a confirmation field, resource, manifest, or `spec_lock.md` entry. Missing or ambiguous targets return upstream; never substitute a search result or guessed URL.
---
@@ -30,69 +26,26 @@ upstream; do not substitute a search result or guessed URL.
| Same-deck jump | `href="#slide-3"` using the 1-based final slide roster |
| Imported shape-plus-run conflict | Importer-only `data-pptx-shape-hyperlink="..."` on the logical `<g>`, with standard inline anchors retained inside |
-**Hard rule — one target syntax**: Author SVG 2 `href`. Import may read legacy
-`xlink:href`, but generated SVG never writes both. Same-deck destinations use
-the exact `#slide-N` form and must resolve inside the final roster. External
-destinations are absolute URIs with an explicit scheme; percent-encode spaces.
-Relative paths, arbitrary fragments, filesystem paths, and `data:`, `file:`,
-`javascript:`, or `vbscript:` destinations fail closed.
-
-**Hard rule — inline run**: Put visible text in one or more `<tspan>` children
-inside the anchor. The anchor and its descendants own no `x`, `y`, `dx`, or
-`dy`; line positioning belongs to the enclosing line `<tspan>`. A linked inline
-formula uses one leaf formula `<tspan>` inside the anchor and retains its native
-math contract.
-
-**Hard rule — whole-object hit area**: Wrap at least one visible SVG element;
-do not put direct text or a bare `<tspan>` in a shape anchor. A multi-object
-anchor links each exported leaf object. Include an explicit background shape
-when gaps inside a button or card must also be clickable.
-
-Ordinary entrance, emphasis, motion-path, exit, and Morph animation may target
-an outer top-level `<g>`. A hyperlink-bearing group cannot also serve as an
-interactive `trigger_shape`; use a separate trigger so one click has one owner.
-
-**Forbidden — ambiguous ownership**: Do not nest `<a>` elements or place an
-anchor inside `defs`, metadata, geometry-detail, or a native-replacement
-subtree. A complete block formula or native Chart/Table marker may be wrapped
-as one whole object; its preview descendants may not contain another anchor.
-
-**Forbidden — authored transport metadata**: Never author
-`data-pptx-shape-hyperlink`. PPTX import uses it only when one source shape has
-both a whole-shape click and descendant run links, because standard SVG cannot
-nest their two anchors. Checker/export accept it only on that logical group
-with at least one real inline `<a>` descendant, then restore both native click
-levels. Every ordinary whole-object link uses the standard outer `<a href>`.
+**Hard rule — one target syntax**: author SVG 2 `href` (import may read legacy `xlink:href`; generated SVG never writes both). Same-deck destinations use the exact `#slide-N` form inside the final roster. External destinations are absolute URIs with an explicit scheme and percent-encoded spaces; relative paths, arbitrary fragments, filesystem paths, and `data:` / `file:` / `javascript:` / `vbscript:` fail closed.
+
+**Hard rule — inline run**: visible text sits in one or more `<tspan>` children inside the anchor; the anchor and its descendants own no `x`, `y`, `dx`, or `dy` — line positioning belongs to the enclosing line `<tspan>`. A linked inline formula is one leaf formula `<tspan>` inside the anchor and keeps its native math contract.
+
+**Hard rule — whole-object hit area**: wrap at least one visible SVG element; no direct text or bare `<tspan>` in a shape anchor. A multi-object anchor links each exported leaf object; include an explicit background shape when gaps inside a button or card must also be clickable. Ordinary animation may target an outer top-level `<g>`, but a hyperlink-bearing group cannot also be an interactive `trigger_shape` — one click has one owner.
+
+**Forbidden**: nested `<a>`; an anchor inside `defs`, metadata, geometry-detail, or a native-replacement subtree (a complete block formula or Chart/Table marker may be wrapped as one whole object, but its preview may not contain another anchor); authored `data-pptx-shape-hyperlink`, which PPTX import writes only when one source shape has both a whole-shape click and descendant run links, and which checker/export accept only on that logical group with at least one real inline `<a>` descendant.
---
## 3. Native Result and Preservation
-| Carrier / target | Native result |
-|---|---|
-| Inline external link | `a:rPr/a:hlinkClick` plus an external hyperlink relationship |
-| Whole-object external link | `p:cNvPr/a:hlinkClick` on each clickable leaf plus one shared external relationship |
-| Inline or whole-object slide jump | The same click carrier plus an internal slide relationship and `ppaction://hlinksldjump` |
-| Supported PPTX import | Reconstruct the same canonical SVG `<a href>` form |
-
-**Hard rule — Edit Native PPTX preservation**: Unchanged round-trip pages keep
-their hyperlink XML and relationships byte-for-byte. External links are
-preserved. With a `page_plan.json`, a same-deck jump is retargeted only when
-its source target maps unambiguously to one output page; omitted or repeated
-targets make `svg_to_pptx.py --roundtrip` fail instead of linking to an orphan
-or wrong slide. New links on an edited page use this SVG authoring contract.
+Inline links become `a:rPr/a:hlinkClick`, whole-object links `p:cNvPr/a:hlinkClick` on each clickable leaf, each with an external hyperlink relationship; slide jumps add an internal slide relationship and `ppaction://hlinksldjump`. Supported PPTX import reconstructs the same canonical `<a href>` form.
+
+**Hard rule — Edit Native PPTX preservation**: unchanged round-trip pages keep their hyperlink XML and relationships byte-for-byte; external links are preserved. With a `page_plan.json`, a same-deck jump is retargeted only when its source target maps unambiguously to one output page — omitted or repeated targets make `svg_to_pptx.py --roundtrip` fail rather than link to an orphan or wrong slide. New links on an edited page use this contract.
---
## 4. Exclusions and Validation
-**Forbidden — unsupported action settings**: Mouse-over links, custom shows,
-first/last/next/previous navigation actions, program or macro execution, OLE or
-file actions, and arbitrary `ppaction://` or relationship injection are outside
-this contract. An `actionButton*` preset remains visual geometry until wrapped
-in an ordinary supported hyperlink anchor.
+**Forbidden — unsupported action settings**: mouse-over links, custom shows, first/last/next/previous navigation, program or macro execution, OLE or file actions, and arbitrary `ppaction://` or relationship injection. An `actionButton*` preset stays visual geometry until wrapped in a supported anchor.
-**Validation**: The final SVG checker validates carrier structure, target
-syntax, and slide range. Export validates relationship type/mode and final
-presentation-roster membership. Unsupported PPTX click actions produce an
-import diagnostic; strict import fails rather than fabricating an SVG link.
+**Validation**: the final SVG checker validates carrier structure, target syntax, and slide range; export validates relationship type/mode and final roster membership. Unsupported PPTX click actions produce an import diagnostic; strict import fails rather than fabricating an SVG link.
diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.json
index 58273d66..91059698 100644
--- a/skills/ppt-master/scripts/prompt_audit_manifest.json
+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json
@@ -21,10 +21,10 @@
"skills/ppt-master/references/executor-base.md": 8000,
"skills/ppt-master/references/executor-structured.md": 5500,
"skills/ppt-master/references/executor-chart.md": 1750,
- "skills/ppt-master/references/executor-visualization.md": 1250,
+ "skills/ppt-master/references/executor-visualization.md": 1000,
"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-table.md": 1000,
"skills/ppt-master/references/executor-image.md": 2000,
"skills/ppt-master/references/executor-web-image.md": 750,
"skills/ppt-master/references/executor-notes.md": 1000,
@@ -47,7 +47,9 @@
"skills/ppt-master/references/confirm-surface.md": 3000,
"skills/ppt-master/references/video-design.md": 2500,
"skills/ppt-master/references/native-formula.md": 1500,
- "skills/ppt-master/references/semantic-svg.md": 1500
+ "skills/ppt-master/references/semantic-svg.md": 1500,
+ "skills/ppt-master/references/native-hyperlinks.md": 1250,
+ "skills/ppt-master/references/canvas-formats.md": 1250
},
"load_sets": {
"bootstrap.routing": {
@@ -1949,7 +1951,7 @@
{
"path": "skills/ppt-master/references/executor-visualization.md",
"role": "compatibility",
- "fingerprint": "055ab59c533e",
+ "fingerprint": "84c1c8a6bec5",
"reason": "This site documents a legacy or omission compatibility boundary."
},
{
@@ -2081,7 +2083,7 @@
{
"path": "skills/ppt-master/references/executor-visualization.md",
"role": "consumer",
- "fingerprint": "8b173848afa7",
+ "fingerprint": "35b3aa28bcad",
"reason": "This consumer needs the field contract for deterministic execution."
},
{