Skip to content

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

refactor(templates): make template workflows AI-directed

hugohe37628f7264760
diff --git a/docs/roadmap.md b/docs/roadmap.md
index 4b59b5aa..37249c1a 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -53,7 +53,7 @@ Structural capability growth since March 2026. Single flags and incremental poli
- **mode catalog grows to 5: add `briefing`** — fills the "neutral information delivery" cell: no thesis, no story, no teaching, no spectacle — topic titles, even weight, complete and scannable, for status updates / reference decks / catalogs / meeting packs / FAQs that inform without arguing. The five now partition presentation *intent* more nearly MECE: persuade (pyramid) · tell a story (narrative) · teach (instructional) · impress (showcase) · simply inform (briefing). `_index` gains a `briefing` vs `pyramid` tie-breaker ("if you'd have to invent a thesis to fit pyramid, it's briefing"). Five presets plus a `custom` escape hatch for a bespoke direction none of them captures (a special cadence, a multi-mode fusion, a particular posture) — either user-requested or Strategist-recommended, confirmed like every lock; a deck always locks one value, and a fusion is one `custom` describing the acts. The only thing to avoid is defaulting to `custom` when a preset genuinely fits. Mirrors the truth-precedence rule that a user-authored outline or direction overrides the mode
- **mode / visual-style system validated on real decks + four calibration tightenings landed** — the 5 modes + 18 visual-styles + the `custom` escape hatch were exercised on five covering decks (briefing×data-journalism / narrative×photo-editorial / instructional×chalkboard / showcase×glassmorphism / custom×zine, with the narrative deck going through the AI-image branch): **zero selection misses** (all four Close-calls tie-breakers fired and held against the real grey-zone pulls), **discipline fully honored** (zero HEX / Reference strength / whole-page layout language), **the `custom` mechanism works** (a `mode_behavior` prose paragraph carried a 10-page generation and reads as plain language at confirmation, not a bare token), **mode ⟂ visual_style holds** (any combination without bleed, including a positive check of the "keynote/launch = mode not style" route), export 5/5 decks × every page with 0 failures. Tightened four spots from the real signal: `strategist §e` now locks the full neutral tier set the visual_style implies up front (killing the mid-deck color top-ups seen in three consecutive decks), [`executor-structured.md`](../skills/ppt-master/references/executor-structured.md) §1 re-skins chart/layout template gradients-shadows-fills to the deck's visual_style (templates supply structure, not skin; mirror templates retain their declared prototype paint per §1.1), `briefing §1` makes `core_message` state coverage rather than a claim (briefing-only; global §IX assertion semantics stay for narrative/instructional/pyramid), and `svg_quality_checker` fixes font-family drift false positives (delimiter-matched capture + stack normalization) and drops the font-size ceiling for showcase mode and poster visual-styles
- **Optional spec-review checkpoint shipped** ([`workflows/stages/refine-spec.md`](../skills/ppt-master/workflows/stages/refine-spec.md)) — an opt-in pause after the Strategist confirmation stage: when the user explicitly asks (default OFF), the Strategist produces the full `design_spec.md` + `spec_lock.md`, then stops so the user can revise any part of the spec (outline / color / typography / layout / image strategy / page rhythm) before generation, keeping both files in sync. Same shape as the split-mode note — it never fires on its own, the default pipeline is unchanged, and it surfaces as one opt-in line inside the Strategist confirmation stage. Review lenses (logical clarity / information density / focus / register / emotional resonance / chapter balance + the design dimensions) give a direction only, never a numeric threshold (`Reference` strength). Prompted by [@cuberoocp](https://github.com/cuberoocp) in [issue #173](https://github.com/hugohe3/ppt-master/issues/173)
-- **Interactive visual Strategist confirmation stage page (Step 4)** ([`scripts/confirm_ui/server.py`](../skills/ppt-master/scripts/confirm_ui/server.py), field schema [`scripts/docs/confirm_ui.md`](../skills/ppt-master/scripts/docs/confirm_ui.md)) — the Strategist confirmation stage moves from chat-only to a browser page that auto-launches by default at Step 4. Template adherence appears only for deck/layout templates and defaults to `adaptive`: every page still maps to the template architecture, while unmatched compositions may create a new explicit Layout under the same Master. `strict` keeps the selected Layout contracts unchanged. The page shares port `5050` with Live Preview and writes authoritative choices to `result.json`.
+- **Interactive visual Strategist confirmation stage page (Step 4)** ([`scripts/confirm_ui/server.py`](../skills/ppt-master/scripts/confirm_ui/server.py), field schema [`scripts/docs/confirm_ui.md`](../skills/ppt-master/scripts/docs/confirm_ui.md)) — the Strategist confirmation stage moves from chat-only to a browser page that auto-launches by default at Step 4. Template application is now AI-authored from the actual workspace and current content; the page does not expose reuse/adherence controls. Internal strict/adaptive values remain available to the structured exporter. The page shares port `5050` with Live Preview and writes authoritative user-facing choices to `result.json`.
- **A batch of source-conversion fidelity gains** — less information dropped as source material enters the pipeline: `doc_to_md` converts Word OMML / Office Math equations to inline LaTeX, `pdf_to_md` recognizes `Figure N |` pipe-delimited captions, and `ppt_to_md` preserves hyperlinks already in the source deck (run-level external `[text](url)` / slide-internal jumps `[text](#slide-N)` / shape-level clicks, with dangerous-scheme filtering and anchor-text Markdown escaping) and transcribes native chart data into Markdown tables (values survive the conversion instead of collapsing to a single picture). Caption recognition is based on [@suay1113](https://github.com/suay1113)'s [PR #191](https://github.com/hugohe3/ppt-master/pull/191); hyperlink preservation is distilled from [@ZhaoZuohong](https://github.com/ZhaoZuohong)'s [PR #155](https://github.com/hugohe3/ppt-master/pull/155)
- **Content-faithful PPT beautification / re-layout profile shipped** ([`workflows/profiles/beautify-pptx.md`](../skills/ppt-master/workflows/profiles/beautify-pptx.md)) — a main-generation profile that mirrors `template-fill`: template-fill reuses a deck's design with new content, while beautify keeps the content and redoes the layout. Given an existing PPTX, **every text string is preserved verbatim (nothing added / removed / reworded)**; it **extracts and inherits the source deck's visual identity (palette / fonts, `theme` or `observed` offered as two confirm-page candidates)** and redoes only layout / hierarchy / whitespace, strict 1:1 page count and order, with charts / tables regenerated natively from extracted data (values frozen) and source pictures re-laid-out. Technically it remains the Generate PPTX route (`ppt_to_md` extracts content → main pipeline → a brand-new deck), not a patch over the original, so it stays clear of Non-goals #53. Adds `beautify_identity.py` / `beautify_inventory.py`; the confirm page is seeded from the source for the user to review. Honest v1 ceiling: it does not relieve information overload (a crowded page improves within itself; true re-pagination is the normal profile), does not guarantee coordinate-level paste-back, and combo / dual-axis / waterfall charts lose the un-captured plots
@@ -122,7 +122,7 @@ The Generate PPTX route is built around full control of newly authored shapes, t
**The basic need is actually simple**: if you just need "replace Excel data into fixed positions in a PPT template", have the AI write a few lines of `python-pptx`. You don't need this pipeline.
-> **Supported boundaries**: Fill Native PPTX (`template-fill-pptx`) directly refills selected source slides. Create Template (`create-template`) either authors a new explicit SVG contract (`standard` / `fidelity`) or maps validated facts from a supported source contract into a new workspace without semantic synthesis (`mirror`). Strict and adaptive downstream compile the resulting declared contract into native structure. What remains out of scope is unreviewed, schema-free substitution against arbitrary third-party placeholder systems.
+> **Supported boundaries**: Fill Native PPTX (`template-fill-pptx`) directly refills selected source slides. Create Template (`create-template`) derives an internal authored or mirror implementation from the natural-language request and source evidence. Strategist later derives strict/adaptive exporter behavior from the actual template and current content. What remains out of scope is unreviewed, schema-free substitution against arbitrary third-party placeholder systems.
### Make native PowerPoint charts the default
diff --git a/docs/technical-design.md b/docs/technical-design.md
index 8f4232b9..563f3a00 100644
--- a/docs/technical-design.md
+++ b/docs/technical-design.md
@@ -88,7 +88,7 @@ Output:
For every workflow that authors or redesigns visual slides through SVG, `svg_output/` is the complete page-design authority, but SVG here means project-canonical SVG accepted by the project contract—not any SVG a browser can render. Every visible text, image, shape, diagram, chart/table fallback, background, and template-derived layout element that should appear on a slide must already exist in that page SVG or be explicitly referenced by it. Templates, `design_spec.md`, and `spec_lock.md` guide SVG authoring; the exporter does not use them as a second visual layer that fills in missing page content.
-Minimal semantic markers do not weaken that closure. Free-design, brand-only, and `template_reuse_scope: style` pages use `pptx_structure.mode: flat`: every represented object stays Slide-local and no Master/Layout identity, layer, or placeholder metadata is authored. Export materializes one clean project-owned Master plus one Blank Layout from the current color/typography lock, removes stock content placeholders and unused built-in Layouts, and retains only the standard date/footer/slide-number capability hooks without promoting 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 confirmed reuse-scope 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-only, and `template_reuse_scope: style` pages use `pptx_structure.mode: flat`: every represented object stays Slide-local and no Master/Layout identity, layer, or placeholder metadata is authored. Export materializes one clean project-owned Master plus one Blank Layout from the current color/typography lock, removes stock content placeholders and unused built-in Layouts, and retains only the standard date/footer/slide-number capability hooks without promoting 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.
| Domain | Authority |
|---|---|
@@ -320,7 +320,7 @@ The three template kinds own different segments of the design contract:
|---|---|---|---|
| `brand` | identity | colors, typography, logo, voice, icon style | locks identity; structure remains free |
| `layout` | brand-neutral structure | canvas, page structure, semantic text roles/spatial behavior, page types, SVG roster | exposes structure; identity and communication application remain downstream decisions |
-| `deck` | application + integrated identity/structure | recurring situations, audiences/outcomes, content policy, identity, and SVG roster | contributes an application contract that Stage 2 derivation compares with the independently confirmed Stage-1 contract before selecting reuse scope |
+| `deck` | application + integrated identity/structure | recurring situations, audiences/outcomes, representative page roles, identity, and actual SVG roster | contributes descriptive context and prototypes that Strategist compares with the independently confirmed Stage-1 contract and current content before deriving the application plan |
Theme, Slide Master, Slide Layout, and Placeholder are compiled PowerPoint
objects, not additional template kinds. Layout owns topology, placement,
@@ -346,7 +346,7 @@ PPT Master uses **role switching within one main agent** rather than parallel su
**Why role-specialized references, not one mega prompt.** Strategist runs in "negotiate with user" mode (open-ended, conversational, willing to back up); Executor runs in "produce strict XML" mode (no improvisation, no missing attributes). Mixing both into one prompt forces the model to hold incompatible discipline in the same turn — every prompt-engineering pathology of mode-mixing shows up. Splitting into per-role files lets each role load only what it needs and discard the rest.
-**Strategist confirmation stage as the only blocking gate.** Strategist ends with one gate delivered in three dependency-ordered stages. Stage 1 confirms an open communication contract and canvas. Its prose boxes contain editable recommendations, but none requires a non-empty answer: confirmation persists the current text exactly, and a cleared value stays empty instead of falling back to the recommendation. Stage 2 is authored once from that contract and confirms the complete deck solution: reading mode, narrative mode, page count, template strategy, coordinated visual system, image sources, and generated-image rendering. Reading mode decides how meaning is carried by page, visuals, presenter, and notes; its cards do not present px values. The browser may apply the deterministic `reading mode → body baseline → unpinned role sizes` dependency locally, while manual size edits pin visible values. It never regenerates Stage 2. Stage 3 is authored once and contains production mechanics only: conditional AI acquisition, formula policy, generation mode, and spec refinement. The compatibility key `delivery_purpose` means reading mode. Generated images inherit the selected deck color roles directly; there is no independent image-palette choice. The final visible state in `confirm_ui/result.json` is authoritative—there is no hidden post-confirm repair—and project validation requires the six contract key lines under `spec_lock.md ## communication` (any prose value may be blank) plus an `Audience move` in every §IX Slide block.
+**Strategist confirmation stage as the only blocking gate.** Strategist ends with one gate delivered in three dependency-ordered stages. Stage 1 confirms an open communication contract and canvas. Its prose boxes contain editable recommendations, but none requires a non-empty answer: confirmation persists the current text exactly, and a cleared value stays empty instead of falling back to the recommendation. Stage 2 is authored once from that contract and confirms the complete deck solution: reading mode, narrative mode, page count, coordinated visual system, image sources, and generated-image rendering. When a template is installed, Strategist also derives its page/prototype application plan internally from the actual workspace and current content; the UI exposes no template-mode controls. Reading mode decides how meaning is carried by page, visuals, presenter, and notes; its cards do not present px values. The browser may apply the deterministic `reading mode → body baseline → unpinned role sizes` dependency locally, while manual size edits pin visible values. It never regenerates Stage 2. Stage 3 is authored once and contains production mechanics only: conditional AI acquisition, formula policy, generation mode, and spec refinement. The compatibility key `delivery_purpose` means reading mode. Generated images inherit the selected deck color roles directly; there is no independent image-palette choice. The final visible state in `confirm_ui/result.json` is authoritative—there is no hidden post-confirm repair—and project validation requires the six contract key lines under `spec_lock.md ## communication` (any prose value may be blank) plus an `Audience move` in every §IX Slide block.
**Image analysis goes through regenerated metadata, not pixels.** When images exist, Strategist and Executor use `analyze_images.py` output (`analysis/image_analysis.csv`) rather than directly opening image files. The CSV is a regenerated view over the live `images/` folder, not a durable cache. Re-running it before image-sensitive decisions is the staleness strategy: user images, extracted images, web images, AI outputs, formulas, and sliced elements all converge into the same measured fact table.
@@ -540,7 +540,7 @@ These direct routes share some analysis primitives with the main pipeline, espec
**Why reusable bounds are design zones, not measured text boxes.** Slot bounds come from the intended safe area, column, panel inset, or picture frame—not glyph width, line count, or the current content's tight box. The current Slide retains its own authored carrier geometry, so 4:6, 3:7, and 5:5 instances may share one Layout when they express the same semantic composition. Text length therefore cannot accidentally split or mutate the reusable Layout contract.
-**Why reuse scope and adherence are separate.** `template_reuse_scope` first selects literal mirror reuse, structural layout reuse, or flat style reference. Only `mirror` and `layout` then use `template_adherence: strict|adaptive` on the structured route: `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 defines a new Layout only when fixed Layout atoms or slot topology/bounds change; the assignment is updated during page authoring rather than inferred later. A template-backed definition may remain unused and still register in the final package. Layout skin remains project-controlled, while mirror additionally preserves literal visuals and text-node topology. `style` has no adherence value or structure mappings.
+**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 defines a new Layout only when fixed Layout atoms or slot topology/bounds change; the assignment is updated during page authoring rather than inferred 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 additionally preserves literal visuals and text-node topology. `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 locked title size 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.
diff --git a/docs/templates-architecture.md b/docs/templates-architecture.md
index 5b7f629d..7137f0cf 100644
--- a/docs/templates-architecture.md
+++ b/docs/templates-architecture.md
@@ -16,13 +16,13 @@
|---|---|---|---|---|
| **Brand** | `templates/brands/<id>/` | Identity segment only: color / typography / logo / voice / icon style | No canvas, page structure, SVG roster | `workflows/create-template/create-brand.md` |
| **Layout** | `templates/layouts/<id>/` | Brand-neutral structure segment only: canvas / page structure / semantic text roles / page types / SVG roster | No brand identity and no recurring communication application | `workflows/create-template/create-layout.md` |
-| **Deck** | `templates/decks/<id>/` | A recurring presentation family: application contract + integrated identity + structure | — | `workflows/create-template/create-deck.md` |
+| **Deck** | `templates/decks/<id>/` | A recurring presentation family: descriptive application context + integrated identity + structure | — | `workflows/create-template/create-deck.md` |
-Every newly created Layout/Deck SVG is a complete preview with root Master/Layout key and picker names, direct atomic Master/Layout elements, and top-level semantic slot groups. A normal slot has positive design-zone bounds and exactly one compatible carrier; composite `object` regions use explicit proxy binding, and zero-slot Layouts are valid. These specialized markers are authoritative; minimal `data-pptx-role` hints are added only for structural page-frame behavior they cannot express. `standard` / `fidelity` author new SVGs and new structure without preserving or distilling source topology. Mirror materializes a new workspace from validated authoring IR: a native PPTX contributes only supported facts still present in its package, while a current-contract SVG template contributes only its declared contract. It never reconstructs missing topology from a legacy SVG; fixed-layer source groups that are valid inputs are mechanically expanded into direct atoms. Strict keeps the selected declared Layout contract; adaptive retains the Master and may create a new Layout identity while authoring. Both export through `pptx_structure.mode: structured`. A flat directory with `design_spec.md` at its root remains a supported compatibility shape only when its SVGs satisfy the current contract. Semantic-legacy packages must be replaced by a newly created template workspace; they are never upgraded in place.
+Every newly created Layout/Deck SVG is a complete preview with root Master/Layout key and picker names, direct atomic Master/Layout elements, and top-level semantic slot groups. A normal slot has positive design-zone bounds and exactly one compatible carrier; composite `object` regions use explicit proxy binding, and zero-slot Layouts are valid. These specialized markers are authoritative; minimal `data-pptx-role` hints are added only for structural page-frame behavior they cannot express. Create Template derives `standard` / `fidelity` / `mirror` internally from the natural-language intent and source evidence. Authored strategies create new SVGs and structure; mirror materializes validated source facts. Strategist later derives strict/adaptive exporter behavior from the actual prototypes and current content. None of these implementation values is a required user choice. A flat directory with `design_spec.md` at its root remains a supported compatibility shape only when its SVGs satisfy the current contract. Semantic-legacy packages must be replaced by a newly created template workspace; they are never upgraded in place.
The three 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:
-The fused project-level `design_spec.md` retains the existing routing `kind`: `deck` when both identity and structure are present, `layout` when only structure is present, and `brand` when only identity is present. For a project-local Brand + Layout composition, this label means “both capabilities are installed”; it does not promote that composition into a reusable library Deck or invent an application contract. The current project's Stage-1 communication contract supplies the application context. The Strategist confirmation page uses `kind` to show `adaptive / strict` only for bundles that actually own page structure.
+The fused project-level `design_spec.md` retains the existing routing `kind`: `deck` when both identity and structure are present, `layout` when only structure is present, and `brand` when only identity is present. For a project-local Brand + Layout composition, this label means “both capabilities are installed”; it does not promote that composition into a reusable library Deck or invent 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.
```yaml
# templates/brands/anthropic/templates/design_spec.md
@@ -54,7 +54,7 @@ Project template kinds do not map one-to-one to PresentationML objects:
|---|---|
| **Brand** | Theme colors/fonts/effects plus logo and other fixed identity-asset rules |
| **Layout** | Master/Layout/Placeholder topology, reusable geometry, semantic text roles, and spatial slot behavior |
-| **Deck** | The Brand and Layout projections plus purpose-specific starting content and usage rules |
+| **Deck** | The Brand and Layout projections plus descriptive recurring-application context and actual prototypes |
A Slide Master may contain both structural geometry and brand visuals. Source
ownership remains separated—Layout owns topology, placement, semantic text
@@ -109,15 +109,15 @@ To make multi-path fusion override cleanly, every field belongs to a named segme
|---|---|---|
| **Identity** | Color Scheme / Typography / Logo / Voice & Tone / Icon Style | brand |
| **Structure** | Portable canvas/page-type metadata, structure-owned Signature rules, SVG Page Roster, and the SVG Master/Layout/slot contract | layout |
-| **Application** | Template Overview: recurring situations, audiences/outcomes, delivery assumptions, stable narrative/page roles, and content reuse policy | deck only; brand / layout don't write this |
+| **Application** | Template Overview: recurring situations, audiences/outcomes, delivery assumptions, and representative narrative/page roles | deck only; brand / layout don't write this |
### Why Deck is its own kind
A Deck encodes a **recurring presentation family**, not merely a pre-combined
-Brand and Layout. It states what communication situations the template serves,
-which audience outcomes it supports, which narrative/page roles remain stable,
-and how starting content must be retained, replaced, or omitted. Identity and
-structure are integrated around that application contract.
+Brand and Layout. It describes the communication situations the template
+serves, the audience outcomes it supports, and representative narrative/page
+roles. Identity and structure are integrated around that context, while the
+current Strategist decides which prototypes and content to use.
`standard` / `fidelity` author a new complete system from confirmed evidence;
mirror maps validated source identities and parentage one-to-one into a new
@@ -245,13 +245,12 @@ primary_color: "<HEX>"
| VI | Assets | Identity/supporting assets; omit when none |
| VII | Placeholder Overrides | Structure vocabulary; omit when none |
-Template Overview must identify the recurring presentation family, intended
-audiences and outcomes, delivery/reading assumptions, stable narrative or page
-roles, and the reuse boundary between fixed, replaceable, optional, and
-example-only content. Page Roster must state the content policy of each
-prototype in addition to its Master/Layout/slot contract. These policies guide
-selection; they do not force every generated presentation to retain the same
-page count or order.
+Template Overview identifies the recurring presentation family, intended
+audiences and outcomes, delivery/reading assumptions, and representative
+narrative or page roles. Page Roster factually describes each prototype's
+Master/Layout/slot contract, visual character, intended role, and capacity. It
+must not assign required/optional/repeatable or fixed/replaceable/example-only
+policy; Strategist derives those decisions for the current content.
Portable canvas fields, `page_count`, and the explicit SVG roster carry the
rest of the structure contract. General spacing, font-ratio, SVG, and
@@ -400,7 +399,7 @@ 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 always confirms the same open communication contract independently of the template. Brand supplies identity constraints while structure stays free; Layout exposes structural capability; Deck also contributes an application contract. Stage 2 derivation compares that stored application with the confirmed current contract rather than silently treating it as truth, then decides whether a compatible Deck/Layout should be consumed as `mirror`, `layout`, or `style` where legal. A mirror-authored workspace therefore enables literal reuse but never selects it automatically. Stage 3 realizes the confirmed direction with the identity, structure, and application rules actually retained by that scope. 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 always confirms the same open communication contract independently of the template. Brand supplies identity constraints while structure stays free; Layout exposes structural capability; Deck also contributes descriptive application context. After Stage 1, Strategist inspects the actual prototypes 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. The Confirm UI exposes no template-mode fields. Planning semantics live in `references/strategist.md` and `references/strategist-template.md`; `templates/schemas/spec_lock.schema.json` owns the machine structure.
---
diff --git a/docs/templates-guide.md b/docs/templates-guide.md
index aabe258b..9e6af270 100644
--- a/docs/templates-guide.md
+++ b/docs/templates-guide.md
@@ -30,7 +30,7 @@ Choose the workspace kind by what must be reused:
|---|---|---|
| **Brand** | Color, typography, logo, voice, icon style | Identity constraints only. Generated pages remain Slide-local under one clean project Master and Blank Layout. |
| **Layout** | Brand-neutral page grammar, Master/Layout identities, semantic text roles, slots, and layout roster | A structured deck with reusable native Masters, named Layouts, and placeholders; identity, reading-mode typography, and communication application are resolved separately. |
-| **Deck** | A recurring presentation family: application rules, identity, page structure, and starting-content policy | A structured deck with the template's integrated identity, reusable native structure, and scenario-aware starting rules. |
+| **Deck** | A recurring presentation family: descriptive application context, identity, page structure, and actual prototypes | A deck whose page/prototype application plan is derived by AI from the template and current content. |
Theme, Slide Master, Slide Layout, and Placeholder are native PowerPoint
objects, not additional workspace kinds. Brand and Layout rules are compiled
@@ -101,19 +101,21 @@ Template workspace: projects/acme_template/
The path labels are optional; the paths themselves are mandatory. If two paths have the same kind, the workflow stops at the existing conflict-resolution gate instead of choosing one silently.
+You do not need to choose a template-use mode. By default, Strategist reads the actual Master/Layout/prototype roster and current content, then decides which pages to select, repeat, skip, reorder, or reorganize. If you care about a specific boundary, state it in ordinary language in the same request—for example, “keep the cover and closing page exactly, choose suitable middle pages yourself” or “use only the visual language”. That explicit sentence wins over AI judgment.
+
### Template catalog
Templates are organized into three kinds, each with a discovery index:
- [`brands_index.json`](../skills/ppt-master/templates/brands/brands_index.json) — identity-only workspaces: color / typography / logo / voice / icon style, with no SVG page roster
- [`layouts_index.json`](../skills/ppt-master/templates/layouts/layouts_index.json) — structure-only workspaces: canvas / page grammar / page types / SVG roster, with identity selected downstream
-- [`decks_index.json`](../skills/ppt-master/templates/decks/decks_index.json) — recurring presentation applications with integrated identity, structure, and content-reuse rules
+- [`decks_index.json`](../skills/ppt-master/templates/decks/decks_index.json) — recurring presentation applications with integrated identity, structure, and factual prototype descriptions
Ask "what templates are available?" for a readable list with workspace paths. The indexes are the current source of truth; the kind-specific READMEs define their contracts. Full data model + fusion / conflict-resolution rules: [`templates-architecture.md`](./templates-architecture.md).
### Free design vs template
-Free design is **not** "no structure" or "no style" — the Strategist still plans the narrative, hierarchy, and visual system for that specific deck. Its generated pages use `pptx_structure.mode: flat`, so every visible object remains Slide-local. A Brand-only workspace also stays `flat` while supplying identity constraints. Layout and Deck workspaces expose a reusable Master / Layout / slot contract: confirmed `mirror` or `layout` use it through `pptx_structure.mode: structured`, while confirmed `style` intentionally discards native structure and generates `flat`.
+Free design is **not** "no structure" or "no style" — the Strategist still plans the narrative, hierarchy, and visual system for that specific deck. Its generated pages use `pptx_structure.mode: flat`, so every visible object remains Slide-local. A Brand-only workspace also stays `flat` while supplying identity constraints. Layout and Deck workspaces expose a reusable Master / Layout / slot contract. Strategist inspects the real prototypes and current content, then automatically decides whether to use that structure or only its visual language.
> Rule of thumb: use a Brand workspace when identity must be fixed; use a Layout workspace when brand-neutral structure should be reused while purpose remains open; use a Deck when a branded structural system or recurring communication application should travel as one contract. Use free design when composition should grow from the current content.
@@ -161,15 +163,15 @@ The entry name always remains **Create Template**. It dispatches exactly one chi
You may provide direct conversation text, pasted requirements, Markdown/TXT, DOCX/PDF/HTML/URL, websites, images/screenshots, logo/icon/font assets, PPTX/SVG files, or any useful combination. The workflow analyzes every applicable channel, keeps source provenance, and surfaces conflicts in the mandatory brief instead of silently choosing one source. Exact values authored by you are decisions whether they arrive in chat, pasted text, or your own brief file; a file carrier does not turn them into facts. Facts require independently traceable external authority or machine-observable source metadata. Visual estimates and vague-text interpretations remain suggestions until confirmed.
-**When an existing deck's native structure matters, hand over the original `.pptx` file.** The importer reads OOXML directly and extracts the Master, Layout, placeholder, theme, native-shape, and reusable-asset facts that are actually present and supported into layered analysis references. In `standard` / `fidelity`, Template_Designer uses them as visual reference and authors a new SVG roster plus a new Master/Layout/slot system. In mirror, it materializes those validated source facts into a new workspace without inventing missing topology or design intent. The original PPTX remains immutable analysis evidence and is not packaged into the new template.
+**When an existing deck's native structure matters, hand over the original `.pptx` file.** The importer reads OOXML directly and extracts the Master, Layout, placeholder, theme, native-shape, and reusable-asset facts that are actually present and supported into layered analysis references. Tell the AI in ordinary language what result you want—for example, “preserve it as-is”, “extract a reusable Master/Layout system”, or “keep the visual language but redesign the structure”. It then chooses the compatible internal implementation. The original PPTX remains immutable analysis evidence and is not packaged into the new template.
You can also design from scratch from a brand guideline: provide a logo, primary color HEX, fonts, tone description, and a few mood references — the AI will design the page skeletons on the spot. This suits brands that don't yet have a finished PPT, only a VI manual.
-> **Evidence boundary:** images, screenshots, text, documents, websites, and loose assets can independently drive `standard`. `fidelity` requires PPTX/SVG page evidence, while `mirror` requires an original PPTX or a complete current structured-SVG contract. Supplemental sources may clarify mirror evidence but cannot invent or change its native topology.
+> **Evidence boundary:** images, screenshots, text, documents, websites, and loose assets can drive a newly authored template. Broad source-aligned coverage requires PPTX/SVG page evidence; literal native preservation requires an original PPTX or a complete current structured-SVG contract. Supplemental sources may clarify preservation intent but cannot invent or change native topology.
### Step 2 — The template brief (mandatory confirmation)
-The workflow does not silently infer values — before generation it lists these items and waits for your reply:
+Before generation, the workflow writes one concise natural-language proposal and waits for corrections or acceptance. It does **not** ask you to choose template modes, fidelity enums, or page/content policies.
| Field | Notes |
|-------|-------|
@@ -178,16 +180,10 @@ The workflow does not silently infer values — before generation it lists these
| **Selected child workflow** | Create Brand / Create Layout / Create Deck, fixed by the entry dispatch |
| **Template ID** | Portable template identity; in library scope it is also the directory / index key. Prefer ASCII slug like `acme_consulting`; non-ASCII names work but must be filesystem-safe |
| **Display name** | Human-readable name for documentation |
-| **Category** | One of `brand` / `general` / `scenario` / `government` / `special` |
-| **Use cases** | Annual report / consulting / defense / government briefing / ... |
-| **Tone summary** | One line, e.g. "modern, restrained, data-driven" |
-| **Theme mode** | Create Layout/Create Deck only: light / dark / gradient / ... |
-| **Canvas format** | Create Layout/Create Deck only; default `ppt169` (16:9), with other formats specified up front |
-| **Replication mode** | Create Layout/Create Deck only: `standard` (default compact, brief-driven roster; may include a small number of explicitly required distinct variants) / `fidelity` (broader source-aligned coverage of useful semantic families) / `mirror` (one materialized prototype per source slide). `standard` / `fidelity` author new SVG semantics; mirror preserves only validated facts already present in the source package. Layout mirror is available only when that source contract is already brand-neutral and application-neutral. |
-| **Native structure facts** | Create Layout/Create Deck only: the brief reports source Master/Layout counts, parent relationships, placeholder identities, and multi-master status. `standard` / `fidelity` treat them as reference only; mirror maps the supported facts one-to-one into the current `structured` contract. |
-| **Visual fidelity** | Create Layout/Create Deck only; required for `standard` / `fidelity` when a reference exists. Choose `literal` or `adapted`. **Not asked for `mirror`** — mirror preserves the supported source visual. |
-| **Keywords** | 3–5 tags for index lookup |
-| Theme color / design notes / asset list | Optional — can be auto-extracted from the source |
+| **Template context** | One proposed category, use case, display name, tone summary, and index keywords; you may correct the prose directly |
+| **Canvas and visual direction** | Create Layout/Create Deck only: the proposed canvas, light/dark behavior, identity, and source-derived visual rules |
+| **Creation plan** | What the AI will preserve, rebuild, simplify, or extract; how broad the prototype set will be; and how native structure will be handled—all described in ordinary language |
+| **Source facts and assets** | Observable Master/Layout facts, supported native features, adopted assets, exclusions, and any material limitation |
After confirmation the workflow echoes the finalized brief and emits the marker `[TEMPLATE_BRIEF_CONFIRMED]`. Subsequent steps only run after that marker. **This is a hard gate — no brief, no generation.**
@@ -195,24 +191,15 @@ Before either scope writes final files, one hard preflight resolves the required
> Why so strict? A template is a structural contract, whether it is reused globally or only inside the current project. Confirming ownership and geometry first avoids partial or misplaced output.
-### Step 3 — Create Layout/Create Deck: `standard`, `fidelity`, or `mirror`?
+### Step 3 — The AI derives the implementation
-This is the most easily confused decision when deriving a structured template. Create Brand skips it because identity-only work has no SVG roster or native structure.
+You do not select a creation mode. The AI translates the confirmed prose into one internal strategy so deterministic tools can run:
-| | **standard** | **fidelity** | **mirror** |
-|---|---|---|---|
-| Output pages | Usually 4–6: cover / chapter / ending, optional TOC, and one or a small explicitly required set of content Layouts | broader useful semantic-family coverage — count driven by the source evidence | one materialized prototype per source slide (1:1 roster) |
-| Abstraction | High — clean, reusable skeleton | Medium — semantic source families redesigned with cleanup | None at the topology level; only mechanical structured-contract normalization |
-| Authoring placeholders | Yes (`{{TITLE}}`, `{{CONTENT_AREA}}`, …) | Yes | Literal text may remain, but imported native content slots still carry semantic metadata |
-| Best for | You want "tone + compact skeleton", including a few brief-required structures, to generate brand-new decks later | The source PPTX itself is a customized layout library and broader source-driven coverage matters | Someone else's polished deck is great as-is, you want every page available as a reference |
-| Typical use | Building a base brand template | Replicating a 20-variant government briefing layout set | Keeping all 50 source compositions available as faithful prototypes |
-| Source requirement | None | PPTX or SVG visual reference | PPTX, or SVGs with a complete explicit structure contract |
-| Decoration complexity | Usually simpler | Must preserve sprite-sheet crop structure | Preserves literal geometry while adding explicit layer ownership |
-
-`mirror` cannot preserve identity/application rules while also producing a
-brand-neutral, application-neutral Layout. Choose `standard` / `fidelity` when
-those rules should be removed and a new Layout authored; choose Create Deck
-mirror when they should remain literal.
+- a compact reusable system when the request calls for distillation;
+- broader source-aligned coverage when the source itself contains useful variants;
+- literal materialization when the request calls for preservation and the source has a complete supported structure contract.
+
+The resulting frontmatter still records `replication_mode: standard|fidelity|mirror` for tool compatibility and audit. It is an implementation record, not a user-facing choice. A brand-neutral Layout cannot literally preserve brand/application facts; the AI either re-authors it as a Layout or keeps those facts in a Deck according to the requested result.
**About sprite sheets**: PPTX-exported assets are often a single large image referenced from multiple slides, each cropping a different region via nested `<svg viewBox=...>` wrappers. In `fidelity` and `mirror` modes this nesting must be preserved — you cannot flatten it to a bare `<image>`, or the crop is lost and the page misaligns. The workflow validates this automatically.
@@ -234,7 +221,7 @@ the designer writes that brief against the published roster.
**Mirror graph boundary**: mirror preserves the complete supported source Master/Layout graph. It emits one complete prototype per source slide and one definition-only `layout_<layout_key>.svg` prototype for every source Layout unused by those slides. The latter registers in PowerPoint through the independent Layout roster without becoming a published page; its parent Master is retained with it. Preflight stops only when required source facts or supported geometry are missing, never merely because a Layout is unused.
-**How a mirror-authored workspace is consumed**: source-to-workspace `replication_mode: mirror` is a capability, not the project choice. After the open communication contract is confirmed, Stage 2 first compares a Deck's stored application contract with the current audience, outcome, and content roles. It recommends `mirror` only for a recurring artifact whose new content fits the existing page roles and text topology; use `layout` when compatible structure should continue but content needs reflow, and `style` when only identity should carry over or the argument needs a different structure. If `mirror` is confirmed, the Strategist picks one prototype per project page and the Executor copies that complete SVG and edits only allowed visible text values while preserving decoration, sprite crops, geometry, and normalized structured declarations. This still does not require the source page count or order. Mirror preserves supported appearance, not the source PPTX group-editing hierarchy.
+**How a mirror-authored workspace is consumed**: source-to-workspace `replication_mode: mirror` is a capability, not a project choice. Strategist inspects the actual prototypes, current content, and any explicit instruction, then decides which pages to select, repeat, skip, or reorder and whether literal, structural, or visual-only reuse is appropriate. Literal reuse copies a complete prototype and edits only allowed visible text values while preserving decoration, sprite crops, geometry, and normalized structured declarations. This never requires the source page count or order.
### Step 4 — Validation, review export, registration, and discovery
@@ -247,10 +234,7 @@ After generation, both scopes run [`svg_quality_checker.py`](../skills/ppt-maste
Library registration makes the template **discoverable** — when someone asks "what templates are available?", the AI lists it from the index. To use either scope, follow [Generate PPTX Step 3](../skills/ppt-master/workflows/generate-pptx.md#step-3-template-option): provide the workspace root before Step 3 runs, for example `use this template: skills/ppt-master/templates/layouts/<your_template_id>/` or `use this template: projects/<name>/`. A project workspace can also be migrated or reused elsewhere because its core shape is identical; register it only if it is placed in the library and should appear in discovery.
-When a deck/layout template is selected, the Strategist confirmation stage asks how it should be used:
-
-- **adaptive** — choose one template SVG per page; keep its Master and assign a new explicit Layout key during authoring when fixed Layout atoms or slot topology/bounds must change
-- **strict** — choose one template SVG per page and keep its Master/Layout/slot contract unchanged
+When a Deck/Layout template is selected, Strategist automatically authors the page/prototype plan. It may use the whole roster or a subset, repeat or reorder prototypes, and reorganize content where needed. `strict` / `adaptive` remain internal exporter values and do not appear as confirmation options.
### Verify that Master and Layout were really applied
diff --git a/docs/zh/roadmap.md b/docs/zh/roadmap.md
index e5823f4e..94a6b466 100644
--- a/docs/zh/roadmap.md
+++ b/docs/zh/roadmap.md
@@ -53,7 +53,7 @@
- **mode catalog 扩档至 5 个:加 `briefing`** — 补上「中性信息平铺」这一格:无论点 / 无故事 / 不教学 / 不冲击,topic 标题、等权铺事实、完整可扫读,服务周报 / 参考册 / 目录 / 会议材料 / FAQ 这类「只告知不论证」的 deck。五个 mode 自此更接近 MECE 地切分**表达意图**:说服(pyramid)· 讲故事(narrative)· 教会(instructional)· 震住(showcase)· 只告知(briefing)。`_index` 加了 `briefing` vs `pyramid` 的灰区判据(「要不要造个 thesis 才塞得进 pyramid → 那就是 briefing」)。五个预设之外加一个 `custom` 兜底,承接预设盖不住的 bespoke 方向(特殊节奏 / 多 mode 融合 / 特定姿态)——用户点名**或策略师推荐**皆可,与所有锁一样由用户确认;一份 deck 永远只锁一个值,融合=一个 custom 描述多幕。唯一要避免的是「预设明明贴合却图省事甩 custom」。这与「用户自带大纲 / 方向覆盖 mode」是同一条真值优先原则
- **mode / visual-style 体系真实 deck 验证完成 + 四项校准收紧落地** — 5 mode + 18 visual-style + `custom` 逃生舱在 5 份覆盖性 deck 上跑过验证(briefing×data-journalism / narrative×photo-editorial / instructional×chalkboard / showcase×glassmorphism / custom×zine,其中 narrative 一份走 AI 图生成分支):**选型零误判**(四对 Close-calls 灰区引力全被触发且全抗住)、**纪律全落实**(零 HEX / Reference 强度 / 整页版面语言)、**custom 机制可用**(`mode_behavior` 散文段落撑过 10 页生成、能讲成大白话让用户确认)、**mode ⟂ visual_style 正交成立**(任意组合无串味,含「keynote/发布会=mode 不是 style」路由正面验证)、导出 5/5 deck × 全页 0 失败。据真实信号收紧四处:`strategist §e` 按 visual_style 预判中性档位一次锁全(消除连续三份的 Executor 中途补色)、[`executor-structured.md`](../../skills/ppt-master/references/executor-structured.md) §1 套模板页重皮到当前 visual_style(模板供结构不供皮,mirror 模板保持已声明的视觉身份)、`briefing §1` 的 `core_message` = 本页覆盖什么而非证明什么(briefing 专属例外,全局 §IX 论断语义保留给 narrative/instructional/pyramid)、`svg_quality_checker` 修字体 drift 误报(按定界符匹配 + font-stack 归一化)+ 放宽 showcase mode 与 poster 类 visual-style 的字号上限
- **可选 spec 复核环节上线**([`workflows/stages/refine-spec.md`](../../skills/ppt-master/workflows/stages/refine-spec.md)) — 策略师确认阶段后新增一个 opt-in 停顿点:用户明确要求时(默认 OFF),Strategist 先产出完整 `design_spec.md` + `spec_lock.md`,停下来让用户对 spec 任意部分(大纲 / 配色 / 排版 / 版式 / 图片策略 / page rhythm)深入讨论修改,改完同步两个文件再进生成。与 split-mode 同构——不主动触发、默认管线零变化,仅在策略师确认阶段里多一行 opt-in 提示。复核视角(逻辑清晰度 / 信息密度 / 焦点 / 口语化 / 感染力 / 章节配比 + 各设计维度)只给方向、不落任何数字阈值(`Reference` 强度)。启发自 [@cuberoocp](https://github.com/cuberoocp) [issue #173](https://github.com/hugohe3/ppt-master/issues/173)
-- **交互式可视化策略师确认页(Step 4)**([`scripts/confirm_ui/server.py`](../../skills/ppt-master/scripts/confirm_ui/server.py),字段 schema [`scripts/docs/confirm_ui.md`](../../skills/ppt-master/scripts/docs/confirm_ui.md)) — 模板遵循方式只在加载 Deck/Layout 模板时显示,默认推荐 `adaptive`:每页仍映射模板架构,无匹配构图时可在同一 Master 下创建新 Layout;`strict` 保持所选 Layout 契约不变。确认页与 Live Preview 共用端口,最终 `result.json` 对下游权威。
+- **交互式可视化策略师确认页(Step 4)**([`scripts/confirm_ui/server.py`](../../skills/ppt-master/scripts/confirm_ui/server.py),字段 schema [`scripts/docs/confirm_ui.md`](../../skills/ppt-master/scripts/docs/confirm_ui.md)) — 模板应用改由 AI 根据真实工作区和当前内容生成,确认页不再显示复用/遵循控件;strict/adaptive 仍作为 structured 导出器的内部值。确认页与 Live Preview 共用端口,最终 `result.json` 对用户可见选择权威。
- **源文档转换保真度提升一批** — 源材料进管线时更少丢信息:`doc_to_md` 把 Word 里的 OMML / Office Math 公式转成内联 LaTeX、`pdf_to_md` 识别 `Figure N |` 竖线分隔的图注、`ppt_to_md` 保留源 deck 已有的超链接(run 级外链 `[text](url)` / slide 内部跳转 `[text](#slide-N)` / shape 级点击,含危险 scheme 过滤与锚文本 Markdown 转义)并把原生图表数据转写成 Markdown 表格(数值随转换存活,不再只剩一张图)。图注识别基于 [@suay1113](https://github.com/suay1113) [PR #191](https://github.com/hugohe3/ppt-master/pull/191),超链接保留提炼自 [@ZhaoZuohong](https://github.com/ZhaoZuohong) [PR #155](https://github.com/hugohe3/ppt-master/pull/155)
- **内容保真的 PPT 美化 / 重排版 profile 上线**([`workflows/profiles/beautify-pptx.md`](../../skills/ppt-master/workflows/profiles/beautify-pptx.md)) — 它是 Generate PPTX 的一个 profile,与 `template-fill` 互为镜像:template-fill 复用某份 deck 的设计换新内容,beautify 反过来保留内容、重做版面。给一份现成 PPTX,**全部文字逐字保留(不增 / 不删 / 不改写)**,从源 deck 提取并**继承其视觉身份(配色 / 字体,`theme` 或 `observed` 两套候选过确认页)**,只重做版面 / 层级 / 留白;严格 1:1 页数页序,图表 / 表格从抽取数据原生重绘(数据冻结)、源配图重新排布。技术上仍走从零生成原生 PPTX 管线(`ppt_to_md` 抽内容 → 主管线 → 全新 deck),不补丁原文件,因此不碰 Non-goals #53。新增 `beautify_identity.py` / `beautify_inventory.py`,confirm 页全字段按源 seed 后用户复核。v1 天花板(诚实标注):不缓解信息过载(挤页只在页内改,真要重排分页属普通 profile)、不保证坐标级 paste-back、combo / dual-axis / waterfall 图丢未捕获的绘图层
@@ -122,7 +122,7 @@ Generate PPTX 路线围绕完全可控的新形状、文字与版式创作。结
**基础诉求其实很简单**:如果只是「固定位置替换 Excel 数据到 PPT 模板」,直接让 AI 写一段 `python-pptx` 脚本即可,几行代码搞定,不需要本项目这套管线。
-> **已支持边界**:Fill Native PPTX(`template-fill-pptx`)直接回填选中的源页面;Create Template(`create-template`)或者创作新的显式 SVG 契约(`standard` / `fidelity`),或者在不做语义归纳的前提下把受支持来源契约中的已验证事实映射进新工作区(`mirror`)。下游 `strict` / `adaptive` 都把这份已声明契约编译成原生结构。仍不做未经审查、没有契约的任意第三方 placeholder 全自动替换。
+> **已支持边界**:Fill Native PPTX(`template-fill-pptx`)直接回填选中的源页面;Create Template(`create-template`)根据自然语言请求和来源证据,在内部推导重新创作或 mirror 物化实现;Strategist 再根据真实模板和当前内容推导 strict/adaptive 导出行为。仍不做未经审查、没有契约的任意第三方 placeholder 全自动替换。
### 把原生 PowerPoint 图表设为默认路线
diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.md
index fd82fa07..f5e0cfd0 100644
--- a/docs/zh/technical-design.md
+++ b/docs/zh/technical-design.md
@@ -87,7 +87,7 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使
凡是通过 SVG 创作或重新设计页面的工作流,`svg_output/` 都是完整的页面设计权威,但这里的 SVG 专指通过项目合同校验的项目规范化 SVG,而不是任意浏览器可渲染的 SVG。最终幻灯片中应出现的文字、图片、形状、图示、图表 / 表格 fallback、背景和模板派生布局元素,都必须已经存在于对应页面 SVG 中,或被它明确引用。模板、`design_spec.md` 和 `spec_lock.md` 负责指导 SVG 创作;导出器不能把它们当成第二层画面来源,在导出阶段补入 SVG 缺失的页面内容。
-最小语义标记不会削弱这条闭包。自由设计、brand-only 和 `template_reuse_scope: style` 页面使用 `pptx_structure.mode: flat`:所有已表达对象保持 Slide 本地,不创作任何 Master/Layout 身份、分层或 placeholder metadata。导出器根据当前配色/字体 lock 生成一个属于本项目的干净 Master 和一个 Blank Layout,删除 title/body 等内置内容占位符与未使用的内置 Layout,仅保留标准日期、页脚和页码能力钩子,但不提升任何 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 路线按照已确认的复用范围创作新页面。flat 项目是有意不带 mapping,不算 legacy。导出器不推断、修补或迁移 Master/Layout 结构与 placeholder。
+最小语义标记不会削弱这条闭包。自由设计、brand-only 和 `template_reuse_scope: style` 页面使用 `pptx_structure.mode: flat`:所有已表达对象保持 Slide 本地,不创作任何 Master/Layout 身份、分层或 placeholder metadata。导出器根据当前配色/字体 lock 生成一个属于本项目的干净 Master 和一个 Blank Layout,删除 title/body 等内置内容占位符与未使用的内置 Layout,仅保留标准日期、页脚和页码能力钩子,但不提升任何 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。
| 领域 | 权威来源 |
|---|---|
@@ -322,7 +322,7 @@ PPT Master 不只服务 PPT——同一套 SVG → DrawingML 流水线还能产
|---|---|---|---|
| `brand` | 身份片段 | 配色、字体、logo、语气、图标风格 | 锁定身份;结构保持自由 |
| `layout` | 品牌中立的结构片段 | 画布、页面结构、语义文字角色/空间行为、页面类型、SVG roster | 提供结构能力;身份与沟通应用仍由下游决定 |
-| `deck` | 应用段 + 一体化身份/结构 | 重复场景、受众与结果、内容政策、身份和 SVG roster | 提供应用契约;Stage 2 推导将其与独立确认的 Stage-1 契约对照,再选择复用范围 |
+| `deck` | 应用段 + 一体化身份/结构 | 重复场景、受众与结果、代表性页面角色、身份和真实 SVG roster | 提供描述性语境和原型;Strategist 将其与独立确认的 Stage-1 契约及当前内容对照,再推导应用计划 |
Theme、Slide Master、Slide Layout 与 Placeholder 是编译生成的 PowerPoint 原生对象,不是新的模板 kind。Layout 决定拓扑、位置、语义文字角色与空间行为,Brand 决定身份值与资产。`template_reuse_scope: layout` 会结合已确认的阅读模式和字号体系解析最终 placeholder 格式;`mirror` 则保留来源的字面格式与文字拓扑。两类规则都可编译进同一套原生 Master/Layout 图谱。
@@ -342,7 +342,7 @@ PPT Master 用的是**单主代理内的角色切换**,不是并行子代理
**为什么是角色专属 reference 而不是一个超大 prompt。** Strategist 跑的是「跟用户协商」模式(开放式、对话式、可以回退),Executor 跑的是「产出严格 XML」模式(不准即兴、不准漏属性)。把两者塞进同一个 prompt,强迫模型在同一个 turn 里持守相互矛盾的纪律——所有混合模式的 prompt 工程病灶都会出现。按角色拆开,每个角色只加载它需要的、扔掉其他。
-**策略师确认阶段是唯一的阻塞 gate。** Strategist 阶段以一个按依赖排序的三阶段 gate 作为核心决策点。第一阶段确认开放式沟通契约与画布。其中的文本框承载可编辑推荐,但没有任何一项要求非空:确认时按当前文本原样保存,清空后的值保持为空,不会回退到推荐内容。第二阶段只从该契约计算一次并确认完整 PPT 方案:阅读模式、叙事 mode、页数、模板策略、成套视觉系统、图片来源和生成图渲染。阅读模式决定信息由页面、视觉、讲者和备注如何共同承担,其选项卡不展示 px 数值。浏览器可以在本地执行确定性的「阅读模式 → 正文基准 → 未锁定角色字号」联动;手动编辑字号即锁定可见值,不会重新计算第二阶段。第三阶段也只计算一次,并且只处理生产机制:条件式 AI 图片获取路径、公式策略、生成模式与规范精修。JSON 为兼容保留 `delivery_purpose` 键,但用户侧统一称为阅读模式。生成图直接继承已选 PPT 色彩角色,不再单设图片调色选择。最终 `confirm_ui/result.json` 中的可见状态是权威输入,不存在确认后的隐藏修正;项目校验还会要求 `spec_lock.md ## communication` 下存在六个沟通契约键(任一文本值都允许留空),并要求 §IX 每个 Slide block 都有 `Audience move`。
+**策略师确认阶段是唯一的阻塞 gate。** Strategist 阶段以一个按依赖排序的三阶段 gate 作为核心决策点。第一阶段确认开放式沟通契约与画布。其中的文本框承载可编辑推荐,但没有任何一项要求非空:确认时按当前文本原样保存,清空后的值保持为空,不会回退到推荐内容。第二阶段只从该契约计算一次并确认完整 PPT 方案:阅读模式、叙事 mode、页数、成套视觉系统、图片来源和生成图渲染。存在模板时,Strategist 还会根据真实工作区和当前内容在内部推导页面/原型应用计划,UI 不提供模板模式控件。阅读模式决定信息由页面、视觉、讲者和备注如何共同承担,其选项卡不展示 px 数值。浏览器可以在本地执行确定性的「阅读模式 → 正文基准 → 未锁定角色字号」联动;手动编辑字号即锁定可见值,不会重新计算第二阶段。第三阶段也只计算一次,并且只处理生产机制:条件式 AI 图片获取路径、公式策略、生成模式与规范精修。JSON 为兼容保留 `delivery_purpose` 键,但用户侧统一称为阅读模式。生成图直接继承已选 PPT 色彩角色,不再单设图片调色选择。最终 `confirm_ui/result.json` 中的可见状态是权威输入,不存在确认后的隐藏修正;项目校验还会要求 `spec_lock.md ## communication` 下存在六个沟通契约键(任一文本值都允许留空),并要求 §IX 每个 Slide block 都有 `Audience move`。
**图片分析走重算元数据,不读像素。** 当项目里存在图片时,Strategist 和 Executor 使用 `analyze_images.py` 的输出(`analysis/image_analysis.csv`),而不是直接打开图片文件。这个 CSV 是基于当前 `images/` 目录重算出来的视图,不是持久缓存。每次做图片敏感决策前重跑分析,就是它的防陈旧策略:用户图、抽取图、网络图、AI 图、公式图和切片图最终都会汇入同一张可度量事实表。
@@ -536,7 +536,7 @@ PowerPoint 的 DrawingML 是 SVG 表达力的严格子集,因此主编译路
**为什么可复用 bounds 是设计区域,不是量出来的文本框。** bounds 来自安全区、分栏、面板内框或图片框,而不是字形宽度、行数或当前内容紧包围盒。当前 Slide 保留自己的 carrier 几何,因此只要语义构图相同,4:6、3:7、5:5 的实例都可复用同一 Layout。文本长度不会意外拆分或改变可复用合同。
-**为什么复用范围与遵循方式要拆开。** `template_reuse_scope` 先选择字面镜像复用、结构化版式复用或 flat 风格参考。只有 `mirror` 和 `layout` 再在 structured 路线上使用 `template_adherence: strict|adaptive`:`page_layouts` 记录完整创作原型,`pptx_masters` / `pptx_layouts` 记录唯一可复用定义,`page_pptx_layouts` 记录页面分配。strict 保持声明的原型合同;adaptive 保持原型 Master,只有固定 Layout 原子或槽位 topology/bounds 改变时才定义新 Layout,并在页面创作时立即更新分配,而不是事后推断。模板定义即使暂时没有页面使用,也能注册进最终文件。layout 的皮肤由项目控制;mirror 还要保持字面视觉与文字节点拓扑。`style` 不带 adherence 或结构 mapping。
+**为什么内部应用计划保留两个字段。** 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 改变时才定义新 Layout,并在页面创作时立即更新分配,而不是事后推断。这些是导出器内部值,不是用户确认选项。模板定义即使暂时没有页面使用,也能注册进最终文件。layout 的皮肤由项目控制;mirror 还要保持字面视觉与文字节点拓扑。`style` 不带 adherence 或结构 mapping。
**为什么显式版式把文字默认值分在 Master 与 Layout 两层。** Flat 与 structured 导出都会把锁定的 title 字号和确定性的九级 body 层级写入 Master 文本默认值,同时保留原有缩进与项目符号设置;在 structured 路线上,每个 Layout 文字槽位还会把 carrier 首个 run 的字号写入一级默认值,同时保留提示文字的直接字号。这样,插入或重置 placeholder 时仍能继承 Layout 特定尺度,而生成 Slide 上的直接 run 不变。
diff --git a/docs/zh/templates-architecture.md b/docs/zh/templates-architecture.md
index 01b2ca62..fefe8097 100644
--- a/docs/zh/templates-architecture.md
+++ b/docs/zh/templates-architecture.md
@@ -16,13 +16,13 @@
|---|---|---|---|---|
| **Brand** | `templates/brands/<id>/` | 仅身份段:color / typography / logo / voice / icon style | 不写 canvas、page structure、SVG roster | `workflows/create-template/create-brand.md` |
| **Layout** | `templates/layouts/<id>/` | 仅品牌中立的结构段:canvas / page structure / 语义文字角色 / page types / SVG roster | 不写品牌身份,也不拥有可重复沟通场景 | `workflows/create-template/create-layout.md` |
-| **Deck** | `templates/decks/<id>/` | 一类可重复演示:应用契约 + 一体化身份与结构 | —— | `workflows/create-template/create-deck.md` |
+| **Deck** | `templates/decks/<id>/` | 一类可重复演示:描述性应用语境 + 一体化身份与结构 | —— | `workflows/create-template/create-deck.md` |
-每张新建的 Layout/Deck SVG 都是完整预览,并在根节点声明 Master/Layout key 与选择器名称;固定 Master/Layout 视觉是直接原子元素;语义槽位是顶层 group。普通槽位必须有正数设计区域 bounds 和恰好一个兼容 carrier;复合 `object` 区域走显式 proxy 绑定,零槽 Layout 也合法。这些专用标记具有最高优先级;最小 `data-pptx-role` 只补充它们无法表达的页面框架行为。`standard` / `fidelity` 重新创作 SVG 和新的结构,不保留、也不蒸馏来源拓扑。Mirror 从已验证的 authoring IR 物化一个新工作区:原生 PPTX 只贡献包内仍然存在且受支持的事实;满足当前合同的 SVG 模板只贡献其已声明合同。它不会从旧 SVG 重建缺失拓扑;作为有效输入的固定结构层 group 只允许机械展开成直接原子。下游 `strict` 保持所选声明合同,`adaptive` 保持 Master 并可在创作时建立新 Layout 身份;两者都使用 `pptx_structure.mode: structured`。根目录平铺 `design_spec.md` 的目录只有在 SVG 已满足当前合同时才兼容;带旧结构语义的包必须替换为新建模板工作区,不能原地升级。
+每张新建的 Layout/Deck SVG 都是完整预览,并在根节点声明 Master/Layout key 与选择器名称;固定 Master/Layout 视觉是直接原子元素;语义槽位是顶层 group。普通槽位必须有正数设计区域 bounds 和恰好一个兼容 carrier;复合 `object` 区域走显式 proxy 绑定,零槽 Layout 也合法。这些专用标记具有最高优先级;最小 `data-pptx-role` 只补充它们无法表达的页面框架行为。Create Template 根据自然语言意图与来源证据在内部推导 `standard` / `fidelity` / `mirror`;Strategist 再根据真实原型与当前内容推导 strict/adaptive 导出行为。这些实现值都不是用户必选项。根目录平铺 `design_spec.md` 的目录只有在 SVG 已满足当前合同时才兼容;带旧结构语义的包必须替换为新建模板工作区,不能原地升级。
三者是**三种并列的可复用规则包**,不是 PowerPoint 包对象类型。在全局库范围内,物理目录与 frontmatter `kind` 字段双向对齐:
-多路径合成后的项目级 `design_spec.md` 沿用现有路由 `kind`:同时具备身份段和结构段时为 `deck`,只有结构段时为 `layout`,只有身份段时为 `brand`。对于项目内临时组合的 Brand + Layout,这个标签只表示“已安装两种能力”,不会把组合自动提升为可注册的 Deck,也不会凭空生成应用契约;当前项目的 Stage 1 沟通契约负责提供场景。Strategist 确认页据此只对真正包含页面结构的 bundle 显示 `adaptive / strict`。
+多路径合成后的项目级 `design_spec.md` 沿用现有路由 `kind`:同时具备身份段和结构段时为 `deck`,只有结构段时为 `layout`,只有身份段时为 `brand`。对于项目内临时组合的 Brand + Layout,这个标签只表示“已安装两种能力”,不会把组合自动提升为可注册的 Deck,也不会凭空生成应用语境;当前项目的 Stage 1 沟通契约负责提供场景。Strategist 在内部生成模板应用计划,确认页不显示模板模式控件。
```yaml
# templates/brands/anthropic/templates/design_spec.md
@@ -54,7 +54,7 @@ native_structure_mode: structured
|---|---|
| **Brand** | Theme 的颜色、字体与效果,以及 Logo 等固定身份资产规则 |
| **Layout** | Master/Layout/Placeholder 拓扑、可复用几何、语义文字角色与槽位空间行为 |
-| **Deck** | Brand 与 Layout 的投影,再加面向用途的起始内容和使用规则 |
+| **Deck** | Brand 与 Layout 的投影,再加描述性重复应用语境和真实原型 |
一个 Slide Master 可以同时包含结构几何和品牌视觉。来源规则仍分开归属:Layout 决定拓扑、位置、语义文字角色与空间行为,Brand 决定身份值与资产。下游选择 `layout` 时,导出结合已确认的阅读模式和字号体系解析最终 placeholder 格式;选择 `mirror` 时则保留来源的字面格式与文字拓扑。最后再把适用规则编译进同一套 Master/Layout 图谱。因此 Theme 是已解析身份的实现投影——身份可以来自 Brand、Deck 或当前项目——而不是第四种模板 kind。
@@ -99,11 +99,11 @@ native_structure_mode: structured
|---|---|---|
| **身份段** | Color Scheme / Typography / Logo / Voice & Tone / Icon Style | brand 覆盖 |
| **结构段** | 可移植 canvas/page-type 元数据、结构归属的 Signature 规则、SVG Page Roster,以及 SVG Master/Layout/slot 合同 | layout 覆盖 |
-| **应用段** | Template Overview:重复场景、受众与结果、交付假设、稳定叙事/页面角色及内容复用政策 | deck 独有;brand / layout 不写 |
+| **应用段** | Template Overview:重复场景、受众与结果、交付假设及代表性叙事/页面角色 | deck 独有;brand / layout 不写 |
### 为什么需要 Deck 这一类
-Deck 编码的是**一类可重复演示**,而不只是预先组合好的 Brand 和 Layout。它要说明模板服务哪些沟通场景、支持哪些受众结果、哪些叙事或页面角色会稳定重复,以及起始内容应保留、替换还是删除。身份与结构围绕这份应用契约形成一个整体。
+Deck 编码的是**一类可重复演示**,而不只是预先组合好的 Brand 和 Layout。它描述模板服务哪些沟通场景、支持哪些受众结果,以及常见的叙事或页面角色。身份与结构围绕这份语境形成一个整体;具体选哪些原型、如何处理内容,由当前 Strategist 决定。
`standard` / `fidelity` 根据已确认的证据创作新完整系统;mirror 把已验证的来源身份与父子关系一对一映射进新工作区。Mirror 能保留来源事实,但不能单独证明来源就是可复用 Deck:创建时仍要识别稳定的应用规则。只得到身份时创建 Brand;得到品牌中立的可复用结构时创建 Layout;结构带品牌身份,或者包含场景叙事与内容语法时创建 Deck。
@@ -217,7 +217,7 @@ primary_color: "<HEX>"
| VI | Assets | 身份/支撑资产;无资产时省略 |
| VII | Placeholder Overrides | 结构词汇;无覆盖时省略 |
-Template Overview 必须写明可重复演示类型、目标受众与结果、交付/阅读假设、稳定叙事或页面角色,以及固定、可替换、可选、仅示例内容之间的复用边界。Page Roster 除 Master/Layout/slot 合同外,还必须说明每个原型的内容政策。这些政策用于选型,不要求每次生成都保持相同页数或页序。
+Template Overview 写明可重复演示类型、目标受众与结果、交付/阅读假设及代表性叙事或页面角色。Page Roster 只需如实描述每个原型的 Master/Layout/slot 合同、视觉特征、用途和容量,不得添加必需/可选/可重复或固定/可替换/仅示例政策;当前 Strategist 会按实际内容推导这些决定。
可移植 canvas 字段、`page_count` 和显式 SVG roster 承载其余结构合同。通用间距、字号比例、SVG 和 placeholder 规则保持集中管理,不复制进每个 deck spec。省略条件章节只表示“采用共享默认值或没有资产”,不表示该段改由其他 kind 所有。
@@ -355,7 +355,7 @@ AI: 你给了两个 brand,检测到段级冲突:
### 策略师确认阶段在不同 kind 下的行为
-安装模板不会让沟通问题消失。Stage 1 始终独立确认同一份开放式沟通契约。Brand 提供身份约束、结构仍然自由;Layout 提供结构能力;Deck 还提供应用契约。Stage 2 推导时才把已保存的应用契约与当前确认结果对照,不能静默当成真值,再根据场景在合法范围内选择 `mirror`、`layout` 或 `style`。因此,按 mirror 创建的工作区只是允许原样复用,不会自动选中原样复用。Stage 3 再用该消费范围实际保留的身份、结构与应用规则实现已确认方向。规划语义由 `references/strategist.md` 与 `references/strategist-template.md` 负责,机器结构由 `templates/schemas/spec_lock.schema.json` 负责。
+安装模板不会让沟通问题消失。Stage 1 始终独立确认同一份开放式沟通契约。Brand 提供身份约束、结构仍然自由;Layout 提供结构能力;Deck 还提供描述性应用语境。Stage 1 之后,Strategist 会读取真实原型和当前内容,生成一份页面/原型计划,只把 `mirror`、`layout` 或 `style` 记录为内部导出值。按 mirror 创建的工作区因此只提供原样复用能力,不会强制使用;Confirm UI 不显示模板模式字段。规划语义由 `references/strategist.md` 与 `references/strategist-template.md` 负责,机器结构由 `templates/schemas/spec_lock.schema.json` 负责。
---
diff --git a/docs/zh/templates-guide.md b/docs/zh/templates-guide.md
index a0e4ee1f..f14a5542 100644
--- a/docs/zh/templates-guide.md
+++ b/docs/zh/templates-guide.md
@@ -4,7 +4,7 @@
---
-PPT Master 模板是一种可复用工作区,明确分为三类:**Brand** 只拥有身份系统,**Layout** 只拥有品牌中立的可复用页面结构,**Deck** 拥有一类可重复演示的应用契约及一体化身份与结构。Layout 与 Deck 工作区包含声明 Master / Layout / slot 合同的完整 SVG 原型;Brand 工作区则有意不包含 SVG roster。每个工作区的 `design_spec.md` 与配套素材共同声明该 kind 实际提供什么。
+PPT Master 模板是一种可复用工作区,明确分为三类:**Brand** 只拥有身份系统,**Layout** 只拥有品牌中立的可复用页面结构,**Deck** 拥有一类可重复演示的描述性应用语境及一体化身份与结构。Layout 与 Deck 工作区包含声明 Master / Layout / slot 合同的完整 SVG 原型;Brand 工作区则有意不包含 SVG roster。每个工作区的 `design_spec.md` 与配套素材共同声明该 kind 实际提供什么。
本文回答三个问题:
@@ -30,7 +30,7 @@ PPT Master 模板是一种可复用工作区,明确分为三类:**Brand**
|---|---|---|
| **Brand** | 颜色、字体、Logo、语调、图标风格 | 只提供身份约束。生成页面保持 Slide 本地,文件只有干净的项目 Master 与 Blank Layout 脚手架。 |
| **Layout** | 品牌中立的页面语法、Master/Layout 身份、语义文字角色、槽位与版式 roster | 结构化 deck,包含可复用原生 Master、具名 Layout 与 placeholder;身份、阅读模式字号和沟通应用另行解析。 |
-| **Deck** | 一类可重复演示:应用规则、身份、页面结构与起始内容政策 | 结构化 deck,同时带一体化身份、可复用原生结构和面向场景的起始规则。 |
+| **Deck** | 一类可重复演示:描述性应用语境、身份、页面结构与真实原型 | AI 根据模板实物与当前内容自动生成页面/原型应用计划。 |
Theme、Slide Master、Slide Layout 与 Placeholder 是 PowerPoint 原生对象,不是新的工作区 kind。Brand 与 Layout 的规则会被编译进这些对象。使用 `layout` 时,语义文字角色来自 Layout,最终字体和字号体系由身份与阅读模式共同解析;使用 `mirror` 时则保留来源的字面格式。最终 Master 可以同时包含结构几何和品牌视觉,但来源合同仍保持分离。
@@ -95,19 +95,21 @@ Layout 工作区:skills/ppt-master/templates/layouts/presentation_core/
“模板工作区”这些标签可以不写,但路径本身必须明确。如果给出两个相同 kind 的路径,工作流会进入既有冲突解决门,不会静默替你选一个。
+你不需要选择模板使用模式。默认由 Strategist 读取真实的 Master/Layout/原型集合和当前内容,决定选哪些页、哪些重复/跳过/重排,以及是否重组。如果你在意某个边界,直接在同一句请求里用普通语言说明即可,例如“封面和结束页原样保留,中间页由你选择”或“只参考视觉语言”;明确文字优先于 AI 判断。
+
### 现有模板一览
模板按三种 kind 分目录,并分别由发现索引维护:
- [`brands_index.json`](../../skills/ppt-master/templates/brands/brands_index.json) — 仅身份工作区:color / typography / logo / voice / icon style,不含 SVG 页面 roster
- [`layouts_index.json`](../../skills/ppt-master/templates/layouts/layouts_index.json) — 仅结构工作区:canvas / 页面语法 / page types / SVG roster,身份系统下游再选
-- [`decks_index.json`](../../skills/ppt-master/templates/decks/decks_index.json) — 可重复演示应用,包含一体化身份、结构与内容复用规则
+- [`decks_index.json`](../../skills/ppt-master/templates/decks/decks_index.json) — 可重复演示应用,包含一体化身份、结构与原型事实描述
直接问“有哪些模板可以用?”即可得到带工作区路径的可读清单。索引是当前安装内容的真值,三类 README 负责定义合同。完整数据模型与三类的合成 / 冲突解决规则见 [`templates-architecture.md`](./templates-architecture.md)。
### 自由设计 vs 模板
-自由设计不是“没有结构”或“没有风格”——Strategist 仍会为这份 deck 规划叙事、层级与视觉系统,但生成页面使用 `pptx_structure.mode: flat`,所有可见对象都保留在 Slide 本地。仅使用 Brand 工作区时同样保持 `flat`,只是由 Brand 提供身份约束。Layout 与 Deck 工作区提供可复用 Master / Layout / slot 合同:确认使用 `mirror` 或 `layout` 时通过 `pptx_structure.mode: structured` 消费;确认使用 `style` 时则有意舍弃原生结构并生成 `flat`。
+自由设计不是“没有结构”或“没有风格”——Strategist 仍会为这份 deck 规划叙事、层级与视觉系统,但生成页面使用 `pptx_structure.mode: flat`,所有可见对象都保留在 Slide 本地。仅使用 Brand 工作区时同样保持 `flat`,只是由 Brand 提供身份约束。Layout 与 Deck 工作区提供可复用 Master / Layout / slot 合同;Strategist 会读取真实原型和当前内容,自动判断是复用结构,还是只参考视觉语言。
> 经验:需要锁定身份系统时用 Brand;需要复用品牌中立结构、但让用途保持开放时用 Layout;需要把品牌化结构或可重复沟通场景作为一份契约复用时用 Deck;希望版式从当前内容出发重新生长时走自由设计。
@@ -155,15 +157,15 @@ Strategist 会把方向拆成两个彼此独立的选择:
你可以直接在对话中输入文字或粘贴要求,也可以提供 Markdown/TXT、DOCX/PDF/HTML/URL、网站、图片/截图、logo/icon/字体资产、PPTX/SVG,或这些材料的任意组合。工作流会分析每个适用通道,保留来源,并在强制简报中暴露冲突,而不是静默选择某一个来源。凡是你本人明确写出的值,无论来自对话、粘贴文字还是你编写的简报文件,都属于决策;文件载体本身不会把它变成事实。事实必须来自可独立追溯的外部权威,或可由机器直接观察的源文件/包元数据。视觉估算与模糊文字的解释在确认前都只是建议。
-**当现有演示文稿的原生结构很重要时,请直接提供原始 `.pptx` 文件。** 导入器会读取 OOXML,把包内实际存在且受支持的 Master、Layout、placeholder、主题、原生形状与可复用素材事实提取成分层分析参考。`standard` / `fidelity` 把它们当视觉参考,创作新的 SVG roster 与 Master/Layout/slot 系统;mirror 则把这些已验证的来源事实物化到新工作区,不补造缺失拓扑或设计意图。原 PPTX 始终是不可变的分析证据,不进入新模板包。
+**当现有演示文稿的原生结构很重要时,请直接提供原始 `.pptx` 文件。** 导入器会读取 OOXML,把包内实际存在且受支持的 Master、Layout、placeholder、主题、原生形状与可复用素材事实提取成分层分析参考。你只需用普通语言说明想要的结果,例如“原样保留”“提取成可复用母版和版式”或“保留视觉语言但重做结构”;AI 会据此选择兼容的内部实现。原 PPTX 始终是不可变的分析证据,不进入新模板包。
也可以基于品牌指南从零设计:提供 logo、主色 HEX、字体、调性描述、几张氛围参考图,AI 会现场设计页面骨架。适合品牌方还没有成型 PPT、只有 VI 手册的场景。
-> **证据边界:** 图片、截图、文字、文档、网站和零散资产都可以独立驱动 `standard`。`fidelity` 需要 PPTX/SVG 页面证据;`mirror` 需要原始 PPTX 或完整的当前结构化 SVG 合同。补充来源可以解释 mirror 证据,但不能补造或改变其原生拓扑。
+> **证据边界:** 图片、截图、文字、文档、网站和零散资产可以驱动重新创作;更广的来源对齐需要 PPTX/SVG 页面证据;字面保留原生结构需要原始 PPTX 或完整的当前结构化 SVG 合同。补充来源可以解释保留意图,但不能补造或改变原生拓扑。
### 第二步:模板简报(强制确认环节)
-工作流不会偷偷推断——它会在动手前向你列出以下条目,等你确认或补全:
+工作流会在动手前写出一份简洁的自然语言方案,等待你修正或确认;不会要求你选择模板模式、保真枚举或页面/内容政策。
| 字段 | 说明 |
|------|------|
@@ -172,16 +174,10 @@ Strategist 会把方向拆成两个彼此独立的选择:
| **已选子工作流** | Create Brand / Create Layout / Create Deck,由入口分派后固定 |
| **模板 ID** | 模板的可移植身份;在 `library` 下同时也是目录名 / 索引键。优先 ASCII slug,如 `acme_consulting`;中文品牌名也行,但要文件系统安全 |
| **显示名称** | 文档中的人类可读名 |
-| **类别** | `brand` / `general` / `scenario` / `government` / `special` 五选一 |
-| **适用场景** | 年报 / 咨询 / 答辩 / 政府汇报…… |
-| **调性概要** | 一句话,如"现代克制、数据驱动" |
-| **主题模式** | 仅 Create Layout/Create Deck:浅色 / 深色 / 渐变…… |
-| **画布格式** | 仅 Create Layout/Create Deck;默认 `ppt169`(16:9),其他格式需提前指定 |
-| **复刻模式** | 仅 Create Layout/Create Deck:`standard`(默认精简、由确认简报驱动;可包含少量明确要求的差异化变体)/ `fidelity`(根据来源证据覆盖更广的有用语义家族)/ `mirror`(每张源页一个物化原型)。`standard` / `fidelity` 创作新 SVG 语义;mirror 只保留来源包内已经存在且验证通过的事实。只有来源合同本身已经品牌中立且应用中立时,Layout 才能使用 mirror。 |
-| **原生结构事实** | 仅 Create Layout/Create Deck:简报会列出源 Master/Layout 数量、父子关系、placeholder 身份和多母版情况。`standard` / `fidelity` 只把它们当参考;mirror 把受支持事实一对一映射进当前 `structured` 合同。 |
-| **保真级别** | 仅 Create Layout/Create Deck;`standard` / `fidelity` 有源时必填,选择 `literal` 或 `adapted`。**`mirror` 模式不询问**——它保留受支持的来源视觉。 |
-| **关键词** | 3–5 个标签,用于索引检索 |
-| 主题色 / 设计风格 / 素材清单 | 可选,可让 AI 从源里自动提取 |
+| **模板语境** | AI 提议一个类别、适用场景、显示名称、调性概要和索引关键词;你可直接修改文字 |
+| **画布与视觉方向** | 仅 Create Layout/Create Deck:建议画布、明暗关系、身份和从来源观察到的视觉规则 |
+| **创建方案** | AI 将保留、重建、简化或提取什么;原型范围多大;如何处理原生结构——全部用普通语言说明 |
+| **来源事实与素材** | 可观察的 Master/Layout 事实、受支持原生能力、采用/排除的素材及重要限制 |
确认后,工作流会回显一份完整简报并写入标记 `[TEMPLATE_BRIEF_CONFIRMED]`,从这一刻起后续步骤才会启动。**这是一个硬门——简报没确认,不会开始生成**。
@@ -189,21 +185,15 @@ Strategist 会把方向拆成两个彼此独立的选择:
> 为什么这么严?无论模板进入全局库,还是只服务当前项目,它都是结构契约。先确认归属和几何,可避免半成品或资产落错目录。
-### 第三步:Create Layout/Create Deck 选择 standard、fidelity 还是 mirror?
+### 第三步:AI 推导内部实现
-这是派生结构型模板里最容易混淆的决策。Create Brand 不执行这一步,因为 identity-only 工作没有 SVG roster 或原生结构。
+你不需要选择创建模式。AI 会把已确认的自然语言方案转换成一个内部策略,供确定性工具执行:
-| | **standard** | **fidelity** | **mirror** |
-|---|---|---|---|
-| 输出页数 | 通常 4–6 页:封面/章节/结尾、可选目录,以及一个或少量简报明确要求的内容 Layout | 覆盖来源证据中更广的有用语义家族——数量由来源决定 | 每张源页一个物化原型(1:1 页面集合) |
-| 抽象程度 | 高 —— 干净可复用骨架 | 中 —— 语义家族重新设计 | 拓扑层面不抽象,只做 structured 合同要求的机械归一化 |
-| 作者占位符 | 是(`{{TITLE}}`、`{{CONTENT_AREA}}` 等) | 是 | 可保留原文字,但导入识别出的原生内容槽仍带语义 metadata |
-| 适合场景 | 你需要“调性 + 精简骨架”,也可能包含少量简报明确要求的结构,未来用于生成全新 deck | 源 PPTX 本身就是高度定制的版式库,需要更广的来源驱动覆盖 | 别人的精装 deck 直接好用、想把每页都当参考页 |
-| 典型例子 | 给品牌做基础模板 | 复刻一套政府汇报的 20 种章节版式 | 把 50 张源构图都保留为视觉忠实的模板原型 |
-| 来源要求 | 无 | PPTX 或 SVG 视觉参考 | PPTX,或带完整显式结构合同的 SVG |
-| 装饰复杂度 | 通常较简洁 | 需要保留精灵图裁剪等结构 | 保留原几何,并补齐显式层级归属 |
+- 需要精炼时,创建紧凑的可复用系统;
+- 来源本身包含有价值的多种版式时,创建更广的来源对齐原型;
+- 明确要求原样保留、且来源结构完整受支持时,进行字面物化。
-`mirror` 不能一边保留身份或应用规则,一边又产出品牌中立、应用中立的 Layout。若要移除这些规则,应选 `standard` / `fidelity` 重新创作 Layout;若要原样保留,应创建 Deck mirror。
+frontmatter 仍会记录 `replication_mode: standard|fidelity|mirror` 以兼容工具并保留审计信息;它是实现记录,不是用户选项。品牌中立的 Layout 不能同时字面保留品牌/应用事实,AI 会按目标重新创作 Layout,或把这些事实留在 Deck 中。
**关于精灵图**:PPTX 导出的素材常常是**一张大图 + 多页通过 viewBox 裁剪不同区域**。`fidelity` 和 `mirror` 模式下必须保留这层嵌套 `<svg viewBox=...>` 包装,不能扁平化为单张 `<image>`——否则裁剪信息丢失,画面会错位。工作流会自动校验这一点。
@@ -223,7 +213,7 @@ python3 skills/ppt-master/scripts/mirror_template_materialize.py \
**Mirror 图谱边界**:mirror 保留完整且受支持的来源 Master/Layout 图谱。它为每张来源 Slide 输出一个完整原型,并为未被任何来源 Slide 使用的 Layout 额外输出一个定义专用的 `layout_<layout_key>.svg`。后者通过独立 Layout roster 注册进 PowerPoint,不会变成发布页面;其父 Master 也随之保留。预检只在必要来源事实或受支持几何缺失时停止,不会仅因 Layout 未使用而停止。
-**按 mirror 创建的工作区怎么消费**:从来源到工作区的 `replication_mode: mirror` 是能力,不是项目选择。开放式沟通契约确认后,Stage 2 先把 Deck 保存的应用契约与当前受众、结果和内容角色对照;只在“重复制作已知固定成果、且新内容适配现有页面角色与文字拓扑”时推荐 `mirror`。结构兼容、但内容需要重排时用 `layout`;只需身份语言或论证必须换结构时用 `style`。确认 `mirror` 后,Strategist 为每个项目页选择一张原型,Executor 复制完整 SVG,只修改允许变更的可见文字,同时保留装饰、精灵图裁剪、几何坐标和规范化结构声明;这仍不要求沿用来源页数或页序。Mirror 保留受支持的画面外观,不承诺保留来源 PPTX 的分组编辑层级。
+**按 mirror 创建的工作区怎么消费**:从来源到工作区的 `replication_mode: mirror` 是一种能力,不是项目选择。Strategist 会读取真实原型、当前内容和用户明确要求,自动决定选哪些页、哪些重复/跳过/重排,以及采用字面、结构还是仅视觉参考。字面复用时,Executor 复制完整 SVG,只修改允许变更的可见文字,同时保留装饰、精灵图裁剪、几何坐标和规范化结构声明;仍不要求沿用来源页数或页序。
### 第四步:验证、预览导出、注册与发现
@@ -236,10 +226,7 @@ python3 skills/ppt-master/scripts/mirror_template_materialize.py \
全局注册让模板**可被发现**——下次有人问“有哪些模板可用?”时,AI 会从索引里把它列出来。两种范围的用法相同:按 [Generate PPTX Step 3](../../skills/ppt-master/workflows/generate-pptx.md#step-3-template-option) 的规则,在 Step 3 运行前给出工作区根目录,例如 `用这个模板:skills/ppt-master/templates/layouts/<your_template_id>/` 或 `用这个模板:projects/<name>/`。项目工作区也可以迁移或被其他工作区复用,因为核心结构完全一致;只有放进全局库并需要被发现时才执行注册。
-选择 Deck/Layout 模板后,Strategist 确认阶段会进一步询问模板的使用方式:
-
-- **适应性使用(adaptive)**——每页都选择一张模板 SVG;没有合适 Layout 时沿用同一 Master 创建新的显式 Layout
-- **严格套用(strict)**——每页都选择一张模板 SVG,并保持其 Master/Layout/Placeholder 契约不变
+选择 Deck/Layout 模板后,Strategist 会自动生成页面/原型应用计划:可以使用全套或子集,重复或重排原型,并按内容需要重组。`strict` / `adaptive` 只作为内部导出值,不再出现在确认选项中。
### 如何确认母版与版式真的生效
diff --git a/skills/ppt-master/references/executor-structured.md b/skills/ppt-master/references/executor-structured.md
index d3be6006..fb745718 100644
--- a/skills/ppt-master/references/executor-structured.md
+++ b/skills/ppt-master/references/executor-structured.md
@@ -48,7 +48,7 @@ Resolve the per-page template SVG from `page_context.template.prototype`; the ow
### 1.1 Mirror reuse — literal page replacement
-When `spec_lock.md` confirms `template_reuse_scope: mirror`, Executor switches to a literal replacement path. The workspace capability `replication_mode: mirror` is a prerequisite, not the trigger by itself:
+When `spec_lock.md` records the AI-derived `template_reuse_scope: mirror`, Executor switches to a literal replacement path. The workspace capability `replication_mode: mirror` is a prerequisite, not the trigger by itself:
1. **Per-page reference selection** — Strategist selects one mirror page per project page via `spec_lock.md page_layouts` (e.g., `P04: 015_content`). The basename is the mirror filename without extension; Strategist made this choice by reading `design_spec.md §V Page Roster` descriptions, not by guessing.
2. **Copy, don't fill** — open the referenced full mirror SVG immediately before authoring the page. Copy it as the starting point, then edit slide-specific text in place. Preserve every non-text element and every `data-pptx-*` structure attribute verbatim.
@@ -58,7 +58,7 @@ When `spec_lock.md` confirms `template_reuse_scope: mirror`, Executor switches t
6. **Visible text editing** — mirror SVGs may keep literal source text rather than `{{...}}` authoring markers. Edit values in place while retaining imported semantic `data-pptx-placeholder` identity and exact text topology.
7. **Output filename** — follow the standard project SVG naming convention (`<NN>_<page_name>.svg` where `<NN>` matches the project page index, not the mirror source index). The mirror filename is the *reference*, not the *output*.
-**Detecting mirror mode**: read `page_context.template.reuse_scope` from the current page-context bundle. `replication_mode: mirror` in the installed template only determines whether that confirmed scope is legal; it must never force mirror behavior when the confirmed scope is `layout` or `style`.
+**Detecting mirror mode**: read `page_context.template.reuse_scope` from the current page-context bundle. `replication_mode: mirror` in the installed template only determines whether that derived scope is legal; it must never force mirror behavior when the lock records `layout` or `style`.
**Mirror + chart pages**: chart structures inside a mirror SVG are already drawn (axis, series, labels). Treat them as visual references — replace the data labels and series text content to match the project's chart spec, but do not redraw the chart from a `templates/charts/<name>.svg` baseline. A mirror template's `page_charts` entries are normally absent for this reason.
@@ -78,7 +78,7 @@ Before generating each page, output which template is used:
### 1.2 PowerPoint Master / Layout Mapping
-This section applies only when a deck/layout template is confirmed with `template_reuse_scope: mirror|layout`. `page_layouts` selects the input SVG prototype, `pptx_masters` / `pptx_layouts` declare unique reusable output definitions, and `page_pptx_layouts` assigns every generated page before the first page is drawn. `template_reuse_scope: style`, free-design, and brand-only routes use `pptx_structure.mode: flat`, omit all four sections, skip the rest of §1.2, and keep every SVG object Slide-local.
+This section applies only when a deck/layout template's AI-derived lock records `template_reuse_scope: mirror|layout`. `page_layouts` selects the input SVG prototype, `pptx_masters` / `pptx_layouts` declare unique reusable output definitions, and `page_pptx_layouts` assigns every generated page before the first page is drawn. `template_reuse_scope: style`, free-design, and brand-only routes use `pptx_structure.mode: flat`, omit all four sections, skip the rest of §1.2, and keep every SVG object Slide-local.
**Hard rule — reuse-scope route**: `template_reuse_scope: mirror|layout` requires `pptx_structure.mode: structured`. `template_reuse_scope: style` requires `mode: flat` even though a template supplied its visual vocabulary. Missing mode or legacy values (`baseline`, `template`, `preserve`), `layout_strategy`, Layout-kind fields, partial mappings, and old direct placeholders stop generation. Create a new template workspace through [`create-template`](../workflows/create-template.md); do not upgrade the active SVG project in place.
diff --git a/skills/ppt-master/references/pptx-structure-interface.md b/skills/ppt-master/references/pptx-structure-interface.md
index 6bc44dd5..73a89c77 100644
--- a/skills/ppt-master/references/pptx-structure-interface.md
+++ b/skills/ppt-master/references/pptx-structure-interface.md
@@ -8,7 +8,7 @@ Conditional interface for PowerPoint Master, Layout, fixed-layer, and placeholde
## 1. PPTX Structure Routing
-Every new SVG project declares one deterministic route. Free-design, brand-only, and `template_reuse_scope: style` projects use `pptx_structure.mode: flat`, omit `pptx_masters` / `pptx_layouts` / `page_pptx_layouts` / `page_layouts`, and author no Master/Layout/layer/placeholder metadata. Export keeps all represented content Slide-local while materializing one clean project-owned Master plus one Blank Layout from the current color/typography lock; stock content placeholders and unused built-in Layouts are removed, while the standard date/footer/slide-number capability hooks remain. Deck/layout template projects confirmed with `template_reuse_scope: mirror|layout` use `mode: structured`; `standard` / `fidelity` templates use their authored contract, while mirror templates use the validated source identities and parentage declared by the newly materialized workspace.
+Every new SVG project declares one deterministic route. Free-design, brand-only, and `template_reuse_scope: style` projects use `pptx_structure.mode: flat`, omit `pptx_masters` / `pptx_layouts` / `page_pptx_layouts` / `page_layouts`, and author no Master/Layout/layer/placeholder metadata. Export keeps all represented content Slide-local while materializing one clean project-owned Master plus one Blank Layout from the current color/typography lock; stock content placeholders and unused built-in Layouts are removed, while the standard date/footer/slide-number capability hooks remain. Deck/layout template projects whose AI-derived lock records `template_reuse_scope: mirror|layout` use `mode: structured`; `standard` / `fidelity` templates use their authored contract, while mirror templates use the validated source identities and parentage declared by the newly materialized workspace.
**Hard rule — no structure inference**: Flat export performs no promotion or deduplication; every object stays Slide-local. Structured template export compiles only declared root identities, atomic fixed layers, and slot groups—it does not assign Layout families, cluster pages, infer placeholders, repair missing metadata, or migrate legacy contracts. Create a new current workspace through [`create-template`](../workflows/create-template.md) before generating structured pages.
diff --git a/skills/ppt-master/references/semantic-svg.md b/skills/ppt-master/references/semantic-svg.md
index 28b01d8f..f23c7a96 100644
--- a/skills/ppt-master/references/semantic-svg.md
+++ b/skills/ppt-master/references/semantic-svg.md
@@ -16,7 +16,7 @@ PPT Master uses rendering-neutral compiler hints only where ordinary SVG cannot
The completed SVG remains the full visible page. Removing the metadata must not change browser rendering. Do not copy visible text, geometry, style, or asset values into metadata.
-**Hard rule — route boundary**: Free-design, brand-only, and `template_reuse_scope: style` pages use `pptx_structure.mode: flat`, declare one canonical root `data-pptx-page-role`, and omit every Master/Layout/layer/placeholder marker in this document. Only deck/layout template pages confirmed with `template_reuse_scope: mirror|layout` declare their final Master and Layout before drawing begins and omit `data-pptx-page-role`; the structured exporter compiles that contract and never selects, clusters, distills, or visually infers it.
+**Hard rule — route boundary**: Free-design, brand-only, and `template_reuse_scope: style` pages use `pptx_structure.mode: flat`, declare one canonical root `data-pptx-page-role`, and omit every Master/Layout/layer/placeholder marker in this document. Only deck/layout template pages whose AI-derived lock records `template_reuse_scope: mirror|layout` declare their final Master and Layout before drawing begins and omit `data-pptx-page-role`; the structured exporter compiles that contract and never selects, clusters, distills, or visually infers it.
**Hard rule — specialized metadata wins**: Use Master/Layout/placeholder metadata for native structure, `data-pptx-replace-with` for optional PowerPoint-native Chart/Table replacement, and the imported/authored shape metadata defined in [`shared-standards-core.md`](./shared-standards-core.md) §§1.4–1.5. Do not duplicate those facts with `data-pptx-role`.
diff --git a/skills/ppt-master/references/strategist-template.md b/skills/ppt-master/references/strategist-template.md
index f6c773c3..8148b385 100644
--- a/skills/ppt-master/references/strategist-template.md
+++ b/skills/ppt-master/references/strategist-template.md
@@ -8,46 +8,56 @@ Conditional extension for applying an installed Brand/Layout/Deck workspace to S
---
-## 1. Reuse Scope and Adherence
+## 1. AI-Authored Template Application Plan
**Template vs preset**: A style mention and a template directory are different inputs. Bare names and style words map to a visual-style preset; only the installed workspace activates the rules below. Its fused `<project_path>/templates/design_spec.md` is the template-design source.
**Legacy template boundary**: A template containing `native_structure.json`, `source_template.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. Do not mutate the input in place.
-**Template reuse confirmation**: Surface `template_reuse_scope` only for an installed `kind: deck` or `kind: layout` workspace. Omit it for brand-only workspaces.
+**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.
-| Reuse scope | Planning and export behavior |
-|---|---|
-| `mirror` | Mirror workspaces only. Start from the full selected page, preserve literal visuals and text-node topology, and replace only allowed visible text values. |
-| `layout` | Reuse the template Master/Layout system and input prototypes, but allow project-controlled reflow/re-skinning and explicit adaptive Layouts. |
-| `style` | Reuse only color, typography, decoration language, and rhythm. Plan `pptx_structure.mode: flat` with no template structure mappings. |
+Immediately before authoring the Stage-2 solution, inspect:
+
+- the installed `design_spec.md`, actual Page Roster, and relevant SVG prototypes;
+- the 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.
+
+Then author one plan that decides all of the following without presenting an option menu:
+
+- whether the full prototype set, a relevant subset, or only the design language is useful;
+- which prototype each generated page starts from, which template pages are skipped, and which prototypes are repeated or reordered;
+- whether content is inserted directly, reorganized inside the existing structure, or rebuilt while retaining only visual language;
+- which visible elements must remain literal because the user said so, and which may change to serve the current content.
-**Deterministic language mapping**: “不要严格复用”, “只参考风格”, “参考这个风格”, and “不必照搬版式” recommend `style` unless the user explicitly asks to retain the layout system, in which case recommend `layout`. “原样复刻”, “替换内容”, and “保持模板页面外观” recommend `mirror` only when `replication_mode: mirror` is available. A bare workspace path with no stronger language defaults to `layout`.
+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.
-For `mirror` / `layout`, surface `template_adherence`. Hide it for `style`.
+Record the resulting exporter plan internally:
-| Value | Planning and export behavior |
+| Internal value | When the authored plan requires it |
|---|---|
-| `strict` | Map every page to one template SVG. Keep its explicit Master/Layout/slot contract and output Layout key unchanged. |
-| `adaptive` | Map every page to the closest template SVG. Keep the template Master contract, but allow a new explicit Layout key when content requires a structural adaptation. |
+| `template_reuse_scope: mirror` | The workspace has `replication_mode: mirror`, the plan calls for literal page reuse, and each page changes only allowed visible text values while preserving visual and text-node topology. |
+| `template_reuse_scope: layout` | The plan reuses the template Master/Layout system and prototypes while allowing current-project content and appearance decisions. |
+| `template_reuse_scope: style` | The plan uses only color, typography, decoration language, or rhythm and intentionally creates flat free-design pages. |
+| `template_adherence: strict` | Every structured page fits an existing prototype contract without changing its Layout identity or slot topology. Mandatory for `template_reuse_scope: mirror`. |
+| `template_adherence: adaptive` | Structured reuse remains useful, but at least one page needs a new explicit Layout under the selected Master. |
-**Default — layout + adaptive**: For a workspace path without stronger language, recommend `layout` and `adaptive`. Preselect `strict` only when the user explicitly asks to keep the selected Layout contract unchanged. Record the confirmed scope in `design_spec.md §I` and `spec_lock.md pptx_structure`; record adherence only for `mirror` / `layout`.
+Write the derived values to `design_spec.md §I` and `spec_lock.md pptx_structure`; omit `template_adherence` for `style`. Do not put these values in `recommendations.json`, the Confirm UI, or `result.json`. Stage 2 may summarize the selected page/prototype plan as part of the complete deck solution, but it must not reopen template use as a separate user control.
---
## 2. Scenario Fit and Inherited Design
-**Mandatory — consume the stored contract at the decision point**: Immediately before recommending reuse for an installed `kind: deck`, re-read `<project_path>/templates/design_spec.md`. Compare its five `## I. Template Overview` application-contract rows with the confirmed audience, intent, outcome, delivery context, artifact afterlife, and source obligations. Compare every `## V. Page Roster` content-policy value with the required narrative/page roles, including required / optional / repeatable status and fixed / replaceable / example-only content. Treat the contract as applicability evidence, never as the current project's truth; do not copy it into blank Stage-1 fields or infer fields it does not declare. For `kind: layout`, no application contract exists: compare only the roster's structural roles, slots, and capacity.
+**Mandatory — inspect the stored resource at the decision point**: For an installed `kind: deck`, re-read `<project_path>/templates/design_spec.md` and compare its descriptive Template Overview with the confirmed audience, intent, outcome, delivery context, artifact afterlife, and source obligations. Compare the actual Page Roster and SVG prototypes with required narrative roles, content shapes, slots, and capacity. The template describes what exists; it never overrides the current project and it does not own required/optional/repeatable or fixed/replaceable/example-only policy. For `kind: layout`, compare only structural roles, slots, and capacity.
-| Scope | Appropriate when |
+| Internal scope | Appropriate when |
|---|---|
| `mirror` | The artifact repeats a known form; literal appearance and text topology are requirements; new content fits existing roles and slots. |
| `layout` | The structural system and brand continue, but the communication outcome requires reflow, new emphasis, or an adaptive Layout. |
| `style` | Only visual identity is reusable, or the outcome requires a different sequence, density, or composition system. |
-When the communication contract conflicts with the workspace, surface the mismatch. Template capability constrains what is legal; scenario fit decides what is useful.
+When the communication contract conflicts with the workspace, choose and state the best-fit application plan in the complete Stage-2 solution. Surface the mismatch only when it materially limits the result; do not respond with a mode questionnaire. Template capability constrains what is legal; scenario fit decides what is useful.
-> Note: `content_divergence` controls source reorganization; `template_reuse_scope` controls the reused layer; `template_adherence` controls strictness inside `mirror` / `layout`.
+> Internal note: `content_divergence` controls source reorganization; the AI-derived `template_reuse_scope` records the reused layer; `template_adherence` records whether a structured plan keeps or extends existing Layout identities.
**Template design precedence**: User overrides win. Otherwise lock declared colors and title/body font stacks from the fused template `design_spec.md` directly; skip generic color/font candidates and do not adjust template values to fit an industry default. Keep the workspace's declared icon and image constraints when producing those conditional plans.
@@ -55,7 +65,7 @@ When the communication contract conflicts with the workspace, surface the mismat
## 3. Structured Lock Planning
-For `mirror` / `layout`, write `pptx_structure.mode: structured` plus `template_adherence: strict|adaptive`. Do not write legacy `baseline`, `template`, `preserve`, `layout_strategy`, or Layout-kind rows.
+For `mirror` / `layout`, write `pptx_structure.mode: structured` plus `template_adherence: strict|adaptive`; mirror always writes `strict`. Do not write legacy `baseline`, `template`, `preserve`, `layout_strategy`, or Layout-kind rows.
- **Master roster**: Write one `pptx_masters` row per Master as `<master_key>: <picker name>` and copy the workspace's prototype roster. Keys use 1–64 ASCII letters, digits, dots, underscores, or hyphens, start with a letter/digit, and contain no spaces; human-readable spaces belong only in the picker name. Master visuals are root-level atomic elements and may never be `<g>`.
- **Reusable Layout roster**: Write every unique Layout once as `<layout_key>: <master_key> | <PowerPoint layout name> | <prototype source>`. Copy installed `template:<basename>` sources, including currently unused Layouts. A new adaptive Layout uses its first generated `P<NN>` as source. Reuse a key only when fixed atoms and slot ids/types/indices/bounds/binding modes are identical. Name authored keys after composition, never page topic. A Layout may intentionally have zero slots; do not manufacture an empty `utility` kind or full-page fake slot.
diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.md
index bc9a43bb..5622758e 100644
--- a/skills/ppt-master/references/strategist.md
+++ b/skills/ppt-master/references/strategist.md
@@ -29,10 +29,10 @@ As a top-tier AI presentation strategist, receive source documents, perform cont
| Stage | Items | Role |
|---|---|---|
| **1 — communication contract** | `c` audience · open-ended communication intent · audience outcome · core message / delivery context / artifact afterlife · `content_divergence` (all prose fields may be blank) · `a` canvas | confirmed first |
-| **2 — complete deck solution** (authored once from the user's *actual* Stage 1) | reading mode (`delivery_purpose`, PPT only) · `d` mode + visual style · `b` page count · template reuse / adherence · `e` color · `f` icon · `g` typography · `h` image source + generated-image rendering | derived from the confirmed contract |
+| **2 — complete deck solution** (authored once from the user's *actual* Stage 1) | reading mode (`delivery_purpose`, PPT only) · `d` mode + visual style · `b` page count · `e` color · `f` icon · `g` typography · `h` image source + generated-image rendering | derived from the confirmed contract; when a template is installed, AI also authors its page/prototype application plan internally |
| **3 — resources / production** (authored once from the user's *actual* Stage 1 + Stage 2) | formula policy · conditional AI-image acquisition path · generation mode · refine-spec toggle | derived from the confirmed solution |
-Do not force communication intent into one catalog label. A deck may report progress, expose risk, and request a decision in the same artifact; Stage 1 records that relationship in prose. Its editable prose fields are recommendation drafts, not required inputs: confirmation accepts the current text exactly, including blanks, and a cleared field must not be repopulated later. Stage 2 then confirms one complete solution: narrative spine, reading density, page budget, template strategy, visual system, and image direction. Present ≥3 coordinated design directions (safe / shifted / bold) so color, type, icons, and generated-image rendering begin coherent; the user may still override each component. Generated images inherit the selected deck colors directly—there is no second image-palette confirmation. Stage 3 asks only how to produce the locked solution. **Page count is derived, not an anchor**—it follows content volume × desired audience outcome × reading mode. Author each stage once: same-stage edits update only visible browser state through documented deterministic dependencies and never trigger a new AI / backend recommendation. The launch / derive / wait mechanics live in [`generate-pptx.md`](../workflows/generate-pptx.md) Step 4; the item specs below keep their `a`–`h` letters.
+Do not force communication intent into one catalog label. A deck may report progress, expose risk, and request a decision in the same artifact; Stage 1 records that relationship in prose. Its editable prose fields are recommendation drafts, not required inputs: confirmation accepts the current text exactly, including blanks, and a cleared field must not be repopulated later. Stage 2 then confirms one complete solution: narrative spine, reading density, page budget, visual system, and image direction. When a template workspace is installed, Strategist also inspects its real prototypes and current content and authors the application plan automatically; template modes are not confirmation fields. Present ≥3 coordinated design directions (safe / shifted / bold) so color, type, icons, and generated-image rendering begin coherent; the user may still override each component. Generated images inherit the selected deck colors directly—there is no second image-palette confirmation. Stage 3 asks only how to produce the locked solution. **Page count is derived, not an anchor**—it follows content volume × desired audience outcome × reading mode. Author each stage once: same-stage edits update only visible browser state through documented deterministic dependencies and never trigger a new AI / backend recommendation. The launch / derive / wait mechanics live in [`generate-pptx.md`](../workflows/generate-pptx.md) Step 4; the item specs below keep their `a`–`h` letters.
> **Execution discipline**: This is the last BLOCKING checkpoint in the pipeline. After confirmation, complete the Design Spec and proceed to image generation / SVG / post-processing without further pauses.
>
@@ -131,7 +131,7 @@ The deck's **visual aesthetic** — shape language, decoration density, whitespa
Write the locked value to `spec_lock.md` `- visual_style:` and the rationale to `design_spec.md`. Executor loads only that one visual-style file.
-**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 reuse/adherence, inherited design precedence, and structured-lock planning. Bare names, style words, and free-design projects do not trigger it.
+**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 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.
**Downstream effect**: e / f / g / h realize the locked mode + visual style. Example: `showcase` + `dark-tech` → e applies one luminous accent on a dark field; g pairs a clean sans with mono; f minimal glow icons; h the `digital-dashboard` rendering.
diff --git a/skills/ppt-master/references/template-designer.md b/skills/ppt-master/references/template-designer.md
index 361d7c0c..16730d13 100644
--- a/skills/ppt-master/references/template-designer.md
+++ b/skills/ppt-master/references/template-designer.md
@@ -4,7 +4,7 @@
## Core Mission
-Generate reusable structured page templates inside the workspace selected by Create Template's Create Layout or Create Deck child workflow, and write a concise `design_spec.md` that captures the source-derived rules that make the template reusable. For Deck, include the recurring application contract; for Layout, keep structure brand-neutral and application-neutral.
+Generate reusable structured page templates inside the workspace selected by Create Template's Create Layout or Create Deck child workflow, and write a concise `design_spec.md` that captures the source-derived rules that make the template reusable. For Deck, include descriptive recurring-application context; for Layout, keep structure brand-neutral and application-neutral.
> This is a standalone role: only triggered by the Create Layout or Create Deck child workflow under `/create-template`. Create Brand never invokes it. Library and project outputs use one workspace shape; this is not the template selection step in the main PPT generation pipeline.
@@ -13,7 +13,7 @@ Generate reusable structured page templates inside the workspace selected by Cre
- **Trigger**: `/create-template` → Create Layout or Create Deck child workflow
- **Workspace root**: `library` (default) → `skills/ppt-master/templates/<kind_dir>/<template_name>/`; `project` → the confirmed `<target_project>/`
- **Template source**: `<template_workspace>/templates/` in both scopes
-- **Input**: finalized template brief (output scope, target project when project-scoped, template ID, display name, kind, structural use cases or Deck application contract, tone, theme mode, canvas format, optional reference assets, accepted basic template norms)
+- **Input**: finalized template brief (output scope, target project when project-scoped, template ID, display name, kind, structural use cases or Deck application context, tone, theme mode, canvas format, optional reference assets, accepted basic template norms)
**Hard rule — scope is execution metadata**: Use `output_scope` and `target_project` to route files, but do not write either field into portable `design_spec.md` frontmatter. Do not create a new PPTX structure mode; deck/layout output declares `native_structure_mode: structured`.
@@ -40,7 +40,7 @@ PPTX import interpretation:
- Charts, SmartArt, diagrams, and OLE objects may appear as typed placeholders in layered SVGs. In flat SVGs they may show preview images. Treat them as source intent markers, not reusable decorative assets.
- The asset filenames referenced by SVGs are governed by the manifest asset map. Prefer those references over inventing duplicate asset names.
-Input priority for PPTX-backed template creation depends on replication mode:
+Input priority for PPTX-backed template creation depends on the AI-derived internal strategy recorded as `replication_mode`:
| Mode | Authoritative inputs | Model-facing inputs |
|---|---|---|
@@ -55,7 +55,7 @@ Use the compact facts in `manifest.json` for orientation. Open screenshots or th
Layout, and Placeholder as PowerPoint implementation objects, not template
kinds. Layout owns topology, placement, semantic text roles, and spatial text
behavior. Deck identity owns paint, typeface identity, and fixed identity
-assets; its application contract owns recurring content semantics. Under
+assets; its application context describes the recurring presentation family. Under
downstream `layout` scope, resolve final placeholder formatting from the Layout
roles plus the confirmed identity, reading mode, and type scale; downstream
`mirror` scope preserves literal source formatting and text topology. Compile
@@ -95,7 +95,7 @@ Never silently drop or merge an identity, and never invent a carrier page.
**Hard rule — no duplicate authored Layout contracts**: In `standard` / `fidelity`, distinct output Layout keys must differ in fixed Layout atoms or slot topology/type/index/bounds/binding. Topic, sample wording, or Slide-local content alone never justifies another authored key. Mirror keeps source Layout identities even when two source contracts are visibly equivalent.
-**Downstream boundary**: Stage 1 independently confirms the current communication contract. Stage 2 derivation then compares it with a Deck's stored application contract and selects `mirror`, `layout`, or `style` and, where applicable, `strict` or `adaptive`. Structured scopes export through `pptx_structure.mode: structured`. Strict keeps the referenced Layout contract; adaptive may create a new Layout identity while retaining the template Master. Template_Designer does not preselect that project-level choice.
+**Downstream boundary**: Stage 1 independently confirms the current communication contract. Strategist then inspects the installed prototypes, the Deck's descriptive application context, and the current content to author one application plan. It records `mirror`, `layout`, or `style` and, where applicable, `strict` or `adaptive` only as internal exporter values. Explicit user language overrides AI judgment, but the confirmation UI never asks the user to choose these implementation labels. Template_Designer does not preselect that project-level plan.
For `mirror`, `design_spec.md §V` must be followed by a `Source Preservation Map` that records each source slide's Master/Layout assignment and output file. The map is evidence of one-to-one preservation, not a design-decision log. `standard` and `fidelity` record only their newly authored output roster and structure; do not add a source-topology disposition table.
@@ -103,13 +103,13 @@ For `mirror`, `design_spec.md §V` must be followed by a `Source Preservation Ma
## Page Roster
-The output page set is determined by **replication mode**, declared in the finalized template brief:
+The output page set is determined by the confirmed natural-language creation intent. Template_Designer derives one internal `replication_mode` so the deterministic authoring tools can execute:
| Mode | When to use | Roster |
|------|-------------|--------|
-| `standard` (default) | Most templates — clean, reusable, compact coverage driven by the confirmed brief | Cover, chapter, ending, optional TOC, and one or a small explicitly required set of distinct content Layouts; typically 4–6 prototypes |
-| `fidelity` | User wants a broader, source-aligned but newly designed template | Canonical roles plus intentionally designed variants that cover the useful source composition range |
-| `mirror` | User wants a new template workspace that preserves validated native source facts | One SVG prototype materialized from the authoring IR per source slide, named `<NNN>_<page_type>.svg` by source order |
+| `standard` (default internal strategy) | The requested result is a clean, reusable, compact system | Cover, chapter, ending, optional TOC, and one or a small explicitly required set of distinct content Layouts; typically 4–6 prototypes |
+| `fidelity` | The natural-language intent calls for broader, source-aligned but newly designed coverage | Canonical roles plus intentionally designed variants that cover the useful source composition range |
+| `mirror` | The natural-language intent calls for preserving validated native source facts | One SVG prototype materialized from the authoring IR per source slide, named `<NNN>_<page_type>.svg` by source order |
**Hard rule — mode controls authorship**: `standard` and `fidelity` create new SVG documents and their own Master/Layout system. `mirror` maps the validated imported source contract into a new workspace and must not reauthor, distill, reinterpret, or supplement its structure.
@@ -125,13 +125,13 @@ The output page set is determined by **replication mode**, declared in the final
**Default — compact authored roster (may override when the confirmed Deck application requires distinct roles)**: Keep Layout content pages structurally flexible. For Deck, add only the distinct prototypes needed to express its confirmed recurring narrative/content roles; do not manufacture variants from hypothetical future uses.
-**Confirmed compact variants**: `standard` may include more than one Layout for the same canonical role when the user brief explicitly requires genuinely different reusable structures, such as two-column evidence and three-card KPI content. Keep the roster compact and brief-driven rather than mining the source page set. When siblings exist, suffix every sibling (`03a_content_two_col.svg`, `03b_content_three_card.svg`) instead of treating one arbitrary variant as the unsuffixed default. This does not require `fidelity`; use `fidelity` when the broader roster is derived from complete PPTX/SVG page evidence.
+**Intent-derived compact variants**: `standard` may include more than one Layout for the same canonical role when the brief requires genuinely different reusable structures, such as two-column evidence and three-card KPI content. Keep the roster compact and brief-driven rather than mining the source page set. When siblings exist, suffix every sibling (`03a_content_two_col.svg`, `03b_content_three_card.svg`) instead of treating one arbitrary variant as the unsuffixed default. This does not require `fidelity`; derive `fidelity` when the broader roster is driven by complete PPTX/SVG page evidence.
**Naming note**: The numeric prefix is the template's own presentation order. Its base sequence stays contiguous; sibling variants share their parent's number only through unique lowercase suffixes such as `03a` / `03b`. When the optional TOC page is included it takes `02_toc.svg` and the later types shift by one: `01_cover`, `02_toc`, `03_chapter`, `04_content`, `05_ending`. Numbers carry no meaning across templates — tooling derives the page type from the token after the underscore, so both spellings of each type are equivalent.
### Fidelity mode
-When the brief sets `Replication mode: fidelity`, design a broader reusable roster that stays close to the source's visual language and useful composition examples. The output Master/Layout system is authored independently from source topology.
+When the derived implementation writes `replication_mode: fidelity`, design a broader reusable roster that stays close to the source's visual language and useful composition examples. The output Master/Layout system is authored independently from source topology.
**Variant naming**: append a lowercase letter suffix to the parent type's index, preserving sort order:
@@ -154,7 +154,7 @@ Extension page types beyond the canonical four (transition / appendix / disclaim
### Mirror mode
-When the brief sets `Replication mode: mirror`, materialize a new template workspace from validated imported facts rather than designing a new system:
+When the derived implementation writes `replication_mode: mirror`, materialize a new template workspace from validated imported facts rather than designing a new system:
- Kind eligibility: Create Layout mirror is legal only when the validated source contract is already brand-neutral and application-neutral. If supported source facts retain organization-specific identity or reusable application policy, stop and return to Create Template dispatch: use `standard` / `fidelity` to author a new Layout, or Create Deck to retain those facts. Removing, repainting, retyping, or discarding application rules is never mirror.
- Model-facing authoring source: `authoring-svg/authoring_summary.json`, layered `authoring-svg/*.svg`, `svg/inheritance.json`, and `native_structure.json`. Do not read `authoring-svg/authoring_manifest.json`; materialization validates it internally. When present, use `authoring-svg-flat/` only for full-page verification. Matching lossless `svg/` and optional `svg-flat/` files are immutable backing; materialization resolves only the layered backing.
@@ -165,7 +165,7 @@ When the brief sets `Replication mode: mirror`, materialize a new template works
- Forbidden: commonality extraction, semantic synthesis, merging, splitting, promotion, demotion, renaming, re-parenting, decorative simplification, placeholder invention, or replacement of supported source-native metadata / SVG fallback with a model-authored approximation.
- `design_spec.md` §V Page Roster lists every emitted file and marks definition-only prototypes explicitly. `Source Preservation Map` records each source-slide assignment plus every unused Layout definition and its parent Master.
-**Mirror consumption boundary**: `replication_mode: mirror` describes source-to-workspace fidelity and enables — but never forces — the downstream `template_reuse_scope: mirror` option. Stage 2 chooses `mirror`, `layout`, or `style` from the confirmed communication contract and, for Deck, the stored application contract. With mirror scope, each output page starts from one selected complete prototype and changes only allowed visible text values; with layout or style scope, the corresponding adaptation rules apply. None of the three scopes forces the generated deck to preserve source page count, source order, or a one-output-slide-per-source-slide mapping; prototypes may still be selected, repeated, skipped, or reordered.
+**Mirror consumption boundary**: `replication_mode: mirror` describes source-to-workspace fidelity and only makes literal downstream reuse technically possible. Strategist independently derives the application plan from the current communication contract, content, actual prototype roster, and any explicit natural-language instruction. It may select, repeat, skip, reorder, or reorganize prototypes; no internal scope forces source page count, source order, or one output slide per source slide.
**What mirror is not**: a redesign, topology-cleanup, or recovery mode. It may mechanically transcode the imported representation into the current explicit SVG/package contract, so byte identity is not promised. Charts, SmartArt, OLE objects, and EMF / WMF media that fail to round-trip in `pptx_template_import.py` will fail the same way in mirror. If the import workspace has missing media or unsupported objects, mirror inherits those gaps — report them before materialization begins.
@@ -223,13 +223,12 @@ page_count: <N>
# [Template Name] — Design Specification
## I. Template Overview
-| Application contract | Definition |
+| Application context | Definition |
|---|---|
| Recurring presentation family | <repeatable situations this Deck serves> |
| Intended audiences and outcomes | <who it serves and what the presentation should enable> |
| Delivery and reading assumptions | <presented / close-read / handoff / mixed> |
-| Stable narrative/page roles | <required, optional, and repeatable roles without fixing one page order> |
-| Content reuse boundary | <fixed, replaceable, optional, and example-only starting content> |
+| Representative narrative/page roles | <roles commonly present in this presentation family; descriptive, not mandatory> |
- Design tone, theme mode (light / dark / mixed), and the visual identity visible at a glance
@@ -248,7 +247,7 @@ page_count: <N>
- Optional XML snippet for any reusable component unique to this template
## V. Page Roster
-One row per emitted SVG describing what this template's version of cover / chapter / content / ending looks like (background treatment, decorative anchors, layout rhythm, image behavior, content density, intended content slot). Add a content-policy value for every row: supported narrative role, required/optional/repeatable status, and which visible content is fixed, replaceable, or example-only. For `standard` / `fidelity`, record the newly authored Layout key and PowerPoint picker name. For `mirror`, record the preserved source Master/Layout keys and picker names without redesigning them. Roster entries must match the actual SVG files on disk.
+One row per emitted SVG describing what this template's version of cover / chapter / content / ending looks like: background treatment, decorative anchors, layout rhythm, image behavior, content density, intended role, reusable slots, and structural capacity. Do not add required/optional/repeatable status or fixed/replaceable/example-only content policy. For `standard` / `fidelity`, record the newly authored Layout key and PowerPoint picker name. For `mirror`, record the preserved source Master/Layout keys and picker names without redesigning them. Roster entries must match the actual SVG files on disk.
For `mirror`, add `### Source Preservation Map` immediately after the roster with columns `Source slide`, `Source Master`, `Source Layout`, `Output SVG`, and `Preservation status`. This is a one-to-one mapping record. Do not add synthesis rationale or source-structure disposition rows to `standard` / `fidelity` templates.
@@ -337,7 +336,7 @@ Templates must strictly follow the finalized template brief and the generated `d
- **Font plan**: Uses the per-role font families declared in the spec
- **Layout principles**: Margins and spacing conform to the spec
- **Image system**: Image placement, crop / mask behavior, full-bleed zones, and overlay rules follow the source-derived norms in the spec
-- **Deck application**: Template Overview and every Page Roster content policy follow the confirmed recurring situations, audiences/outcomes, stable roles, and content reuse boundary
+- **Deck application**: Template Overview describes the recurring situations, audiences/outcomes, and representative roles; Page Roster factually describes the actual prototypes and reusable slots without prescribing future use
If PPTX import output exists:
- Prefer imported theme colors and fonts over visually guessed values
@@ -609,11 +608,11 @@ templates/
- [x] Read `references/template-designer.md`
- [x] Output scope confirmed: `library` | `project`; the common workspace preflight passed before final writes
-- [x] Replication mode confirmed: `standard` | `fidelity` | `mirror`; Layout mirror source is already brand-neutral and application-neutral
+- [x] Internal creation strategy derived from the confirmed natural-language intent: `standard` | `fidelity` | `mirror`; Layout mirror source is already brand-neutral and application-neutral
- [x] Every page listed in `design_spec.md §V Page Roster` saved to `<template_workspace>/templates/`
- [x] Naming convention applied (standard / fidelity: letter-suffix variants; mirror: `<NNN>_<page_type>.svg`)
- [x] Templates follow design spec (colors, fonts, layout)
-- [x] Deck Template Overview and roster content policies implement the confirmed recurring application; Layout output contains no application or identity contract
+- [x] Deck Template Overview and factual Page Roster describe the recurring application and actual prototypes without mandatory use policy; Layout output contains no application or identity contract
- [x] `standard` / `fidelity` SVGs and Master/Layout contracts were newly authored; `mirror` SVGs were materialized from the authoring IR while preserving the source graph without semantic redesign
- [x] Placeholder markers are clear and standardized for `standard` / `fidelity`; preview-only sample text remains readable without changing source markers, while mirror preserves literal source text plus source placeholder type/index/bounds
- [x] Every SVG is a complete preview with explicit root Master/Layout identity and `native_structure_mode: structured`; authored modes use canonical fixed layers/slots, while mirror preserves source ownership and mechanically expands fixed-layer groups into direct atoms
diff --git a/skills/ppt-master/scripts/confirm_ui/server.py b/skills/ppt-master/scripts/confirm_ui/server.py
index b2a072ab..8963f619 100644
--- a/skills/ppt-master/scripts/confirm_ui/server.py
+++ b/skills/ppt-master/scripts/confirm_ui/server.py
@@ -524,8 +524,6 @@ _DECK_DIRECTION_RECOMMEND_KEYS = (
'delivery_purpose',
'mode',
'visual_style',
- 'template_reuse_scope',
- 'template_adherence',
'icons',
'image_usage',
)
@@ -535,43 +533,6 @@ _PRODUCTION_RECOMMEND_KEYS = (
'generation_mode',
)
_LOCKED_RECOMMENDATIONS_KEY = '_locked_recommendations'
-_TEMPLATE_REUSE_SCOPES = frozenset({'mirror', 'layout', 'style'})
-_TEMPLATE_ADHERENCE_MODES = frozenset({'strict', 'adaptive'})
-
-
-def _template_context(project_path: Path) -> dict[str, object]:
- """Return the loaded template kind and replication contract."""
- spec_path = project_path / 'templates' / 'design_spec.md'
- try:
- lines = spec_path.read_text(encoding='utf-8').splitlines()
- except OSError:
- return {'enabled': False, 'kind': None, 'replication_mode': None}
- if not lines or lines[0].strip() != '---':
- return {'enabled': False, 'kind': None, 'replication_mode': None}
- kind = None
- replication_mode = None
- for line in lines[1:]:
- stripped = line.strip()
- if stripped == '---':
- break
- kind_match = re.fullmatch(
- r'kind\s*:\s*["\']?(brand|layout|deck)["\']?',
- stripped,
- )
- if kind_match:
- kind = kind_match.group(1)
- continue
- replication_match = re.fullmatch(
- r'replication_mode\s*:\s*["\']?(standard|fidelity|mirror)["\']?',
- stripped,
- )
- if replication_match:
- replication_mode = replication_match.group(1)
- return {
- 'enabled': kind in {'layout', 'deck'},
- 'kind': kind,
- 'replication_mode': replication_mode,
- }
def _merge_confirmed_choices(data: dict, result_file: Path) -> None:
@@ -990,38 +951,15 @@ def create_app(
rec_stage_number = _recommendation_stage(data)
if rec_stage_number >= 2 and result_file.exists():
_merge_confirmed_choices(data, result_file)
- template_context = _template_context(project_path)
- # Template use is a Stage-2 direction decision derived from the confirmed
- # communication contract. Keep it off the Stage-1 page even when a
- # deck/layout workspace is installed. Legacy single-pass files (stage 0)
- # still expose the controls.
- template_adherence_enabled = bool(
- template_context['enabled'] and rec_stage_number != 1
- )
- data['_template_adherence_enabled'] = template_adherence_enabled
- data['_template_reuse_scope_enabled'] = template_adherence_enabled
- data['_template_replication_mode'] = template_context['replication_mode']
+ # Template application is authored by Strategist from the installed
+ # workspace and current content. Never expose legacy mode fields as
+ # user-facing confirmation controls.
recommend = data.get('recommend')
- if template_adherence_enabled:
- if not isinstance(recommend, dict):
- recommend = data['recommend'] = {}
- recommend.setdefault('template_reuse_scope', 'layout')
- if (
- recommend.get('template_reuse_scope') == 'mirror'
- and template_context['replication_mode'] != 'mirror'
- ):
- recommend['template_reuse_scope'] = 'layout'
- if recommend.get('template_reuse_scope') == 'style':
- recommend.pop('template_adherence', None)
- data.pop('template_adherence', None)
- else:
- recommend.setdefault('template_adherence', 'adaptive')
- else:
- if isinstance(recommend, dict):
- recommend.pop('template_reuse_scope', None)
- recommend.pop('template_adherence', None)
- data.pop('template_reuse_scope', None)
- data.pop('template_adherence', None)
+ if isinstance(recommend, dict):
+ recommend.pop('template_reuse_scope', None)
+ recommend.pop('template_adherence', None)
+ data.pop('template_reuse_scope', None)
+ data.pop('template_adherence', None)
# The page polls this endpoint after a stage-1 confirm until the AI
# overwrites the file with the once-authored stage-2 recommendations, so it
# must never be served from a cache.
@@ -1044,29 +982,8 @@ def create_app(
result_file,
)
stage = _stage_key(result.get('stage'))
- template_context = _template_context(project_path)
- if template_context['enabled'] and stage != 'stage1':
- reuse_scope = result.get('template_reuse_scope')
- if reuse_scope not in _TEMPLATE_REUSE_SCOPES:
- return jsonify({
- 'error': 'template_reuse_scope must be mirror, layout, or style',
- }), 400
- if (
- reuse_scope == 'mirror'
- and template_context['replication_mode'] != 'mirror'
- ):
- return jsonify({
- 'error': 'mirror reuse requires replication_mode: mirror',
- }), 400
- if reuse_scope == 'style':
- result.pop('template_adherence', None)
- elif result.get('template_adherence') not in _TEMPLATE_ADHERENCE_MODES:
- return jsonify({
- 'error': 'template_adherence must be strict or adaptive',
- }), 400
- else:
- result.pop('template_reuse_scope', None)
- result.pop('template_adherence', None)
+ result.pop('template_reuse_scope', None)
+ result.pop('template_adherence', None)
# Staged flow: Stage 1 / Stage 2 submits record intermediate choices but do
# NOT close the page. Only a final submit is a full confirmation. A
# payload with no stage is a single-pass confirmation (chat-opt-out parity).
diff --git a/skills/ppt-master/scripts/confirm_ui/static/app.js b/skills/ppt-master/scripts/confirm_ui/static/app.js
index 5b8e1164..0cb1978c 100644
--- a/skills/ppt-master/scripts/confirm_ui/static/app.js
+++ b/skills/ppt-master/scripts/confirm_ui/static/app.js
@@ -33,7 +33,6 @@
sec_delivery: "How it will be used and what must remain",
sec_narrative: "Narrative direction",
sec_visual: "Visual direction",
- sec_template: "Template direction",
sec_color: "Color scheme",
sec_icons: "Icon usage",
sec_type: "Typography",
@@ -45,8 +44,6 @@
design_directions_hint: "Each direction coordinates style, color, typography, icons, and generated-image rendering. You can fine-tune every field below.",
sub_mode: "Narrative mode",
sub_visual: "Visual style",
- sub_template_reuse_scope: "Template reuse scope",
- sub_template_adherence: "Template adherence",
sub_divergence: "Material divergence (how freely to reshape vs. stay close to the source)",
placeholder_divergence: "In your words — e.g. \"stick closely to the document\" / \"freely restructure and expand within the source\". Leave blank for a balanced default.",
communication_intent: "What should this presentation accomplish?",
@@ -166,7 +163,6 @@
sec_delivery: "どう使い、何を残すか",
sec_narrative: "ナラティブ方針",
sec_visual: "ビジュアル方針",
- sec_template: "テンプレート方針",
sec_color: "配色",
sec_icons: "アイコンの使用",
sec_type: "タイポグラフィ",
@@ -178,8 +174,6 @@
design_directions_hint: "各案はスタイル、配色、書体、アイコン、生成画像のレンダリングを一体で提案します。下の各項目で微調整できます。",
sub_mode: "ナラティブモード",
sub_visual: "ビジュアルスタイル",
- sub_template_reuse_scope: "テンプレートの再利用範囲",
- sub_template_adherence: "テンプレートの適用方法",
sub_divergence: "素材からの発散度(どこまで自由に再構成するか、原文に忠実か)",
placeholder_divergence: "自分の言葉でどうぞ — 例:「文書に忠実に」「元素材の範囲内で自由に再構成・展開」。空欄ならバランス型になります。",
communication_intent: "このプレゼンで何を実現したいですか?",
@@ -299,7 +293,6 @@
sec_delivery: "如何使用、之后留下什么",
sec_narrative: "叙事方向",
sec_visual: "视觉方向",
- sec_template: "模板方向",
sec_color: "色彩方案",
sec_icons: "图标使用",
sec_type: "字体方案",
@@ -311,8 +304,6 @@
design_directions_hint: "每套方向会一起协调风格、配色、字体、图标和生成图渲染;你仍可在下方逐项微调。",
sub_mode: "叙事模式",
sub_visual: "视觉风格",
- sub_template_reuse_scope: "模板复用范围",
- sub_template_adherence: "模板遵循方式",
sub_divergence: "材料发散度(多大程度重塑,还是贴近源材料)",
placeholder_divergence: "用你自己的话写,例如「严格贴着文档来」/「在源材料范围内自由重组并展开」。留空则按平衡处理。",
communication_intent: "这份演示文稿需要完成什么?",
@@ -767,37 +758,6 @@
return !!(REC && REC[field] && typeof REC[field] === "object" && REC[field].locked === true);
}
- function hasTemplateReuseScope() {
- if (!REC) return false;
- if (typeof REC._template_reuse_scope_enabled === "boolean") {
- return REC._template_reuse_scope_enabled;
- }
- if (REC.recommend && REC.recommend.template_reuse_scope != null) return true;
- return REC.template_reuse_scope != null;
- }
-
- function templateReuseScopeOptions() {
- var options = (CAT && CAT.template_reuse_scope) || [];
- if (REC && REC._template_replication_mode === "mirror") return options;
- return options.filter(function (option) { return option.id !== "mirror"; });
- }
-
- function pickTemplateReuseScope() {
- var options = templateReuseScopeOptions();
- var recommended = recId("template_reuse_scope");
- var ids = options.map(function (option) { return option.id; });
- return ids.indexOf(recommended) >= 0 ? recommended : firstId(options);
- }
-
- function hasTemplateAdherence() {
- if (STATE.template_reuse_scope === "style") return false;
- if (!REC) return false;
- if (typeof REC._template_adherence_enabled === "boolean") {
- return REC._template_adherence_enabled;
- }
- if (REC.recommend && REC.recommend.template_adherence != null) return true;
- return REC.template_adherence != null;
- }
// Guaranteed recommendation: the AI's pick, or the first catalog option as a
// fallback so an enumerable field ALWAYS shows a badged recommendation.
function recOrFirst(field, list) {
@@ -1381,35 +1341,6 @@
host.appendChild(sec);
}
- function renderTemplateDirection(host) {
- if (!hasTemplateReuseScope()) return;
- var sec = section(6, "sec_template");
- var reuseOptions = templateReuseScopeOptions();
- sec.appendChild(el("div", "subfield-label", t("sub_template_reuse_scope")));
- enumField(sec, reuseOptions,
- pickTemplateReuseScope(),
- function () { return STATE.template_reuse_scope; },
- function (v) {
- STATE.template_reuse_scope = v;
- if (v === "style") {
- delete STATE.template_adherence;
- } else if (!STATE.template_adherence) {
- STATE.template_adherence = pick("template_adherence", CAT.template_adherence);
- }
- setTimeout(renderAll, 0);
- });
- if (hasTemplateAdherence()) {
- var templateField = el("div", "subfield");
- templateField.appendChild(el("div", "subfield-label", t("sub_template_adherence")));
- enumField(templateField, CAT.template_adherence,
- recOrFirst("template_adherence", CAT.template_adherence),
- function () { return STATE.template_adherence; },
- function (v) { STATE.template_adherence = v; });
- sec.appendChild(templateField);
- }
- host.appendChild(sec);
- }
-
var PALETTE_ROLES = [
"background",
"secondary_bg",
@@ -2396,7 +2327,6 @@
renderDesignDirections(host);
renderNarrativeDirection(host);
renderVisualDirection(host);
- renderTemplateDirection(host);
renderReadingMode(host);
renderPages(host);
var styleGroup = el("div", "style-group");
@@ -2423,7 +2353,6 @@
renderDesignDirections(host);
renderNarrativeDirection(host);
renderVisualDirection(host);
- renderTemplateDirection(host);
renderReadingMode(host);
renderPages(host);
var legacyStyleGroup = el("div", "style-group");
@@ -2490,17 +2419,6 @@
STATE.page_count = (REC.page_count && REC.page_count.value != null) ? String(REC.page_count.value) : (STATE.page_count || "");
STATE.mode = pick("mode", CAT.modes);
STATE.visual_style = pick("visual_style", CAT.visual_styles);
- if (hasTemplateReuseScope()) {
- STATE.template_reuse_scope = pickTemplateReuseScope();
- } else {
- delete STATE.template_reuse_scope;
- }
- if (hasTemplateAdherence()) {
- STATE.template_adherence = pick("template_adherence", CAT.template_adherence);
- } else {
- delete STATE.template_adherence;
- }
-
var cc = colorRecommendationCandidates();
var csel = (REC.color && REC.color.selected != null) ? REC.color.selected :
(designDirectionSpec().selected || 0);
@@ -2600,10 +2518,6 @@
payload.page_count = STATE.page_count;
// Reading mode keeps the legacy delivery_purpose key for compatibility.
if (isPptCanvas(STATE.canvas)) payload.delivery_purpose = STATE.delivery_purpose;
- if (STATE.template_reuse_scope) payload.template_reuse_scope = STATE.template_reuse_scope;
- if (STATE.template_reuse_scope !== "style" && STATE.template_adherence) {
- payload.template_adherence = STATE.template_adherence;
- }
payload.color = JSON.parse(JSON.stringify(STATE.color || {}));
payload.icons = STATE.icons;
payload.typography = JSON.parse(JSON.stringify(STATE.typography || {}));
@@ -2707,7 +2621,6 @@
var payload = JSON.parse(JSON.stringify(STATE));
normalizeTypographyForSubmit(payload);
payload.stage = "final";
- if (payload.template_reuse_scope === "style") delete payload.template_adherence;
payload.image_usage = selectedImageUsageIds(payload.image_usage);
if (!imageUsageValid(payload.image_usage)) return;
if (!String(payload.image_notes || "").trim()) delete payload.image_notes;
diff --git a/skills/ppt-master/scripts/confirm_ui/static/catalogs.json b/skills/ppt-master/scripts/confirm_ui/static/catalogs.json
index 14f2d704..4205a76d 100644
--- a/skills/ppt-master/scripts/confirm_ui/static/catalogs.json
+++ b/skills/ppt-master/scripts/confirm_ui/static/catalogs.json
@@ -555,60 +555,6 @@
"label_ja": "分割モード"
}
],
- "template_reuse_scope": [
- {
- "id": "layout",
- "label": "layout",
- "label_zh": "复用布局体系",
- "label_en": "reuse layout system",
- "label_ja": "レイアウト体系を再利用",
- "desc_zh": "保留模板的 Master、布局语法和结构身份,可按内容重排,并在需要时创建新 Layout。",
- "desc_en": "Keep the template Master and layout grammar, but allow content-driven reflow and new explicit Layouts.",
- "desc_ja": "テンプレートのMasterとレイアウト体系を保ち、内容に応じた再配置や新しいLayoutの作成を許可する。"
- },
- {
- "id": "style",
- "label": "style",
- "label_zh": "只参考视觉风格",
- "label_en": "style reference only",
- "label_ja": "ビジュアルスタイルのみ参照",
- "desc_zh": "只采用颜色、字体、装饰语言和视觉节奏;页面走自由设计,不继承模板 Master/Layout。",
- "desc_en": "Use only color, typography, decoration, and rhythm; author free-design pages without inheriting template Master/Layout structure.",
- "desc_ja": "色、書体、装飾、リズムのみを参照し、テンプレートのMaster/Layoutを継承せず自由設計する。"
- },
- {
- "id": "mirror",
- "label": "mirror",
- "label_zh": "镜像页面替换",
- "label_en": "mirror page replacement",
- "label_ja": "ミラーページ置換",
- "desc_zh": "仅镜像模板可用;复制完整原型,只替换允许变化的可见文字,保持视觉和文本节点拓扑。",
- "desc_en": "Mirror workspaces only: copy the complete prototype, replace allowed visible text, and preserve visual and text-node topology.",
- "desc_ja": "mirrorワークスペース専用。完全な原型を複製し、許可された表示テキストだけを置換して視覚とテキストノード構造を維持する。"
- }
- ],
- "template_adherence": [
- {
- "id": "adaptive",
- "label": "adaptive",
- "label_zh": "适应性使用",
- "label_en": "adaptive",
- "label_ja": "適応的に使用",
- "desc_zh": "每页选择一个模板 SVG 作为架构参考;没有合适版式时沿用同一 Master 创建新的显式 Layout。",
- "desc_en": "Choose a template SVG as the architecture reference for every page; when no layout fits, create a new explicit Layout under the same Master.",
- "desc_ja": "各ページでテンプレートSVGを構造参照として選び、適合する版式がない場合は同じMaster配下に新しい明示的Layoutを作成する。"
- },
- {
- "id": "strict",
- "label": "strict",
- "label_zh": "严格套用",
- "label_en": "strict",
- "label_ja": "厳密に適用",
- "desc_zh": "每一页都从模板 SVG roster 选择版式,并保持其显式 Master、Layout 与 Placeholder 契约不变。",
- "desc_en": "Map every page to the template SVG roster and keep its explicit Master, Layout, and Placeholder contract unchanged.",
- "desc_ja": "すべてのページをテンプレートSVG一覧へ割り当て、明示されたMaster/Layout/Placeholder契約を変更せずに維持する。"
- }
- ],
"delivery_purpose": [
{
"id": "text",
diff --git a/skills/ppt-master/scripts/docs/confirm_ui.md b/skills/ppt-master/scripts/docs/confirm_ui.md
index 0beeded2..495a0aa5 100644
--- a/skills/ppt-master/scripts/docs/confirm_ui.md
+++ b/skills/ppt-master/scripts/docs/confirm_ui.md
@@ -40,7 +40,7 @@ python3 scripts/confirm_ui/server.py <project_path> --shutdown # Step 4 clean
- Refuses to start unless `<project_path>/confirm_ui/recommendations.json` exists (except `--shutdown`, which needs no recommendations).
- Per-project lock at `<project_path>/.confirm_ui.lock` — duplicate launches are refused; stale locks (dead pid) are overwritten.
- Idle auto-shutdown after 900 s by default; `/api/shutdown` exits gracefully and releases the lock.
-- `/api/recommendations` derives `_template_reuse_scope_enabled`, `_template_adherence_enabled`, and `_template_replication_mode` from `<project>/templates/design_spec.md` frontmatter. Stage 1 always suppresses both controls because template use is derived only after the communication contract; from Stage 2 onward, only `kind: deck` / `kind: layout` enables them. No template and `kind: brand` force both off even if stale recommendations contain them. The server defaults reuse scope to `layout`, exposes `mirror` only for `replication_mode: mirror`, defaults adherence to `adaptive` for `mirror` / `layout`, and removes adherence for `style`.
+- `/api/recommendations` and `/api/confirm` strip legacy `template_reuse_scope` and `template_adherence` fields. Template application is authored by Strategist from the installed workspace and current content; it is not a user-facing confirmation control.
Dependency:
@@ -53,11 +53,11 @@ pip install flask
- **Enumerable + custom** — canvas / mode / visual_style / icons. The page lists common options from `static/catalogs.json`, badges the AI's recommendation, and still offers a Custom box for edge cases. In the icon field, concrete libraries stay together while **No icons** and **Custom** each occupy a separate row because they are distinct paths, not additional library styles.
- **Visual examples for hard-to-name choices** — the full-screen confirmation page loads real SVG page samples from `static/style_previews/` for `visual_style`, and renders real sample SVGs from `templates/icons` for `icons`. These thumbnails make style and icon-library choices visually comparable before the user locks them. Preview copy is fixed role text (big title / section title / body / points), not project content from `recommendations.json`, so users compare visual treatment rather than copywriting. These previews are a confirmation aid only: they do not add fields to `recommendations.json` or `result.json`, and they do not replace the later Step 6 live preview.
- **Image usage multi-select** — image sources are selected as one or more catalog ids: `ai` = AI-generated, `web` = Web-sourced, `provided` = User-provided, `placeholder` = Placeholder, `none` = No images. `none` is exclusive. Recommendation and result values may be a legacy single string, but new files should use an array. When several sources are recommended, write the source ids to `recommend.image_usage` and write the actual usage strategy to `image_notes`, not a custom prose value.
-- **Closed enumerable** — PPT reading mode (`delivery_purpose` compatibility key), template reuse scope + adherence (conditional), formula policy / generation mode / refine spec, plus AI source only when image usage includes `ai`. These have no Custom box; out-of-catalog values snap back to the recommended option.
+- **Closed enumerable** — PPT reading mode (`delivery_purpose` compatibility key), formula policy / generation mode / refine spec, plus AI source only when image usage includes `ai`. These have no Custom box; out-of-catalog values snap back to the recommended option.
- **Open prose** — `audience`, `communication_intent`, `audience_outcome`, `core_message`, `delivery_context`, `artifact_afterlife`, `content_divergence`, and `page_count`. `communication_intent` may carry several purposes plus priority / sequence; common paths appear only as help text. `content_divergence` remains a separate source-treatment axis.
- **Coordinated generative directions** — `design_directions` carries ≥3 safe / shifted / bold candidates. Each candidate bundles visual style, color, typography, icon id, and conditional generated-image rendering. The page can still render legacy top-level `color`, `typography`, and `image_strategy` candidates, but new staged recommendations use the coordinated bundle.
-**Custom box** appears only on fields whose universe is genuinely open — `canvas`, `mode`, `visual_style`, and `icons`. Image usage uses a multi-select source list plus `image_notes` instead of a Custom box. Fully closed sets — `template_reuse_scope`, `template_adherence`, `image_ai_path`, `formula_policy`, `generation_mode`, `refine_spec` — have **no** Custom box; an out-of-catalog value there is snapped back to the recommended option.
+**Custom box** appears only on fields whose universe is genuinely open — `canvas`, `mode`, `visual_style`, and `icons`. Image usage uses a multi-select source list plus `image_notes` instead of a Custom box. Fully closed sets — `image_ai_path`, `formula_policy`, `generation_mode`, `refine_spec` — have **no** Custom box; an out-of-catalog value there is snapped back to the recommended option.
**Stage-1 current-value contract.** Each editable prose box starts with the Strategist's recommendation, if one exists. The user may retain, revise, or clear it; no Stage-1 prose field has a non-empty validation gate. On confirmation, the browser submits the current strings and the server preserves them through every later stage and the final `result.json`, including `""`. Blank means no explicit user constraint and may cause downstream default judgment, but it never causes the initial recommendation to be restored. A profile-declared `locked: true` field is read-only and remains the sole exception.
@@ -65,7 +65,7 @@ pip install flask
## Catalogs — `static/catalogs.json` (the finite option universe)
-The front-end loads `/api/catalogs` (served by the confirm server) and falls back to the static `/static/catalogs.json` if that route is unavailable. `/api/catalogs` returns the static file **with the `canvas` list synced live from `config.py CANVAS_FORMATS`** — the set of formats and their `dim` come from config (single source of truth, zero drift), while trilingual labels / use text stay in catalogs.json (a plain fallback label is synthesized for any new id config adds). Keys: `canvas`, `modes`, `visual_styles` (grouped), `template_reuse_scope`, `template_adherence`, `icons`, `image_usage`, `image_ai_path`, `formula_policy`, `generation_mode`, `delivery_purpose`. Each entry is `{ "id", "label", "label_zh", "label_en", "label_ja", ... }`; descriptions use `desc_zh` / `desc_en` / `desc_ja`, and `visual_styles` groups use `group_zh` / `group_en` / `group_ja`. The front-end falls back to legacy `label` / `desc` / `group`, so old catalogs still load, but new user-facing catalog text must cover all three languages (zh / en / ja). English labels should mirror canonical reference names (`pyramid`, `swiss-minimal`, `Path A`, `mixed`, etc.); Chinese and Japanese labels should be translated for users. Descriptions render inline after the option title, not as a separate selected-option line. `visual_styles` is `[{ "group", "group_zh", "group_en", "group_ja", "items": [...] }]`. For `canvas` you only need to maintain the trilingual labels in catalogs.json; the format set and dimensions are authoritative in `config.py CANVAS_FORMATS`.
+The front-end loads `/api/catalogs` (served by the confirm server) and falls back to the static `/static/catalogs.json` if that route is unavailable. `/api/catalogs` returns the static file **with the `canvas` list synced live from `config.py CANVAS_FORMATS`** — the set of formats and their `dim` come from config (single source of truth, zero drift), while trilingual labels / use text stay in catalogs.json (a plain fallback label is synthesized for any new id config adds). Keys: `canvas`, `modes`, `visual_styles` (grouped), `icons`, `image_usage`, `image_ai_path`, `formula_policy`, `generation_mode`, `delivery_purpose`. Each entry is `{ "id", "label", "label_zh", "label_en", "label_ja", ... }`; descriptions use `desc_zh` / `desc_en` / `desc_ja`, and `visual_styles` groups use `group_zh` / `group_en` / `group_ja`. The front-end falls back to legacy `label` / `desc` / `group`, so old catalogs still load, but new user-facing catalog text must cover all three languages (zh / en / ja). English labels should mirror canonical reference names (`pyramid`, `swiss-minimal`, `Path A`, `mixed`, etc.); Chinese and Japanese labels should be translated for users. Descriptions render inline after the option title, not as a separate selected-option line. `visual_styles` is `[{ "group", "group_zh", "group_en", "group_ja", "items": [...] }]`. For `canvas` you only need to maintain the trilingual labels in catalogs.json; the format set and dimensions are authoritative in `config.py CANVAS_FORMATS`.
## Round-trip data contract
@@ -78,13 +78,13 @@ The page runs as a **three-stage wizard in one browser session**. `recommendatio
| `recommendations.json stage` | Page renders | Button | On submit |
|---|---|---|---|
| `"stage1"` | communication contract — audience; open `communication_intent`; audience outcome; core message / delivery context / artifact afterlife / `content_divergence` (all prose fields may be blank); canvas | **Confirm contract & continue** | writes `result.json` `{ stage: "stage1", status: "stage1-confirmed", <communication contract> }`; the page stays open and polls |
-| `"stage2"` | complete deck solution — reading mode, mode, page count, visual / template direction, color, icons, typography, image usage, generated-image rendering | **Confirm solution & continue** | writes `result.json` `{ stage: "stage2", status: "stage2-confirmed", <contract + solution> }`; the page stays open and polls |
+| `"stage2"` | complete deck solution — reading mode, mode, page count, visual direction, color, icons, typography, image usage, generated-image rendering | **Confirm solution & continue** | writes `result.json` `{ stage: "stage2", status: "stage2-confirmed", <contract + solution> }`; the page stays open and polls |
| `"stage3"` | production only — confirmed image-source summary, conditional AI acquisition path, formula policy, generation mode, refine spec | **Confirm** | writes `result.json` `{ stage: "final", status: "confirmed", <all fields> }`, then shuts the page down |
| *(absent)* | legacy single-pass — every section on one page | **Confirm** | single final write (`status: "confirmed"`) — backward-compatible |
The AI launches Stage 1, authors the complete Stage-2 solution once from the user's actual contract, then authors Stage-3 production mechanics once from the confirmed solution. An edit inside the current stage never requests another recommendation. The page preserves earlier answers across transitions. `GET /api/session` is the waiting-state endpoint; `GET /api/recommendations` is `no-store`, and the server folds confirmed earlier-stage choices back into later payloads so refresh / reopen restores the user's actual values—including Stage-2 color, typography, icon, image-source, and rendering choices.
-**Stage progression guard.** Stages confirm strictly in order — a staged `recommendations.json` may only run **one** stage past the last confirmed result. A file that skips ahead (e.g. `"stage3"` while only Stage 1 is confirmed) is never rendered: `/api/session` keeps reporting `waiting_agent` with `stage_skip: true`, and `--wait` / `--wait-only` exit `2` with a directive log line naming the expected stage to rewrite. An active deck/layout template does not exempt Stage 2: template capability is an input to the scenario-fit decision, not a reason to skip it. Legacy single-pass files (no `stage`) are not staged and bypass the guard.
+**Stage progression guard.** Stages confirm strictly in order — a staged `recommendations.json` may only run **one** stage past the last confirmed result. A file that skips ahead (e.g. `"stage3"` while only Stage 1 is confirmed) is never rendered: `/api/session` keeps reporting `waiting_agent` with `stage_skip: true`, and `--wait` / `--wait-only` exit `2` with a directive log line naming the expected stage to rewrite. An active deck/layout template does not exempt Stage 2: Strategist still derives its internal page/prototype plan from the confirmed communication contract. Legacy single-pass files (no `stage`) are not staged and bypass the guard.
### Input — `recommendations.json` (written by Strategist before launch)
@@ -129,8 +129,6 @@ After Stage 1 is confirmed, overwrite the file with the complete Stage-2 solutio
"delivery_purpose": "balanced",
"mode": "pyramid",
"visual_style": "swiss-minimal",
- "template_reuse_scope": "layout",
- "template_adherence": "adaptive",
"image_usage": ["ai", "provided"]
},
"page_count": { "value": "12-15" },
@@ -185,8 +183,7 @@ After Stage 2 is confirmed, overwrite it with Stage-3 production recommendations
- `recommend.*` names the recommended `id` for each enumerable field (must match a `catalogs.json` id, or be a free string for a recommended custom value). The page badges and pre-selects it. **Guarantee**: if a `recommend.*` is omitted, the page falls back to the first catalog option so every enumerable field always shows one badged recommendation — but the AI should still set them for a meaningful default. Legacy aliases are accepted for old files (`line` → `tabler-outline`, `filled` → `tabler-filled`, `monochrome` → `chunk-filled`, `search` → `web`, `default` → `auto`, `builtin` → `host-native`), but new files should write canonical ids.
- `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, while the six communication keys remain present as key lines in `spec_lock.md communication`. `communication_intent` may preserve several purposes plus priority / sequence; never add a `primary_job` enum.
-- `recommend.template_reuse_scope` is conditional. Write `layout`, `style`, or `mirror` only when Step 3 loaded a `kind: deck` or `kind: layout` template. The default is `layout`; `mirror` is displayed only when the installed spec declares `replication_mode: mirror`. `style` means free-design `pptx_structure.mode: flat` and suppresses/removes `template_adherence`.
-- `recommend.template_adherence` is conditional on reuse scope `mirror` or `layout`. Write `adaptive` or `strict`; the default is `adaptive`. Both values require a reference SVG for every page: `strict` keeps the selected Layout contract; `adaptive` may create a new Layout under the same Master. Free design, brand-only templates, and `style` cannot display or return this field.
+- Do not write `recommend.template_reuse_scope` or `recommend.template_adherence`. Strategist records those internal exporter values later in `design_spec.md` / `spec_lock.md` after inspecting the actual template and current content.
- `recommend.image_usage` should be an array of source ids when more than one source applies, e.g. `["ai", "provided"]`. A single string is still accepted for backward compatibility. Do not write bare `"custom"` and do not encode a mixed-source plan as prose here; write the prose to top-level `image_notes.value`.
- `image_notes` is the initial strategy note shown under the image source chips. Use it for page-role guidance and constraints: which source applies where, what to avoid, which user assets are authoritative, how realistic / abstract the imagery should be, and what can remain as placeholders. It is intent guidance, not a separate finite option.
- When confirmed Stage-2 `image_usage` includes `ai`, Stage 3 sets `recommend.image_ai_path` to one of `auto` / `api` / `host-native` / `manual`. Stage 2 never asks for the acquisition mechanism while the user is still deciding the image role.
@@ -217,8 +214,6 @@ After Stage 2 is confirmed, overwrite it with Stage-3 production recommendations
"content_divergence": "freely restructure and expand within the source",
"mode": "pyramid",
"visual_style": "swiss-minimal",
- "template_reuse_scope": "layout",
- "template_adherence": "adaptive",
"color": { "name": "...", "palette": { "background": "#...", "secondary_bg": "#...", "primary": "#...", "accent": "#...", "secondary_accent": "#...", "body_text": "#..." } },
"icons": "tabler-outline",
"typography": { "name": "...", "heading": { "cjk": "...", "latin": "...", "css": "..." }, "body": { "cjk": "...", "latin": "...", "css": "..." }, "body_size": 24, "body_size_unit": "px", "sizes": { "title": 42, "subtitle": 32, "annotation": 18 } },
diff --git a/skills/ppt-master/templates/README.md b/skills/ppt-master/templates/README.md
index bd60622c..1506fda7 100644
--- a/skills/ppt-master/templates/README.md
+++ b/skills/ppt-master/templates/README.md
@@ -21,10 +21,10 @@ PowerPoint package objects are compilation targets, not additional template
kinds. Theme values and identity assets are projected from resolved identity
rules supplied by Brand, Deck, or the current project; Layout rules project
into Master/Layout/Placeholder topology, semantic text roles, and
-spatial behavior; Deck combines both with purpose-specific starting content
-and usage rules. Downstream `layout` scope resolves final placeholder formatting
-with the confirmed identity, reading mode, and type scale; `mirror` preserves
-literal source formatting. A compiled Slide Master may therefore contain both
+spatial behavior; Deck combines both with descriptive recurring-application
+context and actual prototype examples. Downstream AI planning decides which
+prototypes and content to use, then records the required exporter values.
+A compiled Slide Master may therefore contain both
structural geometry and brand visuals even though their source rules remain
separately owned.
@@ -43,13 +43,14 @@ by the user or an exact validated Create Template handoff.
| Axis | Values | Meaning |
|---|---|---|
| Template kind | `brand` / `layout` / `deck` | Which reusable contract the package owns: identity, brand-neutral structure, or a complete recurring application |
-| Creation mode | `standard` / `fidelity` / `mirror` | Create Layout/Create Deck only: newly author a compact or broad roster, or materialize validated source-package facts into a new workspace; Layout mirror additionally requires a source contract already inside the brand-neutral, application-neutral Layout boundary; Create Brand is N/A |
-| Downstream adherence | `strict` / `adaptive` | Preserve the selected Layout contract, or allow explicit new Layout identities |
-| PPTX structure | `flat` / `structured` | Free-design, brand-only, and confirmed `style` stay Slide-local; confirmed `mirror` / `layout` compile declared Masters and Layouts |
-
-These axes must not be used as synonyms. In particular, a mirror-created deck
-is still an ordinary reusable `deck` package after creation; it does not force
-future presentations to keep the source page count or order.
+| Internal creation strategy | `standard` / `fidelity` / `mirror` | AI-derived Create Layout/Create Deck implementation: newly author a compact or broad roster, or materialize validated source-package facts into a new workspace; persisted for tools, never presented as a required user choice |
+| Internal application plan | `template_reuse_scope` plus optional `template_adherence` | Strategist derives literal, structural, or style-only use and any strict/adaptive exporter behavior after inspecting the installed template and current content |
+| PPTX structure | `flat` / `structured` | Derived application plans that use template structure compile declared Masters and Layouts; style-only, brand-only, and free design remain Slide-local |
+
+These axes must not be used as synonyms or exposed as a user mode matrix. In
+particular, a mirror-created deck is still an ordinary reusable `deck` package
+after creation; it does not force future presentations to keep the source page
+count or order.
## Workspace contract
diff --git a/skills/ppt-master/templates/decks/README.md b/skills/ppt-master/templates/decks/README.md
index 24f0b8e2..108b0933 100644
--- a/skills/ppt-master/templates/decks/README.md
+++ b/skills/ppt-master/templates/decks/README.md
@@ -1,20 +1,21 @@
# Deck Templates
**Deck = a reusable solution for a recurring presentation family.** It owns an
-application contract together with presentation identity and reusable page
-structure. The application contract states which communication situations the
-template serves, which audience outcomes it supports, which narrative/page
-roles remain stable, and how starting content should be replaced or retained.
+application context together with presentation identity and reusable page
+structure. The application context states which communication situations the
+template serves, which audience outcomes it supports, and which narrative/page
+roles commonly appear. It describes the resource; it does not decide which
+pages or visible content a future presentation must retain.
A deck template is not a finished content deck, and `kind: deck` does not mean
“mirror the source PPT”. Its construction mode decides whether the system is
newly authored or materialized from validated source facts.
| Axis | Deck behavior |
|---|---|
-| Template kind | `deck`: application contract + integrated identity + structure |
-| Creation mode | `standard` / `fidelity` author a new system; `mirror` materializes validated source-package facts into a new workspace |
-| Downstream adherence | Strategist selects `strict` or `adaptive` when the package is used |
-| PPTX structure | Workspace is `structured`; downstream `mirror` / `layout` use it, while confirmed `style` intentionally retains only visual language and generates `flat` |
+| Template kind | `deck`: descriptive application context + integrated identity + structure |
+| Internal creation strategy | AI derives `standard` / `fidelity` for a new system or `mirror` for validated source-package materialization; the field is tool provenance, not a user choice |
+| Application planning | Strategist automatically decides which prototypes to select, repeat, skip, or reorganize and derives the exporter behavior |
+| PPTX structure | The workspace is `structured`; the derived application plan decides whether generated pages compile its structure or use it only as visual reference |
The discovery source of truth is [`decks_index.json`](./decks_index.json)
(`deck_id → { summary, canvas_format, page_count, primary_color }`). This README
@@ -35,7 +36,7 @@ Selection uses the common explicit-path trigger in
or reading the discovery index does not trigger template use. The conditional
[`apply-template-workspace`](../../workflows/stages/apply-template-workspace.md)
stage owns path normalization, compatibility checks, installation, and fusion.
-This file owns the Deck schema and application contract.
+This file owns the Deck schema and application-context boundary.
---
@@ -72,18 +73,22 @@ page_count: <N>
## VII. Placeholder Overrides # omit when none
```
-`Template Overview` is an application contract, not a style description. It
-must identify the recurring presentation family, intended audiences and
-outcomes, delivery/reading assumptions, stable narrative or page roles, and the
-reuse boundary between fixed, replaceable, optional, and example-only content.
-These values may be broad when the source supports a family of related uses,
-but they must be specific enough to judge whether new content fits the Deck.
+`replication_mode` records how the workspace was produced. Create Template
+derives it from the natural-language brief and source evidence; users do not
+need to select or understand this field.
+
+`Template Overview` is descriptive application context, not a style
+description or future-use policy. It identifies the recurring presentation
+family, intended audiences and outcomes, delivery/reading assumptions, and
+representative narrative or page roles. These values may be broad when the
+source supports a family of related uses, but they must be specific enough to
+help Strategist understand the resource.
`Page Roster` must list every SVG and its declared Master/Layout identity, then
-state the content policy for that prototype: what role it can play, whether it
-is required/optional/repeatable, and which visible content is fixed,
-replaceable, or example-only. This policy does not force future presentations
-to keep the template's page count or order.
+describe its observed or intended role, visual character, reusable slots, and
+structural capacity. It must not mark pages required/optional/repeatable or
+content fixed/replaceable/example-only. Strategist inspects the actual roster
+and current material and decides what to use.
Every additional authored Master represents a distinct reusable design family,
not one Layout or an organizational duplicate.
diff --git "a/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\344\277\241/templates/design_spec.md" "b/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\344\277\241/templates/design_spec.md"
index 7e65bcea..16a7f040 100644
--- "a/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\344\277\241/templates/design_spec.md"
+++ "b/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\344\277\241/templates/design_spec.md"
@@ -21,13 +21,12 @@ page_count: 5
## I. Template Overview
-| Application contract | Definition |
+| Application context | Definition |
| --- | --- |
| Recurring presentation family | 政企数字化方案、转型规划、内部评审和客户汇报 |
| Intended audiences and outcomes | 面向政企客户决策者、项目干系人与内部评审者;帮助受众理解背景与方案、形成判断,并明确下一步 |
| Delivery and reading assumptions | 以会议讲解为主,同时需要会后流转和复核;页面应保留关键结论与必要证据,不依赖口头说明才能辨认主题 |
-| Stable narrative/page roles | 必需封面;可选目录与章节页;正文页可重复;需要正式收束时使用结束页。具体论证顺序由当前项目的沟通契约决定 |
-| Content reuse boundary | Logo、品牌口号与固定品牌图形可保留;项目标题、目录、章节名、正文、数据、来源和联系信息必须替换;原型中的示例文字不得进入成品 |
+| Representative narrative/page roles | 当前原型覆盖封面、目录、章节、开放内容和结束语;具体选页、重复、顺序与内容处理由当前项目的 Strategist 根据材料决定 |
- 视觉基调为白底、通信红结构条、银灰内容承载区与少量城市线稿,强调权威、清晰和克制。
- 结构上分为两个可复用 Master 家族:China Telecom Brand 服务封面、章节与收尾,China Telecom Content 服务目录与正文;它们按视觉体系分工,不是按单个 Layout 拆分出的重复 Master。
@@ -62,13 +61,13 @@ page_count: 5
## V. Page Roster
-| File | Master | Layout key | PowerPoint picker name | Visual character | Reusable slots | Content policy |
-| --- | --- | --- | --- | --- | --- | --- |
-| `01_cover.svg` | China Telecom Brand | cover | Cover | 左侧标题簇、右侧品牌卡片、底部飘带 | 标题、副标题、单位、日期 | 必需起始页;品牌图形固定,演示标题信息全部替换 |
-| `02_toc.svg` | China Telecom Content | agenda | Agenda | 左侧品牌说明卡、右侧四行编号目录 | 页面标题、四个目录项、页码 | 可选;目录项按当前叙事生成,不保留原型示例 |
-| `03_chapter.svg` | China Telecom Brand | section | Section Header | 左侧章节信息、右侧品牌卡片、底部飘带 | 章节号、章节标题、章节副标题 | 可选且可重复;章节信息全部替换,品牌图形固定 |
-| `04_content.svg` | China Telecom Content | content | Title and Content | 红灰页眉与大面积浅灰开放内容区 | 栏目标、页面标题、内容对象、来源、页码 | 可重复;承载当前项目事实、论证、数据或行动,所有内容均替换 |
-| `05_ending.svg` | China Telecom Brand | closing | Closing | 左侧结束语、右侧品牌卡片、底部飘带 | 结束标题、副标题、联系信息、页码 | 可选收束页;品牌图形固定,结束语与联系信息按项目替换 |
+| File | Master | Layout key | PowerPoint picker name | Visual character | Reusable slots |
+| --- | --- | --- | --- | --- | --- |
+| `01_cover.svg` | China Telecom Brand | cover | Cover | 左侧标题簇、右侧品牌卡片、底部飘带 | 标题、副标题、单位、日期 |
+| `02_toc.svg` | China Telecom Content | agenda | Agenda | 左侧品牌说明卡、右侧四行编号目录 | 页面标题、四个目录项、页码 |
+| `03_chapter.svg` | China Telecom Brand | section | Section Header | 左侧章节信息、右侧品牌卡片、底部飘带 | 章节号、章节标题、章节副标题 |
+| `04_content.svg` | China Telecom Content | content | Title and Content | 红灰页眉与大面积浅灰开放内容区 | 栏目标、页面标题、内容对象、来源、页码 |
+| `05_ending.svg` | China Telecom Brand | closing | Closing | 左侧结束语、右侧品牌卡片、底部飘带 | 结束标题、副标题、联系信息、页码 |
## VI. Assets
diff --git "a/skills/ppt-master/templates/decks/\344\270\255\346\261\275\347\240\224/templates/design_spec.md" "b/skills/ppt-master/templates/decks/\344\270\255\346\261\275\347\240\224/templates/design_spec.md"
index ece4dbd8..83ebbff2 100644
--- "a/skills/ppt-master/templates/decks/\344\270\255\346\261\275\347\240\224/templates/design_spec.md"
+++ "b/skills/ppt-master/templates/decks/\344\270\255\346\261\275\347\240\224/templates/design_spec.md"
@@ -21,13 +21,12 @@ page_count: 5
## I. Template Overview
-| Application contract | Definition |
+| Application context | Definition |
| --- | --- |
| Recurring presentation family | 产品认证展示、评测汇报、技术推广和业务来访 |
| Intended audiences and outcomes | 面向客户、技术评审者、合作伙伴与来访团队;帮助受众理解认证或评测能力、信任证据,并推进评审、交流或合作下一步 |
| Delivery and reading assumptions | 以现场讲解和技术交流为主,同时允许会后独立阅读;页面需保留关键结论、证据标签与必要上下文 |
-| Stable narrative/page roles | 必需封面;可选目录与章节页;正文页可重复;正式交流可使用结束页。具体论证顺序由当前项目的沟通契约决定 |
-| Content reuse boundary | Logo、机构英文名与固定结构图形可保留;项目标题、目录、章节名、正文、数据、案例和联系信息必须替换;原型示例不得作为事实复用 |
+| Representative narrative/page roles | 当前原型覆盖封面、目录、章节、开放内容和结束语;具体选页、重复、顺序与内容处理由当前项目的 Strategist 根据材料决定 |
- 视觉以中汽研深蓝、白底内容页、方形章节编号和简洁网格为识别核心,强调专业、可信和工程秩序。
- 结构上分为两个可复用 Master 家族:CATARC Dark 服务封面、章节与收尾,CATARC Light 服务目录与正文;它们按深浅视觉体系分工,不是按单个 Layout 拆分出的重复 Master。
@@ -62,13 +61,13 @@ page_count: 5
## V. Page Roster
-| File | Master | Layout key | PowerPoint picker name | Visual character | Reusable slots | Content policy |
-| --- | --- | --- | --- | --- | --- | --- |
-| `01_cover.svg` | CATARC Dark | cover | Cover | 深蓝背景、居中大型 Logo 与标题簇 | 标题、副标题、单位、英文单位 | 必需起始页;机构标识固定,演示标题信息全部替换 |
-| `02_toc.svg` | CATARC Light | agenda | Agenda | 数字双竖线目录、右侧数据面板 | 页面标题、五个目录项、数据对象、页码 | 可选;目录与数据对象按当前叙事生成,不保留原型示例 |
-| `03_chapter.svg` | CATARC Dark | section | Section Header | 深蓝章节页、居中章节号和标题 | 章节号、章节标题、章节副标题 | 可选且可重复;章节信息全部替换,机构视觉固定 |
-| `04_content.svg` | CATARC Light | content | Title and Content | 方形章节号页眉与开放内容面板 | 章节号、页面标题、内容对象、页码 | 可重复;承载当前项目的事实、证据、数据、案例或行动,所有内容均替换 |
-| `05_ending.svg` | CATARC Dark | closing | Closing | 深蓝网格背景、居中 Logo 与结束语 | 结束标题、英文副标题、联系信息、页脚 | 可选收束页;机构视觉固定,结束语与联系信息按项目替换 |
+| File | Master | Layout key | PowerPoint picker name | Visual character | Reusable slots |
+| --- | --- | --- | --- | --- | --- |
+| `01_cover.svg` | CATARC Dark | cover | Cover | 深蓝背景、居中大型 Logo 与标题簇 | 标题、副标题、单位、英文单位 |
+| `02_toc.svg` | CATARC Light | agenda | Agenda | 数字双竖线目录、右侧数据面板 | 页面标题、五个目录项、数据对象、页码 |
+| `03_chapter.svg` | CATARC Dark | section | Section Header | 深蓝章节页、居中章节号和标题 | 章节号、章节标题、章节副标题 |
+| `04_content.svg` | CATARC Light | content | Title and Content | 方形章节号页眉与开放内容面板 | 章节号、页面标题、内容对象、页码 |
+| `05_ending.svg` | CATARC Dark | closing | Closing | 深蓝网格背景、居中 Logo 与结束语 | 结束标题、英文副标题、联系信息、页脚 |
## VI. Assets
diff --git a/skills/ppt-master/templates/layouts/README.md b/skills/ppt-master/templates/layouts/README.md
index 57f68305..21847770 100644
--- a/skills/ppt-master/templates/layouts/README.md
+++ b/skills/ppt-master/templates/layouts/README.md
@@ -18,16 +18,16 @@ is a Deck.
Neutral colors, safe fonts, and provisional sizes may appear in SVG prototypes
so the structure is reviewable. They are preview values, not a locked identity
segment or final type scale. The reusable rule is the role hierarchy and its
-spatial behavior. Downstream `layout` scope resolves its appearance from the
-Brand, reading mode, and confirmed project lock; explicit `mirror` scope keeps
-literal source formatting.
+spatial behavior. When the workspace is used, Strategist inspects the actual
+prototypes and current content, decides how much structure to reuse, and writes
+the internal exporter plan automatically.
| Axis | Layout behavior |
|---|---|
| Template kind | `layout`: structure only |
-| Creation mode | `standard` / `fidelity` author a new system; `mirror` materializes validated source-package facts into a new workspace |
-| Downstream adherence | Strategist selects `strict` or `adaptive` when the package is used |
-| PPTX structure | Workspace is `structured`; downstream `mirror` / `layout` use it, while confirmed `style` intentionally discards structure and generates `flat` |
+| Internal creation strategy | AI derives `standard` / `fidelity` for a new system or `mirror` for validated source-package materialization; the field is tool provenance, not a user choice |
+| Application planning | Strategist automatically decides literal, structural, or style-only use and derives any strict/adaptive exporter value |
+| PPTX structure | The workspace is `structured`; the derived application plan decides whether generated pages compile its structure or use it only as visual reference |
The discovery source of truth is [`layouts_index.json`](./layouts_index.json)
(`layout_id → { summary, canvas_format, page_count, page_types }`). This README
@@ -85,6 +85,10 @@ page_types: [cover, toc, chapter, content, ending]
## VII. Placeholder Overrides # omit when none
```
+`replication_mode` records how the workspace was produced. Create Template
+derives it from the natural-language brief and source evidence; users do not
+need to select or understand this field.
+
`Signature Design Elements` describes only reusable structure: grids, zones,
image behavior, density rhythm, semantic text roles, alignment/wrapping/
capacity behavior, and slot conventions. It must not introduce a brand
diff --git a/skills/ppt-master/workflows/create-template.md b/skills/ppt-master/workflows/create-template.md
index d3834a3c..59977e25 100644
--- a/skills/ppt-master/workflows/create-template.md
+++ b/skills/ppt-master/workflows/create-template.md
@@ -26,7 +26,7 @@ Create Template is the fixed user-facing entry and common contract. It selects o
|---|---|---|---|
| [`Create Brand`](./create-template/create-brand.md) | Reuse identity only: colors, typography, logo, voice, and icon style | `templates/brands/<brand_id>/` | Identity analysis and identity-only `design_spec.md`; no SVG roster |
| [`Create Layout`](./create-template/create-layout.md) | Reuse a brand-neutral structural skeleton without a recurring communication application | `templates/layouts/<layout_id>/` | Canvas, page grammar, semantic text roles, Master/Layout/slot contract, and SVG roster; no brand identity or application contract |
-| [`Create Deck`](./create-template/create-deck.md) | Reuse a branded structural system or a recurring presentation application | `templates/decks/<deck_id>/` | Application contract, integrated identity/structure, content reuse policy, and SVG roster |
+| [`Create Deck`](./create-template/create-deck.md) | Reuse a branded structural system or a recurring presentation application | `templates/decks/<deck_id>/` | Descriptive application context, integrated identity/structure, and SVG roster |
Select Create Brand only for identity-only intent. Select Create Layout only when identity remains downstream-selectable and the reusable artifact does not prescribe communication objectives, audience outcomes, a required narrative sequence, or scenario-specific starting content. Select Create Deck when structure carries brand identity or reusable application semantics. A complete source PPTX alone does not determine the kind: classify only the stable rules worth reusing. Ask one discriminator question only when the user's requested reusable artifact is genuinely ambiguous; once selected, enter that child workflow and do not repeat route selection inside its confirmation gate.
@@ -82,10 +82,10 @@ Run every applicable input branch for the reference bundle the user supplied. A
### Input source taxonomy
-The rows are evidence channels, not mutually exclusive routes. Run every matching row and retain source-level provenance. The replication-mode column applies to Create Layout/Create Deck. Create Brand uses the same reference formats for identity evidence but has no replication mode, SVG roster, or native-structure path.
+The rows are evidence channels, not mutually exclusive routes. Run every matching row and retain source-level provenance. The internal-strategy column applies to Create Layout/Create Deck. Create Brand uses the same reference formats for identity evidence but has no replication strategy, SVG roster, or native-structure path.
-| Type | What the user supplied | Tool / read path | Replication modes available |
-|------|-------------------------|------------------|------------------------------|
+| Type | What the user supplied | Tool / read path | Internal strategies supported by the evidence |
+|------|-------------------------|------------------|-----------------------------------------------|
| **A** `.pptx` reference | A `.pptx` file path | `pptx_template_import.py` → `manifest.json` + `native_structure.json` + `source_template.pptx` + layered SVGs + `assets/`; flat verification SVGs are opt-in | `standard` / `fidelity` / `mirror` |
| **B** Existing SVG assets | `projects/<x>/svg_output/`, a current template workspace root, a legacy flat template root, or a loose `.svg` folder | Normalize the source directory, create an editable authoring IR bundle with `svg_authoring_view.py`, then use its page SVGs; also read companion `design_spec.md` / `spec_lock.md` when present | `standard` / `fidelity`; `mirror` only when the source already carries a complete explicit Master/Layout/placeholder/native-object contract |
| **C** Image / visual references | PNG/JPG/WebP images, screenshots, moodboards, PDF page visuals, or a visual-reference folder | `ls` + `Read` each supplied visual or PDF (multimodal recognition) | `standard` only by itself |
@@ -95,7 +95,7 @@ The rows are evidence channels, not mutually exclusive routes. Run every matchin
| Bundle rule | Behavior |
|---|---|
| Combine channels | `standard` may use every confirmed visual, textual, documentary, web, and asset source together. Do not force the user to choose one source type. |
-| Determine mode eligibility | `fidelity` requires Type A or B page evidence. `mirror` requires Type A or a complete current Type B structure contract. Type C/D/E evidence may supplement an eligible bundle but never creates native topology. |
+| Derive the execution strategy | The AI translates the user's natural-language intent plus source evidence into an internal strategy. `fidelity` requires Type A or B page evidence. `mirror` requires Type A or a complete current Type B structure contract. Type C/D/E evidence may supplement an eligible bundle but never creates native topology. Do not ask the user to choose these implementation labels. |
| Preserve provenance | Keep facts, explicit user decisions, and AI suggestions distinct. Surface contradictions in Step 2 instead of resolving them silently. |
| Protect mirror | Supplemental text, images, websites, or assets may explain the source but cannot alter a confirmed `mirror` graph or visuals. Use `standard` / `fidelity` when the user wants those inputs to change the resulting system. |
@@ -110,7 +110,7 @@ Type B is supported with caveats:
- **legacy or unstructured type B** — old `baseline` / `preserve` / `layout_strategy: distill` / `data-pptx-layout-kind` / direct-atomic-placeholder inputs, and SVGs with no root Master identity, are visual/contextual reference for `standard` / `fidelity` only. Author a new current contract in the output workspace. Use the original PPTX Type A path when existing native Master/Layout facts must be mirrored; do not mutate the SVG source or claim topology recovery from incomplete metadata.
- **selected free-design subset on type B** — ingest only the explicitly named pages as visual reference, then author a new current structured contract in the output workspace. Do not scan or copy the whole `svg_output/` directory or silently turn unselected pages into template variants.
-**Replication mode boundary**: `standard` and `fidelity` are authored modes: source visuals/assets guide a new SVG roster and a newly designed Master/Layout/slot system, without preserving or distilling source topology. `mirror` is a native-preservation mode: only Master/Layout/placeholder/ownership facts that exist in a PPTX package or complete current Type B contract are authoritative. Mirror may mechanically normalize transport representation for the current compiler, including fixed-layer group expansion, but it never infers missing historical intent or modifies the input. Because mirror preserves supported visual and application facts, Create Layout may use it only when the source contract already satisfies the Layout boundary: brand-neutral and application-neutral. A source outside that boundary must use `standard` or `fidelity` to author a new Layout, or retain those facts through Create Deck. The modes create a template workspace, not a downstream generated deck; future decks are authored anew and do not inherit the source page count/order requirement.
+**Internal creation-strategy boundary**: `standard`, `fidelity`, and `mirror` are implementation labels derived after understanding the request; they are not user-facing creation modes. `standard` and `fidelity` author a new SVG roster and a new Master/Layout/slot system from the requested result. `mirror` preserves native facts that actually exist in a PPTX package or complete current Type B contract. Mirror may mechanically normalize transport representation for the current compiler, including fixed-layer group expansion, but it never infers missing historical intent or modifies the input. Because mirror preserves supported visual and application facts, Create Layout may use it only when the source contract already satisfies the Layout boundary: brand-neutral and application-neutral. A source outside that boundary must be re-authored internally or retained as a Deck. The strategy creates a template workspace, not a downstream generated deck; future decks are authored anew and do not inherit the source page count/order requirement.
### 1A. `.pptx` reference
@@ -350,7 +350,7 @@ Extract only what the source actually states:
- Identity rules: colors, typography, logo usage, voice, icon style, and explicit exclusions.
- Structure rules: canvas, page types, grids, zones, placeholders, density, image behavior, and requested variants.
-- Deck application: recurring situations, intended audiences/outcomes, delivery or reading assumptions, stable narrative/page roles, content reuse boundaries, examples, and negative requirements.
+- Deck application: recurring situations, intended audiences/outcomes, delivery or reading assumptions, representative narrative/page roles, examples, and negative requirements. Do not convert these observations into mandatory future-use policy.
Treat an explicit value authored by the user as `[decision]` regardless of carrier: direct chat, pasted text, or a user-written Markdown/TXT/DOCX/PDF brief all retain user authorship. Merely arriving in a file does not make a statement a fact. Treat a statement as `[fact]` only when it is independently traceable to an identified external authority such as an official manual/site, or when it is machine-observable file/package metadata such as dimensions, hashes, or existing PPTX structure. Any interpretation of vague prose remains `[suggested]` and must pass the Step 3 confirmation gate. Text and asset evidence never supplies Master/Layout topology by itself.
@@ -362,28 +362,28 @@ Skip the analysis. Step 2 will list every Required item as `[decision]`; nothing
## Step 2: Fact-Based Brief Proposal
-Compose a single message that surfaces every Required brief item to the user, **labelling each value's provenance**:
+Compose one concise natural-language proposal that states the template the AI intends to create, **labelling each material value's provenance**:
- **`[fact]`** — independently traceable external authority or machine-observable source metadata (e.g. theme color from `manifest.json`, image dimensions, or an identified official manual); a user-authored brief file is not a fact merely because it is a file
- **`[suggested]`** — AI-inferred from analysis or context (e.g. tone summary, applicable scenarios; visually estimated values from type C)
-- **`[decision]`** — an explicit user-authored instruction or choice, including exact values supplied in conversation, pasted text, or a user-written brief file (e.g. `template_id`, replication mode, category, palette, or layout rule)
+- **`[decision]`** — an explicit user-authored instruction, including exact values supplied in conversation, pasted text, or a user-written brief file (e.g. a template name, a preservation requirement, a palette, or a layout rule)
+- **`[derived]`** — an internal execution value the AI derives from the request and evidence so tools can run deterministically; it is recorded for provenance but never presented as a choice the user must understand
-**Language adaptation rule**: write the Step 2 brief in the user's language. For technical enum values, show the localized label first and keep the English ID in parentheses only when needed for precision, for example `<localized deck label> (deck)`, `<localized layout label> (layout)`, or `<localized mirror label> (mirror)`. Do not assume users know what each English word means.
+**Language adaptation rule**: write the Step 2 proposal in the user's language and describe the intended result in ordinary language. Technical IDs may appear only in a compact implementation note when they are useful for audit or correction; do not require the user to understand them.
-**Option visibility rule**: for every field with a finite option set, show both the recommended value and the other valid options. Do not present a single recommended value as if no alternatives exist. If an option is unavailable for the current bundle evidence, list it under `Unavailable` with the reason.
+**Natural-language planning rule**: present one recommended creation plan, not a menu of template modes, fidelity levels, or content-policy checklists. Translate requests such as “原样还原”, “提取成可复用母版和版式”, “保留风格但重新设计”, or any equivalent prose directly into the plan. Ask a follow-up only when a missing decision would materially change the artifact and cannot be inferred safely. The user may correct any sentence in the proposal.
| Field | Must show |
|---|---|
| Output scope | Recommended `library` (default) plus `project`; explain that both use the same portable workspace routing and only the parent path / global registration differ |
| Target project | Required only for `project`; show the exact initialized project workspace path, not a project nickname |
| Selected child workflow | Echo the already-dispatched Create Brand, Create Layout, or Create Deck workflow; do not reopen kind selection inside the brief |
-| Category | Create Layout/Create Deck only. Show the recommended localized value and alternatives; `brand` is valid for Create Deck but not Create Layout. For Layout, a scenario category records geometric fit only and never grants application ownership. |
-| Application contract | Create Deck only. Show the recurring presentation family, intended audiences/outcomes, delivery/reading assumptions, stable narrative/page roles, and content reuse boundary. Values unsupported by evidence remain `[suggested]` until confirmed. |
-| Theme mode | Create Layout/Create Deck only; recommended localized mode with English ID, plus available modes such as `light` / `dark` / `mixed`. Create Brand records identity colors instead and does not own a page theme mode. |
-| Canvas format | Create Layout/Create Deck only; recommended canvas plus other supported formats from [`canvas-formats.md`](../references/canvas-formats.md) that fit the source aspect ratio or user intent. Always show the concrete pixel size and `viewBox`; do not treat two same-ratio formats such as `ppt169` (`1280x720`) and `banner` (`1920x1080`) as interchangeable. |
-| Replication mode | Create Layout/Create Deck only; recommended localized mode with English ID, plus all modes available for the current input type. State that `standard` / `fidelity` design a new structure while `mirror` materializes validated source-package facts into a new workspace; list unavailable modes with reasons. For Create Layout, mark `mirror` unavailable when the source retains brand identity or reusable application rules. Create Brand has no replication mode. |
-| Native structure policy | Create Layout/Create Deck only. For `standard` / `fidelity`, state that the designer will author a new Master/Layout/slot system without preserving or distilling source topology. Show the planned Master roster; if it contains more than one Master, explain the distinct reusable family owned by each and which Layouts belong to it. Reject one-Master-per-Layout organization and visually/semantically equivalent duplicate Masters. For `mirror`, summarize the exact source Master/Layout/placeholder facts that are present, supported, and will be mapped one-to-one into the new workspace. |
-| Visual fidelity for fixed pages | Create Layout/Create Deck only; recommended localized choice with English ID, plus both `literal` / `adapted` options when applicable |
+| Category | Create Layout/Create Deck only. State the one discovery category inferred from the intended artifact. For Layout, a scenario category records geometric fit only and never grants application ownership. |
+| Application context | Create Deck only. Summarize the recurring presentation family, likely audiences/outcomes, delivery/reading assumptions, and representative page roles. This is descriptive selection context, not a rule saying which template pages or visible content future projects must keep. |
+| Theme direction | Create Layout/Create Deck only. Describe the intended light/dark/mixed behavior in plain language. Create Brand records identity colors instead and does not own a page theme mode. |
+| Canvas | Create Layout/Create Deck only. State the recommended canvas with exact pixel size and `viewBox`; do not enumerate same-ratio alternatives unless the user asks or the evidence is genuinely ambiguous. |
+| Creation plan | Create Layout/Create Deck only. Describe what will be preserved, what will be rebuilt, how broad the prototype roster will be, and how native structure will be handled. The AI derives the internal `replication_mode` from this prose after confirmation; never ask the user to select `standard`, `fidelity`, or `mirror`. |
+| Native structure plan | Create Layout/Create Deck only. State the planned Master/Layout/slot result. For newly authored output, show the planned Master families and reject one-Master-per-Layout organization or equivalent duplicate Masters. For literal preservation, summarize the exact supported source facts that will be mapped into the new workspace. |
| Asset bundling | Recommended included assets, plus excluded candidate assets with a one-line reason when reference assets exist |
Items to surface:
@@ -392,19 +392,18 @@ Items to surface:
|------|----------|--------------------------|
| Output scope | Yes | `[decision]` — `library` (default, globally reusable and indexed) or `project` (same portable workspace routing under one initialized project) |
| Target project | Yes for `project`; N/A for `library` | `[decision]` — explicit path to the initialized target workspace; validate it during the Step 4 preflight |
-| New template ID | Yes | `[decision]` — user chooses a filesystem-safe ASCII slug. In library scope it also becomes the matching index key |
-| Template display name | Yes | `[decision]` (often the source deck title — `[suggested]` from `manifest.json.source.name` for type A) |
-| Category | Create Layout/Create Deck only | `[decision]` — Create Deck: `brand` / `general` / `scenario` / `government` / `special`; Create Layout: `general` / `scenario` / `government` / `special` |
+| New template ID | Yes | `[decision]` when supplied; otherwise propose a filesystem-safe ASCII slug as `[suggested]`. In library scope it also becomes the matching index key |
+| Template display name | Yes | `[decision]` when supplied; otherwise `[suggested]`, often from `manifest.json.source.name` for type A |
+| Category | Create Layout/Create Deck only | `[decision]` when explicit; otherwise `[derived]` for indexing — Create Deck: `brand` / `general` / `scenario` / `government` / `special`; Create Layout: `general` / `scenario` / `government` / `special` |
| Applicable scenarios | Yes | Create Brand: identity use cases. Create Layout: content shapes and delivery settings its geometry can support, without communication or narrative ownership. Create Deck: recurring presentation situations inside the application contract. `[suggested]` from analysis unless explicitly authored or externally sourced; user confirms. |
-| Audience outcomes and stable narrative/page roles | Create Deck only | `[decision]` when supplied explicitly; otherwise `[suggested]` from recurring source patterns. Separate stable reusable rules from one-off source content. |
-| Content reuse boundary | Create Deck only | `[decision]` or `[suggested]` classification of fixed, replaceable, optional, and example-only starting content; never infer that visible source text is reusable merely because it appears in a PPTX. |
+| Application context and representative page roles | Create Deck only | `[decision]` when supplied explicitly; otherwise `[suggested]` from recurring source patterns. Describe the source and intended family without assigning required/optional/repeatable status or fixed/replaceable/example-only policy. |
| Identity tone or structural summary | Yes | Create Brand/Create Deck: identity tone. Create Layout: structural use case and density/rhythm summary only. |
| Theme mode | Create Layout/Create Deck only | A: `[fact]` from `manifest.json` background colors. B: `[fact]` from SVG `fill`. C: `[suggested]` from visual estimate. D: `[fact]` from an independently identified external authority, `[decision]` from user-authored text in any carrier, otherwise `[suggested]`. E: `[decision]`. |
| Canvas format and dimensions | Create Layout/Create Deck only | A/B: `[fact]` from slide size or SVG `width` / `height` / `viewBox`; show `canvas_format`, `canvas_width`, `canvas_height`, `canvas_viewbox`, and `source_viewbox`. C: `[suggested]` from image aspect ratio. D: `[fact]` from an independently identified external authority or `[decision]` from user-authored text in any carrier when specified. E: `[decision]`, default `ppt169` (`1280x720`, `0 0 1280 720`). |
-| Replication mode | Create Layout/Create Deck only | `[decision]` — `standard` is always available and authors a compact roster from the confirmed brief; it may include a small number of explicitly required distinct variants without becoming source-driven. `fidelity` requires A/B page evidence and expands coverage from the useful source composition range; `mirror` requires A or B with a complete explicit structure contract. Create Layout mirror additionally requires the source contract itself to be brand-neutral and application-neutral; stripping identity or application rules is authorship, not mirror. C/D/E channels may supplement an eligible mixed bundle but do not establish mode eligibility. `standard` / `fidelity` author new SVG semantics. Mirror retains one materialized prototype per source slide in source order and adds definition-only prototypes for source Layouts unused by those slides. |
+| Internal creation strategy | Create Layout/Create Deck only | `[derived]` from the confirmed natural-language plan and evidence. `standard` is the compact authored implementation, `fidelity` requires A/B page evidence for broader source-aligned coverage, and `mirror` requires A or B with a complete explicit structure contract for literal materialization. Create Layout mirror additionally requires a brand-neutral and application-neutral source. Persist `replication_mode` for tools, not as a user-facing mode. |
| Native structure facts | Create Layout/Create Deck with Type A or structured Type B | `[fact]` from `native_structure.json` / source SVG contract: master/layout counts, parentage, page assignments, placeholder identities, and multi-master status. Mirror preserves these validated facts in the new workspace; authored modes do not use them as output topology. |
-| Mode-specific ownership | Create Layout/Create Deck only | `standard` / `fidelity`: `[decision]` newly authored Master/Layout ownership, including the reusable-family reason for every additional Master. `mirror`: `[fact]` source ownership mapped without synthesis. Every Master must own at least one emitted Layout and every Layout must have at least one emitted prototype; export never infers either contract. |
-| Visual fidelity for fixed pages | Create Layout/Create Deck `standard` / `fidelity` when reference exists; **N/A for `mirror` and Create Brand** | `[decision]` — `literal` (closely reproduce reference geometry / decoration / sprite crops within a newly authored structure) or `adapted` (use reference tone/composition but allow design evolution). Different page types may take different settings. |
+| Structure ownership plan | Create Layout/Create Deck only | `[derived]` from the requested result. Authored output creates new Master/Layout ownership, including the reusable-family reason for every additional Master; literal preservation maps source ownership without synthesis. Every Master must own at least one emitted Layout and every Layout must have at least one emitted prototype. |
+| Reference treatment | Create Layout/Create Deck when a reference exists | `[derived]` per page from the user's prose: closely reproduce geometry/decoration where requested, otherwise adapt the reference into the newly authored system. Literal materialization preserves supported source facts mechanically. |
| Basic template norms | Yes when reference exists | Create Brand uses the identity fields and provenance rules from its child workflow. Create Layout/Create Deck use `[fact]` / `[suggested]` layout grammar, image system, density rhythm, page roster semantics, and asset policy from Step 1. |
| Reference source | Optional | already known if Step 1 ran |
| Theme color | Create Brand/Create Deck only | A: `[fact]` from theme XML. B: `[fact]` from dominant SVG `fill`. C: `[suggested]` from visual estimate (HEX is approximate). D: `[fact]` from an independently identified external authority, `[decision]` from user-authored text in any carrier, otherwise `[suggested]`. E: `[decision]`. Create Layout may use neutral preview paint but stores no identity color. |
@@ -415,13 +414,13 @@ Items to surface:
When the bundle includes Type A for Create Layout/Create Deck, also include in this message:
-- the exact authoring-manifest documents required by the selected mode and verified during Step 1
+- the exact authoring-manifest documents required by the derived internal strategy and verified during Step 1
- a one-line summary of the source Master/Layout structure
-- the source structure facts, including master/layout counts, multi-master status, and reason codes; state whether they will be preserved in a new workspace (`mirror`) or ignored as output topology (`standard` / `fidelity`)
+- the source structure facts, including master/layout counts, multi-master status, and reason codes; state in plain language whether they will be preserved or used only as design evidence
The user replies with corrections, additions, or "all good".
-> **Persist the portable brief into `design_spec.md`**. In Step 4, declare a YAML frontmatter block with the child-specific ID key (`brand_id`, `deck_id`, or `layout_id`) and only fields owned by that child. Create Brand follows its identity schema. Create Layout/Create Deck persist the confirmed portable fields (`kind`, `category`, `summary`, `keywords`, `primary_color` for deck, `page_types` for layout, `canvas_format`, `canvas_width`, `canvas_height`, `canvas_viewbox`, `source_viewbox`, `replication_mode`, `native_structure_mode`, etc.). A Deck writes its confirmed application contract in Template Overview and content policies in Page Roster rather than duplicating that prose into frontmatter. Do not persist a generic `template_id` field: it is the parent workflow's cross-kind name, not a registrar schema key. Do not persist the execution-only `output_scope` or `target_project` fields. In library scope, `register_template.py` reads this frontmatter in Step 7 so the brief flows directly into the index without the AI re-deriving it from prose.
+> **Persist the portable brief into `design_spec.md`**. In Step 4, declare a YAML frontmatter block with the child-specific ID key (`brand_id`, `deck_id`, or `layout_id`) and only fields owned by that child. Create Brand follows its identity schema. Create Layout/Create Deck persist the confirmed portable fields (`kind`, `category`, `summary`, `keywords`, `primary_color` for deck, `page_types` for layout, `canvas_format`, `canvas_width`, `canvas_height`, `canvas_viewbox`, `source_viewbox`, `replication_mode`, `native_structure_mode`, etc.). `replication_mode` is the AI-derived implementation record, not a user selection. A Deck writes descriptive application context in Template Overview and factual prototype descriptions in Page Roster rather than duplicating that prose into frontmatter. Do not persist a generic `template_id` field: it is the parent workflow's cross-kind name, not a registrar schema key. Do not persist the execution-only `output_scope` or `target_project` fields. In library scope, `register_template.py` reads this frontmatter in Step 7 so the brief flows directly into the index without the AI re-deriving it from prose.
---
@@ -437,17 +436,17 @@ Skipping this gate — including silently inferring values from reference files,
**Required outcome of Step 3** (all must be true before emitting `[TEMPLATE_BRIEF_CONFIRMED]`):
- [ ] User has been shown every Required item in Step 2 with provenance labels
-- [ ] Every finite-option field has shown a recommended value, other available options, and unavailable options with reasons when applicable
-- [ ] User-facing labels and option explanations match the user's language; English enum IDs appear only as precision aids
-- [ ] User has replied with values or explicit acceptance of suggested defaults
+- [ ] The user saw one concise natural-language creation plan rather than a mode menu or content-policy checklist
+- [ ] User-facing language describes the intended result; internal enum IDs are absent or confined to an audit note
+- [ ] User has replied with corrections or explicit acceptance of the proposed result
- [ ] Output scope is confirmed; both scopes use the same workspace shape, while `project` includes an explicit initialized target-project path
- [ ] For Create Layout/Create Deck, the canvas format is fixed before SVG generation
-- [ ] For Create Layout/Create Deck, replication mode is consistent with the bundle evidence (`fidelity` requires A/B page evidence; `mirror` requires A or structured B; C/D/E channels alone permit only `standard`); Create Layout mirror evidence is already brand-neutral and application-neutral
+- [ ] For Create Layout/Create Deck, the AI-derived internal strategy is consistent with the bundle evidence (`fidelity` requires A/B page evidence; `mirror` requires A or structured B; C/D/E channels alone permit only `standard`); Create Layout mirror evidence is already brand-neutral and application-neutral
- [ ] Every supplied visual, textual, documentary, web, and asset channel has been analyzed or explicitly excluded; mixed-input conflicts are surfaced rather than silently resolved
- [ ] For Create Layout/Create Deck mirror, the source graph and supported geometry are complete; every source Layout absent from the source-slide roster is planned as a definition-only prototype, and any genuinely missing/unsupported facts were reported; Create Layout mirror contains no retained brand identity or reusable application policy
- [ ] Child-specific norms from prior content have been surfaced and accepted, or explicitly marked N/A when no reference exists: identity/provenance for Create Brand; layout/image/density/asset behavior for Create Layout/Create Deck
-- [ ] For Create Layout/Create Deck, mode-specific ownership is explicit: `standard` / `fidelity` author a new structure without source-topology distillation; `mirror` maps validated source ownership one-to-one into a new workspace
-- [ ] For Create Deck, the recurring presentation family, intended audiences/outcomes, stable narrative/page roles, and content reuse boundary are confirmed; for Create Layout, no application contract or brand identity has leaked into the structure brief
+- [ ] For Create Layout/Create Deck, the plan makes structure ownership explicit: authored output creates a new structure without source-topology distillation; literal materialization maps validated source ownership one-to-one into a new workspace
+- [ ] For Create Deck, the recurring presentation family, intended audiences/outcomes, and representative page roles are understood without turning them into mandatory page/content policies; for Create Layout, no application contract or brand identity has leaked into the structure brief
- [ ] For Create Brand, all required identity fields from its child workflow are confirmed and canvas/replication/native-structure fields remain N/A
- [ ] For `library`, metadata is complete enough to register into the relevant index; for `project`, the same portable template metadata is complete and no global registration is planned
- [ ] Marker `[TEMPLATE_BRIEF_CONFIRMED]` emitted on its own line after the echoed brief
@@ -502,7 +501,7 @@ When the bundle includes Type D, pass the direct text, converted document/websit
For Type E, pass only the finalized brief.
For a mixed reference bundle, pass the union of the applicable packages while keeping each fact's source and every unresolved conflict explicit.
-The role interprets the package according to replication mode:
+The role interprets the package according to the AI-derived internal creation strategy recorded as `replication_mode`:
| Mode | Final SVG authority | Structure behavior |
|---|---|---|
@@ -582,13 +581,13 @@ syntax here; its single authority is
[`shared-standards-core.md`](../references/shared-standards-core.md), with selection and
usage guidance in the native-shape reference.
-Downstream, a mirror-created workspace supports three separately confirmed reuse scopes. `mirror` and `layout` use `pptx_structure.mode: structured`; `page_layouts` selects one complete authoring prototype per page, `pptx_masters` / `pptx_layouts` declare unique reusable definitions, and `page_pptx_layouts` assigns generated pages. Strict preserves the selected prototype contract. Adaptive keeps its Master and may explicitly create and assign a new Layout key/name while authoring the page that needs it. `mirror` additionally preserves literal visuals/text topology; `layout` allows project-controlled reflow/re-skinning. `style` uses `mode: flat` and takes only the workspace's design language. A retained Layout may remain unassigned while still registering through its definition SVG. No scope forces a future generated deck to keep the source page count or order.
+Downstream, Strategist inspects the installed workspace and current content, then derives an internal application plan. The plan may use the full roster or a subset, repeat or reorder prototypes, and choose literal reuse, structural reuse, or visual-reference-only behavior. For exporter compatibility it records `template_reuse_scope` and, when structured, `template_adherence`; these are machine execution values, not user choices. `page_layouts` selects one complete authoring prototype per generated page, `pptx_masters` / `pptx_layouts` declare unique reusable definitions, and `page_pptx_layouts` assigns generated pages. No internal value forces a future generated deck to keep the source page count or order.
-**Apply the visual-fidelity decision from Step 3 to authored modes**: in `standard` / `fidelity`, pages marked `literal` reproduce the selected reference geometry and decoration while still using a newly designed structure; pages marked `adapted` may evolve the composition. Mirror preserves every supported source visual represented by the validated IR and does not use this authored-page distinction.
+**Apply the confirmed natural-language intent to authored output**: in `standard` / `fidelity`, reproduce reference geometry and decoration where the request calls for close preservation, and adapt compositions where it calls for a reusable redesign. Mirror preserves every supported source visual represented by the validated IR and does not use this authored-page distinction.
**Sprite-sheet preservation (do NOT simplify away)**: PPTX-exported assets are often sprite sheets — a single tall/large image referenced from multiple slides, each cropping a different region via nested `<svg ... viewBox="...">` wrappers around `<image width="1" height="1">`. This nesting is **load-bearing geometry**, not redundant structure. When rebuilding, preserve the exact `viewBox` crop and the outer `<svg>` placement for every image; do not flatten to a single `<image>` with direct `x/y/width/height`. Verify by sampling: if any asset's pixel dimensions don't match the on-page display aspect, it is a sprite and the wrapper must stay.
-**Mirror-mode materialization contract** (type A or B): when `Replication mode: mirror`, the Template_Designer role:
+**Mirror materialization contract** (type A or B): when the derived implementation writes `replication_mode: mirror`, the Template_Designer role:
1. **Materializes one output SVG per source page** in `<template_workspace>/templates/`. Edit and normalize the matching `authoring-svg/` IR document, then run `mirror_template_materialize.py`; the compiler consumes the tool-only authoring manifest together with native structure facts and immutable payload backing. Do not hand-copy or independently rebuild its graph. Preserve the source Master/Layout keys and picker names, Layout parentage, slide assignment, placeholder type/index/bounds, inherited-shape visibility, ownership, paint order, and supported native metadata that are present and validated. Mechanical namespace, root-declaration, asset-path, and fixed-layer group normalization is allowed only when source ownership and appearance remain unchanged.
- Type A model-facing source: `<import_workspace>/authoring-svg/authoring_summary.json` plus the editable SVGs; `<import_workspace>/svg/`, `svg/inheritance.json`, and `native_structure.json` provide payload and structural backing. The compiler alone reads `<import_workspace>/authoring-svg/authoring_manifest.json`. Optional `<import_workspace>/svg-flat/` is verification-only.
@@ -602,13 +601,13 @@ Downstream, a mirror-created workspace supports three separately confirmed reuse
- Type B: resolve relative paths in source `<image href="...">` against the source SVG location and copy each unique asset; if the source already follows PPT Master conventions (assets co-located with SVGs in the same directory), copy the whole asset set and then rewrite paths
- Both scopes: write bitmaps to `<template_workspace>/images/`, point SVG references at `../images/<name>`, and keep non-bitmap template-source assets under `<template_workspace>/templates/`.
4. **Copies imported vector assets once** to `<template_workspace>/icons/imported/` and rewrites their placeholders to `<use data-icon="imported/<name>"/>`. Never place a second copy under `templates/icons/`. Other explicitly adopted icon-library references keep their existing library namespace. Do not inline these assets manually in the template working SVGs; template validation, preview, and final export all resolve icons from the workspace-root `icons/` directory.
-5. Writes `design_spec.md` per [template-designer.md](../references/template-designer.md) §1. The §V Page Roster remains the content-fit index; explicit SVG metadata is the native Master/Layout contract. `replication_mode: mirror` governs template creation and merely enables the separately confirmed downstream `template_reuse_scope: mirror`; it never forces a 1:1 slide sequence.
+5. Writes `design_spec.md` per [template-designer.md](../references/template-designer.md) §1. The §V Page Roster remains a factual prototype index; explicit SVG metadata is the native Master/Layout contract. `replication_mode: mirror` records how the workspace was created and only makes literal downstream reuse technically possible; it never selects that behavior or forces a 1:1 slide sequence.
Mirror mode does not simplify the visual target or synthesize layer ownership. The sprite-sheet preservation rule applies because crop wrappers carry visible geometry; preserve those wrappers and their source scope faithfully.
**Expected outputs from this step** (full spec → [template-designer.md](../references/template-designer.md)):
-1. `design_spec.md` — **package-specific rules only**. A deck writes an application-bearing Template Overview, Color Scheme, Signature Design Elements, and Page Roster with content policies; Typography / Assets / Placeholder Overrides are conditional. A layout writes only structure-owned Signature Design Elements and Page Roster; its frontmatter `summary` carries concise selection context, and it omits the deck-only Template Overview plus every identity section. The Page Roster must match the actual SVG files on disk. Declare portable brief frontmatter; `register_template.py` consumes it only in library scope. **Do not** restate generic SVG constraints, layout pattern libraries, font-size ratio bands, the canonical placeholder table, or content methodology — those are sourced from `shared-standards-core.md` / `pptx-structure-interface.md` / `strategist.md` and are already in the downstream reader's context. Full scope rule and skeleton: [template-designer.md §1](../references/template-designer.md#1-must-generate-design_specmd).
+1. `design_spec.md` — **package-specific rules only**. A deck writes a descriptive Template Overview, Color Scheme, Signature Design Elements, and factual Page Roster; Typography / Assets / Placeholder Overrides are conditional. A layout writes only structure-owned Signature Design Elements and Page Roster; its frontmatter `summary` carries concise selection context, and it omits the deck-only Template Overview plus every identity section. The Page Roster must match the actual SVG files on disk and must not prescribe which pages or sample content a future project keeps. Declare portable brief frontmatter; `register_template.py` consumes it only in library scope. **Do not** restate generic SVG constraints, layout pattern libraries, font-size ratio bands, the canonical placeholder table, or content methodology — those are sourced from `shared-standards-core.md` / `pptx-structure-interface.md` / `strategist.md` and are already in the downstream reader's context. Full scope rule and skeleton: [template-designer.md §1](../references/template-designer.md#1-must-generate-design_specmd).
2. Page roster — see [Page Roster](../references/template-designer.md#page-roster) for `standard` / `fidelity` / `mirror` mode rosters, variant naming, and TOC handling
3. Placeholder vocabulary — pages should adopt the conventional names (`{{TITLE}}`, `{{CONTENT_AREA}}`, ...) when they fit. Full reference: [Placeholder Reference](../references/template-designer.md#4-placeholder-reference-canonical-convention-overridable-per-template). When a template style legitimately needs different vocabulary (consulting → `{{KEY_MESSAGE}}`, branded cover → `{{BRAND_LOGO}}`), declare a `placeholders:` block in `design_spec.md` frontmatter so the registrar and quality checker treat it as the template's authoritative contract. **Avoid** one-off indexed families such as `{{CHAPTER_01_TITLE}}` — use the indexed TOC pattern instead.
- `{{...}}` placeholders are the authoring vocabulary used to generate final slide content. Each emitted SVG also carries the native structure contract: root Master/Layout key/name, direct atomic Master/Layout elements, and direct slot `<g>` elements with explicit design-zone bounds plus exactly one compatible carrier. A validated compact canonical authored-preset `<g>` counts as one semantic atom or one `object` carrier; ordinary groups do not. Composite regions use only the explicit `object` + `proxy` downgrade. Minimal structural `data-pptx-role` hints are added only when specialized metadata cannot express required behavior. Both strict and adaptive downstream set `mode: structured` and require complete `page_layouts`, `page_pptx_layouts`, `pptx_masters`, and `pptx_layouts` from planning onward.
@@ -677,7 +676,7 @@ This checker validates the authoring contract, not the compiled OOXML package. T
**Checklist**:
-- [ ] `design_spec.md` follows the kind-specific package skeleton: deck = application-bearing Overview / Color / Signature / Page Roster plus conditional sections; layout = structure-owned Signature / Page Roster with no Overview, application contract, or identity sections. Generic constraints (SVG rules, pattern libraries, ratio bands, canonical placeholder table) are NOT restated. The source-derived basic norms are present as template-specific layout / image / density / asset rules, not generic advice. Deck Overview identifies recurring situations, audiences/outcomes, delivery assumptions, stable narrative/page roles, and content reuse boundaries; §V Page Roster lists every emitted page and, for Deck, each prototype's content policy
+- [ ] `design_spec.md` follows the kind-specific package skeleton: deck = descriptive Overview / Color / Signature / Page Roster plus conditional sections; layout = structure-owned Signature / Page Roster with no Overview, application contract, or identity sections. Generic constraints (SVG rules, pattern libraries, ratio bands, canonical placeholder table) are NOT restated. The source-derived basic norms are present as template-specific layout / image / density / asset rules, not generic advice. Deck Overview identifies recurring situations, audiences/outcomes, delivery assumptions, and representative narrative/page roles; §V Page Roster factually describes every emitted prototype without required/optional/repeatable or fixed/replaceable/example-only policy
- [ ] Every page declared in `design_spec.md §V Page Roster` exists as an SVG file in the template directory (and vice versa — no orphan files)
- [ ] Variant filenames follow the letter-suffix convention (e.g. `03a_content_two_col.svg`); variants typically reuse the parent type's placeholder set unless the spec frontmatter declares otherwise
- [ ] If TOC exists, placeholder pattern uses the canonical indexed form
@@ -884,7 +883,7 @@ The next Generate PPTX Step 3 input is the exact `<template_workspace>/` root in
1. **SVG technical constraints**: Create Layout/Create Deck load [shared-standards-core.md](../references/shared-standards-core.md) plus [pptx-structure-interface.md](../references/pptx-structure-interface.md), and load [svg-effects.md](../references/svg-effects.md) only when the authored design uses those effects. Create Brand authors no SVG and loads none of these SVG modules. Do not restate the contracts in the template's `design_spec.md`.
2. **Color consistency**: Create Deck SVG files must use the same color scheme as `design_spec.md §II Color Scheme`; Create Layout owns no identity colors, and Create Brand owns no SVG files
-3. **Native-object mapping**: Treat Theme/Master/Layout/Placeholder as compiled PowerPoint objects, not template kinds. Layout owns topology and placement, Brand owns identity values/assets, and Deck adds the reusable application contract.
+3. **Native-object mapping**: Treat Theme/Master/Layout/Placeholder as compiled PowerPoint objects, not template kinds. Layout owns topology and placement, Brand owns identity values/assets, and Deck adds descriptive recurring-application context.
4. **Placeholder convention**: `{{}}` format only; default names listed in [Placeholder Reference](../references/template-designer.md#4-placeholder-reference-canonical-convention-overridable-per-template). Override per template via `placeholders:` frontmatter when needed.
5. **Discovery requirement**: A library template is discoverable only after `register_template.py` has been run against it (Step 7). A project-scoped workspace intentionally stays out of global discovery and is consumed by its explicit workspace-root path.
6. **Review output**: Generate `exports/<template_id>_template_preview.pptx` on request and always for a multi-Master template. It is derived local evidence, never a source input during template application, and library exports stay Git-ignored.
diff --git a/skills/ppt-master/workflows/create-template/create-deck.md b/skills/ppt-master/workflows/create-template/create-deck.md
index 149c5bbc..2c18668a 100644
--- a/skills/ppt-master/workflows/create-template/create-deck.md
+++ b/skills/ppt-master/workflows/create-template/create-deck.md
@@ -15,7 +15,7 @@ Enter this child workflow only after [`Create Template`](../create-template.md)
**Hard rule — child workflow, not a top-level route**: Create Deck executes only inside Create Template. It reuses the parent workflow's Steps 1–8 and never creates a competing entry route or second confirmation gate.
-**Hard rule — recurring application**: A deck owns an application contract together with integrated identity and structure. The contract states the recurring presentation family, intended audiences/outcomes, delivery/reading assumptions, stable narrative/page roles, and content reuse boundary. It is a reusable template workspace, not the user's finished content deck.
+**Hard rule — recurring application**: A deck owns descriptive application context together with integrated identity and structure. The context states the recurring presentation family, intended audiences/outcomes, delivery/reading assumptions, and representative narrative/page roles. It helps later AI planning understand the resource, but it does not prescribe which prototypes or visible content a future project must keep. It is a reusable template workspace, not the user's finished content deck.
## Invocation Points
@@ -25,12 +25,12 @@ Enter this child workflow only after [`Create Template`](../create-template.md)
## 1. Deck Input Interpretation
-Use Create Template Step 1 for source ingestion and replication-mode eligibility. Interpret source evidence across all three segments:
+Use Create Template Step 1 for source ingestion and internal creation-strategy feasibility. Interpret source evidence across all three segments:
- Identity: color, typography, logo, visual voice, and icon style, with fact/suggestion provenance preserved in the brief.
- Structure: canvas, page grammar, Master/Layout families, slot geometry, semantic text roles, alignment/wrapping/capacity behavior, page types, image behavior, and density rhythm.
-- Application: recurring situations, intended audiences/outcomes, delivery or reading assumptions, stable narrative/page roles, and the boundary between fixed, replaceable, optional, and example-only content.
-- `standard` and `fidelity` author a new complete system; source topology is not output topology. `mirror` preserves only validated package/contract facts in a new workspace and never modifies the source.
+- Application: recurring situations, intended audiences/outcomes, delivery or reading assumptions, representative narrative/page roles, and the actual source-page vocabulary. Do not assign required/optional/repeatable status or fixed/replaceable/example-only policy.
+- Internally, `standard` and `fidelity` author a new complete system; source topology is not output topology. `mirror` preserves only validated package/contract facts in a new workspace and never modifies the source. The AI derives this implementation from the natural-language intent; it is not a user mode selector.
Direct conversation text, pasted requirements, converted documents/websites, images, and supplied assets are first-class evidence under Create Template Step 1. In a mixed bundle, combine the applicable identity, structure, and application evidence without erasing provenance. Exact user-authored instructions remain decisions whether they arrive in chat or a user-written brief file; vague prose remains suggested interpretation until the shared confirmation gate.
@@ -46,12 +46,11 @@ Add these child-owned requirements to Create Template Step 2:
| Recurring presentation family | Required; identify the repeatable situations this Deck serves rather than listing every plausible use |
| Intended audiences and outcomes | Required; state who the recurring users/recipients are and what the presentation should enable |
| Delivery and reading assumptions | Required; state whether the family is usually presented, closely read, handed off, or used in a mixed way |
-| Stable narrative/page roles | Required; identify roles that must or may recur without forcing one page count/order |
-| Content reuse boundary | Required; distinguish fixed, replaceable, optional, and example-only starting content |
+| Representative narrative/page roles | Required; describe the roles present in the source or useful to the recurring family without assigning future inclusion rules |
| Identity | Required; primary color plus supported palette, typography, logo policy, visual voice, and icon style |
| Canvas and page grammar | Required; exact canvas, page types, variants, grids, zones, density rhythm, and image behavior |
| Native structure | Required; Master families, Layout ownership, slot vocabulary, and zero-slot Layouts where intentional |
-| Replication mode | Required; `standard`, eligible `fidelity`, or eligible `mirror` under Create Template Step 1 |
+| Creation intent | Required as natural-language prose: what should remain recognizable, what should be rebuilt into a reusable system, and whether the source page set should be preserved broadly or distilled. The AI derives `replication_mode` internally. |
| Adopted assets | Optional; list included and excluded candidates with reasons |
Write this complete schema:
@@ -84,13 +83,14 @@ page_count: <N>
## VII. Placeholder Overrides
```
-Omit Typography only when the shared default is intentionally used. Omit Assets and Placeholder Overrides when none exist. Do not restate generic SVG constraints, layout libraries, font-ratio bands, or the canonical placeholder table.
+`replication_mode` is required machine provenance, not a user-facing choice. Omit Typography only when the shared default is intentionally used. Omit Assets and Placeholder Overrides when none exist. Do not restate generic SVG constraints, layout libraries, font-ratio bands, or the canonical placeholder table.
-Write Template Overview as the application contract. In Page Roster, add one
-content-policy statement per prototype: supported narrative role,
-required/optional/repeatable status, and which visible content is fixed,
-replaceable, or example-only. These policies guide downstream selection but do
-not force future decks to retain the template page count or order.
+Write Template Overview as descriptive application context. In Page Roster,
+describe each prototype's observed or intended role, visual character,
+reusable slots, and structural capacity. Do not add required/optional/
+repeatable status or fixed/replaceable/example-only content policy; downstream
+Strategist inspects the actual template and current content and decides what to
+use.
## 3. Author or Materialize the Deck
@@ -115,7 +115,7 @@ In addition to Create Template Steps 5–6, verify:
- `templates/design_spec.md` contains `deck_id`, `kind: deck`, `summary`, `primary_color`, canvas fields, `replication_mode`, `native_structure_mode: structured`, and `page_count`; `summary` names the recurring presentation family/outcome rather than only visual tone.
- `deck_id` matches the confirmed workspace ID in library scope.
-- Template Overview, Color Scheme, Signature Design Elements, and Page Roster exist; Template Overview covers every application-contract field, every roster row states its content policy, and conditional sections match real choices/assets.
+- Template Overview, Color Scheme, Signature Design Elements, and Page Roster exist; Template Overview describes the recurring application context, every roster row factually describes its prototype and slots without future-use policy, and conditional sections match real choices/assets.
- Every identity color is `#RRGGBB`; the primary table row matches frontmatter, and SVG paint follows the confirmed identity.
- Every SVG in the roster satisfies the shared Master/Layout/slot contract and the roster is bidirectionally complete.
- Every referenced image/icon exists under the same workspace; this workflow created no optional directory solely to leave it empty. Pre-existing initialized-project scaffolding is allowed and remains untouched.
diff --git a/skills/ppt-master/workflows/create-template/create-layout.md b/skills/ppt-master/workflows/create-template/create-layout.md
index ad8e2626..da619a4b 100644
--- a/skills/ppt-master/workflows/create-template/create-layout.md
+++ b/skills/ppt-master/workflows/create-template/create-layout.md
@@ -27,13 +27,13 @@ Neutral colors, safe fonts, and provisional sizes may appear in SVG prototypes s
## 1. Layout Input Interpretation
-Use Create Template Step 1 for source ingestion and replication-mode eligibility. Interpret source evidence only for reusable structure:
+Use Create Template Step 1 for source ingestion and internal creation-strategy feasibility. Interpret source evidence only for reusable structure:
- Canvas dimensions, grid, zones, page taxonomy, repeated chrome, image placement, density rhythm, placeholder geometry, semantic text roles, alignment, wrapping, and capacity may become layout facts or suggestions.
- Colors, font families, branded weight choices, final absolute sizes, logos, voice, and icon style remain source context only. Do not copy them into the layout identity because a layout has no identity segment.
- A source scenario may inform the content shapes or delivery conditions the geometry can support. Do not turn that fit into an application contract. If the reusable artifact prescribes the objective, outcome, narrative sequence, boilerplate, or content policy, return to Create Template dispatch and select Create Deck.
-- When the source is branded, explicitly confirm that Create Layout will strip that identity and restrict replication mode to `standard` or `fidelity`. If the user wants the identity retained with the structure, return to Create Template dispatch and select Create Deck before the shared confirmation marker is emitted.
-- `standard` and `fidelity` author a new Master/Layout/slot system. `mirror` is available only when the complete current source contract is already brand-neutral and application-neutral; it preserves validated structure and visual facts in a new workspace without modifying the source.
+- When the source is branded, state in plain language that Create Layout will omit the identity. The AI therefore derives an authored internal strategy. If the user wants the identity retained with the structure, return to Create Template dispatch and select Create Deck before the shared confirmation marker is emitted.
+- Internally, `standard` and `fidelity` author a new Master/Layout/slot system. `mirror` may be derived only when the complete current source contract is already brand-neutral and application-neutral; it preserves validated structure and visual facts in a new workspace without modifying the source. Never ask the user to choose among these labels.
Direct conversation text, pasted requirements, converted documents/websites, images, and supplied assets may define or illustrate reusable structure. In a mixed bundle, combine those channels without treating identity-only evidence as layout ownership. Exact user-authored instructions remain decisions whether they arrive in chat or a user-written brief file; vague prose remains suggested interpretation until the shared confirmation gate.
@@ -48,7 +48,7 @@ Add these child-owned requirements to Create Template Step 2:
| Canvas | Required; exact format, dimensions, and `viewBox` |
| Page grammar | Required; page types, variants, grids, zones, semantic text roles, alignment/wrapping/capacity, density rhythm, and image behavior |
| Native structure | Required; Master families, Layout ownership, slot vocabulary, and zero-slot Layouts where intentional |
-| Replication mode | Required; `standard`, eligible `fidelity`, or `mirror` only when the complete source contract is already brand-neutral and application-neutral |
+| Creation intent | Required as natural-language prose: what should remain recognizable, what should become reusable structure, and how broad the page vocabulary should be. The AI derives `replication_mode` internally from this intent and the evidence. |
| Identity stripping | Required when branded reference material exists; list the identity facts intentionally excluded |
Write this structure-only schema:
@@ -77,7 +77,7 @@ page_types: [cover, toc, chapter, content, ending]
## VII. Placeholder Overrides
```
-Omit `Placeholder Overrides` when no override exists. Omit Template Overview, Color Scheme, Typography, Logo, Voice, and every other identity section. Do not write `primary_color`.
+`replication_mode` is required machine provenance, not a user-facing choice. Omit `Placeholder Overrides` when no override exists. Omit Template Overview, Color Scheme, Typography, Logo, Voice, and every other identity section. Do not write `primary_color`.
`Signature Design Elements` describes only reusable structure, including text-role hierarchy and spatial behavior without locking the final font identity or type scale. `Page Roster` lists every SVG with its Master/Layout identity, picker name, intended content shape, and slot behavior.
diff --git a/skills/ppt-master/workflows/routing.md b/skills/ppt-master/workflows/routing.md
index d1f06388..74c9fce9 100644
--- a/skills/ppt-master/workflows/routing.md
+++ b/skills/ppt-master/workflows/routing.md
@@ -88,7 +88,7 @@ When a PPTX already contains native Master/Layout parts, `create-template` mirro
|---|---|
| `brand` | Dispatch to [`create-brand`](./create-template/create-brand.md); write identity only and no SVG roster |
| `layout` | Dispatch to [`create-layout`](./create-template/create-layout.md); author brand-neutral, application-neutral structure and an SVG roster |
-| `deck` | Dispatch to [`create-deck`](./create-template/create-deck.md); author a recurring application contract with integrated identity, structure, content policy, and an SVG roster |
+| `deck` | Dispatch to [`create-deck`](./create-template/create-deck.md); author descriptive recurring-application context with integrated identity, structure, and an SVG roster |
Create Template remains the fixed route name and owns the shared contract. These three documents are mutually exclusive child workflows, not additional top-level routes.
diff --git a/skills/ppt-master/workflows/stages/apply-template-workspace.md b/skills/ppt-master/workflows/stages/apply-template-workspace.md
index d769b103..afed0385 100644
--- a/skills/ppt-master/workflows/stages/apply-template-workspace.md
+++ b/skills/ppt-master/workflows/stages/apply-template-workspace.md
@@ -49,8 +49,8 @@ Before copying a Deck or Layout workspace, inspect every SVG root and slot:
| Kind | Install behavior |
|---|---|
| `brand` | Install `templates/` plus existing `images/` and `icons/`; ignore `exports/`. Identity is constrained; structure remains free. |
-| `layout` | Install the same portable roots. Expose reusable structure; Strategist later confirms legal `mirror`, `layout`, or `style` reuse. |
-| `deck` | Install the same portable roots. Expose application, identity, and structure; Strategist compares the stored application with the current communication contract before choosing reuse. |
+| `layout` | Install the same portable roots. Expose the actual reusable structure; Strategist later inspects the prototypes and derives the application plan automatically. |
+| `deck` | Install the same portable roots. Expose descriptive application context, identity, structure, and the actual prototype roster; Strategist compares them with the current communication contract and content, then derives the application plan automatically. |
For a compatible legacy-flat package, route SVG/spec/non-bitmaps to project `templates/`, bitmaps to project `images/`, and declared icons to project `icons/`. Do not infer legacy Master/Layout semantics from the flat directory shape.