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
fix(generate): ground custom directions in catalog sources
hugohe32911901ac10c
diff --git a/docs/technical-design.md b/docs/technical-design.mdindex 53c140b7..8e0f5b08 100644--- a/docs/technical-design.md+++ b/docs/technical-design.md@@ -381,7 +381,7 @@ Why both? `design_spec.md` preserves the complete confirmed solution and rationaThe view omits universal SVG/icon prohibitions already owned by the always-loaded Executor core and retains only project-specific forbidden rows. It selects images from the current page brief, explicit image-resource page assignments, and mirror prototype references. Images assigned elsewhere are excluded; any unresolved legacy image remains in a compatibility subset, and `confirmed-none` appears only when every locked image has a deterministic assignment elsewhere.-The lock is also the per-page routing table. Beyond global colors and typography, it carries `page_rhythm` (`anchor` / `dense` / `breathing`), `page_charts` (which chart template should be adapted), image rows with placement/cropping contracts, and the locked `mode` / `visual_style` references that decide which execution rule files are loaded. A selected custom direction also carries its resolved `mode_behavior` / `visual_style_behavior`, and page-context projects those fields instead of leaving Executor with only the literal `custom` ids. `template_reuse_scope: mirror|layout` projects additionally carry `page_layouts` (which input template SVG each page inherits), unique `pptx_masters` / `pptx_layouts` definitions, and `page_pptx_layouts` assignments. `template_reuse_scope: style`, free-design, and brand-only projects use `pptx_structure.mode: flat` and omit those sections entirely rather than writing empty values. Empty entries elsewhere are meaningful signals: no chart or no image is often a design decision rather than missing data.+The lock is also the per-page routing table. Beyond global colors and typography, it carries `page_rhythm` (`anchor` / `dense` / `breathing`), `page_charts` (which chart template should be adapted), image rows with placement/cropping contracts, and the locked `mode` / `visual_style` values that decide which execution rule files are loaded. A selected custom direction also carries its resolved `mode_behavior` / `visual_style_behavior`. When it actually combines or borrows catalog entries, the lock records their exact ids in optional `mode_references` / `visual_style_references` / `image_rendering_references`, and execution reads every listed file before synthesis; a genuinely novel custom omits the corresponding reference field. Page-context projects these fields instead of leaving Executor with only literal `custom` ids. `template_reuse_scope: mirror|layout` projects additionally carry `page_layouts` (which input template SVG each page inherits), unique `pptx_masters` / `pptx_layouts` definitions, and `page_pptx_layouts` assignments. `template_reuse_scope: style`, free-design, and brand-only projects use `pptx_structure.mode: flat` and omit those sections entirely rather than writing empty values. Empty entries elsewhere are meaningful signals: no chart or no image is often a design decision rather than missing data.`page-context v2` separates bounded continuity state from large references. It deliberately repeats the compact global anchor set on every page and binds it to `lock_source.sha256`; that set is not a color/font allowlist. The current §IX brief, rhythm, image choice, and template/chart assignment form the page delta. The project/template Design Specs plus selected prototype and `templates/charts/<key>.svg` files appear only as scoped path/SHA fingerprints. Executor reads one of those files only when that fingerprint is absent from the active context or changed, then reuses the retained understanding. Flat pages have no prototype reference; structured pages reference the authoritative complete SVG. Manifests and text-slot sidecars remain derived tool diagnostics and are never injected into page authoring.diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.mdindex 177e8d4f..be7bc0ea 100644--- a/docs/zh/technical-design.md+++ b/docs/zh/technical-design.md@@ -377,7 +377,7 @@ Strategist 阶段产出两份看起来冗余但服务不同对象的产物:该视图省略 Executor core 已经恒定加载的通用 SVG/图标禁令,只保留项目专属 forbidden 行。图片从当前页 brief、图片资源表中的显式页分配和 mirror 原型引用中选择;已分配给其他页面的图片会被排除,仍无法归属的 legacy 图片保留在兼容子集中,只有所有锁定图片都能确定归属到其他页面时才记录 `confirmed-none`。-这份 lock 同时也是逐页路由表。除了全局配色和字体,它还承载 `page_rhythm`(`anchor` / `dense` / `breathing`)、`page_charts`(某页应适配哪个图表模板)、带放置/裁剪契约的图片行,以及决定加载哪些执行规则文件的 `mode` / `visual_style`。选定 custom 方向时,lock 还承载已消解的 `mode_behavior` / `visual_style_behavior`,page-context 会把它们投影给 Executor,而不是只留下字面上的 `custom` id。`template_reuse_scope: mirror|layout` 项目额外承载 `page_layouts`(每页继承哪个输入模板 SVG)、唯一的 `pptx_masters` / `pptx_layouts` 定义,以及 `page_pptx_layouts` 页面分配;`template_reuse_scope: style`、自由设计和 brand-only 项目使用 `pptx_structure.mode: flat`,那些段整段省略,而不是写成空值。其余字段的空值本身仍是信号:没有图表、没有图片,很多时候是设计选择,而不是漏填。+这份 lock 同时也是逐页路由表。除了全局配色和字体,它还承载 `page_rhythm`(`anchor` / `dense` / `breathing`)、`page_charts`(某页应适配哪个图表模板)、带放置/裁剪契约的图片行,以及决定加载哪些执行规则文件的 `mode` / `visual_style`。选定 custom 方向时,lock 还承载已消解的 `mode_behavior` / `visual_style_behavior`;当它确实综合或借鉴已有目录项时,再用可选的 `mode_references` / `visual_style_references` / `image_rendering_references` 记录全部精确 id,执行阶段会先读取每个对应文件再综合。真正全新的 custom 不写参考字段。page-context 会把这些字段投影给 Executor,而不是只留下字面上的 `custom` id。`template_reuse_scope: mirror|layout` 项目额外承载 `page_layouts`(每页继承哪个输入模板 SVG)、唯一的 `pptx_masters` / `pptx_layouts` 定义,以及 `page_pptx_layouts` 页面分配;`template_reuse_scope: style`、自由设计和 brand-only 项目使用 `pptx_structure.mode: flat`,那些段整段省略,而不是写成空值。其余字段的空值本身仍是信号:没有图表、没有图片,很多时候是设计选择,而不是漏填。`page-context v2` 把有界的连续性状态与大型引用分开。它有意在每页重复紧凑的全局锚点集,并用 `lock_source.sha256` 绑定版本;这个集合不是颜色/字体白名单。当前 §IX brief、节奏、图片选择和模板/图表分配构成逐页 delta。项目/模板 Design Spec、选中的原型,以及 `templates/charts/<key>.svg` 只以带 scope 的路径/SHA 指纹出现。只有该指纹不在当前执行上下文中或 SHA 已变化时,Executor 才读取文件一次;后续页面直接复用已有理解。flat 页面没有原型引用;structured 页面引用权威的完整 SVG。manifest 与 text-slot sidecar 只保留为派生工具诊断,不注入页面创作上下文。diff --git a/skills/ppt-master/references/image-generator.md b/skills/ppt-master/references/image-generator.mdindex 620c550f..6dfb23da 100644--- a/skills/ppt-master/references/image-generator.md+++ b/skills/ppt-master/references/image-generator.md@@ -56,13 +56,13 @@ Every AI image uses one deck-wide rendering, the deck's stable color anchors/sem|---|---|| [`image-renderings/_index.md`](./image-renderings/_index.md) — rendering catalog + auto-selection table | Always (Step 1 below) || [`image-type-templates/_index.md`](./image-type-templates/_index.md) — type catalog + auto-selection table | Always (Step 1 below) |-| `image-renderings/<chosen>.md` | After Step 2 picks the rendering — only the chosen one |+| `image-renderings/<chosen>.md` | After Step 2 resolves the rendering — one preset file, or every exact reference listed for `custom` || `image-type-templates/<chosen>.md` | After Step 3 picks the type per image — only the types actually used |**Hard rule — on-demand loading**:- Read the rendering and type `_index.md` files once at role entry.-- After locking inputs, read **only** the specific rendering / type files selected.+- After locking inputs, read **only** the specific preset rendering, custom rendering references, and type files selected.- **Never** glob-read an entire subdirectory (`image-renderings/*.md` is forbidden). Token cost balloons and the AI loses focus.---@@ -91,7 +91,7 @@ accent: #D4AF37Use them as identity anchors. Do not create another user-facing image-color choice. The rendering and image subject may derive coherent tonal transitions, material colors, lighting, and atmospheric hues when the context requires them, while the core roles keep their established meaning.-**Hard rule — `custom` escape hatch**: when `image_rendering` is `custom`, do not read a preset rendering file. Splice `image_rendering_behavior` into the prompt. The deck color-role rows remain authoritative.+**Hard rule — `custom` catalog basis**: when `image_rendering` is `custom`, first inspect the optional `image_rendering_references` row. If present, read every exact `image-renderings/<id>.md` it lists and synthesize their line, texture, depth, material, and mood guidance under `image_rendering_behavior` before assembling prompts. If absent, the custom is genuinely novel: read no preset file and use `image_rendering_behavior` directly. Never infer or add adjacent references during execution. The deck color-role rows remain authoritative.**Declared-inference fallback — when an existing `spec_lock.md` omits the `image_rendering` key** (see [`failure-recovery.md`](../workflows/governance/failure-recovery.md) §2):@@ -659,7 +659,7 @@ Diagnose the failure category, adjust the **one specific dimension** responsible- Brand names or HEX codes inside the subject description (degrades output)- Mixing renderings or introducing an unrelated image-only palette across images in the same deck- Tag-soup prompts (keyword lists separated by commas without a coherent visual scene)-- Globbing `image-renderings/*.md` or any subdirectory — read only the chosen file+- Globbing `image-renderings/*.md` or any subdirectory — read only the chosen preset or exact custom-reference files- Placing an image without updating its `image_prompts.json` `status` and the resource list status- Switching rendering or core deck-color semantics for a single image—`hero_page` is not an exception to deck-wide coherence- Embedding body copy, data points, bullet lists, or long quotes inside an image — those route to SVGdiff --git a/skills/ppt-master/references/image-renderings/_index.md b/skills/ppt-master/references/image-renderings/_index.mdindex fdd0c5d5..4e4cbe99 100644--- a/skills/ppt-master/references/image-renderings/_index.md+++ b/skills/ppt-master/references/image-renderings/_index.md@@ -10,7 +10,7 @@ A **rendering** is a visual style family: line quality, texture, depth, material## 1. Catalog (20 renderings)-Each rendering has its own file with: style paragraph, line / texture / depth notes, deck HEX usage, and a fewshot prompt snippet. **Read only the file for the rendering you pick** — never glob the directory.+Each rendering has its own file with: style paragraph, line / texture / depth notes, deck HEX usage, and a fewshot prompt snippet. A preset lock reads that one file. A catalog-based `custom` reads every preset named in `image_rendering_references`; a novel `custom` may omit references. Never glob the directory.### 1.1 Modern / commercial (the corporate-PPT main field)@@ -62,7 +62,7 @@ Whenever proposed image usage includes `ai`, Stage 2 authors one separate, visib|---|---|| Length | One paragraph, 2-5 sentences || Axes covered | line / texture / depth / material / mood (same as preset files) |-| Forbidden | Naming a competing preset ("like blueprint but warmer") |+| Catalog basis | When existing renderings are combined or borrowed, name every exact id and read every named file before synthesis |```yaml- image_rendering: custom@@ -71,6 +71,8 @@ Whenever proposed image usage includes `ai`, Stage 2 authors one separate, visib**Hard rule**: the custom candidate is mandatory when AI images are proposed; selecting `custom` is a tail-case, not the default. See [`strategist-image.md`](../strategist-image.md) for the Stage-2 carrier and downstream lock behavior.+Write `image_rendering_references` only when the custom direction actually uses catalog material. Keep the list exact: a blend of `screen-print` and `watercolor` reads both files and lists both ids. A genuinely new rendering with no catalog source omits the field and proceeds from its standalone behavior; never invent a reference merely to legitimize `custom`.+---## 2. Auto-selection table — `design_spec` → rendering@@ -105,6 +107,6 @@ Match `design_spec.md d` (mode + `visual_style`) against this table. First match1. From `design_spec.md` extract `d. Style` mode + descriptor.2. Find the matching row above; pick the primary recommendation.-3. `read_file image-renderings/<chosen>.md` and apply its style paragraph when assembling each prompt per [`image-generator.md`](../image-generator.md) §4. (For `custom`, this step is replaced by the consumption branch in [`image-generator.md`](../image-generator.md) Step 2 — no preset file to read.)+3. For a preset, read `image-renderings/<chosen>.md`. For `custom`, read every file named in `image_rendering_references`, then synthesize them under the confirmed behavior; with no references, use the novel behavior directly. Apply the result when assembling prompts per [`image-generator.md`](../image-generator.md) §4.**Lock for the whole deck.** Don't change rendering between images in the same deck.diff --git a/skills/ppt-master/references/modes/_index.md b/skills/ppt-master/references/modes/_index.mdindex 84f193c2..b6e1ca5a 100644--- a/skills/ppt-master/references/modes/_index.md+++ b/skills/ppt-master/references/modes/_index.md@@ -8,7 +8,7 @@ A **mode** is the deck's **narrative + persuasion skeleton** — how the argumen## 1. Catalog (5 modes)-Each mode has its own file with: narrative skeleton, page-structure tendencies, speaker-notes register, and a page skeleton example. **Read only the file for the mode you lock** — never glob the directory.+Each mode has its own file with: narrative skeleton, page-structure tendencies, speaker-notes register, and a page skeleton example. A preset lock reads that one file. A catalog-based `custom` reads every preset named in `mode_references`; a novel `custom` may omit references. Never glob the directory.| Mode | Narrative skeleton | Best for ||---|---|---|@@ -54,7 +54,7 @@ Each mode has its own file with: narrative skeleton, page-structure tendencies,1. Strategist reads this index at confirmation `d. Layer 1`.2. Preselect one mode from the auto-selection table + the confirmed communication contract and source structure; separately author the visible AI custom candidate required by §4.3. Record the confirmed mode and rationale in `design_spec.md`, then project `- mode: <name>` into `spec_lock.md`.-4. Executor reads **only** `modes/<locked-mode>.md` at generation entry — never globs this directory.+4. Executor reads `modes/<locked-mode>.md` for a preset. For `custom`, it reads every file listed in `mode_references` before applying `mode_behavior`; with no references, it applies the novel behavior directly. Never glob this directory.**Lock scope**: deck-wide (one mode per deck). The five are the catalog you select from; if the structure is genuinely mixed, pick the mode of the body pages and let pages vary within it, or recommend a `custom` blend (§4). Recommend the best fit; the user confirms.@@ -64,7 +64,9 @@ Each mode has its own file with: narrative skeleton, page-structure tendencies,`custom` holds **any bespoke narrative direction the five don't give as-is** — and what *kind* of thing it is doesn't matter. It might be a nameable cadence (dialectic 正反合, myth-vs-reality, countdown / Top-N, Socratic), a deliberate multi-act fusion of several modes, or the user's own feel for how the deck should carry (confrontational here, detached there). Don't try to taxonomize it.-**Always author the candidate; select it only when warranted.** Stage 2 includes one visible, non-empty AI custom proposal beside the five presets, spelling out the cadence / fusion / posture in plain language. It is initially unselected and does not replace the best-fit preset recommendation unless the user already supplied that exact custom direction; with a template, it must fit available prototype capacity. When the user selects it, the editable prose is saved as `mode: custom` plus `mode_behavior`; otherwise it remains recommendation-only. The Strategist crystallizes a selected custom direction in the Design Spec first, then projects the same pair to `spec_lock.md`. The Executor follows that prose in place of a preset file. (This records the intent so it survives 20 pages of generation — the Executor only ever reads `spec_lock.md`, never the chat.)+**Always author the candidate; select it only when warranted.** Stage 2 includes one visible, non-empty AI custom proposal beside the five presets, spelling out the cadence / fusion / posture in plain language. It is initially unselected and does not replace the best-fit preset recommendation unless the user already supplied that exact custom direction; with a template, it must fit available prototype capacity. When the user selects it, the editable prose is saved as `mode: custom` plus `mode_behavior`; otherwise it remains recommendation-only. The Strategist crystallizes a selected custom direction in the Design Spec first, then projects the behavior and any actual catalog basis to `spec_lock.md`. The Executor reads every listed basis file before following that prose, or follows it directly when the direction is novel. (This records the intent so it survives 20 pages of generation — the Executor only ever reads `spec_lock.md`, never the chat.)++**Mandatory — read every catalog source actually used**: If the proposal combines or borrows an existing mode, name its exact catalog id in the visible proposal and read that mode file before writing the synthesis. A `pyramid` + `narrative` fusion therefore reads both [`pyramid.md`](./pyramid.md) and [`narrative.md`](./narrative.md), then writes `mode_references: pyramid, narrative` beside `mode_behavior`. Do not add loosely related references after the fact. A genuinely new cadence with no catalog source writes no `mode_references` and may proceed from its standalone behavior.> **One value per deck — fusion is *one* `custom`, not several modes.** A deck always locks a single `mode`. A multi-mode blend is expressed as **one** `mode: custom` whose `mode_behavior` paragraph describes the acts — never by locking several modes.>diff --git a/skills/ppt-master/references/strategist-image.md b/skills/ppt-master/references/strategist-image.mdindex 7662bba8..71eefb36 100644--- a/skills/ppt-master/references/strategist-image.md+++ b/skills/ppt-master/references/strategist-image.md@@ -18,9 +18,9 @@ For ≥3 AI-generated same-family spots, plan one unplaced `ai` Illustration She## 2. AI Image Strategy — propose before Stage 2; lock only for confirmed `ai`-When proposed sources include `ai`, read every entry in [`image-renderings/_index.md`](./image-renderings/_index.md) before constructing Stage 2. Unless the user or active template already names a rendering, place at least three credible, distinct preset renderings across the coordinated safe/shifted/bold directions; a genuine compatibility shortfall may return fewer with a reason. Each preset `image_strategy` carries localized `rendering`, `visual`, and `mood` only. Mood includes a recognizable real-world analogy. Image colors always inherit that direction's deck HEX roles; never add an image palette or alter deck colors to rescue a rendering.+When proposed sources include `ai`, read [`image-renderings/_index.md`](./image-renderings/_index.md) before constructing Stage 2. Unless the user or active template already names a rendering, place at least three credible, distinct preset renderings across the coordinated safe/shifted/bold directions; a genuine compatibility shortfall may return fewer with a reason. Each preset `image_strategy` carries localized `rendering`, `visual`, and `mood` only. Mood includes a recognizable real-world analogy. Image colors always inherit that direction's deck HEX roles; never add an image palette or alter deck colors to rescue a rendering.-Also write one `custom_candidates.image_strategy` under the Confirm UI contract: localized `name` / `visual` / `mood`, `rendering: custom`, and non-empty localized `behavior` satisfying the catalog grammar. Keep it unselected unless the user supplied it (`recommend.image_strategy: custom`); under a template it obeys inherited identity and application. Only a selected custom locks its edited behavior as `image_rendering_behavior`; otherwise discard it downstream. Ignore legacy `image_palette`.+Also write one `custom_candidates.image_strategy` under the Confirm UI contract: localized `name` / `visual` / `mood`, `rendering: custom`, and non-empty localized `behavior` satisfying the catalog grammar. If it combines or borrows existing renderings, name every exact id in the visible proposal and read every corresponding `image-renderings/<id>.md` before writing the synthesis. If it is genuinely novel, read no preset file and name no catalog basis. Keep it unselected unless the user supplied it (`recommend.image_strategy: custom`); under a template it obeys inherited identity and application. Only a selected custom locks its edited behavior as `image_rendering_behavior`; when catalog material is actually used, also project the exact ids as `image_rendering_references`, otherwise omit that field. Discard an unselected candidate downstream. Ignore legacy `image_palette`.For specialized or regulated paper-figure subjects, preserve the prompt depth required by [`image-generator.md`](./image-generator.md) §4.2 rather than shortening to a generic brief. Scan the outline for genuine image-led pages, list the proposed hero pages in Stage-2 `image_notes` so the user can retain, edit, or remove them in the same confirmation, then mark only the confirmed pages' AI rows `page_role: hero_page`; local is the default. `text_policy: embedded` is reserved for lettering that must be fused into the artwork; ordinary titles, data, labels, and prose remain editable SVG. Analyze confirmed provided assets before writing §VIII.diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.mdindex 3b05ac02..40682cfb 100644--- a/skills/ppt-master/references/strategist.md+++ b/skills/ppt-master/references/strategist.md@@ -101,7 +101,7 @@ When authoring §IX, translate every purpose named in `communication_intent` intTwo independent layers, each locks one preset or `custom`. Output: `d. Mode: <mode> + Visual style: <visual_style>`.-> **Mandatory AI custom candidates.** Every Stage-2 `recommendations.json` carries visible, non-empty `custom_candidates.mode` and `.visual_style`, initially unselected unless the user supplied that exact direction. If selected, spell the proposal out in plain language and save literal `custom` plus the edited `mode_behavior` / `visual_style_behavior`; otherwise it remains recommendation-only. Never write bespoke prose as the enum value.+> **Mandatory AI custom candidates.** Every Stage-2 `recommendations.json` carries visible, non-empty `custom_candidates.mode` and `.visual_style`, initially unselected unless the user supplied that exact direction. If a proposal combines or borrows catalog entries, read every named entry file before authoring the synthesis and name those exact ids in the visible proposal; a genuinely novel proposal needs no catalog reference. If selected, spell the proposal out in plain language and save literal `custom` plus the edited `mode_behavior` / `visual_style_behavior`; otherwise it remains recommendation-only. Never write bespoke prose as the enum value.#### Layer 1 — Communication mode@@ -112,10 +112,10 @@ The deck's **narrative + persuasion skeleton** — how the argument is organized**Source**:- User supplied their own outline / structure → it is authoritative. Transcribe it into `§IX` as given (page order + titles preserved); still lock a mode, but for register / voice and page-internal treatment, **not** to reshape — never reorder the user's pages or rewrite their given titles. Note in `design_spec.md` that the structure is user-authored. `briefing` imposes the least if no particular "讲法" is intended.- Beautify / re-layout profile ([`beautify-pptx.md`](../workflows/profiles/beautify-pptx.md)) → the extracted source content is authoritative and **verbatim**, one step stricter than the user-outline case above. Each source slide becomes exactly one `§IX` page in source order; transcribe every content block word-for-word — never reshape / re-primary / condense / merge / split / reword. Lock `mode: briefing`; color (e) and typography (g) are whatever the user confirmed in the beautify plan — the source identity (theme or observed) by default, or a content / brand-aware alternative the beautify plan offered and the user picked — locked as truth (the beautify plan already ran the recommendation through the confirm UI, so do not re-recommend here). Charts / tables / images are regenerated from their extracted data in the inherited style (route chart/table data to §VII, pictures to §VIII) — data values stay frozen, the rendering is the deck's own; never carried over verbatim. Layout, hierarchy, rhythm, and visual rendering are what gets redesigned.-- A bespoke direction the five don't give — a nameable cadence (dialectic 正反合, myth-vs-reality, countdown, Socratic), a multi-act fusion of modes, or the user's own feel (confrontational here, detached there). Either the user asks, **or you recommend it** when a fusion / bespoke direction genuinely serves the deck better than a single preset (a recommendation the user confirms, like every lock). The *kind* doesn't matter → `mode: custom` + a `mode_behavior:` paragraph that **crystallizes the intent** (act sequence or posture shifts, title voice, page rhythm, register) concretely enough for the Executor to follow per page; it reads only `spec_lock.md`, never the chat. One deck locks **one** value — a fusion is one `custom` describing the acts, never several modes. Avoid only the *dodge*: don't default to `custom` when a preset genuinely fits, and prefer a dominant mode + page-level variation when one mode leads.+- A bespoke direction the five don't give — a nameable cadence (dialectic 正反合, myth-vs-reality, countdown, Socratic), a multi-act fusion of modes, or the user's own feel (confrontational here, detached there). Either the user asks, **or you recommend it** when a fusion / bespoke direction genuinely serves the deck better than a single preset (a recommendation the user confirms, like every lock). The *kind* doesn't matter → `mode: custom` + a `mode_behavior:` paragraph that **crystallizes the intent** (act sequence or posture shifts, title voice, page rhythm, register) concretely enough for the Executor to follow per page; it reads only `spec_lock.md`, never the chat. If the direction uses existing modes, read every corresponding `modes/<id>.md` before synthesis and retain those exact ids as its catalog basis; if it is genuinely new, do not invent a basis. One deck locks **one** value — a fusion is one `custom` describing the acts, never several modes. Avoid only the *dodge*: don't default to `custom` when a preset genuinely fits, and prefer a dominant mode + page-level variation when one mode leads.- No user structure or cadence → recommend from the confirmed `communication_intent`, `audience_outcome`, source texture, and delivery context using the index's auto-selection table. Composite intent does not automatically require `custom`: choose the dominant spine of the body pages when one exists; use a concrete `custom` act sequence only when no single spine can serve the stated priority / sequence. Present as a recommendation; the user may override.-Record the confirmed mode and rationale in `design_spec.md` first, then project `- mode:` to `spec_lock.md` (for `custom`, also project the sibling `- mode_behavior:` paragraph). Executor loads only that one mode file, or follows `mode_behavior` when the value is `custom`.+Record the confirmed mode and rationale in `design_spec.md` first, including the exact catalog basis when a selected custom uses one. Then project `- mode:` to `spec_lock.md`; for `custom`, also project `- mode_behavior:` and, only when catalog material is actually used, `- mode_references: <id>, <id>`. Executor reads one file for a preset. For `custom`, it reads every listed reference before applying the behavior; an unreferenced novel custom follows the behavior directly.#### Layer 2 — Visual style@@ -131,7 +131,7 @@ The deck's **visual aesthetic** — shape language, decoration density, whitespa**Carries no color.** A visual style governs how the deck's HEX (locked at `e`) is *used* — never which colors, same discipline as [`image-renderings`](./image-renderings/_index.md). When the deck has AI images, prefer the style's paired rendering so layout and illustration share one aesthetic.-Record the confirmed visual style and rationale in `design_spec.md` first, then project `- visual_style:` to `spec_lock.md`. Executor loads only that one visual-style file.+Record the confirmed visual style and rationale in `design_spec.md` first, including the exact catalog basis when a selected custom uses one. Then project `- visual_style:` to `spec_lock.md`; for `custom`, also project `- visual_style_behavior:` and, only when catalog material is actually used, `- visual_style_references: <id>, <id>`. Executor reads one file for a preset. For `custom`, it reads every listed reference before applying the behavior; an unreferenced novel custom follows the behavior directly.**Conditional template workspace**: When Generate Step 3 installed an explicit workspace path into `<project_path>/templates/`, read [`strategist-template.md`](./strategist-template.md) before completing Stage 2. It owns the editable natural-language application plan, confirmed-value consumption, AI-authored prototype selection, internal reuse/adherence derivation, inherited design precedence, and structured-lock planning. Bare names, style words, and free-design projects do not trigger it.@@ -202,7 +202,7 @@ See [`../templates/icons/README.md`](../templates/icons/README.md) for the curre### g. Typography Plan Confirmation (Font + Size)-🚧 **GATE**: Read the locked visual-style file's §2 Typography character before recommending type. For a custom style, use its `visual_style_behavior`. The title carries the character; the body may remain neutral.+🚧 **GATE**: Read the locked preset visual-style file's §2 Typography character before recommending type. For a custom style, first read every file in `visual_style_references` when present, then resolve their typography character under `visual_style_behavior`; a novel custom uses the behavior directly. The title carries the character; the body may remain neutral.**Family selection**:@@ -325,7 +325,7 @@ Confirmation `d` locks two independent catalog items:- **Mode** — narrative skeleton: [`modes/_index.md`](./modes/_index.md) → `pyramid` / `narrative` / `instructional` / `showcase` / `briefing`.- **Visual style** — aesthetic: [`visual-styles/_index.md`](./visual-styles/_index.md) → presets + `custom`.-Read the relevant `_index.md` at confirmation `d` (Layer 1 / Layer 2) for its catalog table and auto-selection. Executor loads the locked mode + visual-style files at generation (see [`generate-pptx`](../workflows/generate-pptx.md) Step 6).+Read the relevant `_index.md` at confirmation `d` (Layer 1 / Layer 2) for its catalog table and auto-selection. Executor loads one locked file per preset, or every exact custom reference before applying its behavior (see [`generate-pptx`](../workflows/generate-pptx.md) Step 6).---@@ -362,7 +362,7 @@ Free-design patterns are starting points, not quotas. Adjust composition, spacin### 6.1 Content Planning Strategy-Content-outline and speaker-notes strategy follow the deck's locked **mode** — see [`modes/_index.md`](./modes/_index.md) and the locked mode's file. The guidance below applies within any mode:+Content-outline and speaker-notes strategy follow the deck's locked **mode** — see [`modes/_index.md`](./modes/_index.md), then the locked preset file or every listed custom reference plus its behavior. The guidance below applies within any mode:**Reading mode controls information carriage, not communication intent.** `result.json delivery_purpose` is retained as the compatibility key for `text` (read-close) / `balanced` (business, default) / `presentation`, confirmed with the complete deck solution in Stage 2. It decides how meaning is divided among the page, visuals, presenter, and notes. The body baseline (§g) is one consequence, not the definition:@@ -411,7 +411,7 @@ Generate Step 4 owns both artifact scaffolds. `design_spec.md` is the Strategist**Contextual extension during execution**: a page-local color, gradient stop, effect paint, or export-safe display family may remain only in that SVG when its use is genuinely local. If the same value acquires a recurring semantic role across pages, add one named row to `spec_lock.md` before the next affected page and regenerate page-context. This reverse lock update is legitimate consolidation, not a checker workaround; never add one-off values merely to silence an informational comparison.- **Communication trace is mandatory**: Keep the full confirmed communication contract in `design_spec.md §I`, then project only `audience`, `objective`, `core_message`, and canonical `consumption_mode` into `spec_lock.md communication`. Write `objective` as one concise execution sentence that preserves both the confirmed `communication_intent` and the success condition in `audience_outcome`; do not copy `delivery_context`, `artifact_afterlife`, dates, provenance, or conflict-resolution commentary into the lock. Before finalizing §IX, check that every named purpose has at least one outline obligation and **every Slide block**, including cover / divider / closing pages, has an `Audience move` that advances the global outcome. A page that advances no purpose or outcome should be merged, rewritten, or cut. `project_manager.py validate` and `svg_quality_checker.py` enforce the compact lock fields and per-page move presence, not their subjective quality.- - **Custom behavior is concise and executable**: For confirmed `custom` mode or visual style, project one resolved `mode_behavior` / `visual_style_behavior` sentence or short paragraph. Preserve the confirmed direction, reference locked role names such as `colors.primary` when needed, and omit selection history, contradictions, precedence explanations, or other Design Spec provenance. Page-context carries these fields directly to Executor.+ - **Custom behavior is concise and executable**: For confirmed `custom` mode or visual style, project one resolved `mode_behavior` / `visual_style_behavior` sentence or short paragraph. When the direction actually combines or borrows catalog entries, also project the exact, comma-separated `mode_references` / `visual_style_references`; omit the field for a genuinely novel direction and never fabricate a nearby reference. Preserve the confirmed direction, reference locked role names such as `colors.primary` when needed, and omit selection history, contradictions, precedence explanations, or other Design Spec provenance. Page-context carries these fields directly to Executor.- **page_rhythm is mandatory**: Based on the page list in §IX Content Outline, assign each page one of `anchor` / `dense` / `breathing`. This is what breaks the uniform "every page is a card grid" feel. New locks may not omit the section; consumer omission behavior is owned by [`executor-base.md`](executor-base.md) §2.1.- **Fact IDs and scenario labels are mandatory when applicable**: Read any `sources/*.facts.json`. For each §IX page, list the stable IDs actually used; never cite an ID whose claim is absent from the page. Mark invented KPIs/targets/internal ratios as `Data class: scenario` and state which values are scenario data. Executor carries external sources into notes/footnotes and renders a visible scenario label for scenario figures.- **Rhythm follows narrative, not quota**: `breathing` pages mark natural pauses — chapter transitions, standalone emphasis (hero quote / big number), SCQA bridges. Dense decks may legitimately be all `dense`. **Do NOT invent filler pages** ("Thank you", empty dividers) to pad rhythm — every `breathing` page must say something independent. Consumption mode biases the overall lean (`presentation` toward more `anchor` / `breathing`, `text` toward `dense`; see §6.1) — a bias, never a quota.diff --git a/skills/ppt-master/references/visual-styles/_index.md b/skills/ppt-master/references/visual-styles/_index.mdindex 8b73aaeb..6f702f15 100644--- a/skills/ppt-master/references/visual-styles/_index.md+++ b/skills/ppt-master/references/visual-styles/_index.md@@ -10,7 +10,7 @@ A **visual style** is how the deck **looks** — shape language, decoration dens## 1. Catalog-Each style has its own file with: shape & decoration, typography character, color-usage discipline (no HEX), texture / elevation, and the paired image-rendering. **Read only the file for the style you lock** — never glob the directory. The catalog mirrors [`image-renderings`](../image-renderings/_index.md): each style's "Paired rendering" names the illustration family that shares its aesthetic.+Each style has its own file with: shape & decoration, typography character, color-usage discipline (no HEX), texture / elevation, and the paired image-rendering. A preset lock reads that one file. A catalog-based `custom` reads every preset named in `visual_style_references`; a novel `custom` may omit references. Never glob the directory. The catalog mirrors [`image-renderings`](../image-renderings/_index.md): each style's "Paired rendering" names the illustration family that shares its aesthetic.> The **`visual_style` value is only ever a first-column `id`** (`swiss-minimal`, `editorial`, …). The "Paired rendering" column lists **§h image-rendering** names (`flat`, `minimalist-swiss`, `digital-dashboard`, …) — never lock one of those as the `visual_style`; they belong to confirmation h.>@@ -94,6 +94,8 @@ Each style has its own file with: shape & decoration, typography character, coloStage 2 always authors one visible, non-empty AI custom proposal beside the preset spectrum. Its paragraph names shape language, composition geometry (page-scale moves), decoration density, whitespace, typographic character, and texture — **no HEX, no color names as values**. The proposal is initially unselected and remains recommendation-only unless the user chooses it; a template-backed proposal must stay inside the inherited identity and confirmed application plan. When selected, record the edited aesthetic in the Design Spec first, then project `- visual_style: custom` plus `- visual_style_behavior:` to `spec_lock.md`. The candidate is mandatory; selecting `custom` remains a tail-case, not the default.+**Mandatory — read every catalog source actually used**: If a custom proposal combines or borrows existing styles, name their exact ids in the visible proposal and read each corresponding file before synthesizing its shape, composition, typography, whitespace, and texture rules. Persist those ids as `visual_style_references`. Do not attach references merely because they are adjacent in the catalog. A genuinely new aesthetic with no catalog source omits `visual_style_references` and proceeds from its standalone behavior.+---## 4. How to use@@ -101,6 +103,6 @@ Stage 2 always authors one visible, non-empty AI custom proposal beside the pres1. Strategist reads this index at confirmation `d. Layer 2`.2. Preselect one style from the auto-selection table + the deck's vibe; separately author the visible AI custom proposal from §3.3. Record the confirmed style and rationale in `design_spec.md`, then project `- visual_style: <name>` into `spec_lock.md`.-4. Executor reads **only** `visual-styles/<locked-style>.md` at generation entry — never globs this directory.+4. Executor reads `visual-styles/<locked-style>.md` for a preset. For `custom`, it reads every file listed in `visual_style_references` before applying `visual_style_behavior`; with no references, it applies the novel behavior directly. Never glob this directory.**Lock scope**: deck-wide (one style per deck). It anchors taste as a **reference**, not a whitelist — pages may deviate with reason.diff --git a/skills/ppt-master/scripts/confirm_ui/static/app.js b/skills/ppt-master/scripts/confirm_ui/static/app.jsindex 0326e686..1ba9679d 100644--- a/skills/ppt-master/scripts/confirm_ui/static/app.js+++ b/skills/ppt-master/scripts/confirm_ui/static/app.js@@ -83,7 +83,7 @@image_strategy_visual: "Visual",image_strategy_mood: "Mood",image_strategy_ai_custom: "AI custom proposal",- image_strategy_ai_custom_desc: "A complete out-of-catalog rendering proposal. Select it to edit.",+ image_strategy_ai_custom_desc: "A novel or multi-reference rendering proposal. Select it to edit.",image_strategy_custom_placeholder: "Describe the exact generated-image direction, subjects, composition, style cues, or things to avoid.",image_strategy_reference_hint: "Reference images show rendering only. Final AI images inherit the deck color scheme selected above.",image_strategy_no_reference: "No reference image for this custom choice.",@@ -221,7 +221,7 @@image_strategy_visual: "ビジュアル",image_strategy_mood: "ムード",image_strategy_ai_custom: "AIカスタム案",- image_strategy_ai_custom_desc: "カタログ外の完全なレンダリング案です。選択後に編集できます。",+ image_strategy_ai_custom_desc: "新規または複数の既存表現を統合したレンダリング案です。選択後に編集できます。",image_strategy_custom_placeholder: "生成画像の方向性、被写体、構図、スタイル要素、避けたい要素を具体的に入力してください。",image_strategy_reference_hint: "参照画像はレンダリングのみを示します。最終AI画像の色は上で選んだデッキ配色を継承します。",image_strategy_no_reference: "このカスタム選択には参照画像がありません。",@@ -359,7 +359,7 @@image_strategy_visual: "视觉",image_strategy_mood: "情绪",image_strategy_ai_custom: "AI 自定义方案",- image_strategy_ai_custom_desc: "一套完整的目录外渲染方案;选择后可以编辑。",+ image_strategy_ai_custom_desc: "一套全新或综合多个已有风格的渲染方案;选择后可以编辑。",image_strategy_custom_placeholder: "描述生成图的具体方向、主体、构图、风格关键词或需要避免的内容。",image_strategy_reference_hint: "参考图只展示渲染风格;最终 AI 图片直接继承上方已选的整套 PPT 配色。",image_strategy_no_reference: "自定义选择没有参考图。",diff --git a/skills/ppt-master/scripts/docs/confirm_ui.md b/skills/ppt-master/scripts/docs/confirm_ui.mdindex a2b516a0..75d74664 100644--- a/skills/ppt-master/scripts/docs/confirm_ui.md+++ b/skills/ppt-master/scripts/docs/confirm_ui.md@@ -202,7 +202,7 @@ After Stage 2 is confirmed, overwrite it with Stage-3 production recommendations```- `recommend.*` names each recommended id. New mode / style values use a catalog id or literal `custom`; arbitrary prose values are legacy-only. Use `recommend.image_strategy: "custom"` only when an explicit user-supplied image direction should start selected. Missing recommendations fall back to the normal preset. Legacy aliases remain accepted; new files write canonical ids.-- `custom_candidates` is recommendation-only. Mode / style carry localized `name` + `behavior`; conditional image strategy also carries `rendering: "custom"`, `visual`, and `mood`. The server rejects missing required candidates; the UI shows full copy, edits it only after selection, rejects a selected blank, and omits unselected candidates from `result.json`. Template-backed proposals obey inherited identity, prototype capacity, and `template_application`.+- `custom_candidates` is recommendation-only. Mode / style carry localized `name` + `behavior`; conditional image strategy also carries `rendering: "custom"`, `visual`, and `mood`. When a proposal combines or borrows existing catalog entries, the visible behavior names every exact id and Strategist reads every corresponding file before authoring it; a genuinely novel proposal names none. The server rejects missing required candidates; the UI shows full copy, edits it only after selection, rejects a selected blank, and omits unselected candidates from `result.json`. Template-backed proposals obey inherited identity, prototype capacity, and `template_application`.- `audience`, `communication_intent`, and `audience_outcome` are load-bearing Stage-1 reasoning inputs, so seed concrete recommendations when the evidence supports them; they are not required user inputs. Every Stage-1 prose field may be blank after confirmation. The complete six-field contract stays in `result.json` and `design_spec.md`; `spec_lock.md communication` receives only the compact `audience` / `objective` / `core_message` execution projection plus the applicable reading mode. `communication_intent` may preserve several purposes plus priority / sequence; never add a `primary_job` enum.- Do not write `recommend.template_reuse_scope` or `recommend.template_adherence`. Strategist records those internal exporter values later in `spec_lock.md` after inspecting the actual template and current content.- For an active template workspace, write one editable prose field as top-level `template_application.value`. It summarizes actual page/prototype use and preservation/reorganization decisions. Omit it for free design. The UI returns the current string through Stage 2, Stage 3, and final confirmation; Strategist then persists the final effective plan as `- **Template Application**: ...` in `design_spec.md §I`, and `page-context` projects it to Executor. Never replace it with internal reuse/adherence ids or a fixed option menu.@@ -215,7 +215,7 @@ After Stage 2 is confirmed, overwrite it with Stage-3 production recommendations- **Per-role size override** (parallel to color's per-role HEX override): besides `body_size`, the page exposes editable inputs for `title` / `subtitle` / `annotation`. The browser applies one documented deterministic dependency chain: `reading mode → body baseline → unpinned role sizes` (role ramp: `body ×` the §g ratios). Changing reading mode updates the body and all unpinned roles locally; changing body updates unpinned roles locally. Editing body or a role pins that value, so later reading-mode changes do not overwrite it. Font / direction-card selection preserves all current sizes. This is a browser-only state update: it performs no fetch, asks the backend to author no new recommendations, and a re-render preserves exactly what the user sees. Each role input is labelled as px and shows an approximate pt equivalent (`1px = 0.75pt`) for orientation. The final values are written to `result.json` as `typography.sizes: { "title", "subtitle", "annotation" }` in **px** — every canvas, no pt and no `sizes_pt` provenance. Candidate `sizes` remain accepted for compatibility, but the fresh Stage-2 baseline is normalized through the same local ramp before first render.- **`delivery_purpose` compatibility key / Reading mode** (enumerable, PPT only) decides where meaning is carried, not merely how large type is: `text` makes pages self-contained with complete sentences, short prose, captions, tables, and necessary detail; `balanced` shares explanation between page and presenter; `presentation` uses one idea, concise claims, and visual evidence while speech / notes carry the detail. It therefore governs page grammar, granularity, density / rhythm, and note burden. Reading-mode cards intentionally show **no px value**; the typography section owns the separately visible body / role sizes and applies any local default. It is surfaced in Stage 2 beside the visual system, separate from communication intent. `recommend.delivery_purpose` pre-selects one; `result.json` retains the key, while `spec_lock.md` uses canonical `consumption_mode`. Non-PPT canvases omit it.- **Combined style preview** — a compact live "overall impression" strip sits just above the color section and is **sticky**: it pins under the topbar so it stays visible while the user scrolls through the color / icon / typography sections, keeping the picking controls and their combined effect on screen together. It applies the currently selected color palette **and** typography (heading sample in `primary` over `background`, body sample in `body_text`, an `accent` bar, a `secondary_bg` chip) and repaints on every color / HEX-override / font / `body_size` change. It does not replace the per-candidate swatches or font samples (those stay for picking); it is deliberately an abstract style chip, **not** a slide-layout preview — page layout preview remains the live-preview server's job (Step 6). No schema field; it derives entirely from the existing color + typography selections.-- **Generated-image direction** appears only for `image_usage: ai`: up to three preset cards plus one full-width AI custom proposal. Custom has no preset dropdown; selection makes it editable and submits `rendering: "custom"` + `behavior`. The live preview follows the selection. No image palette is written; deck colors remain authoritative, and legacy `image_strategy.palette` is ignored.+- **Generated-image direction** appears only for `image_usage: ai`: up to three preset cards plus one full-width AI custom proposal. Custom has no preset dropdown; selection makes it editable and submits `rendering: "custom"` + `behavior`. If that behavior uses catalog renderings, it visibly names their exact ids; Strategist retains that confirmed basis as optional `image_rendering_references` in `spec_lock.md`. A genuinely novel behavior produces no reference row. The live preview follows the selection. No image palette is written; deck colors remain authoritative, and legacy `image_strategy.palette` is ignored.- **`design_directions`** is the canonical Stage-2 spectrum: ≥3 safe / shifted / bold bundles with localized copy, style, icons, conditional image strategy, complete CJK/Latin typography, and HEX `background`, `secondary_bg`, `primary`, `accent`, `secondary_accent`, `body_text`. Selection applies the bundle; component controls override it. `result.json` stores components, not a direction id.- `recommend.generation_mode` and `refine_spec` mirror the two mandatory notes in [`generate-pptx`](../../workflows/generate-pptx.md) Step 4. Confirmed `generation_mode: "split"` / `refine_spec: true` are explicit user choices, equivalent to opting in through chat.- `content_divergence` is a **free-text** Stage-1 source-treatment field. Blank means a balanced default; facts stay sourced at every level. Strategist consumes it while authoring §IX and records it in `design_spec.md §I`; it is not written to `spec_lock.md`. Beautify sends `{ "value": "keep source wording and page structure verbatim", "locked": true }`, so the UI displays it read-only and the server restores it on every staged submit. Template-fill does not use this confirmation flow and does not surface it.@@ -254,7 +254,7 @@ After Stage 2 is confirmed, overwrite it with Stage-3 production recommendations}```-The shape above is final. Selected custom values use `mode: custom` + `mode_behavior`, `visual_style: custom` + `visual_style_behavior`, or `image_strategy.rendering: custom` + `behavior`. Intermediate writes retain accumulated fields; legacy tier names remain read-compatible.+The shape above is final. Selected custom values use `mode: custom` + `mode_behavior`, `visual_style: custom` + `visual_style_behavior`, or `image_strategy.rendering: custom` + `behavior`. During Design Spec and lock authoring, Strategist projects optional `mode_references`, `visual_style_references`, or `image_rendering_references` only when that confirmed behavior actually uses named catalog sources; genuinely novel custom behavior has no reference list. Intermediate writes retain accumulated fields; legacy tier names remain read-compatible.**Final-result consumption contract.** A final result is the user-confirmed input contract for the Strategist's Design Spec, not another recommendation input. After the final wait, Generate Step 4 reads the complete final object exactly once and retains it while Strategist writes and audits `design_spec.md` against every explicitly present field. Normal lock authoring and downstream execution do not reopen `result.json`; the completed Design Spec is the durable authority. Only after that audit passes does Strategist author `spec_lock.md` from the Design Spec plus current execution context, selecting stable anchors and routing rather than copying every field or enumerating every legal color/font. It must not omit, substitute, narrow, weaken, reinterpret, or re-recommend a confirmed value. If one value cannot be honored, the owning workflow reports or pauses under failure recovery; it never deletes the requirement to keep the pipeline moving.diff --git a/skills/ppt-master/scripts/docs/project.md b/skills/ppt-master/scripts/docs/project.mdindex 368fc40b..c1205bdd 100644--- a/skills/ppt-master/scripts/docs/project.md+++ b/skills/ppt-master/scripts/docs/project.md@@ -42,7 +42,10 @@ Notes:- `validate` parses the existing Markdown artifacts against`templates/schemas/design_spec.schema.json` and`templates/schemas/spec_lock.schema.json`. It reports missing sections and- fields, illegal enums, malformed page keys, and unmet conditional sections;+ fields, illegal enums, malformed page keys, and unmet conditional sections.+ When optional custom reference lists are present, it also requires every id+ to resolve to the matching mode, visual-style, or image-rendering catalog,+ rejects duplicates, and rejects reference rows on non-custom selections;it does not rewrite either artifact or compare their values for textualequality. It also does not prove final-confirmation → Design Spec fidelity orDesign Spec/context → lock semantic fidelity; Generate Step 4 owns those twodiff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex 47ee3b5b..dcb13af3 100644--- a/skills/ppt-master/scripts/prompt_audit_manifest.json+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json@@ -28,12 +28,12 @@"skills/ppt-master/references/svg-effects.md": 11600,"skills/ppt-master/references/native-data-interface.md": 6200,"skills/ppt-master/references/pptx-structure-interface.md": 4300,- "skills/ppt-master/references/strategist.md": 12400,- "skills/ppt-master/references/strategist-image.md": 1800,+ "skills/ppt-master/references/strategist.md": 12900,+ "skills/ppt-master/references/strategist-image.md": 2100,"skills/ppt-master/references/strategist-template.md": 2100,"skills/ppt-master/templates/design_spec_reference.md": 850,- "skills/ppt-master/templates/spec_lock_reference.md": 1450,- "skills/ppt-master/workflows/generate-pptx.md": 12000,+ "skills/ppt-master/templates/spec_lock_reference.md": 1650,+ "skills/ppt-master/workflows/generate-pptx.md": 12200,"skills/ppt-master/workflows/stages/apply-template-workspace.md": 1800},"load_sets": {@@ -120,7 +120,7 @@"max_tokens": 10800},"route.generate.planning": {- "description": "Fixed Generate-PPTX planning context through the Strategist core; schemas and scaffolds are tool-consumed.",+ "description": "Generate-PPTX planning through Strategist, including representative multi-source custom mode/style synthesis; schemas and scaffolds are tool-consumed.","scope": "cumulative","include": ["bootstrap.routing"@@ -133,17 +133,26 @@"skills/ppt-master/references/visual-styles/_index.md","skills/ppt-master/scripts/docs/confirm_ui.md","skills/ppt-master/templates/icons/README.md",+ {+ "glob": "skills/ppt-master/references/modes/*.md",+ "exclude": [+ "*/_index.md"+ ],+ "select": 3,+ "load_event": "strategist-custom",+ "registry": "modes"+ },{"glob": "skills/ppt-master/references/visual-styles/*.md","exclude": ["*/_index.md"],- "select": 1,- "load_event": "strategist",+ "select": 3,+ "load_event": "strategist-custom","registry": "visual-styles"}],- "max_tokens": 47300+ "max_tokens": 62000},"route.generate.planning-image": {"description": "Generate-PPTX planning context after a non-none image source is proposed or confirmed.",@@ -153,7 +162,7 @@"stage.generate.strategist.image-layout"],"files": [],- "max_tokens": 55100+ "max_tokens": 70000},"route.generate.planning-formula": {"description": "Formula-only planning context with no non-formula image resource or layout catalog.",@@ -163,18 +172,27 @@"stage.generate.strategist.image"],"files": [],- "max_tokens": 49100+ "max_tokens": 64000},"route.generate.planning-ai": {- "description": "Generate-PPTX planning context when AI image direction is available.",+ "description": "Generate-PPTX planning when AI image direction is available, including representative multi-source custom rendering synthesis.","scope": "cumulative","include": ["route.generate.planning-image"],"files": [- "skills/ppt-master/references/image-renderings/_index.md"+ "skills/ppt-master/references/image-renderings/_index.md",+ {+ "glob": "skills/ppt-master/references/image-renderings/*.md",+ "exclude": [+ "*/_index.md"+ ],+ "select": 3,+ "load_event": "strategist-image-custom",+ "registry": "image-renderings"+ }],- "max_tokens": 57100+ "max_tokens": 76000},"stage.generate.apply-template-workspace": {"description": "Conditional Step 3 workspace validation, installation, and fusion framework.",@@ -286,10 +304,10 @@"stage.generate.executor.notes"],"files": [],- "max_tokens": 68700+ "max_tokens": 75500},"route.generate.flat-ai-two-types": {- "description": "Generate-PPTX context with AI images, one rendering, and two local types.",+ "description": "Generate-PPTX context with AI images, representative multi-source custom rendering, and two local types.","scope": "cumulative","include": ["route.generate.planning-ai",@@ -299,7 +317,7 @@"stage.generate.image.ai-two-types"],"files": [],- "max_tokens": 105000+ "max_tokens": 116000},"route.generate.flat-in-hand-image": {"description": "Generate-PPTX context with provided, placeholder, or formula images and no acquisition role.",@@ -311,7 +329,7 @@"stage.generate.executor.notes"],"files": [],- "max_tokens": 82000+ "max_tokens": 89000},"route.generate.flat-web-image": {"description": "Generate-PPTX context with web image acquisition.",@@ -324,7 +342,7 @@"stage.generate.image.web"],"files": [],- "max_tokens": 89300+ "max_tokens": 96500},"route.enhance-native-pptx.audio": {"description": "Enhance Native PPTX with the shared narration-audio stage.",@@ -344,7 +362,7 @@"profile.generate.beautify-pptx"],"files": [],- "max_tokens": 75500+ "max_tokens": 82000},"route.generate.flat-no-image-chart": {"description": "Default flat Generate-PPTX path with chart authoring, native-data replacement, and verification.",@@ -357,7 +375,7 @@"stage.generate.verify-charts"],"files": [],- "max_tokens": 94900+ "max_tokens": 99500},"route.generate.brand-flat-no-image": {"description": "Brand-preset flat Generate-PPTX path without image acquisition.",@@ -369,7 +387,7 @@"stage.generate.template.brand"],"files": [],- "max_tokens": 75700+ "max_tokens": 82200},"route.generate.deck-structured-no-image": {"description": "Deck-preset structured Generate-PPTX path without image acquisition.",@@ -381,7 +399,7 @@"stage.generate.template.deck"],"files": [],- "max_tokens": 85600+ "max_tokens": 92000},"route.generate.layout-structured-no-image": {"description": "Layout-preset structured Generate-PPTX path without image acquisition.",@@ -393,7 +411,7 @@"stage.generate.template.layout"],"files": [],- "max_tokens": 86000+ "max_tokens": 92500},"route.generate.topic-only-flat-no-image": {"description": "Topic research followed by the default flat no-image Generate-PPTX path.",@@ -403,10 +421,10 @@"route.generate.flat-no-image"],"files": [],- "max_tokens": 70500+ "max_tokens": 77000},"stage.generate.executor.flat": {- "description": "Incremental flat Executor core with one locked mode and visual style.",+ "description": "Incremental flat Executor core with representative multi-source custom mode/style execution.","scope": "incremental","files": ["skills/ppt-master/references/executor-base.md",@@ -417,22 +435,23 @@"exclude": ["*/_index.md"],- "select": 1,+ "select": 3,"load_event": "executor",- "registry": "modes"+ "registry": "modes",+ "allow_repeat": true},{"glob": "skills/ppt-master/references/visual-styles/*.md","exclude": ["*/_index.md"],- "select": 1,+ "select": 3,"load_event": "executor","registry": "visual-styles","allow_repeat": true}],- "max_tokens": 20700+ "max_tokens": 36500},"stage.generate.executor.structured": {"description": "Structured template execution layered on the flat/shared core.",@@ -444,10 +463,10 @@"skills/ppt-master/references/executor-structured.md","skills/ppt-master/references/pptx-structure-interface.md"],- "max_tokens": 30150+ "max_tokens": 37000},"stage.generate.image.ai-two-types": {- "description": "Incremental AI-image role with one preset rendering and two selected local types.",+ "description": "Incremental AI-image role with representative multi-source custom rendering and two selected local types.","scope": "incremental","files": ["skills/ppt-master/references/image-base.md",@@ -464,8 +483,10 @@"exclude": ["*/_index.md"],- "select": 1,- "registry": "image-renderings"+ "select": 3,+ "load_event": "image-generator",+ "registry": "image-renderings",+ "allow_repeat": true},{"glob": "skills/ppt-master/references/image-type-templates/*.md",@@ -476,7 +497,7 @@"registry": "image-type-templates"}],- "max_tokens": 21000+ "max_tokens": 23000},"stage.generate.image.web": {"description": "Incremental web-image acquisition role.",@@ -500,7 +521,7 @@"skills/ppt-master/workflows/stages/resume-execute.md","skills/ppt-master/references/artifact-ownership.md"],- "max_tokens": 43400+ "max_tokens": 51000},"stage.generate.resume-execute-image": {"description": "Fresh-session resume when the locked resource plan contains image rows.",@@ -510,7 +531,7 @@"stage.generate.executor.image"],"files": [],- "max_tokens": 48900+ "max_tokens": 56500},"stage.generate.topic-research": {"description": "Topic-only intake stage.",@@ -638,7 +659,7 @@"stage.generate.strategist.template"],"files": [],- "max_tokens": 49400+ "max_tokens": 54000},"route.generate.planning-template-ai": {"description": "Explicit template workspace plus confirmed AI-image planning.",@@ -648,7 +669,7 @@"route.generate.planning-ai"],"files": [],- "max_tokens": 59100+ "max_tokens": 66000},"stage.generate.artifact-schema-guide": {"description": "Compact human guide loaded only to diagnose planning-artifact schema or scaffold failures.",@@ -657,7 +678,7 @@"skills/ppt-master/templates/design_spec_reference.md","skills/ppt-master/templates/spec_lock_reference.md"],- "max_tokens": 2250+ "max_tokens": 2400},"stage.generate.executor.chart": {"description": "Conditional chart/table page execution rules.",@@ -673,7 +694,7 @@"files": ["skills/ppt-master/references/strategist-image.md"],- "max_tokens": 1800+ "max_tokens": 1950},"stage.generate.strategist.image-layout": {"description": "Non-formula image planning plus the image-layout pattern catalog required for Section VIII rows.",@@ -684,7 +705,7 @@"files": ["skills/ppt-master/references/image-layout-patterns.md"],- "max_tokens": 7800+ "max_tokens": 8000},"stage.generate.strategist.template": {"description": "Conditional Strategist module for an explicitly installed template workspace.",diff --git a/skills/ppt-master/templates/spec_lock_reference.md b/skills/ppt-master/templates/spec_lock_reference.mdindex bc8e1ed7..079b0690 100644--- a/skills/ppt-master/templates/spec_lock_reference.md+++ b/skills/ppt-master/templates/spec_lock_reference.md@@ -39,9 +39,9 @@ Optional data sections: `images`, `page_charts`.| Trigger | Required addition || --- | --- |-| `mode.mode: custom` | `mode_behavior` in `mode` |-| `visual_style.visual_style: custom` | `visual_style_behavior` in `visual_style` |-| `colors.image_rendering: custom` | `image_rendering_behavior` in `colors` |+| `mode.mode: custom` | `mode_behavior` in `mode`; optional `mode_references` only when catalog modes are actually used |+| `visual_style.visual_style: custom` | `visual_style_behavior` in `visual_style`; optional `visual_style_references` only when catalog styles are actually used |+| `colors.image_rendering: custom` | `image_rendering_behavior` in `colors`; optional `image_rendering_references` only when catalog renderings are actually used || `icons.library: tabler-outline` | `stroke_width: 1.5`, `2`, or `3` || `pptx_structure.mode: structured` | `template_reuse_scope: layout\|mirror`, `template_adherence`, plus `pptx_masters`, `pptx_layouts`, `page_pptx_layouts`, and `page_layouts` || `pptx_structure.template_reuse_scope: mirror` | `mode: structured` and `template_adherence: strict` |@@ -73,6 +73,7 @@ Structured section value shapes:- `font_family` grammar: one non-empty PPT-safe exported family stack; role-specific families may extend it in the same section.- `objective` grammar: one concise sentence preserving the deck goal and audience success condition.- `image_rendering` grammar: one catalog id, or `custom` with `image_rendering_behavior`.+- Custom reference grammar: comma-separated exact catalog ids with no duplicates. Reference fields are valid only for `custom`; omit them for a genuinely novel direction.- `stroke_width` grammar: `1.5`, `2`, or `3`; present only for `tabler-outline`.- `page_rhythm` grammar: `P` + at least two digits (`P01`, `P100`) followed by `anchor|dense|breathing`.- `page_charts` grammar: `P` + at least two digits followed by a `charts_index` key; the key and `<key>.svg` must both exist.@@ -81,6 +82,15 @@ Structured section value shapes:- `page_pptx_layouts` grammar: `P` + at least two digits followed by a declared Layout key.- `page_layouts` grammar: `P` + at least two digits followed by a template SVG basename.+Catalog-based custom example:++```markdown+## mode+- mode: custom+- mode_references: pyramid, narrative+- mode_behavior: Lead each act with the decision-first clarity of pyramid, then develop it through a narrative tension-and-resolution arc.+```+---## 5. Machine Validationdiff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.mdindex 2f6ea671..094dd6d2 100644--- a/skills/ppt-master/workflows/generate-pptx.md+++ b/skills/ppt-master/workflows/generate-pptx.md@@ -335,11 +335,11 @@ Read the execution references for this deck's locked `mode` + `visual_style` (frRead references/executor-base.md # REQUIRED: flat/shared execution coreRead references/shared-standards-core.md # REQUIRED: SVG compatibility coreRead references/semantic-svg.md # REQUIRED: semantic metadata boundary-Read references/modes/<locked-mode>.md # narrative skeleton (spec_lock.md `mode`)-Read references/visual-styles/<locked-style>.md # aesthetic (spec_lock.md `visual_style`)+Read references/modes/<resolved-id>.md # one preset id, or each `mode_references` id+Read references/visual-styles/<resolved-id>.md # one preset id, or each `visual_style_references` id```-> Read only the five always-on references above plus the conditionally triggered modules below. For `mode: custom` or `visual_style: custom`, skip that preset file and follow `mode_behavior` / `visual_style_behavior` from `spec_lock.md` instead. Never glob `modes/` or `visual-styles/`.+> Read only the five always-on references above plus the conditionally triggered modules below. A preset reads its one locked file. For `mode: custom` or `visual_style: custom`, read every exact file named by the optional `mode_references` / `visual_style_references`, then synthesize those sources under the corresponding behavior. If the reference field is absent, the direction is genuinely novel: read no preset file and follow the behavior directly. Never infer adjacent references or glob `modes/` / `visual-styles/`.| Deterministic trigger | Additional references ||---|---|diff --git a/skills/ppt-master/workflows/stages/resume-execute.md b/skills/ppt-master/workflows/stages/resume-execute.mdindex 34ba98fe..473aa05d 100644--- a/skills/ppt-master/workflows/stages/resume-execute.md+++ b/skills/ppt-master/workflows/stages/resume-execute.md@@ -50,7 +50,7 @@ Read skills/ppt-master/workflows/generate-pptx.mdThen jump to `### Step 6: Executor Phase` and run the documented pipeline:-- Read the Step 6 flat core (`executor-base`, `shared-standards-core`, and the locked mode / visual-style files), then only the branches selected by its condition table+- Read the Step 6 flat core (`executor-base`, `shared-standards-core`, and the locked preset mode / visual-style files); for custom directions, reload every optional `*_references` file from `spec_lock.md` before applying the behavior, then only the branches selected by the condition table- Design Parameter Confirmation- Read the project Design Spec and, when structured, the template Design Spec once; retain both in the fresh execution context- Per-page `python3 skills/ppt-master/scripts/project_manager.py page-context <project_path> P<NN> --record-usage` load + sequential page generation; the stable anchor projection repeats intentionally without becoming a color/font allowlist, while each prototype/chart SVG is loaded only before its first use or after its SHA changes