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): rename four overloaded terms across the runtime corpus
hugohe32dadc99d16d7
diff --git a/docs/rules/ownership.md b/docs/rules/ownership.mdindex a30f2964..0b51b07b 100644--- a/docs/rules/ownership.md+++ b/docs/rules/ownership.md@@ -18,7 +18,7 @@ rule about it, and keep each tier's rules in its own role's files.|---|---|---|---|| Plan-only | Needs a prepared file before authoring; holds only across the whole roster; needs one user confirmation; or comes from source semantics | Contract, canvas, page count, roster ids/order, `page_rhythm`, identity anchors (color, type, spacing, icons, style, mode), resources, per-page content, facts, semantic units and their relationships | Execution never reopens or substitutes it; a misfit returns upstream || Execution-only | Judged only with the objects on the canvas | Carrier mix, geometry and native contours, composition, coordinates, spacing, hierarchy treatment, effects, per-page icon and image treatment, wrapping | Plan writes no detail here, not even as advice |-| Reference (grey zone) | Useful as a first sketch, decidable either way | Macro composition and focus, continuity and motif, cover/closing composition, Chart/Table `family/key`, image `Layout pattern`, motion suggestions | Plan writes a starting sketch; Executor adjusts or replaces it freely for the page's purpose, with no upstream repair and no stated reason. It carries no binding semantics — anything that must hold is written in a plan-only field. It binds only when labeled `(binding)` because the user, a template, or a resource contract requires that property (explicit *must* / *only* / *exactly* / *verbatim*); Executor then follows it literally |+| Reference (grey zone) | Useful as a first sketch, decidable either way | Macro composition and focus, continuity and motif, cover/closing composition, Chart/Table `family/key`, image `Image pattern`, motion suggestions | Plan writes a starting sketch; Executor adjusts or replaces it freely for the page's purpose, with no upstream repair and no stated reason. It carries no binding semantics — anything that must hold is written in a plan-only field. It binds only when labeled `(binding)` because the user, a template, or a resource contract requires that property (explicit *must* / *only* / *exactly* / *verbatim*); Executor then follows it literally |Depth test: one plan given to two competent Executors yields the same contentwith different looks — converging looks mean the plan wrote execution,@@ -31,7 +31,7 @@ a capability exists before choosing among capabilities; otherwise a load triggercircularly depends on a choice made without that capability. The always-readcore of the authoring role therefore carries the recall of every constructioncapability — the everyday device menu and effects, the complete preset-vocabulary, the Structure decision, and one routing row per deeper module —+vocabulary, the topology decision, and one routing row per deeper module —while the deeper module itself (effects beyond the everyday block, native-shapeauthoring, relationship grammar and topology assembly, and the rarer formula,hyperlink, chart/table, structured-template, video, animation, and web-imagediff --git a/docs/rules/prompt-layers.md b/docs/rules/prompt-layers.mdindex 9b7b94e3..17deab4d 100644--- a/docs/rules/prompt-layers.md+++ b/docs/rules/prompt-layers.md@@ -48,7 +48,7 @@ case is what makes a rule hard to recall at authoring time.**Hard rule — one owner, pointers elsewhere**: a rule is stated in full in exactly one file. Every other file that needs it carries a pointer naming the file and section, not a paraphrase. A paraphrase is a second owner: it drifts, contradicts the original after the next edit, and doubles the tokens. The cross-file duplicate check in `prompt_audit.py` catches verbatim copies only; paraphrases are caught by reading.-**Hard rule — planning reads everything, execution loads on triggers, the core keeps the recall**: the planning role reads its complete bundle. The execution core (`executor-base.md`, `shared-standards-core.md`, `semantic-svg.md`, the preset vocabulary, plus the confirmed mode / visual-style catalog file when the confirmation points to one — a `custom` with `*_references` reads only those files, a `custom` without references reads none) stays resident and carries the everyday forms and a recall of every deeper module — device menu, everyday effects, preset families, the Structure decision — so a capability is known before its file is opened. The preset vocabulary stays resident with the core so contours are known before selection. Each deeper module (effects, native-shape authoring, relationship grammar and topology, images, charts/tables, formula, hyperlink, structured templates, video, animation, web-image attribution) loads on one observable trigger — named in the core's routing table for construction modules, or in the owning route step for video, animation, and post-processing stages — evaluated once over the whole roster before P01 so that reading stays out of the page loop, or at the page that first reaches an unforeseen capability; it is read completely and stays for the run, and the page's module line records what the page uses. A module with no recall in the core is the failure where a capability not in context is never used.+**Hard rule — planning reads everything, execution loads on triggers, the core keeps the recall**: the planning role reads its complete bundle. The execution core (`executor-base.md`, `shared-standards-core.md`, `semantic-svg.md`, the preset vocabulary, plus the confirmed mode / visual-style catalog file when the confirmation points to one — a `custom` with `*_references` reads only those files, a `custom` without references reads none) stays resident and carries the everyday forms and a recall of every deeper module — device menu, everyday effects, preset families, the topology decision — so a capability is known before its file is opened. The preset vocabulary stays resident with the core so contours are known before selection. Each deeper module (effects, native-shape authoring, relationship grammar and topology, images, charts/tables, formula, hyperlink, structured templates, video, animation, web-image attribution) loads on one observable trigger — named in the core's routing table for construction modules, or in the owning route step for video, animation, and post-processing stages — evaluated once over the whole roster before P01 so that reading stays out of the page loop, or at the page that first reaches an unforeseen capability; it is read completely and stays for the run, and the page's module line records what the page uses. A module with no recall in the core is the failure where a capability not in context is never used.---diff --git a/docs/rules/rule-owners.md b/docs/rules/rule-owners.mdindex fe5446e7..36bd1489 100644--- a/docs/rules/rule-owners.md+++ b/docs/rules/rule-owners.md@@ -41,4 +41,13 @@## 4. Term renames (recorded here when decided)-No rename has been decided yet. Candidates and the files each would touch are listed in the maintainer notes for the 2026-09 readability pass; a rename enters this table only with its complete file list and the code it changes.+Decided 2026-09-02 and applied in one sweep. Each row names the old term, the new term, and every file the rename touched; a later file that still uses the old term is a defect.++| Old term | New term | Meaning kept | Files touched |+|---|---|---|---|+| §IX `Layout` line | `Composition` | The page's macro-composition Reference | `templates/design_spec_reference.md`, `templates/scaffolds/design_spec.md`, `references/plan-core.md` §4, `references/strategist.md` §4, `references/executor-base.md` §2.1, `SKILL.md` Vocabulary |+| §VIII `Layout pattern` column | `Image pattern` | One image-composition suggestion per placed row | `templates/design_spec_reference.md`, `templates/scaffolds/design_spec.md`, `templates/spec_lock_reference.md`, `references/image-base.md`, `references/svg-image-embedding.md`, `references/strategist-image.md`, `references/strategist.md`, `references/image-generator.md`, `references/executor-image.md`, `scripts/svg_quality/checker.py` (reads the new column, falls back to the old spelling), `scripts/docs/advanced-image-motion-smoke.md`, `docs/technical-design.md`, `docs/zh/technical-design.md`, `ownership.md`, `SKILL.md` Vocabulary |+| Structure decision (`Structure=yes|no`) | topology decision (`topology=yes|no`) | The per-page yes/no on whether geometry carries `Relationships` | `references/executor-base.md`, `references/executor-structure.md`, `references/topology-assembly.md`, `references/native-shape-authoring.md`, `references/plan-core.md` §5, `workflows/profiles/quick-generate.md`, `workflows/stages/resume-execute.md`, `scripts/prompt_audit_manifest.json`, `ownership.md`, `prompt-layers.md`, `SKILL.md` Vocabulary |+| "content carrier" (second sense of carrier) | carrier (single sense); `data-pptx-carrier` is an attribute, not the term | What a page unit sits in | `SKILL.md` Vocabulary, `scripts/pptx_shapes/data/presetShapeSemantics.json` |++`Layout` now means only a PowerPoint Layout under a Master or the Layout template kind. `pptx_structure.mode` and the retired §VII `Structure` catalog key are unchanged.diff --git a/docs/technical-design.md b/docs/technical-design.mdindex 6ce4ec98..8909f3b9 100644--- a/docs/technical-design.md+++ b/docs/technical-design.md@@ -670,7 +670,7 @@ Whenever the image branch is active, its compact placement vocabulary in [`refer**Why the catalog uses two-level IDs.** Handles such as `#P2-01` and `#M1-01` expose both composition responsibility and the local family, so combinations remain readable. The final number follows current browse order rather than preserving historical numbering. These are prompt vocabulary, not runtime effect codes: the Executor realizes the accompanying composition guidance, and the exporter does not map an ID to fixed DrawingML.-**Why composition intent flows through Strategist's resource list.** The `Layout pattern` column in `§VIII Image Resource List` carries one non-empty free-form suggestion and may optionally cite hierarchical ids from the library; an image-led `adaptive` row also names the page job the image resolves, so the composition reaching Executor arrives with the reason it was chosen. `Crop Policy` separately records `adaptive` or `no-crop`. This preserves a useful starting point across session re-entry without making any catalog entry or id mandatory. Executor may resize, reflow, reposition, rebalance, replace the suggestion, or use another composition when that communicates better. Resource identity, must-use/content obligations, `no-crop`, and explicit user/template constraints remain binding; only changing those requires an upstream Design Spec update.+**Why composition intent flows through Strategist's resource list.** The `Image pattern` column in `§VIII Image Resource List` carries one non-empty free-form suggestion and may optionally cite hierarchical ids from the library; an image-led `adaptive` row also names the page job the image resolves, so the composition reaching Executor arrives with the reason it was chosen. `Crop Policy` separately records `adaptive` or `no-crop`. This preserves a useful starting point across session re-entry without making any catalog entry or id mandatory. Executor may resize, reflow, reposition, rebalance, replace the suggestion, or use another composition when that communicates better. Resource identity, must-use/content obligations, `no-crop`, and explicit user/template constraints remain binding; only changing those requires an upstream Design Spec update.**Why true hard constraints stay upstream.** Cross-cutting SVG authoring and PPTX-compatibility exceptions live in the authority set routed by [`shared-standards.md`](../skills/ppt-master/references/shared-standards.md). The layout patterns file points to that router rather than restating the contract, so each rule still has one owning module and no stale duplicate in the pattern catalog.diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.mdindex c4e477cc..2941858c 100644--- a/docs/zh/technical-design.md+++ b/docs/zh/technical-design.md@@ -567,7 +567,7 @@ Generate 路由会在加载流程前选定一份运行时权威:[`workflows/ge**为什么采用两级 id。** `#P2-01`、`#M1-01` 这类编号会同时暴露构图责任与局部家族,让组合一眼可读;末尾序号跟随当前浏览顺序,不承担历史编号兼容。它们只是提示词词汇,不是运行时 effect code:Executor 根据条目里的构图说明自由实现,导出器不会把某个 id 映射成固定 DrawingML。-**为什么构图意图走 Strategist 资源列表。** `§VIII 图片资源列表` 的 `Layout pattern` 列承载一句非空自由格式建议,也可以按需引用灵感库的两级编号;图片主导的 `adaptive` 行还会写出该图要解决的页面职能,使到达 Executor 的构图自带选它的理由;`Crop Policy` 独立记录 `adaptive` 或 `no-crop`。这让可用的构图起点通过 lock 投影在 session 重入后继续存在,但不要求使用编号。Executor 可以调整尺寸、位置、流向与权重,也可以替换建议或使用其他构图。资源身份、必用 / 内容义务、`no-crop` 和显式用户 / 模板约束仍具有约束力;只有改变这些边界才需要先更新 Design Spec。+**为什么构图意图走 Strategist 资源列表。** `§VIII 图片资源列表` 的 `Image pattern` 列承载一句非空自由格式建议,也可以按需引用灵感库的两级编号;图片主导的 `adaptive` 行还会写出该图要解决的页面职能,使到达 Executor 的构图自带选它的理由;`Crop Policy` 独立记录 `adaptive` 或 `no-crop`。这让可用的构图起点通过 lock 投影在 session 重入后继续存在,但不要求使用编号。Executor 可以调整尺寸、位置、流向与权重,也可以替换建议或使用其他构图。资源身份、必用 / 内容义务、`no-crop` 和显式用户 / 模板约束仍具有约束力;只有改变这些边界才需要先更新 Design Spec。**为什么真正的硬约束留在上游。** 跨切的 SVG 创作与 PPTX 兼容性例外属于 [`shared-standards.md`](../../skills/ppt-master/references/shared-standards.md) 路由的权威集。版式词表只指向该路由,不再复述合同;每条规则仍只有一个所属模块,词表里也不会留下过期副本。diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.mdindex d31311df..5ca16e8a 100644--- a/skills/ppt-master/SKILL.md+++ b/skills/ppt-master/SKILL.md@@ -79,11 +79,13 @@ more than one sense, the sense is named here and the files say which one.|---|---|| **Reference** (label) | A starting sketch the executing role adjusts or replaces freely, with no upstream repair or stated reason; `(binding)` after a field label removes that freedom || **Relationships** | The §IX line naming a page's semantic units and their source-stated `order` / `link` / `parent` / `membership` / `contrast` / `overlap`, or `none` |-| **Structure decision** | The per-page yes/no on whether geometry must carry the page's `Relationships`; unrelated to `pptx_structure.mode` |+| **Topology decision** | The per-page yes/no on whether geometry must carry the page's `Relationships` (`topology=yes` / `topology=no`); unrelated to `pptx_structure.mode` || **`pptx_structure.mode`** | `flat` (every object Slide-local) or `structured` (declared Master/Layout/slot metadata); a packaging route, never information structure |-| **Layout** | Three senses: the §IX `Layout` line (a Reference for macro composition); a PowerPoint Layout under a Master; the Layout template kind. `Layout pattern` is the §VIII image-composition suggestion |+| **Composition** | The §IX `Composition` line: a Reference for a page's macro composition, hierarchy, and focus |+| **Image pattern** | The §VIII column carrying one image-composition suggestion in ordinary words (optionally citing `#P`/`#M` ids) |+| **Layout** | A PowerPoint Layout under a Master, or the Layout template kind; never a page-composition sketch || **Device** | An everyday page carrier — card, band, icon-and-label, KPI tile, divider, quote block — recalled in the Executor's device menu |-| **Carrier** | Two senses: the content carrier a page unit sits in (a device, an image, native geometry), and the `data-pptx-carrier` child of a structured slot. The **carrier receipt** is the checker's per-page inventory of what was actually drawn |+| **Carrier** | What a page unit sits in: a device, an image, or native geometry; the family names are carrier and field, direction and sequence, grouping and ownership, emphasis and annotation. `data-pptx-carrier` is a structured-slot attribute, not this term. The **carrier receipt** is the checker's per-page inventory of what was actually drawn || **Page job** | What one page must do for the reader; the input every carrier, contour, and effect decision is judged against || **Page field** | One large surface, outline, aperture, or off-canvas contour that organizes zones instead of a card per unit || **Contour / preset / atom** | A contour is a shape's silhouette; a preset is one of the 187 Office `prst` contours drawn through `preset_shape_svg.py`; an atom is one object that compiles to one DrawingML shape |diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.mdindex 09fc364a..b1a407e2 100644--- a/skills/ppt-master/references/executor-base.md+++ b/skills/ppt-master/references/executor-base.md@@ -11,7 +11,7 @@ Always-loaded Executor authority for flat SVG page authoring, shared by Default| Any value-driven geometry, including a chart-family reference, mini chart, sparkline, inset, or small multiple | [`executor-chart.md`](./executor-chart.md) || Any semantic cell grid, including a table-family reference | [`executor-table.md`](./executor-table.md) || A page uses a preset pattern fill, or an independent Chart/Table object is resolved as `<object-key>=yes` | [`native-data-interface.md`](./native-data-interface.md) before emitting the pattern or replacement metadata |-| The per-page Structure decision is `yes` for the first time | [`executor-structure.md`](./executor-structure.md) + [`topology-assembly.md`](./topology-assembly.md) |+| The per-page topology decision is `yes` for the first time | [`executor-structure.md`](./executor-structure.md) + [`topology-assembly.md`](./topology-assembly.md) || A page's contour reaches beyond rectangle, rounded rectangle, circle, ellipse, and line — an inflected carrier (snipped or one-sided rounded rectangle, plaque, bevel, polygon, pie / arc / donut, frame, corner, folded corner, trapezoid, parallelogram) as much as a relationship symbol (block arrow, chevron, callout, flowchart node, banner, star, bracket, connector) — or needs a Boolean / freeform decision | [`native-shape-authoring.md`](./native-shape-authoring.md), read completely (the preset vocabulary is already resident) || A page's visual job reaches beyond the everyday block below — faux glass, constructed styles (hand-drawn, ink, riso, pixel, halftone, paper-cut, facets, gradient ribbon), gradient stroke, text picture/texture fill, gauge / sunburst / explicit arc geometry, freeform curves, transforms beyond rotate, or an unsupported effect needing a native-safe alternative | [`svg-effects.md`](./svg-effects.md) || Any image | [`executor-image.md`](./executor-image.md) + [`image-layout-spec.md`](./image-layout-spec.md) + [`image-layout-patterns.md`](./image-layout-patterns.md) + [`svg-image-embedding.md`](./svg-image-embedding.md) |@@ -183,7 +183,7 @@ Executor receives the plan and builds on it: Default reads the retained `design_Missing or unresolved material stops execution and returns upstream. Never search, generate, download, sync, invent, or substitute it.-**Reference — planning sketches are adjusted freely**: §V/§IX `Layout`, cover/closing composition, capability recommendations, §III motif direction, Chart/Table `family/key` references, §VIII image-layout patterns, and Motion suggestions are starting sketches. Adjust or replace each for the page's purpose, with no upstream repair or stated reason; they carry no binding semantics. A `(binding)` field is followed literally. Executor owns final carrier choice, page-scale composition, information-preserving visualization, geometry, spacing, coordinates, native construction, and effects.+**Reference — planning sketches are adjusted freely**: §V and the §IX `Composition` line, cover/closing composition, capability recommendations, §III motif direction, Chart/Table `family/key` references, §VIII image-layout patterns, and Motion suggestions are starting sketches. Adjust or replace each for the page's purpose, with no upstream repair or stated reason; they carry no binding semantics. A `(binding)` field is followed literally. Executor owns final carrier choice, page-scale composition, information-preserving visualization, geometry, spacing, coordinates, native construction, and effects.**Hard rule — content vs expression**: §IX owns each page's semantic content — complete preferred wording and block texture at `complete` depth, a short block list at `brief`. Its wording is not verbatim unless marked literal.@@ -231,7 +231,7 @@ With notes disabled, never omit required content on the assumption that notes ca**Default — authored texture (may override when information-equivalent)**: start from each §IX block's written texture (`complete`) or expand its block phrasing (`brief`) under the reading mode. Keep prose where continuity carries cause, argument, narrative, qualification, or emphasis. Use bullets or keywords only for genuinely parallel or ordered material or a clearer information-equivalent structure. A list that is merely easier to lay out, or a template slot that expects a list, is not a reason: widen, reflow, or drop the card before converting prose to fill it. The locked mode shapes voice and register, not §IX's authored titles or page order; a user-authored topic label stays a label even when the mode favors assertions. Block-level phrasing applies *within* the page's `page_rhythm` density, not against it.-**Step 4 — Structure decision (Mandatory)**: before drawing, read the page's §IX `Relationships` (Quick: the transient relationship statement), then `Visualization` and `Content`, and decide whether geometry must carry that qualitative `order`, `link`, `parent`, `membership`, `contrast`, or `overlap` relationship. Decide from the semantic relationship alone; a suggested carrier, topology, or composition does not decide it, and a Chart/Table reference never substitutes. `no` stays on this base path. `yes` applies the grammar of [`executor-structure.md`](./executor-structure.md) and [`topology-assembly.md`](./topology-assembly.md) (routing table) and keeps the relationship statement in active page context with no catalog reference, lock row, or artifact. A missing line is a Design Spec defect: repair that §IX block first (continuous run) or return upstream; never infer the relationship at execution.+**Step 4 — topology decision (Mandatory)**: before drawing, read the page's §IX `Relationships` (Quick: the transient relationship statement), then `Visualization` and `Content`, and decide whether geometry must carry that qualitative `order`, `link`, `parent`, `membership`, `contrast`, or `overlap` relationship. Decide from the semantic relationship alone; a suggested carrier, topology, or composition does not decide it, and a Chart/Table reference never substitutes. `no` stays on this base path. `yes` applies the grammar of [`executor-structure.md`](./executor-structure.md) and [`topology-assembly.md`](./topology-assembly.md) (routing table) and keeps the relationship statement in active page context with no catalog reference, lock row, or artifact. A missing line is a Design Spec defect: repair that §IX block first (continuous run) or return upstream; never infer the relationship at execution.**Step 5 — layout rhythm (`page_rhythm`)**: before drawing, apply the page's tag (key `P<NN>` matching §IX):@@ -251,7 +251,7 @@ Mechanical repetition comes from reusing one carrier and topology without a page**Step 8 — image composition (image pages only)**: Apply the per-page image composition decision of [`executor-image.md`](./executor-image.md) §1 once, immediately before geometry; a deliberate plain placement is valid when it communicates better.-**Step 9 — geometry move (Mandatory)**: after the Structure result and any topology, decide the page's geometry before writing coordinates. A move beyond basic primitives follows [`native-shape-authoring.md`](./native-shape-authoring.md) §2.1 — exact-fit comparison, composition lenses, relationship and carrier fit, contour-family choice, the reader effect of a generic or undrawn result, the running geometry signature, and the materialization boundary for both Structure results. Keep the decision in active context; never change the Structure result. Materialize under §3.0.+**Step 9 — geometry move (Mandatory)**: after the topology decision and any assembled topology, decide the page's geometry before writing coordinates. A move beyond basic primitives follows [`native-shape-authoring.md`](./native-shape-authoring.md) §2.1 — exact-fit comparison, composition lenses, relationship and carrier fit, contour-family choice, the reader effect of a generic or undrawn result, the running geometry signature, and the materialization boundary for both topology results. Keep the decision in active context; never change the topology decision. Materialize under §3.0.**Step 10 — coordinates and bounds**: Write the sentence first, then the zone; the grouping, bounds, and width-estimation contract is §3 Technical contract.diff --git a/skills/ppt-master/references/executor-image.md b/skills/ppt-master/references/executor-image.mdindex 187c39ea..34e28751 100644--- a/skills/ppt-master/references/executor-image.md+++ b/skills/ppt-master/references/executor-image.md@@ -18,7 +18,7 @@ Conditional Executor authority for image status handling, placement, crop behavi**Template-bundled images**: [`apply-template-workspace.md`](../workflows/stages/apply-template-workspace.md) copies them into project `images/`; every page, including `mirror`, rebases the same bytes to exact `../images/<name>` (a transport rewrite, not a visual edit). Never keep a bare or source-template href.-**Contract — crop policy**: read the §VIII row and its lock projection (`source`, `crop`). On every slide that uses a `crop=no-crop` source (or legacy `| no-crop`), keep one visible complete instance with one of the nine legal `meet` anchors — never `none`, `clip-path`, `mask`, overflow clipping, or a nested crop viewport; an auxiliary same-slide detail or lens may crop the source only while that instance stays visible. `crop=adaptive` permits cropping without requiring it: choose `meet` or a focal-safe `slice` from purpose, ratio, focus, and container. A missing or conflicting projection returns upstream; the §VIII `Layout pattern` is a Reference — a starting sketch adjusted freely unless labeled `(binding)`.+**Contract — crop policy**: read the §VIII row and its lock projection (`source`, `crop`). On every slide that uses a `crop=no-crop` source (or legacy `| no-crop`), keep one visible complete instance with one of the nine legal `meet` anchors — never `none`, `clip-path`, `mask`, overflow clipping, or a nested crop viewport; an auxiliary same-slide detail or lens may crop the source only while that instance stays visible. `crop=adaptive` permits cropping without requiring it: choose `meet` or a focal-safe `slice` from purpose, ratio, focus, and container. A missing or conflicting projection returns upstream; the §VIII `Image pattern` is a Reference — a starting sketch adjusted freely unless labeled `(binding)`.**Hard rule — same-source addressable crops, only when adopted**: no layout suggestion (including `#M1-11`) activates this transport, and `#M1-09` is a deliberate-offset treatment with no registered or Morph continuity. Use it only when independent crops must preserve one exact scene map or an explicit editable/Morph requirement needs them: reuse one exact `href` without slice assets, give every independent object a stable page-unique id and its own nested crop wrapper, and derive every wrapper `viewBox` from one shared source-to-page transform over the union of the visible containers, so gaps remove pixels without rescaling. The wrapper grammar and the shaped-frame clip form are [`svg-effects.md`](./svg-effects.md) §6.5; repeated crops or SVG/PPT drift fail. A compound clip on one `<image>` is `#M1-10`, not a substitute when the objects must stay independently editable or Morphable.diff --git a/skills/ppt-master/references/executor-structure.md b/skills/ppt-master/references/executor-structure.mdindex 5069735b..a363bf79 100644--- a/skills/ppt-master/references/executor-structure.md+++ b/skills/ppt-master/references/executor-structure.md@@ -2,7 +2,7 @@# Executor Shape Composition Grammar-Runtime grammar for Slide-local qualitative relationships built from editable shapes; not a diagram catalog. Default and Quick read it once at the first page whose Structure decision is `yes` and reuse it for every later page; loading it selects no `Structure=yes` and creates no geometry quota.+Runtime grammar for Slide-local qualitative relationships built from editable shapes; not a diagram catalog. Default and Quick read it once at the first page whose topology decision is `yes` and reuse it for every later page; loading it selects no `topology=yes` and creates no 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.@@ -71,7 +71,7 @@ The last column names common transform axes, not an exhaustive set: combine, def**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 parent contour/direction → contact → joint or intentional void → z-order/occlusion → canvas-edge behavior before labels/garnish; skip inapplicable operations.+**Structural carriers**: a relationship-bearing field, spine, node carrier, or directional shape can be the page-scale move; `topology=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.---diff --git a/skills/ppt-master/references/image-base.md b/skills/ppt-master/references/image-base.mdindex 3516e495..a9c0d20f 100644--- a/skills/ppt-master/references/image-base.md+++ b/skills/ppt-master/references/image-base.md@@ -10,7 +10,7 @@ Shared baseline for both acquisition paths and for prepared derivatives.Status enum: [`svg-image-embedding.md`](svg-image-embedding.md). Per non-skipped row `Acquire Via` and `Status` are required; `Reference` is required for every `web` / `slice` row, every newly authored `ai` row, and every derivative (an existing `ai` row with a blank `Reference` continues only through [`image-generator.md`](./image-generator.md) §8's declared inference). Quick: explicit user assets, URLs, and path instructions win; otherwise the agent chooses `user` / `ai` / `web` / `slice` rows and AI path `auto` without interaction.-| Filename | Dimensions | Purpose / Type | Layout pattern | Crop Policy | Acquire Via | Status | Reference |+| Filename | Dimensions | Purpose / Type | Image pattern | Crop Policy | Acquire Via | Status | Reference ||---|---|---|---|---|---|---|---|| `<planned file>` | `<planned size>` | `<planned role>` | `<owner-resolved recommendation>` | `adaptive` / `no-crop` | `ai` / `web` / `slice` | Pending | `<acquisition brief>` |diff --git a/skills/ppt-master/references/image-generator.md b/skills/ppt-master/references/image-generator.mdindex 9ffbe4c4..b5da1fa7 100644--- a/skills/ppt-master/references/image-generator.md+++ b/skills/ppt-master/references/image-generator.md@@ -69,7 +69,7 @@ Rendering decides how the image is drawn. Color begins from the deck roles — b| Field | Resolution ||---|---|-| `Layout pattern` | Never copied into the prompt. When page use depends on stable composition, carry the row's `Reference` / §IX / active-context contract — subject and quiet zones, boundary or direction, overlap/seam, approximate share — without inventing layout |+| `Image pattern` | Never copied into the prompt. When page use depends on stable composition, carry the row's `Reference` / §IX / active-context contract — subject and quiet zones, boundary or direction, overlap/seam, approximate share — without inventing layout || `page_role` | The row's value, else `local` (`hero_page` is Strategist-explicit in Default; Quick may resolve it) || `text_policy` | The row's value, else `none` or `embedded` from `Purpose`, `Reference`, and page intent || Type | An Illustration Sheet omits `type` and follows §4.3; another local structural infographic takes one of the 11 types only on a real index match, otherwise §4.1 E prose; a local single-subject/portrait uses §4.1 A/B; a `hero_page` uses §4.1 A–E. Read `image-type-templates/<type>.md` only when selected |diff --git a/skills/ppt-master/references/native-shape-authoring.md b/skills/ppt-master/references/native-shape-authoring.mdindex dea8e59b..1dbf66ef 100644--- a/skills/ppt-master/references/native-shape-authoring.md+++ b/skills/ppt-master/references/native-shape-authoring.md@@ -30,7 +30,7 @@ python3 ${SKILL_DIR}/scripts/shape_boolean_svg.py render <svg-file> \**Hard rule — contour before encoding**: choose the page-fit contour from the intended job and active visual system across the full vocabulary before any syntax. Rectangle, rounded rectangle, circle, and ellipse are not an earlier tier because SVG spells them short; easier syntax never selects a contour.-**Default — exact page-fit geometry before generic neutrality (may override when neutrality itself communicates the page)**: resolve relationship fit when the content carries direction, sequence, membership, hierarchy, convergence, reveal, or contrast; independently resolve page-field / carrier fit from ownership, focal hierarchy, boundary strength, and the deck's edge / opening language (`Structure=no` removes only relationship topology). Choose a plain primitive, uniform grid, or no drawn carrier only when that lack of inflection gives the reader a concrete benefit or avoids a false inference — and before it wins, name the strongest fitting native or compound alternative and why its inflection would add nothing, mislead, weaken hierarchy, or conflict with the job. Quick speed, restrained style, readability, equal importance, precedent, and shorter syntax alone never qualify.+**Default — exact page-fit geometry before generic neutrality (may override when neutrality itself communicates the page)**: resolve relationship fit when the content carries direction, sequence, membership, hierarchy, convergence, reveal, or contrast; independently resolve page-field / carrier fit from ownership, focal hierarchy, boundary strength, and the deck's edge / opening language (`topology=no` removes only relationship topology). Choose a plain primitive, uniform grid, or no drawn carrier only when that lack of inflection gives the reader a concrete benefit or avoids a false inference — and before it wins, name the strongest fitting native or compound alternative and why its inflection would add nothing, mislead, weaken hierarchy, or conflict with the job. Quick speed, restrained style, readability, equal importance, precedent, and shorter syntax alone never qualify.**Hard rule — style does not narrow capability**: the visual system weights contour fit and controls paint, stroke, texture, density, and recurrence; it never removes primitives, presets, composition, Boolean, or necessary freeform from consideration. Style-specific syntax guidance applies only to the named style-defining mark.@@ -66,7 +66,7 @@ python3 ${SKILL_DIR}/scripts/shape_boolean_svg.py render <svg-file> \### 2.1 Topology assembly and compound page geometry-**Trigger**: after the page's communication / slot job, composition anchors, and any [`executor-structure.md`](./executor-structure.md) topology are resolved, before writing coordinates — at every active granularity. For `Structure=yes`, assemble the resolved topology without changing it, with [`topology-assembly.md`](./topology-assembly.md) as material; for every page, resolve the page-scale geometry move carrying its background field, content zoning, focal hierarchy, or reading path. Before repeating stacked cards or uniform equal columns, compare a page-field, outline, nesting, or continuity construction and the relevant family's exact members; the first workable arrangement's readability does not close this gate, and the gate creates no decoration requirement.+**Trigger**: after the page's communication / slot job, composition anchors, and any [`executor-structure.md`](./executor-structure.md) topology are resolved, before writing coordinates — at every active granularity. For `topology=yes`, assemble the resolved topology without changing it, with [`topology-assembly.md`](./topology-assembly.md) as material; for every page, resolve the page-scale geometry move carrying its background field, content zoning, focal hierarchy, or reading path. Before repeating stacked cards or uniform equal columns, compare a page-field, outline, nesting, or continuity construction and the relevant family's exact members; the first workable arrangement's readability does not close this gate, and the gate creates no decoration requirement.| Pass | Action | Result ||---|---|---|@@ -89,7 +89,7 @@ python3 ${SKILL_DIR}/scripts/shape_boolean_svg.py render <svg-file> \At topology scale, independent pieces, one body with dividers, overlapping siblings, fitted joints, intentional gaps, and retained `fragment` regions are common strategies, not a set; never map a topology name to a shape list or infer equal size or spacing.-**Default — running geometry signature (may override for literal pages or isolated prototypes)**: the *geometry signature* of a page is the retained line `page job → composition move → contour / edge language` (plus `relationship → topology` for `Structure=yes`). After each page retain its signature and compare it with the previous pages' before drawing the next; repeat a signature only for the same job / relationship or deliberate continuity — section, equal weight, style, and precedent are insufficient. The final carrier-receipt review reads these signatures back. No artifact, no second pass.+**Default — running geometry signature (may override for literal pages or isolated prototypes)**: the *geometry signature* of a page is the retained line `page job → composition move → contour / edge language` (plus `relationship → topology` for `topology=yes`). After each page retain its signature and compare it with the previous pages' before drawing the next; repeat a signature only for the same job / relationship or deliberate continuity — section, equal weight, style, and precedent are insufficient. The final carrier-receipt review reads these signatures back. No artifact, no second pass.**Boolean decision gate**:diff --git a/skills/ppt-master/references/plan-core.md b/skills/ppt-master/references/plan-core.mdindex 42ab079d..28081046 100644--- a/skills/ppt-master/references/plan-core.md+++ b/skills/ppt-master/references/plan-core.md@@ -71,14 +71,14 @@ With notes disabled the last column is unavailable: every required meaning stays**Page rhythm**: give every page one tag — `anchor` (structural: cover, chapter, TOC, ending), `dense` (information-heavy; the baseline), or `breathing` (a low-density pause) — as a body-content frame and density judgment per page rather than one uniform fill; the tag is what breaks the uniform card-grid feel, and leans by reading mode are a bias, not a quota.-**Mandatory — whole-roster rhythm check**: while composing §IX, compare neighbors and section arcs — chapter entries visibly reset; same-density, same-resource, or same-relationship runs are intentional sub-arcs; a repeated motif carries a continuity job; any visible-state sequence keeps a recognizable map while its next change is legible; each section follows a mode-fitting progression (including framework → explanation/evidence → judgment/action when it serves); the final arc resolves the objective before a genuine ending lowers load. Same section, equal density, one style, and precedent establish no sub-arc. Repair roster, `Layout`, and `page_rhythm` in place; preserve intentional continuity, legitimately all-`dense` material, and 1:1 order; add no filler — a `breathing` page marks a real pause and must stand alone. No field, lock row, artifact, or second pass.+**Mandatory — whole-roster rhythm check**: while composing §IX, compare neighbors and section arcs — chapter entries visibly reset; same-density, same-resource, or same-relationship runs are intentional sub-arcs; a repeated motif carries a continuity job; any visible-state sequence keeps a recognizable map while its next change is legible; each section follows a mode-fitting progression (including framework → explanation/evidence → judgment/action when it serves); the final arc resolves the objective before a genuine ending lowers load. Same section, equal density, one style, and precedent establish no sub-arc. Repair roster, `Composition`, and `page_rhythm` in place; preserve intentional continuity, legitimately all-`dense` material, and 1:1 order; add no filler — a `breathing` page marks a real pause and must stand alone. No field, lock row, artifact, or second pass.**Cover impact is mandatory**: give `P01` one concrete hook from the source's strongest claim, metaphor, number, moment, or conflict plus one optional composition Reference in ordinary words (a distilled display phrase may carry the cover while the complete title stays a native subtitle; with no suitable image, a native-SVG hook). The hook binds; the composition is a Reference. `P01` stays `anchor`, defaulting away from generic content-page templates unless content, user, or template makes a card grid, agenda, or equal-weight columns the clearest cover. Beautify preservation is exempt.**Closing impact (only when the deck closes)**: for a genuine conclusion, CTA, or final takeaway, name the binding takeaway plus a recommended composition; never an information-empty "Thank you", contact-only slide, or cover reprise (an explicit contact/event CTA may serve), and never an invented closing page. Preservation is exempt.-**Reference — a starting sketch, never a constraint**: a §IX `Layout` line names the macro relationship the page's content suggests (one focal claim, equal comparison, dominant evidence + takeaway, parallel sequence, core + surrounding forces, wide visual + explanation) in ordinary words; Executor owns the structure and geometry that realize it (its layout-structure vocabulary lives in [`executor-base.md`](./executor-base.md) Page Expression Core) and adjusts or replaces the line freely after reading the page. Never write element-level sizes or coordinates into §IX.+**Reference — a starting sketch, never a constraint**: a §IX `Composition` line names the macro relationship the page's content suggests (one focal claim, equal comparison, dominant evidence + takeaway, parallel sequence, core + surrounding forces, wide visual + explanation) in ordinary words; Executor owns the structure and geometry that realize it (its layout-structure vocabulary lives in [`executor-base.md`](./executor-base.md) Page Expression Core) and adjusts or replaces the line freely after reading the page. Never write element-level sizes or coordinates into §IX.-Once the roster and planned resources are known, recommend a cross-page motif or element family when it can carry identity or meaning — title/corner ornaments, a directional contour, an opening, a line lattice, an oversized numeral — recording its continuity job and reuse mode in §III `Theme` and mentioning it only in the §IX `Layout` blocks that benefit; Executor owns its geometry and may decline it; no motif field, lock row, or quota.+Once the roster and planned resources are known, recommend a cross-page motif or element family when it can carry identity or meaning — title/corner ornaments, a directional contour, an opening, a line lattice, an oversized numeral — recording its continuity job and reuse mode in §III `Theme` and mentioning it only in the §IX `Composition` blocks that benefit; Executor owns its geometry and may decline it; no motif field, lock row, or quota.---@@ -95,7 +95,7 @@ Once the roster and planned resources are known, recommend a cross-page motif or| AI decorative lettering asset | Any stable display string — a complete long or multi-line title, cover hook, chapter word, place or product name, dish or exhibit name, year, hero number, pull quote, motif word — reads better with a material, dimensional, hand-rendered, or illustrative treatment than as ordinary text || Motion | A section/state change or continuity across adjacent pages, or a reveal / emphasis / movement order within a page, clarifies sequence, causality, comparison, or hierarchy |-Every communication job maps to a prepared resource or an information model; this menu never satisfies the Executor's per-page Structure decision:+Every communication job maps to a prepared resource or an information model; this menu never satisfies the Executor's per-page topology decision:| Communication job | Prepared resource or information model ||---|---|diff --git a/skills/ppt-master/references/strategist-image.md b/skills/ppt-master/references/strategist-image.mdindex 7c307c72..6251cc41 100644--- a/skills/ppt-master/references/strategist-image.md+++ b/skills/ppt-master/references/strategist-image.md@@ -6,7 +6,7 @@ Always-on Stage-2 rendering-candidate extension plus, after confirmation, image**Trigger**: load before every fresh Stage-2 direction set. Author the three rendering candidates first (§2) from the rendering index; [`strategist.md`](./strategist.md) independently owns the source recommendation. A confirmed non-`none` source activates the resource sections; confirmed `none` stops before them. Candidates are authored once before confirmation and never backfilled from a later source toggle.-**Contract — what this module writes**: one `image_strategy` per direction (§2); §VIII rows only for planned images, each with filename, dimensions/ratio, layout suggestion, crop policy, purpose/type, `Acquire Via` (`ai`, `web`, `user`, `placeholder`, `slice`), status under [`svg-image-embedding.md`](./svg-image-embedding.md), reference, and conditional AI fields; after final confirmation, each placed row projected into `spec_lock.md images` as `<path> | source=<Acquire Via> | crop=<adaptive|no-crop>` (unplaced source/sheet rows omitted; `Layout pattern` stays in §VIII as preferred expression). An unavailable planned or required asset stays `Pending` or `Needs-Manual`, never deleted or reclassified.+**Contract — what this module writes**: one `image_strategy` per direction (§2); §VIII rows only for planned images, each with filename, dimensions/ratio, layout suggestion, crop policy, purpose/type, `Acquire Via` (`ai`, `web`, `user`, `placeholder`, `slice`), status under [`svg-image-embedding.md`](./svg-image-embedding.md), reference, and conditional AI fields; after final confirmation, each placed row projected into `spec_lock.md images` as `<path> | source=<Acquire Via> | crop=<adaptive|no-crop>` (unplaced source/sheet rows omitted; `Image pattern` stays in §VIII as preferred expression). An unavailable planned or required asset stays `Pending` or `Needs-Manual`, never deleted or reclassified.---@@ -36,10 +36,10 @@ For specialized or regulated paper-figure subjects keep the prompt depth of [`im**Prepared derivatives**: keep the canonical row and add a deterministic child with a distinct `.png`, `Reference: Derived from <bare filename>; treatment=<operation>;`, inheriting acquisition (§4.4 follows `user` / `ai` above); lock placed children; [`image-base.md`](./image-base.md) §1–2 owns preparation.-**References describe visual intent**: AI rows carry subject + intent + composition without repeating rendering or HEX; web rows carry the exact subject, view/mood, focal/quiet region, crop safety, and positive quality cues, from which Image_Searcher derives a separate short provider query (complete entity names or disambiguation may use more words). When page use depends on stable composition, put subject/quiet zones, boundary or direction, intended overlap/seam, and approximate share in `Reference` or the §IX block, not only in `Layout pattern`.+**References describe visual intent**: AI rows carry subject + intent + composition without repeating rendering or HEX; web rows carry the exact subject, view/mood, focal/quiet region, crop safety, and positive quality cues, from which Image_Searcher derives a separate short provider query (complete entity names or disambiguation may use more words). When page use depends on stable composition, put subject/quiet zones, boundary or direction, intended overlap/seam, and approximate share in `Reference` or the §IX block, not only in `Image pattern`.**Prepared-user fast path**: for initial imported or user-supplied assets confirmed as `provided`, copy the exact basename, derive `Dimensions` / `Ratio` from the row's EXIF-corrected `Width` / `Height` / `AspectRatio` in the latest `analysis/image_analysis.csv` (`SourceDisplayRatio` is source context, not the crop ratio), drop source-side directories, set `Acquire Via: user` and `Status: Existing`, and decide the rest normally; existing §VIII, lock, or provenance records override this inference, and assets declared `ai`, `web`, `slice`, or manual keep that provenance wherever they sit.-**Layout pattern** (one non-empty value per placed row, required by the checker): preferred expression in ordinary words, not locked geometry (an id from [`image-layout-patterns.md`](./image-layout-patterns.md) only when already known; Executor loads that catalog); Executor adjusts it freely as a Reference while keeping resource identity, must-use status, crop/content, and explicit constraints (layout-only changes need no upstream rewrite). A useful entry names the job the image does for the content or the page's shapes — the catalog is recall, an uncatalogued technique answers a job equally, plain split and full bleed stay valid, and a `no-crop` or supporting row keeps one concise suggestion. Choose narrative intent before dimensions, then derive `Dimensions` / `Ratio` from the intended region of the confirmed canvas (placement geometry itself is Executor's [`image-layout-spec.md`](./image-layout-spec.md)); a cutout, blurred crop, or desaturated copy requires that prepared asset.+**Image pattern** (one non-empty value per placed row, required by the checker): preferred expression in ordinary words, not locked geometry (an id from [`image-layout-patterns.md`](./image-layout-patterns.md) only when already known; Executor loads that catalog); Executor adjusts it freely as a Reference while keeping resource identity, must-use status, crop/content, and explicit constraints (layout-only changes need no upstream rewrite). A useful entry names the job the image does for the content or the page's shapes — the catalog is recall, an uncatalogued technique answers a job equally, plain split and full bleed stay valid, and a `no-crop` or supporting row keeps one concise suggestion. Choose narrative intent before dimensions, then derive `Dimensions` / `Ratio` from the intended region of the confirmed canvas (placement geometry itself is Executor's [`image-layout-spec.md`](./image-layout-spec.md)); a cutout, blurred crop, or desaturated copy requires that prepared asset.**Crop policy**: `no-crop` whenever cropping could remove required pixels, labels, evidence, identity, or edge content (screenshots, charts, certificates, dense diagrams, logos, product markings are common triggers); otherwise `adaptive` — Executor may use complete display or a focal-safe crop, and the value never commands cropping. Judge `text_policy` per AI row under [`image-generator.md`](./image-generator.md) §5.3; paper figures, schematics, panel comparisons, data-axis graphics, and stable lettering are triggers to reconsider an all-`none` plan. Step 5 dispatches pending `ai` / `slice` rows to Image_Generator and `web` rows to Image_Searcher.diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.mdindex f3a0987d..d82d0d0e 100644--- a/skills/ppt-master/references/strategist.md+++ b/skills/ppt-master/references/strategist.md@@ -169,7 +169,7 @@ Resource need from the roster, the native-construction Hard rule, the capability| Capability | Design Spec handoff ||---|---|-| Image composition | Propose a permitted source; when selected, apply [`strategist-image.md`](./strategist-image.md), record a concise §VIII `Layout pattern` in ordinary words, and state how several images relate in §IX `Images` |+| Image composition | Propose a permitted source; when selected, apply [`strategist-image.md`](./strategist-image.md), record a concise §VIII `Image pattern` in ordinary words, and state how several images relate in §IX `Images` || Composable illustration family | Plan transparent elements by compatible family under `strategist-image.md`, record fixed reuse or adaptive variation in §VIII `Reference`, and describe each page's carrier relationships in §IX || AI decorative lettering asset | Under `strategist-image.md`: preserve every exact string, group compatible marks, keep chrome/body native; the asset may carry the complete title as its display layer while a native title/subtitle stays in a separate frame wherever a searchable, selectable, or outline-visible heading is needed; never shorten copy toward a wordmark || Motion | Optional §IX `Motion suggestion`: the communication job, the units involved, and their meaningful order or initial → end state; effects, ids, options, and timing stay with Executor, and a suggestion never activates the custom stage |@@ -215,9 +215,9 @@ Owned by [`plan-core.md`](./plan-core.md) §6.1: precedence, proportion, anchor----## 4. Layout Reference and Motif+## 4. Composition Reference and Motif-The §IX `Layout` line and the cross-page motif recommendation are [`plan-core.md`](./plan-core.md) §4: both are References Executor adjusts or declines; the motif's continuity job and reuse mode go in §III `Theme`.+The §IX `Composition` line and the cross-page motif recommendation are [`plan-core.md`](./plan-core.md) §4: both are References Executor adjusts or declines; the motif's continuity job and reuse mode go in §III `Theme`.---diff --git a/skills/ppt-master/references/svg-image-embedding.md b/skills/ppt-master/references/svg-image-embedding.mdindex 9da21623..9f590f2f 100644--- a/skills/ppt-master/references/svg-image-embedding.md+++ b/skills/ppt-master/references/svg-image-embedding.md@@ -11,7 +11,7 @@ Status names, resource lifecycle, and the embedding workflow for images in SVG pEach image carries an `Acquire Via` field plus a status. Default Generate's authority is `design_spec.md §VIII` plus its lock projection (run `analyze_images.py` after confirmation when user images are selected and complete the list before Executor); Quick's is the main agent's active-context decisions (explicit user paths first, unspecified acquisition resolved automatically, all preparation finished before SVG authoring without confirmation or a persisted roster).```markdown-| Filename | Dimensions | Purpose | Type | Layout pattern | Crop Policy | Acquire Via | Status | Reference |+| Filename | Dimensions | Purpose | Type | Image pattern | Crop Policy | Acquire Via | Status | Reference ||----------|------------|---------|------|----------------|-------------|-------------|--------|-----------|| team.jpg | 800x600 | Team photo | Photography | `Put faces behind the hiring claim; #P1-02 + #M2-08 fading the photo edge into the page so copy meets it without a frame` | adaptive | web | Pending | Diverse engineering team in modern office |```diff --git a/skills/ppt-master/references/topology-assembly.md b/skills/ppt-master/references/topology-assembly.mdindex 347a351e..d86aa429 100644--- a/skills/ppt-master/references/topology-assembly.md+++ b/skills/ppt-master/references/topology-assembly.md@@ -2,7 +2,7 @@# Topology Assembly Reference-Generative material for turning one resolved qualitative topology into editable native-shape components with coherent relative registration, before coordinates. Default and Quick read it once with `executor-structure.md` at the first `Structure=yes` page and reuse it for every later assembly.+Generative material for turning one resolved qualitative topology into editable native-shape components with coherent relative registration, before coordinates. Default and Quick read it once with `executor-structure.md` at the first `topology=yes` page and reuse it for every later assembly.**Hard rule — relative constraints, never copyable geometry**: state exact preset or primitive identities, semantic counts, inter-component relations, and only the relative geometry that makes the assembly hold; never coordinates, points, sizes, ratios, adjustment values, path data, SVG fragments, full-page frames, copy, color, styling, or page composition. Materialize every adopted call through `native-shape-authoring.md`.diff --git a/skills/ppt-master/scripts/docs/advanced-image-motion-smoke.md b/skills/ppt-master/scripts/docs/advanced-image-motion-smoke.mdindex ba67c912..df8b0bbb 100644--- a/skills/ppt-master/scripts/docs/advanced-image-motion-smoke.md+++ b/skills/ppt-master/scripts/docs/advanced-image-motion-smoke.md@@ -133,7 +133,7 @@ preset = (## VIII. Image Resource List-| Filename | Dimensions | Ratio | Purpose | Type | Layout pattern | Crop Policy | Acquire Via | Status | Reference | text_policy | page_role |+| Filename | Dimensions | Ratio | Purpose | Type | Image pattern | Crop Policy | Acquire Via | Status | Reference | text_policy | page_role || --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- || scene.png | 1280x720 | 16:9 | Morph crop continuity | Photo | #M1-11 same-source independent crops with a shaped detail | adaptive | user | Existing | Synthetic three-band scene for crop and Morph verification | none | local |diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex 03fe2639..3b844c32 100644--- a/skills/ppt-master/scripts/prompt_audit_manifest.json+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json@@ -1193,7 +1193,7 @@"max_tokens": 10000},"stage.generate.executor.structure": {- "description": "Qualitative relationship grammar and topology assembly; loaded at the first page whose Structure decision is yes.",+ "description": "Qualitative relationship grammar and topology assembly; loaded at the first page whose topology decision is yes.","scope": "incremental","files": ["skills/ppt-master/references/executor-structure.md",diff --git a/skills/ppt-master/templates/design_spec_reference.md b/skills/ppt-master/templates/design_spec_reference.mdindex 6c6cae39..d0a8282b 100644--- a/skills/ppt-master/templates/design_spec_reference.md+++ b/skills/ppt-master/templates/design_spec_reference.md@@ -4,7 +4,7 @@ Project-level `design_spec.md` is a human-readable English-heading Markdown arti## 1. Author the complete artifact-Compose the entire document in active context, then create `<project_path>/design_spec.md` once, first line through §X. **Depth follows the confirmed `design_spec_depth`** — `brief` (default) or `complete`; both keep every required heading and machine-read field. `brief` serves a continuous run whose author also draws the pages: §I records production mechanics without restating Stage-1 prose, §VI may leave the scenario column empty, §IX `Content` is a short block list (one bullet per block in the phrasing that fits — a sentence for prose, `·`-joined parallel fragments, `/`-joined labels — never full copy), and `Layout` is one optional line; `Relationships` is written at both depths. `complete` writes full wording and layout prose; split mode, `refine_spec: true`, and preservation profiles force it.+Compose the entire document in active context, then create `<project_path>/design_spec.md` once, first line through §X. **Depth follows the confirmed `design_spec_depth`** — `brief` (default) or `complete`; both keep every required heading and machine-read field. `brief` serves a continuous run whose author also draws the pages: §I records production mechanics without restating Stage-1 prose, §VI may leave the scenario column empty, §IX `Content` is a short block list (one bullet per block in the phrasing that fits — a sentence for prose, `·`-joined parallel fragments, `/`-joined labels — never full copy), and `Composition` is one optional line; `Relationships` is written at both depths. `complete` writes full wording and layout prose; split mode, `refine_spec: true`, and preservation profiles force it.**Mandatory — new-project write**: the first non-empty line is exactly `<!-- ppt-master-schema: design-spec/v1 -->`, then `# <Project Name> - Design Spec`; every required section carries final values and the complete roster; conditional §VII appears only with a real catalog reference. Never write a placeholder-bearing file, copy example rows, or patch a scaffold field by field (`project_manager.py scaffold-spec` is an optional manual troubleshooting tool, not part of Generate authoring; resume and refine edit the existing completed Design Spec).@@ -148,13 +148,13 @@ A custom rendering adds `Image Rendering Behavior`, and `Image Rendering Referen## VIII. Image Resource List-| Filename | Dimensions | Ratio | Purpose | Type | Layout pattern | Crop Policy | Acquire Via | Status | Reference | text_policy | page_role |+| Filename | Dimensions | Ratio | Purpose | Type | Image pattern | Crop Policy | Acquire Via | Status | Reference | text_policy | page_role || --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |```§VII lists at most one `chart|table` reference per page (canonical `family/key` plus semantic Usage; omit when empty; legacy rows stay readable, new specs use four columns). §IX owns child visuals and unmatched fallbacks in `Visualization`; qualitative relationships live only on the `Relationships` line; Layout/Deck alone owns reusable PowerPoint structure. In §IX `Visualization`, key every independent data chart or pure text-grid table in `kebab-case` and add one `Native-ready` map `<key>=yes|no; ...` — `yes` by default, `no` only when the native payload cannot express the object; qualitative relationships and incidental microvisuals stay unkeyed.-§VIII authors every planned or required resource from the confirmed source boundary: one concise non-empty `Layout pattern` suggestion in ordinary language (optionally citing hierarchical ids from the layout library; an image-led `adaptive` row names the page job the image resolves next to the composition serving it); `Crop Policy` `adaptive` or `no-crop`; `Acquire Via` `ai`, `web`, `user`, `placeholder`, or `slice`; unresolved required assets kept as `Pending` or `Needs-Manual`; native formulas never enter it. `Layout pattern` is per-resource — how several images relate on one page (repeated views, sequencing) is stated once in §IX `Images` as a Reference, never as duplicate rows; paint, overlay, and geometry are Executor's.+§VIII authors every planned or required resource from the confirmed source boundary: one concise non-empty `Image pattern` suggestion in ordinary language (optionally citing hierarchical ids from the layout library; an image-led `adaptive` row names the page job the image resolves next to the composition serving it); `Crop Policy` `adaptive` or `no-crop`; `Acquire Via` `ai`, `web`, `user`, `placeholder`, or `slice`; unresolved required assets kept as `Pending` or `Needs-Manual`; native formulas never enter it. `Image pattern` is per-resource — how several images relate on one page (repeated views, sequencing) is stated once in §IX `Images` as a Reference, never as duplicate rows; paint, overlay, and geometry are Executor's.### 2.4 Complete page roster and notes@@ -169,7 +169,7 @@ One ordered Slide block per page; count and order equal §I `Page Count`; `Conte- **Audience move**: <audience state before → after>- **Relationships**: <the page's semantic units and the source-stated order / link / parent / membership / contrast / overlap among them, or none; no shape, carrier, or authoring words>-- **Layout**: <Reference — macro composition, hierarchy, and visual focus as a starting sketch; chosen prototype when template-active; optional at brief depth>+- **Composition**: <Reference — macro composition, hierarchy, and visual focus as a starting sketch; chosen prototype when template-active; optional at brief depth>- **Title**: <preferred page title>- **Core message**: <one governing assertion>- **Content**: <complete content at complete depth; short block list at brief depth>@@ -187,7 +187,7 @@ One ordered Slide block per page; count and order equal §I `Page Count`; `ConteWith Speaker Notes disabled, §X keeps only `- **Generation**: disabled`; an explicit notes-off/audio-on conflict blocks before authoring. When a final/literal narration script will become notes or audio, §X `Content` names the source and says `preserve verbatim`, with the segmented script kept in `notes/total.md`.-Optional Slide lines, added only when the capability earns a place (never an empty or `none` placeholder): `Mathematical content` (a valid delimiter-free LaTeX body — content authority for [`native-formula.md`](../references/native-formula.md), not a policy or marker; Executor chooses text, inline, or block); `Visualization` / `Images` when the Slide consumes §VII/§VIII or a page-local visual model, naming every value-driven geometry, cell grid, and child visual (only independent Chart/Table entries carry keys; qualitative relationships stay on the `Relationships` line, never a model name or grammar enum; §IX may choose a custom fallback; native construction is discovered by Executor, never a Design Spec field); `Motion suggestion` (purpose and semantic order/relationship, never registry keys, options, timing, ids, or coverage — it never activates execution, creates content, or binds implementation; required visible image states go in `Layout` / `Images` only for an explicit motion requirement or an enabled outcome); keyed `Native-ready`; `Fact IDs` for sourced claims; `Data class: scenario` for invented values. Except on preservation paths, `Cover impact` carries a binding hook and adaptable composition, and `Closing impact` the same split only when the deck genuinely resolves. Roster, order, content, and `Relationships` stay authoritative; §V/§IX layout, cover/closing composition, capability, motif, non-`ai` §VIII image-layout, and §VII directions are References under [`strategist.md`](../references/strategist.md) §1 Confirmed-value semantics. When the user, a template, or a resource contract requires such a property, write `(binding)` after the field label (`- **Layout (binding)**:`) and Executor follows it literally. For free-design pages, `Layout` describes relationships, hierarchy, focus, and optional macro region/span suggestions — never element-level `x` / `y` / `width` / `height`, fixed gaps, or an authoring method; literal geometry is preserved only when the user requires it or a mirror/template contract owns it.+Optional Slide lines, added only when the capability earns a place (never an empty or `none` placeholder): `Mathematical content` (a valid delimiter-free LaTeX body — content authority for [`native-formula.md`](../references/native-formula.md), not a policy or marker; Executor chooses text, inline, or block); `Visualization` / `Images` when the Slide consumes §VII/§VIII or a page-local visual model, naming every value-driven geometry, cell grid, and child visual (only independent Chart/Table entries carry keys; qualitative relationships stay on the `Relationships` line, never a model name or grammar enum; §IX may choose a custom fallback; native construction is discovered by Executor, never a Design Spec field); `Motion suggestion` (purpose and semantic order/relationship, never registry keys, options, timing, ids, or coverage — it never activates execution, creates content, or binds implementation; required visible image states go in `Composition` / `Images` only for an explicit motion requirement or an enabled outcome); keyed `Native-ready`; `Fact IDs` for sourced claims; `Data class: scenario` for invented values. Except on preservation paths, `Cover impact` carries a binding hook and adaptable composition, and `Closing impact` the same split only when the deck genuinely resolves. Roster, order, content, and `Relationships` stay authoritative; §V/§IX layout, cover/closing composition, capability, motif, non-`ai` §VIII image-layout, and §VII directions are References under [`strategist.md`](../references/strategist.md) §1 Confirmed-value semantics. When the user, a template, or a resource contract requires such a property, write `(binding)` after the field label (`- **Composition (binding)**:`) and Executor follows it literally. For free-design pages, `Composition` describes relationships, hierarchy, focus, and optional macro region/span suggestions — never element-level `x` / `y` / `width` / `height`, fixed gaps, or an authoring method; literal geometry is preserved only when the user requires it or a mirror/template contract owns it.---diff --git a/skills/ppt-master/templates/scaffolds/design_spec.md b/skills/ppt-master/templates/scaffolds/design_spec.mdindex 2df132f5..cf268b05 100644--- a/skills/ppt-master/templates/scaffolds/design_spec.md+++ b/skills/ppt-master/templates/scaffolds/design_spec.md@@ -93,7 +93,7 @@## VIII. Image Resource List-| Filename | Dimensions | Ratio | Purpose | Type | Layout pattern | Crop Policy | Acquire Via | Status | Reference | text_policy | page_role |+| Filename | Dimensions | Ratio | Purpose | Type | Image pattern | Crop Policy | Acquire Via | Status | Reference | text_policy | page_role || --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |## IX. Content Outline@@ -103,7 +103,7 @@#### Slide 01 - [fill]- **Audience move**: [fill]-- **Layout**: [non-binding macro composition direction]+- **Composition**: [non-binding macro composition direction]- **Title**: [fill]- **Core message**: [fill]- **Content**: [fill]diff --git a/skills/ppt-master/templates/spec_lock_reference.md b/skills/ppt-master/templates/spec_lock_reference.mdindex 3d419a7d..203c97e4 100644--- a/skills/ppt-master/templates/spec_lock_reference.md+++ b/skills/ppt-master/templates/spec_lock_reference.md@@ -82,7 +82,7 @@ Typography projection (excluding Character/upgrade References): Title font stack- `icons.library`: `chunk-filled`, `tabler-filled`, `tabler-outline`, `phosphor-duotone`, or `none`; `simple-icons/*` marks may appear alone or alongside in `inventory` without becoming a library or confirmation choice; every SVG under `<project_path>/icons/` remains valid material; illustrated-icon slices create no icon field — their paths belong under `images`, and the unplaced sheet stays out.- `objective`: one concise sentence preserving goal and audience success condition.- `image_rendering`: one catalog id, or `custom` with `image_rendering_behavior`.-- `images`: `- <key>: <path> | source=<via> | crop=<adaptive|no-crop>` (e.g. `- p04: images/a.png | source=user | crop=no-crop`); canonical `images/<filename>` path; `source` and `crop` project §VIII exactly; `Layout pattern` is not projected (Executor reads it from §VIII as a recommendation); a legacy `pattern=<layout>` segment is accepted; omit unplaced sheets.+- `images`: `- <key>: <path> | source=<via> | crop=<adaptive|no-crop>` (e.g. `- p04: images/a.png | source=user | crop=no-crop`); canonical `images/<filename>` path; `source` and `crop` project §VIII exactly; `Image pattern` is not projected (Executor reads it from §VIII as a recommendation); a legacy `pattern=<layout>` segment is accepted; omit unplaced sheets.- Custom reference fields: comma-separated exact catalog ids without duplicates, valid only for `custom`; omit for a genuinely novel direction.- `stroke_width`: `1.5`, `2`, or `3`, only for `tabler-outline`.- `page_rhythm`: `P` + at least two digits (`P01`, `P100`) followed by `anchor|dense|breathing`.diff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.mdindex 6c5f1edc..75e33b18 100644--- a/skills/ppt-master/workflows/profiles/quick-generate.md+++ b/skills/ppt-master/workflows/profiles/quick-generate.md@@ -111,7 +111,7 @@ Read ${SKILL_DIR}/templates/tables/table-vocabulary.md- **Reading and typography**: canvas, visual direction, wording, viewing distance, and reading mode (`presentation` for distance-first projected or recorded viewing, `balanced` for mixed, `text` for close content-heavy reading). Take the initial body anchor and sanity band from [`canvas-formats.md`](../../references/canvas-formats.md) § Typography Scale Start, then resolve one typography plan for the delivery target of [`shared-standards-core.md`](../../references/shared-standards-core.md) §4.1 — never the authoring host's fonts — with stable anchors for title, body, annotation, and every recurring role. When content does not fit, restructure, shorten, or split within the invariants; if none is permitted, surface the fit rather than shrinking a recurring role.- **Color roles**: the semantic color roles the roster needs (background/surface, primary/secondary text, dominant/accent, status), each with a concrete anchor. Honor user, template/brand, fidelity, and resolved-style semantics before deriving the missing roles; decide which dominate, support, or stay rare; keep meaning-bearing text legible; pair any newly authored color-coded distinction with a label, symbol, line, or geometry cue.- **Density**: a body-content frame and a density judgment per page (`anchor`, `dense`, `breathing`) rather than one uniform fill.-- **Relationships**: for each page, its semantic units and their source-stated relationship (`order` / `link` / `parent` / `membership` / `contrast` / `overlap`, or none), entry, and outcome — the input to §3's Structure decision; zones, geometry, and carriers are §3 authoring decisions.+- **Relationships**: for each page, its semantic units and their source-stated relationship (`order` / `link` / `parent` / `membership` / `contrast` / `overlap`, or none), entry, and outcome — the input to §3's topology decision; zones, geometry, and carriers are §3 authoring decisions.- **Shape language and motif**: the deck-level shape language under [`visual-styles/_index.md`](../../references/visual-styles/_index.md) §2, and, when it earns a continuity job, one transient motif system with an invariant and a reuse mode (fixed chrome, adaptive variation, or both). Restraint governs weight and recurrence, never the omission of an evidenced identity or communication motif.- **Resource decisions** for immediate preparation: manifests may carry filenames, page relationship, status, and generation/crop/focal cues (plus subject/quiet zones, boundary, seam, and share when composition depends on them); no general roster or icon-to-page assignment. Each formula's LaTeX and each hyperlink's exact target stay in context, with no manifest. An explicit user implementation path wins; otherwise the registered default.@@ -119,7 +119,7 @@ Read ${SKILL_DIR}/templates/tables/table-vocabulary.md**Prepared final narration**: an explicit final/literal script for notes or audio is segmented by scene while resolving the roster, every word preserved, and written once before P01 to `notes/total.md` (`# Slide <number>` headings, `---` separators) as production input, split only after the roster exists. Draft narration stays source material for the ordinary notes branch.-**Resource need per page**: decide it under [`plan-core.md`](../../references/plan-core.md) §5 before resources. SVG/emoji icons keep their curated-pool boundary, and the page's carrier mix is §3's authoring decision, not a preparation decision. The resolved style controls treatment and recurrence but never eligibility, source, or the native vocabulary. A compact icon cue does not discharge a scene, subject, or visual-weight job a photo or illustration family would serve. The communication-job menu never satisfies the per-page Structure decision in §3.+**Resource need per page**: decide it under [`plan-core.md`](../../references/plan-core.md) §5 before resources. SVG/emoji icons keep their curated-pool boundary, and the page's carrier mix is §3's authoring decision, not a preparation decision. The resolved style controls treatment and recurrence but never eligibility, source, or the native vocabulary. A compact icon cue does not discharge a scene, subject, or visual-weight job a photo or illustration family would serve. The communication-job menu never satisfies the per-page topology decision in §3.**Image sources, grounding, families, lettering, per-image source, and treatment**: [`plan-core.md`](../../references/plan-core.md) §5.1 owns the credentials Hard rule, visual grounding before a zero-image deck, illustration families and illustrated icons, decorative-lettering candidates, the per-image source decision, and image treatment and subject layers. In Quick, web search keeps zero-config providers, AI capability is resolved during preparation, and the no-AI replan below owns exhaustion.@@ -171,7 +171,7 @@ Read the execution core together, never file by file: [`shared-standards-core.md**Mandatory — native formulas and hyperlinks**: no resource or manifest for either. Keep the exact LaTeX and choose ordinary text, same-paragraph inline math, or a standalone block with its SVG preview under [`native-formula.md`](../../references/native-formula.md). Keep each link's exact target, choose an inline or whole-object carrier, and author canonical `<a href>` under [`native-hyperlinks.md`](../../references/native-hyperlinks.md), never guessing a destination.-**Mandatory — per-page Structure decision and geometry move**: after the page's content and communication move, before any geometry, decide whether geometry must carry `order`, `link`, `parent`, `membership`, `contrast`, or `overlap` (`executor-base.md` §2.2) — `no` stays on the base path, `yes` loads and applies the Shape Composition Grammar and topology assembly. Then, when the page's geometry reaches beyond basic primitives, load and apply [`native-shape-authoring.md`](../../references/native-shape-authoring.md) §2.1 to the transient geometry job, content, deck shape language, resolved style, and full vocabulary before coordinates (`describe --compact` only when objective facts could change a serious candidate). Both decisions stay in context; the capability menu, visualization recall, and template geometry never stand in for them. Quick runs [`verify-charts.md`](../stages/verify-charts.md) after the roster and before the final checker whenever data-driven chart geometry exists.+**Mandatory — per-page topology decision and geometry move**: after the page's content and communication move, before any geometry, decide whether geometry must carry `order`, `link`, `parent`, `membership`, `contrast`, or `overlap` (`executor-base.md` §2.2) — `no` stays on the base path, `yes` loads and applies the Shape Composition Grammar and topology assembly. Then, when the page's geometry reaches beyond basic primitives, load and apply [`native-shape-authoring.md`](../../references/native-shape-authoring.md) §2.1 to the transient geometry job, content, deck shape language, resolved style, and full vocabulary before coordinates (`describe --compact` only when objective facts could change a serious candidate). Both decisions stay in context; the capability menu, visualization recall, and template geometry never stand in for them. Quick runs [`verify-charts.md`](../stages/verify-charts.md) after the roster and before the final checker whenever data-driven chart geometry exists.**Per-page anchors**: apply the core-message, typography-role, color, body-frame, density, and composition anchors from §2 while authoring. When `notes/total.md` was frozen, keep each page's segment in view so its visible state and direct-root groups support the spoken words without copying the script into body text.@@ -230,7 +230,7 @@ python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path> --quick-generate --no## ✅ Quick Generate Complete- [x] Source/resource preparation complete; the planning-capability batch and every selected detail source were read before the roster-- [x] The complete preset vocabulary was read before P01; each page resolved its Structure decision, geometry move, and carrier mix without a quota and compared its geometry signature before the next page+- [x] The complete preset vocabulary was read before P01; each page resolved its topology decision, geometry move, and carrier mix without a quota and compared its geometry signature before the next page- [x] Image need was decided independently of credentials; every image decided its own source, every `slice_names` output exists after an exit-0 strict-alpha run, and every exhausted AI job was replanned under the no-AI rule with its disclosure retained- [x] Every selected formula and hyperlink uses its checker-valid native form- [x] The frozen Template Application paragraph was applied, every installed Layout/Deck SVG was read, and structure matches the installed capability (flat vs explicit all-page structured)diff --git a/skills/ppt-master/workflows/stages/resume-execute.md b/skills/ppt-master/workflows/stages/resume-execute.mdindex 63a19749..082b1580 100644--- a/skills/ppt-master/workflows/stages/resume-execute.md+++ b/skills/ppt-master/workflows/stages/resume-execute.md@@ -40,7 +40,7 @@ python3 skills/ppt-master/scripts/visualization_recall.py validate <family/key>python3 skills/ppt-master/scripts/visualization_recall.py validate --legacy-bare <legacy-key> [...]```-Then continue the documented Step 6–7 pipeline exactly as `generate-pptx.md` lists it: read the frozen `notes/total.md` once when §X declares a final/literal script; when mid-deck, read the latest completed SVG and current image metadata after their paths are verified; read the Step 6 construction core and one locked preset file or only the exact `*_references` of a custom, never reopening the mode or visual-style catalogs; load only the branches the condition table selects; make the per-page Structure decision from retained §IX before any geometry; when structured, read the template Design Spec and each selected prototype once. Use `page-context` only for explicit diagnostics or an unresolved path-SHA question ([`artifact-ownership.md`](../../references/artifact-ownership.md) §1), never as a routine pre-page load. Then the quality gate, conditional notes, conditional custom animation, Step 7 (`total_md_split` → `finalize_svg` → `svg_to_pptx`; disabled notes use `--no-notes`), and `generate-audio` when Narration Audio is enabled.+Then continue the documented Step 6–7 pipeline exactly as `generate-pptx.md` lists it: read the frozen `notes/total.md` once when §X declares a final/literal script; when mid-deck, read the latest completed SVG and current image metadata after their paths are verified; read the Step 6 construction core and one locked preset file or only the exact `*_references` of a custom, never reopening the mode or visual-style catalogs; load only the branches the condition table selects; make the per-page topology decision from retained §IX before any geometry; when structured, read the template Design Spec and each selected prototype once. Use `page-context` only for explicit diagnostics or an unresolved path-SHA question ([`artifact-ownership.md`](../../references/artifact-ownership.md) §1), never as a routine pre-page load. Then the quality gate, conditional notes, conditional custom animation, Step 7 (`total_md_split` → `finalize_svg` → `svg_to_pptx`; disabled notes use `--no-notes`), and `generate-audio` when Narration Audio is enabled.A newer explicit instruction after final Stage 2 updates only its effective outcome and provenance in `design_spec.md §I`, then resumes at the owning step — no Confirm UI, no lock entry; apply Generate's notes/audio dependency gate before writing and its sidecar suppression rules at export.