Skip to content

AI turns documents or topics into real, native PowerPoint decks—with native shapes, transitions and animations, data-backed charts and tables on demand, audio narration from speaker notes, and support for your own .pptx templates. · by Hugo He

docs(templates): align application policy across runtimes

hugohe33798aefe64b7
diff --git a/docs/faq.md b/docs/faq.md
index 47045a0e..1e9500aa 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -361,9 +361,11 @@ Quick omits the separate planning phase, but the repository does not document
a measured or guaranteed token reduction; per-page SVG authoring remains.
Quick keeps the same page-level visual and
resource-authoring capabilities and the shared SVG/resource blocking
-standards. It does not run Spec Lock alignment checks; its package keeps
-converter-default Theme scaffolding instead of deriving Theme colors, fonts,
-and Master title/body size defaults from a lock. It does not promise the same
+standards. It does not run Spec Lock alignment checks or derive a
+current-project Theme from a lock. Flat Quick keeps converter-default Theme
+scaffolding; structured Quick retains installed per-Master source Themes when
+available and infers Master title/body size defaults from semantic slot
+carriers. It does not promise the same
design decisions or wall-clock time as Default because it has no confirmed
design contract, first-page calibration, or resumable decision history.
diff --git a/docs/getting-started.md b/docs/getting-started.md
index 64157967..2d251e91 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -114,8 +114,12 @@ Quick mode never opens the Confirm UI template selector. Give it up to one exact
Brand / Style / Layout / Deck workspace root per kind and it validates,
installs, and uses them directly; give it no exact root and it uses free design.
A bare template name or style phrase is still only a design brief. Quick keeps
-its lockless flat export, so Layout / Deck prototypes guide the authored pages
-but do not compile into reusable native Master / Layout objects.
+its lockless workflow but preserves template capability: free design and
+Brand / Style-only output stays flat, while a supplied Layout / Deck workspace
+keeps explicit Master / Layout / slot metadata in the authored SVGs and compiles
+it into reusable native structure. Before P01, the agent reads every installed
+template SVG and freezes one natural-language application paragraph in active
+context; no confirmation/spec artifact is created.
It does not skip capabilities: source conversion, research on identified factual gaps, shared aesthetic guidance, image / icon preparation, and native-shape / chart / table authoring still run as needed. Structural formulas are authored directly as native PowerPoint markers rather than prepared as image assets. A missing explicitly selected manual asset or other irreplaceable file dependency blocks until you provide it. If automated AI generation or required dependent slicing is exhausted, Quick removes the failed jobs and stale manifest entries, replans with native editable text/SVG or already-prepared non-AI assets, continues the same run, and reports the replacement in its final handoff.
diff --git a/docs/powerpoint-svg-mapping.md b/docs/powerpoint-svg-mapping.md
index 6af86cfe..8d05481c 100644
--- a/docs/powerpoint-svg-mapping.md
+++ b/docs/powerpoint-svg-mapping.md
@@ -45,7 +45,7 @@ Each row owns one PowerPoint capability. The mapping cardinality is not always o
| Object position and size | Absolute SVG coordinates and element bounds | `a:xfrm` offsets and extents | `Native-normalized` through coordinate conversion | Values must be finite and use the registered coordinate grammar |
| Z-order | SVG source order, back to front | PowerPoint shape-tree order | Reconstructed in shape-tree order | Do not rely on browser-only stacking behavior |
| Rotation, scale, translation, and mirror | Supported SVG transform forms | DrawingML transform or normalized geometry | `Native-normalized`; matrices may be decomposed | Skew and shear outside the registered transform contract are not accepted |
-| Theme colors and fonts | Default uses stable roles anchored in `spec_lock.md`; Quick keeps transient design anchors in active context without a persisted lock | Default derives the package Theme and retains theme-aware tokens where an exact anchor role applies; otherwise it writes direct DrawingML values. Quick uses converter-default Theme scaffolding and writes SVG-derived page colors/fonts as direct values | `Native-stable` for registered roles/direct values | Default validates lock alignment; Quick omits that comparison. Both reject invalid values; font portability and target-system availability remain advisory, while contextual colors and export-safe one-off fonts remain allowed |
+| Theme colors and fonts | Default uses stable roles anchored in `spec_lock.md`; Quick keeps transient design anchors in active context without a persisted lock | Default derives the package Theme and retains theme-aware tokens where an exact anchor role applies; otherwise it writes direct DrawingML values. Flat Quick uses converter-default Theme scaffolding. Structured Quick retains an installed per-Master source Theme when available and infers Master title/body size defaults from semantic slot carriers; SVG page colors/fonts remain direct values | `Native-stable` for registered roles/direct values | Default validates lock alignment; Quick omits that comparison. Both reject invalid values; font portability and target-system availability remain advisory, while contextual colors and export-safe one-off fonts remain allowed |
| PowerPoint-only package identity | `spec_lock.md` structure declarations and the package builder | Presentation, Master, Layout, relationship, and content-type registrations | Read back from package structure, not inferred from page appearance | Final-package read-back must match the declared roster |
See [`canvas-formats.md`](../skills/ppt-master/references/canvas-formats.md) for supported canvases and [`shared-standards-core.md` §4.1](../skills/ppt-master/references/shared-standards-core.md#41-semantic-svg-marker-contract) for the normative root-`viewBox` contract.
diff --git a/docs/roadmap.md b/docs/roadmap.md
index fb85aa05..f042321c 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -84,7 +84,7 @@ A presentation is four layers: what is on the slide, how it is arranged, how it
| Concern | Status | Notes |
|---|---|---|
| Slide size | Systematized | The canvas contract selects the presentation format; the SVG `viewBox` is the single geometry truth with fail-closed validation, and every page in a deck must agree on one format |
-| Theme | Systematized | Lock-backed Default export derives each deck's `clrScheme`, major/minor fonts, and Master title/body size defaults from its palette and typography contract. Lockless Quick keeps converter-default Theme scaffolding while writing SVG-derived page colors and fonts as direct values |
+| Theme | Systematized | Lock-backed Default export derives each deck's `clrScheme`, major/minor fonts, and Master title/body size defaults from its palette and typography contract. Flat Quick keeps converter-default Theme scaffolding. Structured Quick retains installed per-Master source Themes when available and infers Master title/body size defaults from semantic slot carriers; SVG-derived page colors and fonts remain direct values |
| Font embedding | Bounded by design | Fonts are never embedded in the package; a brand or web face leads only after confirmed availability on the target system, otherwise export uses a safe family and keeps the intended face recorded in the Design Spec |
| Slide sections | Asymmetric by design | Source-preserving native workflows retain existing section metadata as untouched package structure. Routes that generate or rebuild a slide roster do not author PowerPoint Sections because page roles and optional Design Spec Parts do not form one required, route-wide section contract. Sections change only how the thumbnail rail organizes a deck and never change page appearance; grouping a long deck by hand in PowerPoint takes about a minute and is done once |
| Master / Layout | Systematized | Real `p:sldMaster` / `p:sldLayout` parts on structured routes |
@@ -177,9 +177,10 @@ planning phase no longer happens — the Strategist reference load, the
trip — its token cost disappears with it, while per-page SVG authoring is
unchanged. It keeps the same page-level visual and resource-authoring
capabilities and the shared SVG/resource blocking standards. It does not run
-Spec Lock alignment checks; its package keeps converter-default Theme
-scaffolding instead of deriving Theme colors, fonts, and Master title/body size
-defaults from a lock. Without a confirmed design contract, first-page
+Spec Lock alignment checks or derive a current-project Theme from a lock. Flat
+Quick keeps converter-default Theme scaffolding; structured Quick retains
+installed per-Master source Themes when available and infers Master title/body
+size defaults from semantic slot carriers. Without a confirmed design contract, first-page
calibration, or resumable decision history it does not promise the same design
decisions or wall-clock time as Default.
diff --git a/docs/technical-design.md b/docs/technical-design.md
index ce6c8a7d..6070b003 100644
--- a/docs/technical-design.md
+++ b/docs/technical-design.md
@@ -156,7 +156,7 @@ For every workflow that authors or redesigns visual slides through SVG, `svg_out
The always-loaded core also owns the fallback visual-quality and numeric leading defaults. Explicit user, template / brand, and locked-style requirements override compatible aesthetic defaults; when those authorities are silent, hierarchy, typography, alignment, negative space, purposeful assets, and the core's density-based leading ranges still apply. Default and Quick Generate always load `svg-effects.md` and run its §6.1 job diagnostic before completing a page, with the Visual Job Router as recall for what that diagnostic finds. None of these aesthetic choices can override a technical Required / Forbidden boundary.
-Minimal semantic markers do not weaken that closure. Free-design, brand-only, `quick-generate`, and `template_reuse_scope: style` pages use flat Slide-local ownership: every represented object stays on the Slide and no Master/Layout identity, layer, or placeholder metadata is authored. Default export materializes one clean project-owned Master plus one Blank Layout from the current color/typography lock; lockless `quick-generate` uses converter-default theme scaffolding. Neither promotes Slide content. Only `template_reuse_scope: mirror|layout` uses the structured route, where every new page declares its Master/Layout identity from the first SVG draft. Fixed Master/Layout visuals are direct atomic root children, while reusable content slots are top-level groups with explicit design-zone bounds and one compatible carrier; composite `object` regions use an explicit proxy fallback, and zero-slot Layouts are valid. `data-pptx-role` is reserved for the few structural page-frame objects whose package or animation behavior is not already expressed by specialized metadata. A semantic-legacy template package is not upgraded in place or accepted as a structured Step 3 input: create a new workspace through `create-template`, using a native PPTX's still-present package facts or an old SVG's visuals only as reference, then author new pages through the AI-derived application route. A flat project is intentionally unmapped, not legacy. Export never infers, repairs, or migrates Master/Layout structure or placeholders.
+Minimal semantic markers do not weaken that closure. Free-design, brand/style-only, and Default `template_reuse_scope: style` pages use flat Slide-local ownership: every represented object stays on the Slide and no Master/Layout identity, layer, or placeholder metadata is authored. Default flat export materializes one clean project-owned Master plus one Blank Layout from the current color/typography lock; lockless Quick flat export uses converter-default theme scaffolding. Neither promotes Slide content. Default `template_reuse_scope: mirror|layout`, and Quick with an installed Layout/Deck structure owner, use the structured route, where every new page declares its Master/Layout identity from the first SVG draft. Fixed Master/Layout visuals are direct atomic root children, while reusable content slots are top-level groups with explicit design-zone bounds and one compatible carrier; composite `object` regions use an explicit proxy fallback, and zero-slot Layouts are valid. `data-pptx-role` is reserved for the few structural page-frame objects whose package or animation behavior is not already expressed by specialized metadata. A semantic-legacy template package is not upgraded in place or accepted as a structured Step 3 input: create a new workspace through `create-template`, using a native PPTX's still-present package facts or an old SVG's visuals only as reference, then author new pages through the AI-derived application route. A flat project is intentionally unmapped, not legacy. Export never infers, repairs, or migrates Master/Layout ownership or placeholders; Quick only infers flat versus structured packaging from an already explicit, complete all-page SVG contract.
| Domain | Authority |
|---|---|
@@ -848,7 +848,7 @@ it as a picture or SVG-derived shapes would violate round-trip intent.
**Why the internal application plan retains two fields.** Strategist derives `template_reuse_scope` to record literal mirror reuse, structural layout reuse, or flat style reference. Structured plans then derive `template_adherence: strict|adaptive`: `page_layouts` records the complete authoring prototype, `pptx_masters` / `pptx_layouts` record unique reusable definitions, and `page_pptx_layouts` records page assignment. Strict preserves the declared prototype contract. Adaptive retains its Master, and Strategist may declare a new Layout only when fixed Layout atoms or slot topology/bounds change. If construction reveals that need, execution returns upstream and resumes only after Strategist updates, reads back, and validates the definition and assignment; the exporter never infers it later. These are exporter values, not user confirmation options. A template-backed definition may remain unused and still register in the final package. Layout skin remains project-controlled, while mirror preserves its authored prototype structure and comparable presentation; JSON-first Chart/Table preview children may be regenerated without literal tree identity. `style` has no adherence value or structure mappings.
-**Why explicit-Layout text defaults are split between Master and Layout.** Both flat and structured export write the declared title anchor and a deterministic nine-level body hierarchy into Master defaults while preserving indentation and bullet settings. On structured routes, each generated Layout text slot additionally copies its carrier's first run size into the level-one default while retaining the prompt's direct size. This preserves Layout-specific scale when placeholder text is inserted or reset; direct runs on generated Slides remain unchanged.
+**Why explicit-Layout text defaults are split between Master and Layout.** Both flat and structured export write a title anchor and a deterministic nine-level body hierarchy into Master defaults while preserving indentation and bullet settings. Default reads those anchors from the locked typography contract; lockless Quick structured export infers them from semantic slot carriers across the complete SVG roster, with deterministic fallbacks when a carrier size is absent. On structured routes, each generated Layout text slot additionally copies its carrier's first run size into the level-one default while retaining the prompt's direct size. This preserves Layout-specific scale when placeholder text is inserted or reset; direct runs on generated Slides remain unchanged.
**Why structured output is read back before publication.** Metadata preflight cannot prove package serialization preserved every relationship and registration. Export therefore reopens the temporary PPTX and validates published Slides separately from the complete Master/Layout roster, including definitions unused by all Slides. It checks Presentation → Master → Layout → Slide registration, physical part/content-type rosters, picker identities, exact static-object order, placeholder type/effective index/bounds, carrier bindings, hidden proxies, and zero-slot Layouts before publishing the file.
diff --git a/docs/templates-architecture.md b/docs/templates-architecture.md
index 793c6c01..207d5835 100644
--- a/docs/templates-architecture.md
+++ b/docs/templates-architecture.md
@@ -23,7 +23,7 @@ Every newly created Layout/Deck SVG is a complete preview with root Master/Layou
The four are **parallel reusable-rule bundles**, not PowerPoint package-object types. In library scope, the physical directory and the frontmatter `kind` field correspond one-to-one:
-Each installed spec keeps its own `kind` and id; there is no merged project spec and no combined capability label. The routing consequence is derived while reading: structure comes from an installed Layout or Deck, identity from an installed Brand or Deck, direction from an installed Style. A project-local Brand + Layout pair therefore has both capabilities installed without being promoted into a reusable library Deck or inventing application context. The current project's Stage-1 communication contract supplies that context. Strategist derives the template application plan internally; the confirmation page exposes no template mode controls.
+Each installed spec keeps its own `kind` and id; there is no merged project spec and no combined capability label. The routing consequence is derived while reading: structure comes from an installed Layout or Deck, identity from an installed Brand or Deck, direction from an installed Style. A project-local Brand + Layout pair therefore has both capabilities installed without being promoted into a reusable library Deck or inventing application context. The current project's Stage-1 communication contract supplies that context. Strategist derives the template application plan internally; confirmation exposes the editable natural-language plan, not internal reuse/adherence mode controls.
```yaml
# templates/brands/anthropic/templates/design_spec.md
@@ -417,7 +417,8 @@ ownership.
### Segment ownership is resolved while reading
The consuming role — Default final Stage 2, or Quick's agent before authoring —
-reads every installed spec and resolves these segments in context:
+reads every installed spec and, when Layout/Deck owns structure, every installed
+SVG prototype, then resolves these segments in context:
| Segment | Starting owner |
|---|---|
@@ -503,7 +504,22 @@ Bitmaps share the workspace `images/` pool and template SVGs reference them thro
### Strategist confirmation stage behavior per kind
-Installing a template does not narrow away the communication question. Stage 1 confirms the same open communication contract together with, but independently from, the template choice. The communication recommendation uses only the current request, source facts, conversation constraints, and project initialization; even template canvas is excluded. Only after Stage 1 closes and any selection is installed does final Stage 2 inspect that state and confirm the complete solution and production plan. Brand supplies identity constraints while structure stays free; Style supplies method and visual-default seeds while remaining flat; Layout exposes structural capability; Deck contributes descriptive reusable application context for comparison, not the current project's contract. For Style-only use, Strategist does not look for prototypes and deterministically records `template_reuse_scope: style` with flat structure. It otherwise inspects the effective prototypes—Layout when present, otherwise Deck—and current content, then authors one page/prototype plan and records `mirror`, `layout`, or `style` only as internal exporter values. A mirror-authored workspace therefore enables literal reuse but never forces it. Confirm UI exposes Free design / Use templates and candidate selectors, but not internal reuse/adherence fields. Planning semantics live in `references/strategist.md` and `references/strategist-template.md`; `templates/schemas/spec_lock.schema.json` owns the machine structure.
+Installing a template does not narrow away the communication question. Stage 1 confirms the same open communication contract together with, but independently from, the template choice. The communication recommendation uses only the current request, source facts, conversation constraints, and project initialization; even template canvas is excluded. Only after Stage 1 closes and any selection is installed does final Stage 2 inspect that state and confirm the complete solution and production plan. Brand supplies identity constraints while structure stays free; Style supplies method and visual-default seeds while remaining flat; Layout exposes structural capability; Deck contributes descriptive reusable application context for comparison, not the current project's contract. For Style-only use, Strategist does not look for prototypes and deterministically records `template_reuse_scope: style` with flat structure. It otherwise inspects every effective prototype—Layout when present, otherwise Deck—and current content, then authors one page/prototype plan and records `mirror`, `layout`, or `style` only as internal exporter values. A mirror-authored workspace therefore enables literal reuse but never forces it.
+
+Default confirms one natural-language `template_application` paragraph; Quick
+freezes the same decision only in active context. Explicit user wording wins,
+otherwise the agent decides from content and the complete SVG roster, with
+reference-led use as the fallback. Reference, augment-only, and
+replacement-only are descriptive patterns rather than fixed fields. Every
+prototype-specific exception names the exact SVG basename. Runtime choice does
+not change structural capability: free/Brand/Style-only output is flat, while
+Layout/Deck output preserves explicit Master/Layout/slot metadata unless the
+user explicitly requests visual-only use. Confirm UI exposes Free design / Use
+templates and the prose field, but not internal reuse/adherence fields. Planning
+semantics live in `references/strategist.md` and
+`references/strategist-template.md`; `templates/schemas/spec_lock.schema.json`
+owns the durable Default machine structure, while Quick validates the all-page
+SVG structure contract directly.
---
diff --git a/docs/templates-guide.md b/docs/templates-guide.md
index 47e7bece..29da8ba4 100644
--- a/docs/templates-guide.md
+++ b/docs/templates-guide.md
@@ -65,9 +65,10 @@ not infer a specific template from the topic.
> request are validated and used directly, with at most one contribution per
> kind. Layout and Deck may coexist, with Layout taking structural precedence;
> a multi-kind root contributes all of its specs.
-> No exact root means free design. Bare names still do not resolve. Quick remains
-> a lockless flat export, so Layout/Deck prototypes are authoring inputs rather
-> than reusable native Master/Layout output.
+> No exact root means free design. Bare names still do not resolve. Quick is
+> lockless, not structureless: free design and Brand/Style-only output stays
+> flat, while an installed Layout/Deck structure owner remains explicit
+> Master/Layout/slot metadata in the authored SVGs and exported PPTX.
### How to use the selector
@@ -101,6 +102,16 @@ Stage 2 then compares the confirmed communication contract with that installed
state; `template_application` describes **how** to use it and never chooses
**which** template to use.
+`template_application` is one natural-language paragraph, not a mode selector.
+Explicit user instructions win; otherwise the AI reads every installed template
+SVG, decides from the current content, and defaults to reference-led use when no
+stronger fit exists. Reference-led use may redesign after studying the full
+roster; augment-only preserves existing non-slot objects, permits slot edits,
+and only adds; replacement-only changes information carriers while preserving
+the rest. These are examples, not fixed options. Any prototype-specific exception
+names the exact SVG basename. Quick makes and freezes the same paragraph only in
+its active context instead of writing confirmation/spec artifacts.
+
> **Current-workspace preflight:** Step 3 accepts only a workspace root exposing its Design Spec under `templates/`. Flat-root, former atomic-placeholder, unmapped Master/Layout, and other semantic-legacy packages are rejected; run `create-template` to create a new workspace, then generate new structured pages from that workspace. Nothing upgrades the old package in place.
### What does NOT select a template automatically
diff --git a/docs/zh/faq.md b/docs/zh/faq.md
index b9771373..f64dfb10 100644
--- a/docs/zh/faq.md
+++ b/docs/zh/faq.md
@@ -314,7 +314,7 @@ python3 skills/ppt-master/scripts/svg_to_pptx.py <project> -a auto --animation-t
原生图表 / 表格替换、讲稿、动效、旁白和诊断等普通导出能力仍可按需使用;讲稿、自定义对象动画和旁白默认关闭,Agent 可在用户要求或 deck 确有需要时自动启用,不会打开确认流程。使用默认输出路径时会生成普通 postflight 报告,并把 `svg_output/` 备份到 `backup/`;显式指定输出路径时沿用普通流程不创建备份的行为。页数本身既不会自动触发,也不会阻止快速生成。
-Quick 省略独立规划阶段,但仓库没有文档化的测量或保证表明它会降低多少 token;逐页 SVG 创作仍然存在。Quick 保留同一套页面级视觉与资源创作能力,以及共享的 SVG / 资源阻塞标准;它不运行 Spec Lock 对齐检查,包内保留转换器默认 Theme 脚手架,而不是从 lock 派生主题色、字体与 Master 标题/正文默认字号。由于没有已确认的设计契约、首屏校准或可恢复的决策历史,它不承诺与 Default 作出相同设计,也不承诺具体耗时。
+Quick 省略独立规划阶段,但仓库没有文档化的测量或保证表明它会降低多少 token;逐页 SVG 创作仍然存在。Quick 保留同一套页面级视觉与资源创作能力,以及共享的 SVG / 资源阻塞标准;它不运行 Spec Lock 对齐检查,也不从 lock 派生当前项目 Theme。Flat Quick 保留转换器默认 Theme 脚手架;structured Quick 在工作区提供时保留逐 Master 源 Theme,并从语义 slot carrier 推导 Master 标题/正文字号默认值。由于没有已确认的设计契约、首屏校准或可恢复的决策历史,它不承诺与 Default 作出相同设计,也不承诺具体耗时。
## Q: 长 PPT 一次生成会不会上下文爆掉?
diff --git a/docs/zh/getting-started.md b/docs/zh/getting-started.md
index a8ba0909..805694fc 100644
--- a/docs/zh/getting-started.md
+++ b/docs/zh/getting-started.md
@@ -113,8 +113,11 @@ Default Generate 把模板选择放在 Stage 1,与沟通契约同屏确认;
快速模式不会打开 Confirm UI 的模板选择页。每个 kind 最多给出一个精确的
Brand / Style / Layout / Deck 工作区 root,它会直接校验、安装并使用;没有
给出精确 root,就直接自由设计。只写模板名或风格词仍然只是设计说明。
-Quick 保持无锁 flat 导出,因此 Layout / Deck 原型会指导页面创作,但不会
-编译成可复用的原生 Master / Layout 对象。
+Quick 保持无锁流程,但不丢失模板能力:自由设计及仅 Brand / Style 的输出
+保持 flat;一旦提供 Layout / Deck 工作区,创作 SVG 中的显式 Master /
+Layout / slot 元数据会保留,并编译成可复用原生结构。P01 前,agent 会读取
+全部已安装模板 SVG,并在当前上下文冻结一段自然语言应用方案;不创建确认页
+或 spec 工件。
它不跳过能力:来源转换、事实缺口研究、共享美学规范、图片 / 图标准备,以及原生形状 / 图表 / 表格创作仍按需运行。结构性公式直接写成 PowerPoint 原生 marker,不再作为图片素材准备。显式选择的 manual 素材或其他不可替代的文件依赖缺失时,Quick 会阻塞并索取文件;自动 AI 生成或其必需切片路径耗尽时,Quick 会移除失败任务与过期 manifest 条目,改用原生可编辑文字 / SVG 或已经备好的非 AI 素材,继续本次运行,并在最终交接中披露替代结果。
diff --git a/docs/zh/powerpoint-svg-mapping.md b/docs/zh/powerpoint-svg-mapping.md
index 2805fec7..e99793d2 100644
--- a/docs/zh/powerpoint-svg-mapping.md
+++ b/docs/zh/powerpoint-svg-mapping.md
@@ -45,7 +45,7 @@ PowerPoint 意图
| 对象位置与尺寸 | SVG 绝对坐标与元素边界 | `a:xfrm` 偏移和范围 | 经坐标换算后为 `Native-normalized` | 数值必须有限,并使用已登记坐标语法 |
| Z 顺序 | SVG 源码顺序,由后到前 | PowerPoint shape tree 顺序 | 按 shape tree 顺序重建 | 不得依赖浏览器专属堆叠行为 |
| 旋转、缩放、平移与镜像 | 受支持的 SVG transform 形式 | DrawingML transform 或归一化几何 | `Native-normalized`;matrix 可能被分解 | 已登记 transform 合同以外的倾斜与错切不可接受 |
-| 主题颜色与字体 | Default 使用 `spec_lock.md` 锚定的稳定角色;Quick 在当前上下文维持临时设计锚点,但不持久化 lock | Default 派生包内 Theme,并在精确匹配锚点角色时保留 theme token,否则写直接 DrawingML 值;Quick 使用转换器默认 Theme 脚手架,并把 SVG 派生的页面颜色与字体写成直接值 | 已登记角色与直接值为 `Native-stable` | Default 校验 lock 对齐,Quick 跳过该比较;两者都拒绝非法值,字体可移植性与目标系统可用性仅作提示;情境色和 export-safe 一次性字体仍然允许 |
+| 主题颜色与字体 | Default 使用 `spec_lock.md` 锚定的稳定角色;Quick 在当前上下文维持临时设计锚点,但不持久化 lock | Default 派生包内 Theme,并在精确匹配锚点角色时保留 theme token,否则写直接 DrawingML 值。Flat Quick 使用转换器默认 Theme 脚手架;structured Quick 在工作区提供时保留逐 Master 源 Theme,并从语义 slot carrier 推导 Master 标题/正文字号默认值;SVG 页面颜色与字体仍写成直接值 | 已登记角色与直接值为 `Native-stable` | Default 校验 lock 对齐,Quick 跳过该比较;两者都拒绝非法值,字体可移植性与目标系统可用性仅作提示;情境色和 export-safe 一次性字体仍然允许 |
| PowerPoint 包身份 | `spec_lock.md` 结构声明与打包器 | Presentation、Master、Layout、relationship 与 content type 注册 | 从包结构读回,不从页面外观推断 | 最终包读回必须与声明的 roster 一致 |
受支持的画布见 [`canvas-formats.md`](../../skills/ppt-master/references/canvas-formats.md),根 `viewBox` 的规范合同见 [`shared-standards-core.md` §4.1](../../skills/ppt-master/references/shared-standards-core.md#41-semantic-svg-marker-contract)。
diff --git a/docs/zh/roadmap.md b/docs/zh/roadmap.md
index 6035a08d..214268ae 100644
--- a/docs/zh/roadmap.md
+++ b/docs/zh/roadmap.md
@@ -84,7 +84,7 @@
| 关注点 | 状态 | 说明 |
|---|---|---|
| 画布尺寸 | 系统化 | 画布契约选定演示文稿格式;SVG `viewBox` 是页面几何的唯一真值,配 fail-closed 校验,且同一 deck 的所有页面必须使用同一格式 |
-| Theme | 系统化 | 有锁的 Default 导出根据配色与字体合同逐 deck 派生 `clrScheme`、major/minor 字体与 Master 标题/正文默认字号;无锁的 Quick 保留转换器默认 Theme 脚手架,SVG 派生的页面颜色与字体仍按直接值写入 |
+| Theme | 系统化 | 有锁的 Default 导出根据配色与字体合同逐 deck 派生 `clrScheme`、major/minor 字体与 Master 标题/正文默认字号。Flat Quick 保留转换器默认 Theme 脚手架;structured Quick 在工作区提供时保留逐 Master 源 Theme,并从语义 slot carrier 推导 Master 标题/正文字号默认值;SVG 派生的页面颜色与字体仍按直接值写入 |
| 字体嵌入 | 有意边界 | 从不在包内嵌入字体;品牌 / 网络字体只有确认目标系统可用后才领衔,否则导出安全字体族,并把原意向字体记录在 Design Spec 中 |
| 幻灯片节 | 有意的不对称 | 源保留型原生路线把既有节元数据作为未改动的包结构保留;生成或重建页面列表的路线不创作 PowerPoint 原生节,因为页面角色与可选的 Design Spec Part 并不构成所有路线都具备的必需章节合同。节只改变缩略图栏的组织方式,从不改变任何页面外观;长 deck 需要分组时,在 PowerPoint 里手动分节约一分钟,且只做一次 |
| Master / Layout | 系统化 | 结构化路线输出真实的 `p:sldMaster` / `p:sldLayout` part |
@@ -169,7 +169,7 @@ Generate PPTX 路线围绕完全可控的新形状、文字与版式创作。结
会做:通过 prompt 精简 / 缓存命中率提升带来的间接改善。
-显式 `quick-generate` 是用户主动选择的工作流短路:它跳过 Strategist、确认和首屏 gate,随后创作 SVG、运行一次无锁最终质量门,再导出最终 PPTX。由于整个规划阶段不再发生——Strategist 系 reference 的加载、`design_spec.md` / `spec_lock.md` 的写入、分步确认往返——这部分 token 开销随之消失,而逐页 SVG 创作的开销不变。它保留同一套页面级视觉与资源创作能力,以及共享的 SVG / 资源阻塞标准;它不运行 Spec Lock 对齐检查,包内保留转换器默认 Theme 脚手架,而不是从 lock 派生主题色、字体与 Master 标题/正文默认字号。由于没有已确认的设计契约、首屏校准或可恢复的决策历史,它不承诺与 Default 作出相同设计,也不承诺具体耗时。
+显式 `quick-generate` 是用户主动选择的工作流短路:它跳过 Strategist、确认和首屏 gate,随后创作 SVG、运行一次无锁最终质量门,再导出最终 PPTX。由于整个规划阶段不再发生——Strategist 系 reference 的加载、`design_spec.md` / `spec_lock.md` 的写入、分步确认往返——这部分 token 开销随之消失,而逐页 SVG 创作的开销不变。它保留同一套页面级视觉与资源创作能力,以及共享的 SVG / 资源阻塞标准;它不运行 Spec Lock 对齐检查,也不从 lock 派生当前项目 Theme。Flat Quick 保留转换器默认 Theme 脚手架;structured Quick 在工作区提供时保留逐 Master 源 Theme,并从语义 slot carrier 推导 Master 标题/正文字号默认值。由于没有已确认的设计契约、首屏校准或可恢复的决策历史,它不承诺与 Default 作出相同设计,也不承诺具体耗时。
默认 Generate 流程仍坚持质量优先。
diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.md
index 410595c4..08a1ba1a 100644
--- a/docs/zh/technical-design.md
+++ b/docs/zh/technical-design.md
@@ -126,7 +126,7 @@ narration 标记。
始终必读的 core 还负责兜底视觉质量与数值行距默认值。显式用户要求、模板 / 品牌和已锁定风格可以覆盖相容的美学默认;这些上层权威未规定时,层级、字体、对齐、留白、有目的的素材使用以及按密度设置的行距范围仍然生效。Default 与 Quick Generate 始终加载 `svg-effects.md`,并在完成每页前运行 §6.1 职能诊断;Visual Job Router 是诊断结果的召回入口。任何美学选择都不能覆盖技术上的 Required / Forbidden 边界。
-最小语义标记不会削弱这条闭包。自由设计、brand-only、`quick-generate` 和 `template_reuse_scope: style` 页面都采用 flat 的 Slide 本地所有权:所有已表达对象保持在 Slide,不创作 Master/Layout 身份、分层或 placeholder metadata。默认导出器根据当前配色/字体 lock 生成一个属于本项目的干净 Master 和一个 Blank Layout;无 lock 的 `quick-generate` 使用转换器默认 theme 壳。两者都不会提升任何 Slide 内容。只有 `template_reuse_scope: mirror|layout` 使用 structured 路线,每张新页面从第一版 SVG 起就声明 Master/Layout 身份。固定 Master/Layout 视觉是根节点直接原子元素;可复用内容槽位是顶层 group,带显式设计区域 bounds 和一个兼容 carrier;复合 `object` 区域走显式 proxy 降级,Layout 也允许零槽。`data-pptx-role` 只补充专用 metadata 尚未表达的少量页面框架、package 或动画行为。带旧结构语义的模板包不能原地升级,也不能作为 Step 3 的 structured 输入:先通过 `create-template` 创建新工作区;原生 PPTX 只提供包内仍然存在的事实,旧 SVG 只作为视觉参考;随后由 Generate PPTX 路线按照 AI 推导的应用计划创作新页面。flat 项目是有意不带 mapping,不算 legacy。导出器不推断、修补或迁移 Master/Layout 结构与 placeholder。
+最小语义标记不会削弱这条闭包。自由设计、仅 Brand/Style,以及 Default 的 `template_reuse_scope: style` 页面采用 flat 的 Slide 本地所有权:所有已表达对象保持在 Slide,不创作 Master/Layout 身份、分层或 placeholder metadata。Default flat 导出器根据当前配色/字体 lock 生成一个属于本项目的干净 Master 和一个 Blank Layout;Quick 的无锁 flat 导出使用转换器默认 theme 壳。两者都不会提升任何 Slide 内容。Default 的 `template_reuse_scope: mirror|layout`,以及安装了 Layout/Deck 结构所有者的 Quick,使用 structured 路线;每张新页面从第一版 SVG 起就声明 Master/Layout 身份。固定 Master/Layout 视觉是根节点直接原子元素;可复用内容槽位是顶层 group,带显式设计区域 bounds 和一个兼容 carrier;复合 `object` 区域走显式 proxy 降级,Layout 也允许零槽。`data-pptx-role` 只补充专用 metadata 尚未表达的少量页面框架、package 或动画行为。带旧结构语义的模板包不能原地升级,也不能作为 Step 3 的 structured 输入:先通过 `create-template` 创建新工作区;原生 PPTX 只提供包内仍然存在的事实,旧 SVG 只作为视觉参考;随后由 Generate PPTX 路线按照 AI 推导的应用计划创作新页面。flat 项目是有意不带 mapping,不算 legacy。导出器不推断、修补或迁移 Master/Layout 归属与 placeholder;Quick 只根据已经显式且全页完整的 SVG 合同判断使用 flat 还是 structured 打包。
| 领域 | 权威来源 |
|---|---|
@@ -709,7 +709,7 @@ SVG 与 DrawingML 的表达模型并不等价,因此主编译路径不把“
**为什么内部应用计划保留两个字段。** Strategist 推导 `template_reuse_scope`,记录字面镜像复用、结构化版式复用或 flat 风格参考;structured 计划再推导 `template_adherence: strict|adaptive`。`page_layouts` 记录完整创作原型,`pptx_masters` / `pptx_layouts` 记录唯一可复用定义,`page_pptx_layouts` 记录页面分配。strict 保持声明的原型合同;adaptive 保持原型 Master,只有固定 Layout 原子或槽位 topology/bounds 改变时,Strategist 才可声明新 Layout。若制作过程暴露出这一需求,执行必须退回上游修复。layout 的皮肤由项目控制;mirror 保持已创作原型的结构和相似展示,JSON-first Chart/Table 的派生 preview 子树无需字面同构。`style` 不带 adherence 或结构 mapping。
-**为什么显式版式把文字默认值分在 Master 与 Layout 两层。** Flat 与 structured 导出都会把声明的 `title` 锚点和确定性的九级 body 层级写入 Master 文本默认值,同时保留原有缩进与项目符号设置;在 structured 路线上,每个 Layout 文字槽位还会把 carrier 首个 run 的字号写入一级默认值,同时保留提示文字的直接字号。这样,插入或重置 placeholder 时仍能继承 Layout 特定尺度,而生成 Slide 上的直接 run 不变。
+**为什么显式版式把文字默认值分在 Master 与 Layout 两层。** Flat 与 structured 导出都会把标题锚点和确定性的九级 body 层级写入 Master 文本默认值,同时保留原有缩进与项目符号设置。Default 从锁定的字体合同读取这些锚点;无锁 Quick structured 导出则根据完整 SVG roster 中的语义 slot carrier 推导,carrier 未声明字号时使用确定性兜底值。在 structured 路线上,每个 Layout 文字槽位还会把 carrier 首个 run 的字号写入一级默认值,同时保留提示文字的直接字号。这样,插入或重置 placeholder 时仍能继承 Layout 特定尺度,而生成 Slide 上的直接 run 不变。
**为什么 structured 输出要在发布前回读。** 元数据预检不能证明 package 序列化保留了所有 relationship 与注册信息。导出器会重新打开临时 PPTX,把已发布 Slide 与完整 Master/Layout roster 分开校验,包括没有任何 Slide 使用的定义;同时核对 Presentation → Master → Layout → Slide 注册链、物理 part/content-type roster、选择器身份、固定对象顺序、placeholder 类型/有效索引/bounds、carrier 绑定、隐藏 proxy 与零槽 Layout,只有通过后才发布。
diff --git a/docs/zh/templates-architecture.md b/docs/zh/templates-architecture.md
index ef5f18c1..5d026e93 100644
--- a/docs/zh/templates-architecture.md
+++ b/docs/zh/templates-architecture.md
@@ -23,7 +23,7 @@
四者是**四种并列的可复用规则包**,不是 PowerPoint 包对象类型。在全局库范围内,物理目录与前置元数据中的 `kind` 字段双向对齐:
-每份已装 spec 各自保留自己的 `kind` 与 id;不存在合并后的项目 spec,也没有组合出来的能力标签。路由结果在读取时推导:结构优先来自 Layout,没有 Layout 时才来自 Deck;身份来自 Brand 或 Deck,方向来自 Style。项目内临时组合的 Brand + Layout 因此只是“两种能力都已安装”,不会被自动提升为可注册的 Deck,也不会凭空生成应用语境;当前项目的 Stage 1 沟通契约负责提供场景。Strategist 在内部生成模板应用计划,确认页不显示模板模式控件。
+每份已装 spec 各自保留自己的 `kind` 与 id;不存在合并后的项目 spec,也没有组合出来的能力标签。路由结果在读取时推导:结构优先来自 Layout,没有 Layout 时才来自 Deck;身份来自 Brand 或 Deck,方向来自 Style。项目内临时组合的 Brand + Layout 因此只是“两种能力都已安装”,不会被自动提升为可注册的 Deck,也不会凭空生成应用语境;当前项目的 Stage 1 沟通契约负责提供场景。Strategist 在内部生成模板应用计划;确认页显示可编辑的自然语言方案,不显示内部复用/遵循模式控件。
```yaml
# templates/brands/anthropic/templates/design_spec.md
@@ -364,7 +364,7 @@ project scope 的 Create Template 产物,永远不会被当作已安装模板
### 片段所有权在读取时解析
消费方——Default 的最终 Stage 2,或 Quick 在创作前的当前 agent——读取全部已装
-spec,并在上下文中解析下列片段:
+spec;若 Layout/Deck 拥有结构,还要读取全部已安装 SVG 原型,然后在上下文中解析下列片段:
| 片段 | 起始所有者 |
|---|---|
@@ -433,7 +433,9 @@ apply 阶段解析一份 library 裸 spec 或全部 project 限定名 spec;根
### 策略师确认阶段在不同 kind 下的行为
-安装模板不会让沟通问题消失。Stage 1 把同一份开放式沟通契约与模板选择同时确认,但两者相互独立:沟通推荐只使用当前请求、源材料事实、对话约束和项目初始化状态,连模板画布也不能参与。Stage 1 完成且所选模板安装后,最终 Stage 2 才读取该状态,并确认完整方案与制作计划。Brand 提供身份约束、结构仍然自由;Style 提供方法和视觉默认值候选并保持 flat;Layout 提供结构能力;Deck 提供描述性的可复用应用语境供对照,但不充当当前项目契约。Style-only 时 Strategist 不读取原型,固定写入 `template_reuse_scope: style` 与 flat 结构;其他情况只读取有效原型(有 Layout 时用 Layout,否则用 Deck)和当前内容,生成页面/原型计划,并把 `mirror`、`layout` 或 `style` 记录为内部导出值。按 mirror 创建的工作区因此只提供原样复用能力,不会强制使用;Confirm UI 会显示自由设计/使用模板和候选控件,但不显示内部复用/遵循字段。规划语义由 `references/strategist.md` 与 `references/strategist-template.md` 负责,机器结构由 `templates/schemas/spec_lock.schema.json` 负责。
+安装模板不会让沟通问题消失。Stage 1 把同一份开放式沟通契约与模板选择同时确认,但两者相互独立:沟通推荐只使用当前请求、源材料事实、对话约束和项目初始化状态,连模板画布也不能参与。Stage 1 完成且所选模板安装后,最终 Stage 2 才读取该状态,并确认完整方案与制作计划。Brand 提供身份约束、结构仍然自由;Style 提供方法和视觉默认值候选并保持 flat;Layout 提供结构能力;Deck 提供描述性的可复用应用语境供对照,但不充当当前项目契约。Style-only 时 Strategist 不读取原型,固定写入 `template_reuse_scope: style` 与 flat 结构;其他情况读取全部有效原型(有 Layout 时用 Layout,否则用 Deck)和当前内容,生成页面/原型计划,并把 `mirror`、`layout` 或 `style` 记录为内部导出值。按 mirror 创建的工作区因此只提供原样复用能力,不会强制使用。
+
+Default 确认一段自然语言 `template_application`;Quick 形成同样的决策,但只冻结在当前上下文。用户明确要求优先;否则 agent 根据内容与完整 SVG roster 判断,没有更强理由时默认按参照型使用。参照型、增强型、替换型只是描述性范式,不是固定字段;任何针对单个原型的例外必须写出精确 SVG 文件名。运行时选择不改变模板结构能力:自由设计及仅 Brand/Style 的输出保持 flat;Layout/Deck 输出保留显式 Master/Layout/slot 元数据,除非用户明确要求只参考视觉并舍弃结构。Confirm UI 显示自由设计/使用模板和这段文本,但不显示内部复用/遵循字段。规划语义由 `references/strategist.md` 与 `references/strategist-template.md` 负责;Default 的持久机器结构由 `templates/schemas/spec_lock.schema.json` 负责,Quick 则直接校验全页 SVG 结构合同。
---
diff --git a/docs/zh/templates-guide.md b/docs/zh/templates-guide.md
index a8893a2a..491e7a8b 100644
--- a/docs/zh/templates-guide.md
+++ b/docs/zh/templates-guide.md
@@ -56,8 +56,9 @@ root 时会预选,多 root 仍只作为未选候选。系统不会根据主题
> 校验并使用,每个 kind 最多一份;Layout 与 Deck 可以共存,结构由 Layout
> 优先提供。多 kind root
> 会原子地贡献其全部 spec。没有精确 root 就直接自由设计,裸模板名仍不会
-> 被解析。Quick 继续采用无锁 flat 导出,因此 Layout/Deck 原型是页面创作
-> 输入,不会变成可复用的原生 Master/Layout 输出。
+> 被解析。Quick 是无锁而不是无结构:自由设计和仅 Brand/Style 的输出保持
+> flat;一旦由 Layout/Deck 提供结构,创作 SVG 与导出的 PPTX 都保留显式
+> Master/Layout/slot 元数据。
### 怎么使用选择器
@@ -83,6 +84,15 @@ Layout 提供结构。指定地址最多选一个,并原子携带
`images/`、`icons/`。最终 Stage 2 再把已确认沟通契约与安装状态适配;
`template_application` 只描述**如何使用**,不负责决定**选哪个模板**。
+`template_application` 是一段自然语言,不是模式选择器。用户有明确要求时以
+用户要求为准;没有时,AI 阅读全部已安装模板 SVG,根据当前内容判断;没有
+更强理由时,默认按参照型使用。参照型是在读完整套 SVG 后允许重新设计;增强型
+冻结已有非 slot 对象、允许修改 slot,并且只新增;替换型只更换信息载体,
+其余内容保持不动。这些只是常见意图表达,不是固定选项。任何只针对某一原型的
+规则都必须写出精确 SVG 文件名。Quick
+也形成并冻结同样的一段方案,只是保留在当前上下文,不写确认页、Design Spec
+或 lock。
+
> **当前工作区预检:** Step 3 只接受在 `templates/` 下提供 Design Spec 的工作区根目录。根目录平铺、旧的原子 placeholder、未映射 Master/Layout 等语义旧包都会被拒绝。先运行 `create-template` 创建新工作区,再从该工作区生成新的 structured 页面;不会原地升级旧包。
### 什么**不会**自动选中模板
diff --git a/skills/ppt-master/references/artifact-ownership.md b/skills/ppt-master/references/artifact-ownership.md
index b5900d79..1808f446 100644
--- a/skills/ppt-master/references/artifact-ownership.md
+++ b/skills/ppt-master/references/artifact-ownership.md
@@ -60,7 +60,7 @@ history, or resumable planning state. Context loss restarts the Quick run.
| `notes/slide_*.md` | Conditional split notes | Per-slide notes generated from `total.md` | Derived by `total_md_split.py` only when speaker notes are enabled |
| `svg_final/` | Default-only derived visual preview | Self-contained post-processed SVGs that may be opened directly or inserted as SVG pictures | Default rebuilds it from `svg_output/` with `finalize_svg.py`; Quick omits it. Never use it as a supported PPTX source. |
| `validation/workflow.log` | Cold workflow audit log | Append-only Python command envelopes, material tagged outcomes, bounded warning/OK/stderr samples, per-run omission counts, and selective manual entries for important details with no owning Python output | `project_manager.py init` creates the log and records its milestone. Later project-scoped Python tools find that existing log through the shared CLI bootstrap and record the bounded audit selection without a wrapper command; their full console output is not copied. A helper whose arguments/cwd do not identify the active project receives `PPT_MASTER_PROJECT_PATH=<project_path>` on the same Python command. A role may run `workflow_log.py` once for a material non-Python stage handoff or rework reason, user-approved exception, or manual recovery choice; never duplicate artifacts, routine progress, or private reasoning. Detached services retain detailed output in their component logs. Never read this log during normal generation/resume or use it as stage, artifact, or quality authority; inspect it only for an explicit user-requested run review. In Quick it remains an incomplete operational audit, not a design history or resume source. |
-| `validation/svg_quality_report.json` | Final SVG quality provenance | Final SVG gate split into blocking / introduced / inherited / source-import categories, bound to the checked SVG bytes by SHA-256 | Default runs `svg_quality_checker.py --canonical-authoring --stage final --json`; Quick adds `--quick-generate` so the checker ignores Design Spec/lock and validates the lockless flat roster. Export links the report only when fingerprints match; Quick requires that link to pass before PPTX creation. |
+| `validation/svg_quality_report.json` | Final SVG quality provenance | Final SVG gate split into blocking / introduced / inherited / source-import categories, bound to the checked SVG bytes by SHA-256 | Default runs `svg_quality_checker.py --canonical-authoring --stage final --json`; Quick adds `--quick-generate` so the checker ignores Design Spec/lock and infers flat versus structured validation from the complete SVG roster. Export links the report only when fingerprints match; Quick requires that link to pass before PPTX creation. |
| `validation/<output_stem>.report.json` | Published-package audit | PPTX package/resource postflight status, part counts, and quality-gate linkage | Both Generate profiles write it and emit `[POSTFLIGHT]` after package validation. |
| `exports/` | Delivery artifacts | Native DrawingML PPTX and explicit native-object/narration variants | Default Step 7.3 or Quick direct export writes final deliverables from `svg_output/`. |
| `backup/<timestamp>/svg_output/` | Default-path frozen author-source archive | Re-export source without re-running LLM | Both Generate profiles write a snapshot for default-path exports; explicit `-o/--output` skips it. |
diff --git a/skills/ppt-master/references/shared-standards-core.md b/skills/ppt-master/references/shared-standards-core.md
index 49030c7b..87c94e96 100644
--- a/skills/ppt-master/references/shared-standards-core.md
+++ b/skills/ppt-master/references/shared-standards-core.md
@@ -647,8 +647,8 @@ These forms are needed only when the stated PPT behavior matters:
| One editable PPT text frame with mixed formatting or multiline prose | Use one `<text>` per logical paragraph and non-positional `<tspan>` children for inline runs. Keep the first authored line as direct text; later lines use direct positioned `<tspan>` children that repeat parent `x` with positive relative `dy`; an all-`<tspan>` form may start at `dy="0"`. Default retains these breaks without PowerPoint wrapping; `--reflow-text` may join eligible lines. A font-size change, list marker, or larger accepted gap starts another paragraph. Sibling `<text>` elements are forbidden as one paragraph's line breaks; they remain valid for independent frames. |
| Stable object grouping or object-level animation anchor | Wrap the intended object in `<g id="...">`. Content grouping is **mandatory** per §4.3 — a top-level `<g id>` is also the animation anchor; it is not an optional convenience. |
| Native PowerPoint background promotion | Outside structured mode, the first eligible visual layer may be a direct full-canvas `<rect>` or one inside a simple single-child group. Its fill must have a registered native mapping (solid, linear/radial gradient, or preset pattern), and it must have no transform, filter, clip, rounding, or visible stroke. Export writes the fill as Slide `p:bg`; image elements remain pictures. Structured routes use the narrower explicit solid-background ownership contract in [`pptx-structure-interface.md`](./pptx-structure-interface.md). |
-| Free-design / brand-only PowerPoint structure | Use `pptx_structure.mode: flat`. Keep every represented object Slide-local; export materializes one clean project-owned Master plus one Blank Layout from the current lock, removes stock content placeholders/Layout inventory, and retains only the standard date/footer/slide-number capability hooks. Do not author Master/Layout identities, layers, or placeholder slots. Quick-generate uses the same flat object ownership but converter-default theme scaffolding because no lock exists. |
-| Reusable template-based PowerPoint Layout | Select one complete authoring SVG per page in `page_layouts`, declare each unique Master/Layout definition once, and assign pages through `page_pptx_layouts`. Strict preserves the prototype contract; adaptive retains its Master and uses a current or new Layout key already declared and assigned by Strategist. Construction cannot extend or mutate that mapping downstream. Non-mirror skin follows `spec_lock`. |
+| Free-design / brand-only PowerPoint structure | Use `pptx_structure.mode: flat`. Keep represented objects Slide-local; export emits one clean Master plus Blank Layout, removes stock content placeholders/Layout inventory, and retains the standard date/footer/slide-number hooks. Do not author Master/Layout identities, layers, or slots. Without a Layout/Deck owner, Quick uses the same ownership with converter-default theme scaffolding. |
+| Reusable template-based PowerPoint Layout | Default maps complete page prototypes through `page_layouts` and declared Master/Layout definitions through `page_pptx_layouts`; strict preserves the contract and adaptive uses a declared current/new Layout under its Master. Quick has no lock: read the complete roster and author the selected Master/Layout/slot contract in every output SVG; its all-or-none gate infers structured packaging. Never infer ownership from repeated Slide-local geometry. |
**Default — leading by role and density (may be overridden for user, template, typeface, legibility, or locked visual-style fit)**: For direct positioned `<tspan>` rows, start multiline titles around `1.2–1.3 × font-size`, dense / small body around `1.4–1.5 ×`, ordinary body around `1.5–1.6 ×`, and large / sparse / breathing body around `1.6–2.0 ×`. These are starting ranges, not checker quotas; display headlines may be tighter when the selected style calls for it. Author the spacing as positive relative `dy`, not CSS/SVG `line-height`, which has no registered DrawingML mapping.
diff --git a/skills/ppt-master/references/strategist-template.md b/skills/ppt-master/references/strategist-template.md
index fac93965..a5ecdb9e 100644
--- a/skills/ppt-master/references/strategist-template.md
+++ b/skills/ppt-master/references/strategist-template.md
@@ -12,16 +12,16 @@ Conditional extension for applying an installed Brand/Style/Layout/Deck workspac
**Template vs preset**: A style mention and a Style workspace are different inputs. Bare names and style words remain interpretive input and never resolve to a local path; only a selected and installed workspace activates the rules below. Every installed `<project_path>/templates/design_spec.<kind>.<id>.md` is a template-design source; read all of them. The presence of a `design_spec.style.*.md` file is what marks an active Direction / method segment. Whether a source root was labelled `library` or `explicit` is installation provenance only and never affects Stage-2 precedence.
-**Source-analysis template boundary**: A Layout/Deck template containing `analysis/native_structure.json`, `sources/source.pptx`, missing root Master identity, direct atomic placeholders, or old `baseline` / `preserve` / distillation metadata is not a Generate Step 3 input. Create a current workspace through [`create-template`](../workflows/create-template.md), preferably from the original PPTX when native topology matters. Brand and Style are intentionally roster-free; never reject either for omitting SVG or Master identity. Do not mutate the input in place.
+**Source-analysis template boundary**: A legacy or incomplete Layout/Deck is not a Generate Step 3 input. Rebuild it through [`create-template`](../workflows/create-template.md), preferably from the original PPTX when native topology matters. Brand and Style are intentionally roster-free. Never mutate the input.
-**No template-mode confirmation**: Never ask the user to select `template_reuse_scope`, `template_adherence`, `mirror`, `layout`, `style`, `strict`, or `adaptive`. These are internal execution values for the current exporter. The user communicates intent in natural language; explicit instructions such as “全部原样保留”, “从中选合适的页面”, “可以重组”, or “只参考视觉” are authoritative. Without an explicit instruction, Strategist decides.
+**No template-mode confirmation**: Never ask the user to choose internal exporter reuse/adherence values. Natural-language instructions win. Otherwise decide from current content and installed state. Common readings are: reference-led may redesign after full-roster study; augment-only freezes non-slot objects, permits slot edits, and only adds; replacement-only changes information carriers while preserving the rest. They are examples, not fixed modes; use reference-led when no stronger fit exists.
**Hard rule — no Stage-1 influence**: Do not load this module, the installed template spec, prototypes, assets, or template canvas while authoring Stage 1. Stage 1 is already confirmed when this module begins; never revise it to match the workspace.
Immediately before authoring the Stage-2 solution, load each relevant template
resource once per path + SHA and inspect:
-- every installed `design_spec.<kind>.<id>.md`; inspect the actual Page Roster and relevant complete Slide prototypes from Layout when present, otherwise from Deck; a mirror scope note about omitted source identities is evidence, not a page-candidate list;
+- every installed `design_spec.<kind>.<id>.md`; inspect the actual Page Roster and every complete Slide prototype from Layout when present, otherwise from Deck; a mirror scope note about omitted source identities is evidence, not a page-candidate list;
- the Identity, Structure, Reusable Application Context, and Direction / method segment owners, resolved here from the installed set under [`apply-template-workspace`](../workflows/stages/apply-template-workspace.md) §5;
- the confirmed current communication contract, source obligations, planned page count, and content shape of every planned page;
- the user's natural-language instructions, including any page names/numbers or elements they explicitly require.
@@ -34,6 +34,9 @@ Then author one plan that decides all of the following without presenting an opt
- for Style, which communication method, visual language, composition rhythm, and information-expression defaults are adopted or adapted without inventing page prototypes;
- which visible elements must remain literal because the user said so, and which may change to serve the current content.
+If a prototype detail becomes uncertain, re-read its installed SVG; do not
+substitute memory, a semantic label, or the source PPTX.
+
For Layout/Deck, template size is evidence, not policy. A short template may use every prototype when the content genuinely fits; a 20–30 page source may contribute only a few suitable pages, or several pages may be reorganized into a new sequence. Never infer that all pages must be kept or that visible sample content is protected merely because it exists in the template. Style and Brand have no prototype set.
**Hard rule — Slide prototypes drive authoring**: Every template SVG is a
@@ -54,7 +57,7 @@ Record the resulting exporter plan internally:
Write only the derived values to `spec_lock.md pptx_structure`; omit `template_adherence` for `style`. Do not put these internal values in `design_spec.md`, recommendation stage files, the Confirm UI, or `result.json`.
-**Mandatory — natural-language Stage-2 plan**: For Layout/Deck, summarize which prototypes are used/skipped/repeated/reordered, what stays literal, and what may be replaced or reorganized. For Brand/Style, summarize the installed identity or Direction / method constraints and state that pages remain freely composed unless another workspace supplies structure. Write the result to top-level `template_application.value` in `recommendations.stage2.json`; omit it without an active template. After Stage 2, re-read the confirmed `result.json` value (or exact chat answer), never the initial recommendation. Blank returns the decision to Strategist. Persist the effective plan on one line as `- **Template Application**: <prose>` in `design_spec.md §I`, then derive internal reuse/adherence values and mappings; never copy the prose to `spec_lock.md`. Do not add a questionnaire, internal controls, or fixed template-use options.
+**Mandatory — natural-language Stage-2 plan**: Write one concise paragraph. For Layout/Deck, state prototype use/order, what stays literal, and what may change; name exact SVG basenames for prototype-specific exceptions, never roles such as “cover”. For Brand/Style, state identity or Direction / method constraints and free composition unless structure comes from another workspace. Write top-level `template_application.value` in `recommendations.stage2.json`; omit it without a template. After Stage 2, re-read the confirmed `result.json` value (or exact chat answer); blank returns the decision to Strategist. Persist `- **Template Application**: <prose>` in `design_spec.md §I`, derive internal mappings, and never copy it to `spec_lock.md` or add fixed options.
**Two-stage boundary**: An installed template changes the content of final Stage 2, never the confirmation sequence. Run Stage 1 → final Stage 2 in order in both Confirm UI and chat fallback; do not skip a stage or treat template inspection as user confirmation. On browser timeout, return to the same stage in chat.
@@ -62,7 +65,7 @@ Write only the derived values to `spec_lock.md pptx_structure`; omit `template_a
## 2. Scenario Fit and Inherited Design
-**Mandatory — decide from the §1 inspection**: For an installed `kind: deck`, compare the retained Template Overview with the confirmed audience, intent, outcome, delivery context, artifact afterlife, and source obligations. Deck application is reusable context for this comparison, never the current project's application contract and never an override. Compare the retained Page Roster/relevant SVG prototypes with required narrative roles, content shapes, slots, and capacity. Reopen a resource only when its path + SHA changed. The template describes what exists; it never overrides the current project or own required/optional/repeatable or fixed/replaceable/example-only policy. For `kind: layout`, compare only structural roles, slots, and capacity. For an active Style segment, compare its communication method with the current contract and its composition requirements with any selected Layout/Deck structure. Surface a material incompatibility; never silently weaken one segment to make it fit.
+**Mandatory — decide from the §1 inspection**: For an installed `kind: deck`, compare the retained Template Overview with the confirmed audience, intent, outcome, delivery context, artifact afterlife, and source obligations. Deck application is reusable context for this comparison, never the current project's application contract and never an override. Compare the retained Page Roster and complete SVG roster with required narrative roles, content shapes, slots, and capacity. Reopen a resource only when its path + SHA changed. The template describes what exists; it never overrides the current project or own required/optional/repeatable or fixed/replaceable/example-only policy. For `kind: layout`, compare only structural roles, slots, and capacity. For an active Style segment, compare its communication method with the current contract and its composition requirements with any selected Layout/Deck structure. Surface a material incompatibility; never silently weaken one segment to make it fit.
| Internal scope | Appropriate when |
|---|---|
diff --git a/skills/ppt-master/scripts/confirm_ui/static/app.js b/skills/ppt-master/scripts/confirm_ui/static/app.js
index a05d51c5..fe925890 100644
--- a/skills/ppt-master/scripts/confirm_ui/static/app.js
+++ b/skills/ppt-master/scripts/confirm_ui/static/app.js
@@ -72,8 +72,8 @@
direction_restore: "Restore authored direction",
scheme_component_options: "Project-specific custom choices · select a card to edit",
sec_template_application: "Template application",
- template_application_hint: "The AI recommends how to apply the installed template to this deck. Revise the plan directly in natural language.",
- placeholder_template_application: "Describe which template pages or prototypes to use, skip, repeat, or reorder; what must stay; and what may be replaced or reorganized.",
+ template_application_hint: "After reading every installed template SVG, the AI proposes one natural-language application plan. Edit it directly; this is not a mode selector.",
+ placeholder_template_application: "Name exact SVG files for page-specific rules; describe what to use, skip, repeat, or reorder, what stays fixed, and what may be replaced or reorganized.",
sub_mode: "Narrative mode",
sub_visual: "Visual style",
sub_divergence: "Material divergence (how freely to reshape vs. stay close to the source)",
@@ -255,8 +255,8 @@
direction_restore: "元の案に戻す",
scheme_component_options: "プロジェクト専用カスタム案 · カードを選んで編集",
sec_template_application: "テンプレートの適用方法",
- template_application_hint: "AIが現在の内容に合わせたテンプレートの使い方を提案します。自然言語で直接修正できます。",
- placeholder_template_application: "使用・省略・反復・並べ替えするページやプロトタイプ、保持する要素、差し替え・再構成できる内容を記述します。",
+ template_application_hint: "AIがインストール済みテンプレートの全SVGを確認し、自然言語の適用方針を1段落で提案します。モード選択ではなく、文章を直接修正できます。",
+ placeholder_template_application: "ページ固有の規則は正確なSVGファイル名で示し、使用・省略・反復・並べ替え、固定する要素、差し替え・再構成できる内容を記述します。",
sub_mode: "ナラティブモード",
sub_visual: "ビジュアルスタイル",
sub_divergence: "素材からの発散度(どこまで自由に再構成するか、原文に忠実か)",
@@ -438,8 +438,8 @@
direction_restore: "恢复原方案",
scheme_component_options: "项目专属自定义方案 · 选中卡片后可编辑",
sec_template_application: "模板应用方式",
- template_application_hint: "AI 会根据当前内容推荐如何使用已安装模板;你可以直接用自然语言修改。",
- placeholder_template_application: "说明使用、跳过、重复或重排哪些模板页面/原型,哪些内容必须保留,哪些可以替换或重组。",
+ template_application_hint: "AI 会先阅读已安装模板的全部 SVG,再给出一段自然语言应用方案;这不是模式选择,你可以直接修改文字。",
+ placeholder_template_application: "页面级规则请写明精确 SVG 文件名;说明使用、跳过、重复或重排哪些原型,哪些内容固定,哪些可以替换或重组。",
sub_mode: "叙事模式",
sub_visual: "视觉风格",
sub_divergence: "材料发散度(多大程度重塑,还是贴近源材料)",
@@ -621,8 +621,8 @@
direction_restore: "還原原始方案",
scheme_component_options: "專案專屬自訂方案 · 選取卡片後可編輯",
sec_template_application: "範本套用方式",
- template_application_hint: "AI 會根據目前內容推薦如何使用已安裝範本;你可以直接用自然語言修改。",
- placeholder_template_application: "說明使用、跳過、重複或重排哪些範本頁面/原型,哪些內容必須保留,哪些可以替換或重組。",
+ template_application_hint: "AI 會先閱讀已安裝範本的全部 SVG,再提出一段自然語言套用方案;這不是模式選擇,你可以直接修改文字。",
+ placeholder_template_application: "頁面級規則請寫明精確 SVG 檔名;說明使用、略過、重複或重排哪些原型,哪些內容固定,哪些可以替換或重組。",
sub_mode: "敘事模式",
sub_visual: "視覺風格",
sub_divergence: "材料發散度(多大程度重塑,還是貼近源材料)",
diff --git a/skills/ppt-master/scripts/docs/confirm_ui.md b/skills/ppt-master/scripts/docs/confirm_ui.md
index bcd9c54d..c7e69af5 100644
--- a/skills/ppt-master/scripts/docs/confirm_ui.md
+++ b/skills/ppt-master/scripts/docs/confirm_ui.md
@@ -514,7 +514,7 @@ The example shows one candidate's complete shape; the actual array repeats that
- `custom_candidates` is an optional legacy recommendation-only shape. New files place all three project-specific variants inside `design_directions`; each remains separately selectable and becomes editable in place. A custom behavior may use zero, one, or many exact catalog bases. Reference count has no fixed cap: every named id must contribute a distinct executable job, the behavior omits any id whose contribution it cannot state, and one basis never requires a decorative second. The UI rejects a selected blank and submits only the edited current value. Template-backed variants obey inherited identity, prototype capacity, and `template_application`.
- Seed `audience`, `communication_intent`, `audience_outcome`, and `delivery_context` when evidence supports them; users need not supply them, and every Stage-1 prose field may end blank. The contract and `primary_language` stay in `result.json` and `design_spec.md`; `spec_lock.md communication` receives `primary_language`, compact `audience` / `objective` / `core_message`, and reading mode. `communication_intent` may preserve multiple purposes and 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 a confirmed templates-mode handoff, write one editable prose field as top-level `template_application.value`. It summarizes **how to use** the already selected project-local template: actual page/prototype use and preservation/reorganization decisions. It never chooses, changes, or reinstalls a workspace. Omit it for free design. The UI returns the current string through final Stage 2; Strategist then persists the final effective plan as `- **Template Application**: ...` in `design_spec.md §I`, which Executor reads from the retained Design Spec. Never replace it with internal reuse/adherence ids or a fixed option menu.
+- For a confirmed templates-mode handoff, write one editable prose paragraph as top-level `template_application.value`. It summarizes **how to use** the already selected project-local template after every installed template SVG has been inspected: actual prototype use and preservation/reorganization decisions, with the exact SVG basename for every prototype-specific rule. Explicit user instructions win; otherwise Strategist decides from the content and workspace, falling back to reference-led use when no stronger fit exists. Reference, augment-only, and replacement-only are useful interpretations, never submitted enum values or a fixed option menu. The field never chooses, changes, or reinstalls a workspace. Omit it for free design. The UI returns the current string through final Stage 2; Strategist then persists the final effective plan as `- **Template Application**: ...` in `design_spec.md §I`, which Executor reads from the retained Design Spec. Never replace it with internal reuse/adherence ids.
Template-mode-only Stage-2 fragment:
diff --git a/skills/ppt-master/scripts/docs/svg-pipeline.md b/skills/ppt-master/scripts/docs/svg-pipeline.md
index 4acb6026..6d680b27 100644
--- a/skills/ppt-master/scripts/docs/svg-pipeline.md
+++ b/skills/ppt-master/scripts/docs/svg-pipeline.md
@@ -709,8 +709,11 @@ python3 scripts/svg_to_pptx.py <project_path> --quick-generate
This direct-export flag takes `svg_output/` as its authored page source, resolves
valid project-local resources referenced by those pages, infers one consistent
-canvas, uses flat converter-default package scaffolding, and does not read or
-require `spec_lock.md`. Notes, motion, narration, native objects, conversion
+canvas, and does not read or require `spec_lock.md`. It infers one all-page PPTX
+structure mode from the authored SVGs: no structure metadata creates clean flat
+package scaffolding; any structure metadata requires every page to satisfy the
+complete Master/Layout/slot contract and creates structured output. A mixed or
+partial roster fails closed. Notes, motion, narration, native objects, conversion
trace, and other ordinary exporter capabilities remain available; notes,
custom object animation, and narration start off in Quick and may be enabled
when needed. The exporter refuses a missing, blocking, non-final, or stale
diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.json
index d03b445f..19cd937b 100644
--- a/skills/ppt-master/scripts/prompt_audit_manifest.json
+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json
@@ -1875,9 +1875,15 @@
},
{
"path": "skills/ppt-master/workflows/stages/apply-template-workspace.md",
- "role": "compatibility",
- "fingerprint": "4375357b2252",
- "reason": "This site documents a legacy or omission compatibility boundary."
+ "role": "consumer",
+ "fingerprint": "2a2c42538a76",
+ "reason": "This stage documents how each Generate runtime consumes the prototype mapping."
+ },
+ {
+ "path": "skills/ppt-master/references/shared-standards-core.md",
+ "role": "reference",
+ "fingerprint": "846de4145cbe",
+ "reason": "This reference distinguishes durable Default mappings from Quick active-context use."
}
]
},
@@ -1906,7 +1912,7 @@
{
"path": "skills/ppt-master/references/shared-standards-core.md",
"role": "reference",
- "fingerprint": "8afb713e37e8",
+ "fingerprint": "e27448d68611",
"reason": "This reference mirrors the owner field grammar or ownership boundary."
},
{
diff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.md
index 865d0faa..0be8ca4f 100644
--- a/skills/ppt-master/workflows/profiles/quick-generate.md
+++ b/skills/ppt-master/workflows/profiles/quick-generate.md
@@ -27,7 +27,7 @@ never change CWD or inherit a prior shell working directory.
| Interaction | The current main agent decides content, design, resources, and implementation without Strategist, Confirm UI, or approval stops |
| Execution memory | Keep routine page, visual, and resource decisions only in the current active context; losing that context restarts Quick instead of reconstructing a plan from project files |
| Inputs | Any supported Generate input; convert/import sources and run bounded factual research when the input requires them |
-| Templates | Directly validate and install at most one exact workspace root per kind supplied for this run; when none are supplied, use free design without catalog selection or Confirm UI |
+| Templates | Directly validate and install at most one exact workspace root per kind supplied for this run; before P01, inspect the complete installed template SVG roster and freeze one natural-language application paragraph in active context; when none are supplied, use free design without catalog selection or Confirm UI |
| Resources | Prepare every project-local image, icon, and required provenance/manifest artifact before its SVG; author native formula markers and hyperlink anchors directly in the affected SVG; sound waits for §4 |
| Planning artifacts | Do not author a root project `design_spec.md`, `spec_lock.md`, confirmation payloads, or any substitute planning artifact; installed `templates/design_spec.<kind>.<id>.md` files remain template input |
| Traceability | Operational resource manifests, checker reports, postflight, and bounded Python command/outcome audit entries may remain, but they do not record the AI's design reasoning or form a resumable generation history |
@@ -249,18 +249,30 @@ the project-local asset pools. All later reads use that installed state, never
the original roots.
Before writing P01, read every installed
-`templates/design_spec.<kind>.<id>.md` once and, for Layout/Deck, inspect the
-relevant SVG prototypes. Apply Brand identity, Style direction/method, the
-selected structure owner's useful prototype geometry, and Deck application
-context directly in the active context under the existing segment precedence
+`templates/design_spec.<kind>.<id>.md` once and, for Layout/Deck, inspect every
+SVG prototype in the installed roster. Apply Brand identity, Style
+direction/method, the selected structure owner's prototype geometry, and Deck
+application context directly in the active context under the existing segment precedence
([`apply-template-workspace`](../stages/apply-template-workspace.md) §5). A
segment owner's instruction about how a value should dominate, recede, or stay
rare binds as strongly as the value itself; a Style composition or whitespace
tendency never demotes a Brand's declared dominant color to an incidental
-accent. Follow explicit instructions about literal or visual-only
-use; otherwise decide which prototypes to use, skip, repeat, reorder, or adapt
-while authoring. Persist no separate template-application artifact. If no
-template was installed, make the same design choices freely.
+accent.
+
+Resolve one concise **Template Application** paragraph before P01 and freeze it
+for this run. Explicit user instructions win. Otherwise decide from the current
+content and the complete installed roster; when no stronger fit exists, default
+to reference-led use of the template's design and structural system. Common
+readings are: reference-led may redesign after full-roster study; augment-only
+freezes existing non-slot objects, permits slot edits, and only adds; replacement-only
+changes information carriers while preserving the rest. These are examples,
+not enum values or a menu. The paragraph states which prototypes may be used, skipped, repeated,
+reordered, or adapted and what stays fixed versus replaceable. Any exceptional
+rule names the exact SVG basename instead of a semantic label such as “cover”.
+Keep the paragraph only in active context; do not create a substitute planning
+artifact. If a detail becomes uncertain later, re-read the exact installed SVG
+instead of relying on memory or reopening the source PPTX. If no template was
+installed, make the same design choices freely.
Before resolving the one-pass design, read this fixed planning-capability batch
in one pass:
@@ -649,15 +661,25 @@ viewBox. Template canvas is a default, not a compatibility gate; an explicit
user canvas may adapt the installed visual system. The first SVG establishes
the export canvas; every remaining page must match it exactly.
-**PPTX structure**: author flat, Slide-local SVG only, including when a Layout or
-Deck workspace is installed. In that branch, visibly realize the resolved
-template rules and prototype geometry in the complete pages; do not fall back to
-free design or merely explain how the template could be used. Include the
-complete visible page and all resource references in each SVG; set one root
-`data-pptx-page-role` from `cover`, `toc`, `section`, `content`, or `ending`,
-and omit Master/Layout/layer/placeholder metadata. A request that specifically
-requires reusable native Master/Layout/placeholder output is incompatible with
-the lockless Quick exporter and must use the default lock-backed profile.
+**PPTX structure**: runtime speed does not flatten template structure. Free
+design and Brand/Style-only use author flat, Slide-local SVG and omit
+Master/Layout/layer/placeholder metadata. When Layout or Deck owns structure,
+author every page as a complete structured Slide SVG: preserve or deliberately
+adapt the selected prototype's root Master/Layout identity, fixed layers, and
+semantic slots, then place current Slide content on top. A Style contribution
+never strips that structure. Only an explicit instruction to use the workspace
+as visual language while discarding its structure permits flat output.
+
+Structured Quick pages use the same all-or-none SVG contract as Default: once
+any page declares PPTX structure metadata, every page root declares non-empty
+Master/Layout keys and picker names, and every reused Layout repeats an
+identical fixed-layer/slot contract. The current agent may author a new complete
+Layout under the selected Master when the frozen application paragraph calls
+for adaptation; it never infers ownership from repeated Slide-local geometry.
+The lockless final checker and exporter derive `structured` solely from that
+complete SVG roster. Include all visible content and resource references in each
+SVG, and set one root `data-pptx-page-role` from `cover`, `toc`, `section`,
+`content`, or `ending` independently of the native structure metadata.
**Typography**: name a concrete target-installed/approved PowerPoint family
under [`shared-standards-core.md`](../../references/shared-standards-core.md)
@@ -764,8 +786,10 @@ python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path> \
`--quick-generate` reads `svg_output/` as the page source and resolves the
project-local assets referenced by those SVGs. It infers one consistent canvas,
-uses a lockless flat PowerPoint package, and does not force-disable ordinary
-export options. Notes, Custom Animations, and narration remain off unless
+then infers one all-page structure mode: no structure metadata produces a clean
+flat package, while complete explicit Master/Layout/slot metadata produces a
+structured package. It does not read or require `spec_lock.md` and does not
+force-disable ordinary export options. Notes, Custom Animations, and narration remain off unless
selected by the agent or required by the Quick video rule above. Append
`--native-charts-and-tables` only when the effective delivery decision
explicitly requires native Chart/Table objects; marker presence, imported
@@ -801,6 +825,8 @@ or lock.
- [x] Every selected formula uses the checker-valid ordinary/inline/block form with a matching visible SVG preview and no formula image resource
- [x] Every selected hyperlink uses a checker-valid inline/whole-object anchor and an exact external or same-deck target
- [x] Resolved SVG pages and their project-local references exist
+- [x] The frozen Template Application paragraph was applied; every installed Layout/Deck SVG was read, and any page-specific exception names an exact SVG basename
+- [x] Quick structure matches the installed template capability: free/Brand/Style-only pages are flat, while a Layout/Deck structure owner remains explicit and all-page consistent unless the user explicitly requested visual-only use
- [x] Every role declared by an installed template spec is locatable in the finished pages, or its non-use is deliberate — checked per installed spec, not from memory
- [x] Every triggered capability-specific preparation and pre-checker verification completed
- [x] The current final report's carrier receipt was compared with the retained page jobs and any factual contradiction was repaired before export, without treating counts as quotas
diff --git a/skills/ppt-master/workflows/routing.md b/skills/ppt-master/workflows/routing.md
index b3f1d1e5..c534ee73 100644
--- a/skills/ppt-master/workflows/routing.md
+++ b/skills/ppt-master/workflows/routing.md
@@ -69,12 +69,14 @@ loads both runtimes.
stays inside Generate PPTX but owns an explicit SVG → PPTX short circuit. Page
count alone never activates or blocks it. Conversion, bounded research, and
project-local resources remain available. Package capabilities may be requested
-or agent-selected. Quick may consume exact Brand/Style/Layout/Deck workspaces as
-flat authoring inputs, with at most one contribution per kind. All four kinds
-may combine; Layout takes structural precedence over Deck. A multi-kind project
-root contributes all of its specs atomically;
-compiling reusable Master/Layout/placeholder structure still requires the
-default lock-backed Generate pipeline. Once selected, Quick
+or agent-selected. Quick may consume exact Brand/Style/Layout/Deck workspaces,
+with at most one contribution per kind. All four kinds may combine; Layout takes
+structural precedence over Deck. A multi-kind project root contributes all of
+its specs atomically. Brand/Style-only and free-design Quick pages remain flat;
+when Layout or Deck owns structure, Quick authors the complete explicit
+Master/Layout/slot metadata and its lockless checker/exporter infers structured
+output from that all-page SVG contract. Runtime choice controls interaction and
+durable planning, not whether an installed structural template survives. Once selected, Quick
is the complete runtime procedure and never loads `generate-pptx.md`; Default
never loads `quick-generate.md`. Image to PPTX is the narrow profile-owned
Quick activation; Beautify may select either runtime, but never both.
@@ -86,7 +88,7 @@ Quick activation; Beautify may select either runtime, but never both.
**Hard rule — no direct structure grafting**: An existing PPTX or SVG is never upgraded in place by adding Master/Layout/placeholder structure. If reusable native structure is required:
1. Run [`create-template`](./create-template.md) to produce a separate validated workspace.
-2. Pass that workspace root to [`generate-pptx`](./generate-pptx.md) as a Stage-1 template candidate.
+2. Pass that workspace root to Default as a Stage-1 template candidate, or supply its exact root directly to explicit Quick Generate.
3. Author new structured SVG pages whose Master/Layout contract exists from their first generated draft.
4. Export a new PPTX from those pages.
@@ -99,7 +101,7 @@ When a PPTX already contains native Master/Layout parts, `create-template` mirro
| One or more images containing page frames + explicit final-deck reconstruction intent | Generate PPTX with the Codex-supported, Quick-only [`image-to-pptx`](./profiles/image-to-pptx.md); normalize page frames first and do not infer reusable native structure from pixels |
| Raw PPTX called a template + new content | Fill Native PPTX unless the user explicitly asks for a reusable template workspace |
| Any supported reference bundle or direct-text brief + reusable template request | Create Template |
-| Current template workspace root + content | [`generate-pptx`](./generate-pptx.md) Stage-1 template choice |
+| Current template workspace root + content | Default: [`generate-pptx`](./generate-pptx.md) Stage-1 template choice; explicit Quick: direct validated workspace application |
| Semantic-legacy or incomplete structured package | Create a new workspace through Create Template; do not migrate in place |
| Request to add a master directly to an existing PPTX/SVG | Unsupported; explain the Create Template → Generate PPTX lifecycle |
diff --git a/skills/ppt-master/workflows/stages/apply-template-workspace.md b/skills/ppt-master/workflows/stages/apply-template-workspace.md
index e9e2e0ca..66228598 100644
--- a/skills/ppt-master/workflows/stages/apply-template-workspace.md
+++ b/skills/ppt-master/workflows/stages/apply-template-workspace.md
@@ -123,8 +123,8 @@ After that root-level copy, kinds have these downstream effects:
| Kind | Consumption behavior |
|---|---|
| `brand` | Identity is constrained; structure remains free unless the selected set also includes Layout or Deck. |
-| `style` | Expose reusable direction/method without identity truth, page prototypes, or native structure. Default Style-only and Style + Brand derive `template_reuse_scope: style` and stay flat; Style + Layout/Deck follows the selected structure plan. Quick always realizes the resolved combination as flat pages. A Style workspace never activates visual review. |
-| `layout` | Expose the actual reusable structure and take structural precedence over Deck; Default Strategist later inspects these prototypes, while Quick's current agent uses them for immediate flat authoring decisions in active context. |
+| `style` | Expose direction/method without identity, prototypes, or structure. Style-only and Style + Brand stay flat; Style + Layout/Deck follows that structure owner. Style never activates visual review. |
+| `layout` | Expose reusable structure and take precedence over Deck; Default plans against its prototypes, while Quick reads the complete roster and authors its Master/Layout/slot contract directly. |
| `deck` | Expose descriptive application context and identity. It also supplies structure and the actual prototype roster only when no Layout is selected. |
**Atomic install preflight**:
@@ -151,8 +151,11 @@ is installation input, not a later prompt source. If source and target are the
same project root, that in-place root already satisfies this boundary.
Template SVGs are complete Slide authoring prototypes, not export-time overlays. They already resolve Master + Layout context, so `page_layouts` selects one directly. Standalone Master/Layout definition SVGs are invalid; an unselected authored Slide prototype may still back a reusable Layout definition.
-Quick instead realizes the selected prototypes into complete flat, Slide-local
-SVGs and never writes `page_layouts` or Master/Layout/placeholder metadata.
+Default records `page_layouts` and the durable structure lock. Quick has no such
+planning artifact: it freezes the natural-language application paragraph in
+active context and writes the selected Master/Layout/slot contract directly
+into the complete output SVG pages. Quick stays flat only without a Layout/Deck
+structure owner or under an explicit visual-only instruction.
For a template-owned Chart/Table carrying
`data-pptx-native-authority="json"`, the installed inline JSON remains the