AI turns documents or topics into real, native PowerPoint decks—with native shapes, transitions and animations, data-backed charts and tables on demand, audio narration from speaker notes, and support for your own .pptx templates. · by Hugo He
docs(templates): separate layout structure from deck application
hugohe3ac7df6cea450
diff --git a/docs/technical-design.md b/docs/technical-design.mdindex 9ede3821..fd6138f7 100644--- a/docs/technical-design.md+++ b/docs/technical-design.md@@ -310,17 +310,25 @@ All current Brand/Layout/Deck packages use one workspace routing contract. Brand`<template_workspace>` is either `skills/ppt-master/templates/<kind>/<id>/` or `projects/<name>/`. Step 3 receives that root. The workspace is portable between locations without reshaping; global index registration is the only scope-specific behavior. Empty optional directories are absent, and template application never copies `exports/`.-`standard` and `fidelity` write new SVG documents and a new Master/Layout/slot system; source topology is visual evidence only and is neither preserved nor distilled. `mirror` materializes a new workspace from the source page order, Master/Layout identities and parentage, placeholder facts, and supported visuals that are actually present and validated, without semantic synthesis or gap filling. Because structural layers cannot be `<g>`, fixed-layer source group wrappers are mechanically expanded into direct atoms while preserving ownership, paint order, and appearance.+`standard` and `fidelity` write new SVG documents and a new Master/Layout/slot system; source topology is visual evidence only and is neither preserved nor distilled. `mirror` materializes a new workspace from the source page order, Master/Layout identities and parentage, placeholder facts, and supported visuals that are actually present and validated, without semantic synthesis or gap filling. Layout mirror is legal only when that preserved source is already brand-neutral and application-neutral; otherwise author a new Layout or retain the facts as Deck. Because structural layers cannot be `<g>`, fixed-layer source group wrappers are mechanically expanded into direct atoms while preserving ownership, paint order, and appearance.The three template kinds own different segments of the design contract:| Kind | Owns | Typical contents | Effect on Strategist ||---|---|---|---|| `brand` | identity | colors, typography, logo, voice, icon style | locks identity; structure remains free |-| `layout` | structure | canvas, page structure, page types, SVG roster | locks structure; identity is confirmed in the Strategist confirmation stage |-| `deck` | identity + structure + template overview | complete identity + structure package | locks the full template grammar, with only content-specific choices left |+| `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 |-When several paths are supplied, fusion is segment-level, not field-level. A brand overrides the identity segment, a layout overrides the structure segment, and a deck supplies the middle/template-overview segment. Same-kind conflicts are surfaced as conflicts rather than resolved by implicit ordering. This keeps template composition debuggable: a fused spec can say exactly which bundle owns each segment.+Theme, Slide Master, Slide Layout, and Placeholder are compiled PowerPoint+objects, not additional template kinds. Layout owns topology, placement,+semantic text roles, and spatial behavior; Brand owns identity values and+assets. Under `template_reuse_scope: layout`, export resolves final placeholder+formatting from those rules plus the confirmed reading mode/type scale;+`mirror` preserves literal source formatting and text topology. Export may+place both rule sets into the same native Master/Layout graph.++When several paths are supplied, fusion is segment-level, not field-level. A brand overrides the identity segment, a layout overrides the structure segment, and a deck supplies the application segment. A Layout may replace Deck structure only when its page roles and slots can express the Deck's required narrative/content roles; otherwise fusion surfaces a conflict. A project-local Brand + Layout composition gets its application context from Stage 1 and is not automatically promoted into a reusable library Deck. Same-kind conflicts are surfaced rather than resolved by implicit ordering. This keeps template composition debuggable: a fused spec can say exactly which bundle owns each segment.**Raw PPTX templates are outside Step 3.** A `.pptx` may be source material, and PPTX intake can extract its identity and geometry. But a raw PPTX template plus a request to generate a new PPTX routes to `template-fill`, because the user's expectation is native slide cloning and text/table/chart replacement. The SVG route can consume only a reusable template workspace; to use a PPTX's design language in the SVG route, the PPTX must first pass through `create-template`, then the resulting workspace-root path can be supplied to Step 3.@@ -589,7 +597,7 @@ Supporting files stay separate only to keep route contracts focused and load opt| Class | Runbooks | Owning route ||---|---|---|| Generation profile | `beautify-pptx` | Generate PPTX with wording, page count, and page order frozen 1:1 |-| Template child workflows | `create-brand`, `create-layout`, `create-deck` | Create Template dispatches exactly one based on identity-only, structure-only, or integrated intent |+| Template child workflows | `create-brand`, `create-layout`, `create-deck` | Create Template dispatches exactly one for identity-only, brand-neutral/application-neutral structure, or a recurring application with integrated identity/structure || Generation stages | `topic-research`, `resume-execute`, `refine-spec`, `verify-charts`, `visual-review`, `live-preview`, `customize-animations` | Generate PPTX at their defined intake, planning, editing, quality, or post-processing points || Shared stage | `generate-audio` | Generate PPTX post-processing or Enhance Native PPTX narration integration || Governance | `failure-recovery` | Global stop/continue policy for all four routes; concrete recovery matrix and resume pointers for Generate PPTX |diff --git a/docs/templates-architecture.md b/docs/templates-architecture.mdindex 65629fcb..73468b79 100644--- a/docs/templates-architecture.md+++ b/docs/templates-architecture.md@@ -15,14 +15,14 @@| Kind | Library workspace root | What it writes | What it does NOT write | Originating workflow ||---|---|---|---|---|| **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>/` | Structure segment only: canvas / page structure / page types / SVG roster | No brand identity (no logo, no locked brand color) | `workflows/create-template/create-layout.md` |-| **Deck** | `templates/decks/<id>/` | All segments: identity + structure + middle (template overview) | — | `workflows/create-template/create-deck.md` (default child) |+| **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` |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.-The three are **parallel reference bundles**. In library scope, the physical directory and the frontmatter `kind` field correspond one-to-one:+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` must also retain an accurate `kind`: `deck` when both identity and structure are present, `layout` when only structure is present, and `brand` when only identity is present. The Strategist confirmation page uses this field to show `adaptive / strict` only for Deck/Layout 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 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.```yaml# templates/brands/anthropic/templates/design_spec.md@@ -46,6 +46,26 @@ native_structure_mode: structured---```+### Native PowerPoint objects are compilation targets++Project template kinds do not map one-to-one to PresentationML objects:++| Project contract | Native projection |+|---|---|+| **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 |++A Slide Master may contain both structural geometry and brand visuals. Source+ownership remains separated—Layout owns topology, placement, semantic text+roles, and spatial behavior; Brand owns identity values and assets. Under+downstream `layout` scope, export resolves final placeholder formatting from+those rules plus the confirmed reading mode/type scale; `mirror` preserves+literal source formatting and text topology. Export then compiles the+applicable rules into the same native Master/Layout graph. Theme is therefore+an implementation projection of resolved identity—whether supplied by Brand,+Deck, or the current project—not a fourth template kind.+### Output scope is separate from kind`create-template` confirms where a Layout/Deck workspace is placed. This execution choice does not add a fourth kind and does not add a PPTX structure mode:@@ -89,13 +109,29 @@ 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 |-| **Middle** | Template Overview (use cases / design intent / page rhythm narrative) | deck only; brand / layout don't write this |+| **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 |### Why Deck is its own kind-A deck is the **full identity + structure reference** derived from an existing PPT or confirmed design direction — its geometry, color palette, and typefaces form one coherent system. Its value is "validated cohesion", which a free layout + brand combo can't always reach.--Its construction depends on replication mode. `standard` / `fidelity` author a new system from visual reference; mirror maps validated source identities and parentage one-to-one into a new workspace. Once packaged, either form is a complete reference solution that can be overridden by an explicitly supplied brand or layout.+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.++`standard` / `fidelity` author a new complete system from confirmed evidence;+mirror maps validated source identities and parentage one-to-one into a new+workspace. Mirror preserves source facts but does not prove that the source is+a reusable Deck: creation still has to identify the stable application rules.+A source that yields only identity becomes Brand; a brand-neutral reusable+structure becomes Layout; a branded structural system or scenario-bearing+content grammar becomes Deck.++This also constrains creation mode: Layout mirror is valid only when the source+contract is already brand-neutral and application-neutral. Removing brand+paint, fonts, logos, fixed identity objects, or reusable application rules is+authorship, so a source outside that boundary must either use `standard` /+`fidelity` to create a new Layout or retain those facts as Deck mirror.---@@ -154,18 +190,23 @@ page_types: [<cover, toc, chapter, content, ending, ...>]---```-**Body sections** (personality-only structure segment)+**Body sections** (package-specific structure segment)| § | Title | Required fields ||---|---|---|-| IV | Signature Design Elements | Layout-specific grid, zones, image behavior, density rhythm, neutral framing, and slot conventions |+| IV | Signature Design Elements | Layout-specific grid, zones, image behavior, density rhythm, neutral framing, semantic text roles, alignment/wrapping/capacity behavior, and slot conventions || V | Page Roster | Every SVG file, Layout key, picker name, intended content, and slot behavior |`Placeholder Overrides` is conditional and appears only when the layout changesthe canonical authoring vocabulary. The frontmatter `summary` carries conciseselection context. Layouts omit the deck-only Template Overview.-**Forbidden**: Color Scheme, Typography, brand logo, brand voice & tone, Icon Style, or official-truth color (`provenance: fact`). Neutral SVG paint is allowed only as review scaffolding; it is not an identity segment. Color and typography are decided in the Strategist confirmation stage or supplied by another template kind.+`category: scenario` is discovery fit only. A Layout may be optimized for a+content shape or delivery setting, but it must not prescribe the communication+objective, audience outcome, required narrative sequence, fixed boilerplate,+or example content. If those rules are reusable, create a Deck instead.++**Forbidden**: Color Scheme, brand typeface/weight identity, final resolved type scale, brand logo, brand voice & tone, Icon Style, or official-truth color (`provenance: fact`). A Layout may retain semantic text roles, alignment, wrapping, and capacity because those are structural; neutral SVG paint/font/size values are review scaffolding only. Final color and typography are resolved in the Strategist confirmation stage or supplied by another template kind.### Deck schema@@ -177,7 +218,7 @@ deck_id: <slug>kind: deckcategory: brand | general | scenario | government | specialnative_structure_mode: structured-summary: <one-line use cases>+summary: <one-line recurring presentation family and intended outcome>keywords: [tag1, tag2, tag3]canvas_format: <ppt169 | ...>canvas_width: <pixels>@@ -192,11 +233,11 @@ primary_color: "<HEX>"---```-**Body sections** (personality-only complete reference)+**Body sections** (application + integrated identity/structure)| § | Title | Segment ||---|---|---|-| I | Template Overview | Middle |+| I | Template Overview | Application || II | Color Scheme | Identity || III | Typography | Identity; omit only when the shared default stack is used || IV | Signature Design Elements | Template-specific identity motifs and reusable structural grammar |@@ -204,12 +245,19 @@ 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.+Portable canvas fields, `page_count`, and the explicit SVG roster carry therest of the structure contract. General spacing, font-ratio, SVG, andplaceholder rules remain centralized and are not copied into each deck spec.-Deck still owns the complete identity + structure reference; omitted-conditional sections mean “shared default or no asset”, not “another kind owns-this segment”.+Omitted conditional sections mean “shared default or no asset”, not “another+kind owns this segment”.---@@ -254,7 +302,7 @@ These indexes cover library scope only. A project-root workspace is intentionall```json{"<deck_id>": {- "summary": "China Telecom government-enterprise briefing deck",+ "summary": "China Telecom government-enterprise briefing for explaining a plan and aligning next actions","canvas_format": "ppt169","page_count": 5,"primary_color": "#XXXXXX"@@ -263,7 +311,8 @@ These indexes cover library scope only. A project-root workspace is intentionall```- Includes `primary_color` (decks carry identity) + structural metadata-- Does not expand `page_types` — decks share the same page-type set as layouts; redundant to record+- `summary` leads with the recurring presentation family and outcome, not merely visual tone+- The detailed application contract stays in Template Overview; this compact index does not duplicate it---@@ -279,10 +328,17 @@ When the user supplies a set of paths in their initial message, Step 3 fuses the| brand only | Copy brand wholesale; structure stays free design || layout only | Copy layout wholesale; identity stays free design (Strategist fields e/f/g decide) || deck only | Copy deck wholesale |-| brand + layout | brand provides identity, layout provides structure (follows existing SKILL.md fusion table) |-| brand + deck | brand overrides deck's identity segment at segment level; structure + middle come from deck |-| layout + deck | layout overrides deck's structure segment at segment level; identity + middle come from deck |-| brand + layout + deck | brand overrides identity + layout overrides structure + deck provides middle; deck's original identity/structure segments are discarded wholesale |+| brand + layout | brand provides identity, layout provides structure; this is a project-local assembled input, not a reusable Deck application contract |+| brand + deck | brand overrides deck's identity segment at segment level; structure + application come from deck |+| layout + deck | layout may override deck structure only when it can express the Deck's required narrative/content roles; identity + application come from deck |+| brand + layout + deck | brand overrides identity + a compatible layout overrides structure + deck provides application; deck's original identity/structure segments are discarded wholesale |++Before applying a Layout override to a Deck, compare the Deck application+contract against the Layout's page roles, slot types, and capacity. If a+required role cannot be represented, surface a fusion conflict: keep the Deck+structure, choose another Layout, or explicitly revise the application+contract. Never retain an application promise that the selected structure+cannot satisfy.### Whole-segment replacement (default granularity)@@ -344,7 +400,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. Brand supplies identity constraints while structure stays free; Layout and Deck expose structural capabilities, but Stage 2 still decides whether the project should consume them 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 and structure actually retained by that scope. The detailed rules live in `references/strategist.md` and `spec_lock_reference.md`.+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. The detailed rules live in `references/strategist.md` and `spec_lock_reference.md`.---@@ -355,7 +411,7 @@ Installing a template does not narrow away the communication question. Stage 1 a| `workflows/create-template.md` | Fixed Create Template entry and shared scope, confirmation, preflight, structured-authoring, registration, completion, and handoff contract; dispatches exactly one child workflow || `workflows/create-template/create-brand.md` | Identity-only Brand workspace; no SVG roster and empty optional directories are omitted || `workflows/create-template/create-layout.md` | Brand-neutral structural Layout workspace with a structured SVG roster |-| `workflows/create-template/create-deck.md` | Integrated identity-and-structure Deck workspace with a structured SVG roster; selected by default when both segments are requested |+| `workflows/create-template/create-deck.md` | Recurring application contract with integrated identity/structure and a structured SVG roster; selected when the reusable artifact is branded or scenario-bearing, not merely because the source is a complete PPTX |In library scope, the frontmatter `kind` field determines which workspace parent is used under `templates/brands/` / `templates/layouts/` / `templates/decks/`. Project scope keeps the same kind semantics at the project workspace root. A complete workspace may move between scopes without reshaping; add or remove only the library index registration.@@ -367,3 +423,5 @@ In library scope, the frontmatter `kind` field determines which workspace parent- **No batch conflict resolution for three or more of the same kind** — ask the user to narrow it down in chat first- **No bilingual name mapping table** — templates are named in their brand / scenario's native language (Chinese templates use Chinese names; English templates use snake_case); no forced unification- **No output-scope structure fork or CLI flag** — output scope is a `create-template` brief decision; both layout/deck scopes declare `native_structure_mode: structured`+- **No fourth Theme kind** — Theme projects resolved identity from Brand, Deck, or the current project; it is not a separate user-facing reusable contract+- **No automatic promotion of Brand + Layout into a reusable library Deck** — the composition may route as a project-local deck-capability bundle, while a reusable Deck still requires an application contractdiff --git a/docs/templates-guide.md b/docs/templates-guide.mdindex bb6feebe..e5c5c43f 100644--- a/docs/templates-guide.md+++ b/docs/templates-guide.md@@ -4,7 +4,7 @@----A PPT Master template is a reusable workspace with one of three explicit kinds: **Brand** owns identity, **Layout** owns reusable page structure, and **Deck** owns both plus deck-specific overview context. Layout and Deck workspaces include complete SVG prototypes with declared Master / Layout / slot contracts; Brand workspaces intentionally have no SVG roster. Each workspace's `design_spec.md` and matching assets declare exactly what that kind contributes.+A PPT Master template is a reusable workspace with one of three explicit kinds: **Brand** owns identity, **Layout** owns brand-neutral reusable page structure, and **Deck** owns a recurring presentation application together with integrated identity and structure. Layout and Deck workspaces include complete SVG prototypes with declared Master / Layout / slot contracts; Brand workspaces intentionally have no SVG roster. Each workspace's `design_spec.md` and matching assets declare exactly what that kind contributes.This guide answers three questions:@@ -29,8 +29,16 @@ Choose the workspace kind by what must be reused:| Kind | Reuses | Native PowerPoint result ||---|---|---|| **Brand** | Color, typography, logo, voice, icon style | Identity constraints only. Generated pages remain Slide-local under one clean project Master and Blank Layout. |-| **Layout** | Page grammar, Master/Layout identities, slots, and layout roster | A structured deck with reusable native Masters, named Layouts, and placeholders; identity is chosen separately. |-| **Deck** | Brand identity and page structure together | A structured deck with the template's complete identity plus reusable native Masters, named Layouts, and placeholders. |+| **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. |++Theme, Slide Master, Slide Layout, and Placeholder are native PowerPoint+objects, not additional workspace kinds. Brand and Layout rules are compiled+into those objects. Under `layout` reuse, semantic text roles come from Layout+while final font and type scale are resolved from identity and reading mode;+`mirror` instead keeps literal source formatting. A final Master may contain+both structural geometry and brand visuals even though their source contracts+stay separate.The two rules that prevent most mistakes:@@ -99,15 +107,15 @@ 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) — complete identity + structure workspaces, including deck-specific overview context+- [`decks_index.json`](../skills/ppt-master/templates/decks/decks_index.json) — recurring presentation applications with integrated identity, structure, and content-reuse rulesAsk "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 use `pptx_structure.mode: structured`, because they contribute an explicit reusable Master / Layout / slot contract.+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`.-> Rule of thumb: use a Brand workspace when identity must be fixed, a Layout workspace when page structure must be reused, and a Deck workspace when both must travel together. Use free design when the deck should develop its own composition from the content.+> 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.### Styles are not templates@@ -147,7 +155,7 @@ Please use the /create-template workflow to generate a new template based on theThe workflow will then **mandatorily** confirm a template brief with you before doing anything (this gate cannot be skipped).-The entry name always remains **Create Template**. It dispatches exactly one child workflow: Create Brand for identity only, Create Layout for brand-neutral structure only, or Create Deck for identity and structure together (the default when both are needed). The selected child is not reconsidered inside the brief.+The entry name always remains **Create Template**. It dispatches exactly one child workflow: Create Brand for identity only, Create Layout for brand-neutral structure whose communication application remains open, or Create Deck for a branded structural system or recurring presentation application. A complete source PPTX alone does not determine the kind; the workflow classifies the stable rules worth reusing. The selected child is not reconsidered inside the brief.### Step 1 — Prepare a reference bundle or brief@@ -175,7 +183,7 @@ The workflow does not silently infer values — before generation it lists these| **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. |+| **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 |@@ -201,6 +209,11 @@ This is the most easily confused decision when deriving a structured template. C| 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.+**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.**About native PowerPoint shapes**: the lossless import SVG stays immutable in the temporary analysis workspace as native-payload backing. Template creation uses the lightweight editable `authoring-svg/` IR and its source-ref/hash manifest. Authored modes use project-canonical SVG and compact authored-preset groups only for exact registered preset matches. Mirror materializes final template SVGs from the IR, reusing converter-supported payload only for unchanged Slide-local/slot refs; fixed Master/Layout layers remain direct atoms, unsupported or edited objects keep the current SVG fallback, and final templates contain no IR-only refs.@@ -221,7 +234,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 recommends `mirror` only for a recurring artifact whose new content fits the existing page roles and text topology; use `layout` when the 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 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.### Step 4 — Validation, review export, registration, and discoverydiff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.mdindex f60388d5..fb69d02b 100644--- a/docs/zh/technical-design.md+++ b/docs/zh/technical-design.md@@ -312,17 +312,19 @@ PPT Master 不只服务 PPT——同一套 SVG → DrawingML 流水线还能产`<template_workspace>` 可以是 `skills/ppt-master/templates/<kind>/<id>/`,也可以是 `projects/<name>/`。Step 3 接收这个根目录。工作区可在两个位置之间迁移而不改形;唯一的范围差异是全局索引注册。空的可选目录不创建,`exports/` 也不会复制进新项目。-`standard` 与 `fidelity` 会重新创作 SVG 和新的 Master/Layout/slot 系统;来源拓扑只作为视觉证据,不保留、也不蒸馏。`mirror` 把来源包内实际存在且已验证的页序、Master/Layout 身份与父子关系、placeholder 事实和受支持视觉物化到新工作区,不做语义归纳或缺口补造。由于结构层不能是 `<g>`,固定结构层的来源 group wrapper 只允许机械展开成直接原子,同时保持归属、paint order 和视觉一致。+`standard` 与 `fidelity` 会重新创作 SVG 和新的 Master/Layout/slot 系统;来源拓扑只作为视觉证据,不保留、也不蒸馏。`mirror` 把来源包内实际存在且已验证的页序、Master/Layout 身份与父子关系、placeholder 事实和受支持视觉物化到新工作区,不做语义归纳或缺口补造。只有被保留的来源本身已经品牌中立且应用中立时,Layout mirror 才合法;否则应重新创作 Layout,或把这些事实保留为 Deck。由于结构层不能是 `<g>`,固定结构层的来源 group wrapper 只允许机械展开成直接原子,同时保持归属、paint order 和视觉一致。三类模板拥有不同的设计契约片段:| Kind | 拥有的片段 | 典型内容 | 对 Strategist 的影响 ||---|---|---|---|| `brand` | 身份片段 | 配色、字体、logo、语气、图标风格 | 锁定身份;结构保持自由 |-| `layout` | 结构片段 | 画布、页面结构、页面类型、SVG roster | 锁定结构;身份仍在策略师确认阶段里确定 |-| `deck` | 身份 + 结构 + 模板总览 | 完整身份 + 结构包 | 锁定完整模板语法,只剩内容相关选择 |+| `layout` | 品牌中立的结构片段 | 画布、页面结构、语义文字角色/空间行为、页面类型、SVG roster | 提供结构能力;身份与沟通应用仍由下游决定 |+| `deck` | 应用段 + 一体化身份/结构 | 重复场景、受众与结果、内容政策、身份和 SVG roster | 提供应用契约;Stage 2 推导将其与独立确认的 Stage-1 契约对照,再选择复用范围 |-当用户提供多个路径时,融合是**片段级**而不是字段级:brand 覆盖身份片段,layout 覆盖结构片段,deck 提供中间的 template overview 片段。同类冲突会被显式列为冲突,而不是按输入顺序默默决定。这样融合后的 spec 能明确说明每个片段来自哪里,便于审计和复现。+Theme、Slide Master、Slide Layout 与 Placeholder 是编译生成的 PowerPoint 原生对象,不是新的模板 kind。Layout 决定拓扑、位置、语义文字角色与空间行为,Brand 决定身份值与资产。`template_reuse_scope: layout` 会结合已确认的阅读模式和字号体系解析最终 placeholder 格式;`mirror` 则保留来源的字面格式与文字拓扑。两类规则都可编译进同一套原生 Master/Layout 图谱。++当用户提供多个路径时,融合是**片段级**而不是字段级:brand 覆盖身份片段,layout 覆盖结构片段,deck 提供应用段。只有 Layout 的页面角色和槽位能够表达 Deck 的必需叙事/内容角色时,才能覆盖 Deck 结构,否则必须显式提出合成冲突。项目内 Brand + Layout 组合的应用语境来自 Stage 1,不会自动升级成可注册的 Deck。同类冲突也会显式列出,而不是按输入顺序默默决定。这样融合后的 spec 能明确说明每个片段来自哪里,便于审计和复现。**原生 PPTX 模板不属于 Step 3。** `.pptx` 可以作为源材料进入流水线,PPTX intake 也能抽取其身份和几何信息。但“给一个原生 PPTX 模板并生成新 PPTX”的请求会进入 `template-fill`,因为用户期望的是克隆 PowerPoint 页面壳并替换文本 / 表格 / 图表。SVG 路线只能消费可复用模板工作区;如果要把某个 PPTX 的设计语言用于 SVG 路线,必须先通过 `create-template` 生成工作区,再把工作区根目录路径提供给 Step 3。@@ -591,7 +593,7 @@ ChartEx 导入被有意限制为 7 个已验证数据模型:`treemap`、`sunbu| 分类 | 文档 | 归属路线 ||---|---|---|| 生成 profile | `beautify-pptx` | Generate PPTX;逐字措辞、页数与页序 1:1 冻结 |-| 模板子工作流 | `create-brand`、`create-layout`、`create-deck` | Create Template 根据“仅身份 / 仅结构 / 身份与结构一体化”只分派其中一个 |+| 模板子工作流 | `create-brand`、`create-layout`、`create-deck` | Create Template 在“仅身份 / 品牌中立且应用中立的结构 / 应用契约与身份结构一体化”中只分派一个 || 生成阶段 | `topic-research`、`resume-execute`、`refine-spec`、`verify-charts`、`visual-review`、`live-preview`、`customize-animations` | Generate PPTX 中各自定义的 intake、planning、editing、quality 或 post-processing 节点 || 共享阶段 | `generate-audio` | Generate PPTX 后处理,或 Enhance Native PPTX 的旁白集成 || 治理文档 | `failure-recovery` | 四条顶层路线的全局停止 / 继续规则;Generate PPTX 的具体故障矩阵与续跑入口 |diff --git a/docs/zh/templates-architecture.md b/docs/zh/templates-architecture.mdindex 36bc1ae3..03f18a82 100644--- a/docs/zh/templates-architecture.md+++ b/docs/zh/templates-architecture.md@@ -15,14 +15,14 @@| 分类 | 全局库工作区根目录 | 写什么 | 不写什么 | 出处工作流 ||---|---|---|---|---|| **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 | 不写品牌身份(无 logo、无品牌色硬约束) | `workflows/create-template/create-layout.md` |-| **Deck** | `templates/decks/<id>/` | 全段:身份段 + 结构段 + 中间段(template overview) | —— | `workflows/create-template/create-deck.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` |每张新建的 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 已满足当前合同时才兼容;带旧结构语义的包必须替换为新建模板工作区,不能原地升级。-三者是**三种并列的 reference bundle**。在全局库范围内,物理目录与 frontmatter `kind` 字段双向对齐:+三者是**三种并列的可复用规则包**,不是 PowerPoint 包对象类型。在全局库范围内,物理目录与 frontmatter `kind` 字段双向对齐:-多路径合成后的项目级 `design_spec.md` 也必须保留准确的 `kind`:同时具备身份段和结构段时为 `deck`,只有结构段时为 `layout`,只有身份段时为 `brand`。Strategist 确认页据此只对真正包含页面结构的 Deck/Layout 显示 `adaptive / strict`。+多路径合成后的项目级 `design_spec.md` 沿用现有路由 `kind`:同时具备身份段和结构段时为 `deck`,只有结构段时为 `layout`,只有身份段时为 `brand`。对于项目内临时组合的 Brand + Layout,这个标签只表示“已安装两种能力”,不会把组合自动提升为可注册的 Deck,也不会凭空生成应用契约;当前项目的 Stage 1 沟通契约负责提供场景。Strategist 确认页据此只对真正包含页面结构的 bundle 显示 `adaptive / strict`。```yaml# templates/brands/anthropic/templates/design_spec.md@@ -46,6 +46,18 @@ native_structure_mode: structured---```+### PowerPoint 原生对象是编译目标++项目模板 kind 与 PresentationML 对象不是一一对应关系:++| 项目合同 | 原生投影 |+|---|---|+| **Brand** | Theme 的颜色、字体与效果,以及 Logo 等固定身份资产规则 |+| **Layout** | Master/Layout/Placeholder 拓扑、可复用几何、语义文字角色与槽位空间行为 |+| **Deck** | Brand 与 Layout 的投影,再加面向用途的起始内容和使用规则 |++一个 Slide Master 可以同时包含结构几何和品牌视觉。来源规则仍分开归属:Layout 决定拓扑、位置、语义文字角色与空间行为,Brand 决定身份值与资产。下游选择 `layout` 时,导出结合已确认的阅读模式和字号体系解析最终 placeholder 格式;选择 `mirror` 时则保留来源的字面格式与文字拓扑。最后再把适用规则编译进同一套 Master/Layout 图谱。因此 Theme 是已解析身份的实现投影——身份可以来自 Brand、Deck 或当前项目——而不是第四种模板 kind。+### 输出范围与 kind 相互独立`create-template` 会确认 Layout/Deck 工作区放在哪里。这个执行选择不会增加第四种 kind,也不会增加新的 PPTX 结构模式:@@ -87,13 +99,15 @@ 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(use cases / design intent / page rhythm 等叙事字段)| deck 独有;brand / layout 不写 |+| **应用段** | Template Overview:重复场景、受众与结果、交付假设、稳定叙事/页面角色及内容复用政策 | deck 独有;brand / layout 不写 |### 为什么需要 Deck 这一类-Deck 是从一份现存 PPT 或明确设计方向形成的完整身份与结构参考——配色、字体、视觉节奏与页面类型共同组成一个整体。它的价值是「已验证的整体感」,是 layout + brand 自由拼合未必能达到的成品。+Deck 编码的是**一类可重复演示**,而不只是预先组合好的 Brand 和 Layout。它要说明模板服务哪些沟通场景、支持哪些受众结果、哪些叙事或页面角色会稳定重复,以及起始内容应保留、替换还是删除。身份与结构围绕这份应用契约形成一个整体。-它的构建方式由 replication mode 决定:`standard` / `fidelity` 根据视觉参考创作新系统;mirror 把已验证的来源身份与父子关系一对一映射进新工作区。打包完成后,两者都作为可被显式 brand / layout 覆盖的完整参考方案使用。+`standard` / `fidelity` 根据已确认的证据创作新完整系统;mirror 把已验证的来源身份与父子关系一对一映射进新工作区。Mirror 能保留来源事实,但不能单独证明来源就是可复用 Deck:创建时仍要识别稳定的应用规则。只得到身份时创建 Brand;得到品牌中立的可复用结构时创建 Layout;结构带品牌身份,或者包含场景叙事与内容语法时创建 Deck。++这也约束创建模式:只有来源合同本身已经品牌中立且应用中立时,Layout mirror 才成立。删除品牌色、字体、Logo、固定身份对象或可复用应用规则都属于重新创作;越过这条边界的来源要么使用 `standard` / `fidelity` 创作新的 Layout,要么保留这些事实并创建 Deck mirror。---@@ -152,17 +166,19 @@ page_types: [<cover, toc, chapter, content, ending, ...>]---```-**正文章节**(personality-only 的结构段)+**正文章节**(该包特有的结构段)| 节 | 标题 | 必写字段 ||---|---|---|-| IV | Signature Design Elements | 该 Layout 特有的网格、区域、图片行为、密度节奏、中性框架和 slot 约定 |+| IV | Signature Design Elements | 该 Layout 特有的网格、区域、图片行为、密度节奏、中性框架、语义文字角色、对齐/换行/容量行为和 slot 约定 || V | Page Roster | 每个 SVG 文件、Layout key、picker name、适用内容与 slot 行为 |只有 Layout 改写规范占位词汇时才增加 `Placeholder Overrides`。frontmatter`summary` 承担简短的选型语境;Layout 不写 deck 独有的 Template Overview。-**不允许出现**:Color Scheme、Typography、品牌 logo、品牌 voice & tone、Icon Style 或官方真值色(`provenance: fact`)。SVG 可以使用便于审阅的中性预览 paint,但它不属于身份段;色彩与字体由 策略师确认阶段或其他模板 kind 决定。+`category: scenario` 只表示发现时的适配标签。Layout 可以针对某种内容形态或交付环境优化几何,但不能规定沟通目的、受众结果、必需叙事顺序、固定措辞或示例内容;如果这些规则也要重复使用,应创建 Deck。++**不允许出现**:Color Scheme、品牌字体家族/字重身份、最终字号体系、品牌 logo、品牌 voice & tone、Icon Style 或官方真值色(`provenance: fact`)。Layout 可以保留语义文字角色、对齐、换行与容量规则,因为它们属于结构;SVG 中性 paint、字体和字号只用于审阅。最终色彩与字体由策略师确认阶段或其他模板 kind 解析。### Deck schema@@ -174,7 +190,7 @@ deck_id: <slug>kind: deckcategory: brand | general | scenario | government | specialnative_structure_mode: structured-summary: <一句话描述用途>+summary: <一句话描述可重复演示类型与预期结果>keywords: [tag1, tag2, tag3]canvas_format: <ppt169 | ...>canvas_width: <像素>@@ -189,11 +205,11 @@ primary_color: "<HEX>"---```-**正文章节**(personality-only 的完整参考)+**正文章节**(应用契约 + 一体化身份/结构)| 节 | 标题 | 归属段 ||---|---|---|-| I | Template Overview | 中间段 |+| I | Template Overview | 应用段 || II | Color Scheme | 身份段 || III | Typography | 身份段;只有使用共享默认字体栈时才省略 || IV | Signature Design Elements | 模板特有的身份图形与可复用结构语法 |@@ -201,7 +217,9 @@ primary_color: "<HEX>"| VI | Assets | 身份/支撑资产;无资产时省略 || VII | Placeholder Overrides | 结构词汇;无覆盖时省略 |-可移植 canvas 字段、`page_count` 和显式 SVG roster 承载其余结构合同。通用间距、字号比例、SVG 和 placeholder 规则保持集中管理,不复制进每个 deck spec。Deck 仍拥有完整身份 + 结构;省略条件章节只表示“采用共享默认值或没有资产”,不表示该段改由其他 kind 所有。+Template Overview 必须写明可重复演示类型、目标受众与结果、交付/阅读假设、稳定叙事或页面角色,以及固定、可替换、可选、仅示例内容之间的复用边界。Page Roster 除 Master/Layout/slot 合同外,还必须说明每个原型的内容政策。这些政策用于选型,不要求每次生成都保持相同页数或页序。++可移植 canvas 字段、`page_count` 和显式 SVG roster 承载其余结构合同。通用间距、字号比例、SVG 和 placeholder 规则保持集中管理,不复制进每个 deck spec。省略条件章节只表示“采用共享默认值或没有资产”,不表示该段改由其他 kind 所有。---@@ -246,7 +264,7 @@ primary_color: "<HEX>"```json{"<deck_id>": {- "summary": "China Telecom government-enterprise briefing deck",+ "summary": "中国电信政企方案说明与下一步对齐汇报","canvas_format": "ppt169","page_count": 5,"primary_color": "#XXXXXX"@@ -255,7 +273,8 @@ primary_color: "<HEX>"```- 含 `primary_color`(deck 自带身份)+ 结构元数据-- 不展开 `page_types` —— deck 的页面类型与 layout 的相同集合,不冗余记录+- `summary` 优先描述可重复演示类型与预期结果,而不只是视觉气质+- 详细应用契约留在 Template Overview;紧凑索引不重复整份契约---@@ -271,10 +290,12 @@ primary_color: "<HEX>"| 只 brand | 复制 brand 全部,结构走自由设计 || 只 layout | 复制 layout 全部,身份走自由设计(策略师确认阶段 e/f/g 决策) || 只 deck | 复制 deck 全部 |-| brand + layout | brand 提供身份段 + layout 提供结构段,沿用 SKILL.md 现有 fusion 表 |-| brand + deck | brand 段级覆盖 deck 的身份段,结构段与中间段从 deck 拿 |-| layout + deck | layout 段级覆盖 deck 的结构段,身份段与中间段从 deck 拿 |-| brand + layout + deck | brand 覆盖身份 + layout 覆盖结构 + deck 提供中间段;身份/结构段的 deck 原值整段丢弃 |+| brand + layout | brand 提供身份段 + layout 提供结构段;这是项目内组合输入,不是可复用 Deck 应用契约 |+| brand + deck | brand 段级覆盖 deck 的身份段,结构段与应用段从 deck 拿 |+| layout + deck | 只有 layout 能表达 Deck 的必需叙事/内容角色时才覆盖结构段;身份段与应用段从 deck 拿 |+| brand + layout + deck | brand 覆盖身份 + 兼容的 layout 覆盖结构 + deck 提供应用段;身份/结构段的 deck 原值整段丢弃 |++Layout 覆盖 Deck 前,必须把 Deck 应用契约与 Layout 的页面角色、槽位类型和容量对照。如果必需角色无法表达,就把它作为合成冲突交给用户:保留 Deck 结构、改选 Layout,或明确修改应用契约。不能保留一份当前结构无法兑现的场景承诺。### 段级整段替换(默认粒度)@@ -334,7 +355,7 @@ AI: 你给了两个 brand,检测到段级冲突:### 策略师确认阶段在不同 kind 下的行为-安装模板不会让沟通问题消失。Stage 1 始终确认同一份开放式沟通契约。Brand 提供身份约束、结构仍然自由;Layout 与 Deck 提供可用的结构能力,但 Stage 2 仍要根据场景判断,在合法范围内选择 `mirror`、`layout` 或 `style`。因此,按 mirror 创建的工作区只是允许原样复用,不会自动选中原样复用。Stage 3 再用该消费范围实际保留的身份与结构实现已确认方向。具体规则落在 `references/strategist.md` 与 `spec_lock_reference.md`。+安装模板不会让沟通问题消失。Stage 1 始终独立确认同一份开放式沟通契约。Brand 提供身份约束、结构仍然自由;Layout 提供结构能力;Deck 还提供应用契约。Stage 2 推导时才把已保存的应用契约与当前确认结果对照,不能静默当成真值,再根据场景在合法范围内选择 `mirror`、`layout` 或 `style`。因此,按 mirror 创建的工作区只是允许原样复用,不会自动选中原样复用。Stage 3 再用该消费范围实际保留的身份、结构与应用规则实现已确认方向。具体规则落在 `references/strategist.md` 与 `spec_lock_reference.md`。---@@ -345,7 +366,7 @@ AI: 你给了两个 brand,检测到段级冲突:| `workflows/create-template.md` | 固定 Create Template 入口,以及范围、确认、预检、结构创作、注册、完成和交接的共享合同;只分派一个子工作流 || `workflows/create-template/create-brand.md` | 仅身份的 Brand 工作区;无 SVG roster,空的可选目录省略 || `workflows/create-template/create-layout.md` | 品牌中立、带结构化 SVG roster 的 Layout 工作区 |-| `workflows/create-template/create-deck.md` | 身份与结构一体化、带结构化 SVG roster 的 Deck 工作区;两段都需要时默认选择 |+| `workflows/create-template/create-deck.md` | 应用契约与身份/结构一体化、带结构化 SVG roster 的 Deck 工作区;可复用成果带品牌身份或场景语义时选择,不能只因来源是一份完整 PPTX 就默认选择 |在全局库范围,frontmatter `kind` 字段决定工作区父目录位于 `templates/brands/` / `templates/layouts/` / `templates/decks/`。项目范围在项目工作区根目录保留同一 kind 语义。完整工作区可在两种范围之间移动而不改形,只需增加或移除全局索引注册。@@ -357,3 +378,5 @@ AI: 你给了两个 brand,检测到段级冲突:- **不为同类三份及以上设计批量冲突解决** —— 用户先在 chat 里收敛到两份- **不引入双名映射表** —— 模板命名按其品牌/场景母语(中文模板用中文名,英文模板用 snake_case),不强制统一- **不为输出范围新增结构分支或 CLI flag** —— 输出范围是 `create-template` 简报里的执行选择;两种范围的 Layout/Deck 都声明 `native_structure_mode: structured`+- **不增加第四种 Theme kind** —— Theme 投影 Brand、Deck 或当前项目解析后的身份,不是新的用户侧复用合同+- **不把 Brand + Layout 自动提升成可注册的 Deck** —— 项目内组合可以按同时具备身份/结构能力来路由,但可复用 Deck 仍必须包含应用契约diff --git a/docs/zh/templates-guide.md b/docs/zh/templates-guide.mdindex aa73d554..1e3cc2f6 100644--- a/docs/zh/templates-guide.md+++ b/docs/zh/templates-guide.md@@ -4,7 +4,7 @@----PPT Master 模板是一种可复用工作区,明确分为三类:**Brand** 只拥有身份系统,**Layout** 只拥有可复用页面结构,**Deck** 同时拥有两者及 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 实际提供什么。本文回答三个问题:@@ -29,8 +29,10 @@ PPT Master 模板是一种可复用工作区,明确分为三类:**Brand**| Kind | 复用什么 | 原生 PowerPoint 结果 ||---|---|---|| **Brand** | 颜色、字体、Logo、语调、图标风格 | 只提供身份约束。生成页面保持 Slide 本地,文件只有干净的项目 Master 与 Blank Layout 脚手架。 |-| **Layout** | 页面语法、Master/Layout 身份、槽位与版式 roster | 结构化 deck,包含可复用原生 Master、具名 Layout 与 placeholder;身份系统另行选择。 |-| **Deck** | 品牌身份与页面结构一起复用 | 结构化 deck,同时带完整身份系统和可复用原生 Master、具名 Layout 与 placeholder。 |+| **Layout** | 品牌中立的页面语法、Master/Layout 身份、语义文字角色、槽位与版式 roster | 结构化 deck,包含可复用原生 Master、具名 Layout 与 placeholder;身份、阅读模式字号和沟通应用另行解析。 |+| **Deck** | 一类可重复演示:应用规则、身份、页面结构与起始内容政策 | 结构化 deck,同时带一体化身份、可复用原生结构和面向场景的起始规则。 |++Theme、Slide Master、Slide Layout 与 Placeholder 是 PowerPoint 原生对象,不是新的工作区 kind。Brand 与 Layout 的规则会被编译进这些对象。使用 `layout` 时,语义文字角色来自 Layout,最终字体和字号体系由身份与阅读模式共同解析;使用 `mirror` 时则保留来源的字面格式。最终 Master 可以同时包含结构几何和品牌视觉,但来源合同仍保持分离。最容易避免误用的两条规则:@@ -99,15 +101,15 @@ Layout 工作区:skills/ppt-master/templates/layouts/presentation_core/- [`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) — 完整身份 + 结构工作区,包含 deck 专属概览信息+- [`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 工作区使用 `pptx_structure.mode: structured`,因为它们提供显式可复用的 Master / Layout / slot 合同。+自由设计不是“没有结构”或“没有风格”——Strategist 仍会为这份 deck 规划叙事、层级与视觉系统,但生成页面使用 `pptx_structure.mode: flat`,所有可见对象都保留在 Slide 本地。仅使用 Brand 工作区时同样保持 `flat`,只是由 Brand 提供身份约束。Layout 与 Deck 工作区提供可复用 Master / Layout / slot 合同:确认使用 `mirror` 或 `layout` 时通过 `pptx_structure.mode: structured` 消费;确认使用 `style` 时则有意舍弃原生结构并生成 `flat`。-> 经验:需要锁定身份系统时用 Brand,需要复用页面结构时用 Layout,两者都要一起复用时用 Deck;希望版式从内容出发重新生长时走自由设计。+> 经验:需要锁定身份系统时用 Brand;需要复用品牌中立结构、但让用途保持开放时用 Layout;需要把品牌化结构或可重复沟通场景作为一份契约复用时用 Deck;希望版式从当前内容出发重新生长时走自由设计。### 风格不是模板@@ -147,7 +149,7 @@ Strategist 会把方向拆成两个彼此独立的选择:接下来工作流会**强制**先和你确认一份模板简报(不允许跳过)。-入口名称始终保持 **Create Template**。它只分派一个子工作流:仅复用身份走 Create Brand,仅复用品牌中立的结构走 Create Layout,身份与结构一起复用走 Create Deck(两者都需要时默认选它)。子工作流一旦选定,不会在简报里再次选 kind。+入口名称始终保持 **Create Template**。它只分派一个子工作流:仅复用身份走 Create Brand;复用品牌中立结构、且沟通应用保持开放时走 Create Layout;复用品牌化结构或可重复演示应用时走 Create Deck。来源是一份完整 PPTX 并不会自动决定 kind,工作流只按真正稳定、值得重复使用的规则分类。子工作流一旦选定,不会在简报里再次选 kind。### 第一步:准备参考材料包或简报@@ -175,7 +177,7 @@ Strategist 会把方向拆成两个彼此独立的选择:| **调性概要** | 一句话,如"现代克制、数据驱动" || **主题模式** | 仅 Create Layout/Create Deck:浅色 / 深色 / 渐变…… || **画布格式** | 仅 Create Layout/Create Deck;默认 `ppt169`(16:9),其他格式需提前指定 |-| **复刻模式** | 仅 Create Layout/Create Deck:`standard`(默认精简、由确认简报驱动;可包含少量明确要求的差异化变体)/ `fidelity`(根据来源证据覆盖更广的有用语义家族)/ `mirror`(每张源页一个物化原型)。`standard` / `fidelity` 创作新 SVG 语义;mirror 只保留来源包内已经存在且验证通过的事实。 |+| **复刻模式** | 仅 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 个标签,用于索引检索 |@@ -201,6 +203,8 @@ Strategist 会把方向拆成两个彼此独立的选择:| 来源要求 | 无 | PPTX 或 SVG 视觉参考 | PPTX,或带完整显式结构合同的 SVG || 装饰复杂度 | 通常较简洁 | 需要保留精灵图裁剪等结构 | 保留原几何,并补齐显式层级归属 |+`mirror` 不能一边保留身份或应用规则,一边又产出品牌中立、应用中立的 Layout。若要移除这些规则,应选 `standard` / `fidelity` 重新创作 Layout;若要原样保留,应创建 Deck mirror。+**关于精灵图**:PPTX 导出的素材常常是**一张大图 + 多页通过 viewBox 裁剪不同区域**。`fidelity` 和 `mirror` 模式下必须保留这层嵌套 `<svg viewBox=...>` 包装,不能扁平化为单张 `<image>`——否则裁剪信息丢失,画面会错位。工作流会自动校验这一点。**关于 PowerPoint 原生形状**:完整导入 SVG 作为原生载荷后备留在临时分析工作区且保持不可变;模板创建使用轻量、可编辑的 `authoring-svg/` IR 及其 source-ref/hash manifest。创作模式使用项目规范化 SVG,只有精确匹配已登记 preset 时才使用 compact authored-preset 组。Mirror 从 IR 物化最终模板 SVG,只为未改且 hash 匹配的 Slide-local/slot ref 重新接入转换器已支持的载荷;固定 Master/Layout 层保持直接原子,不支持或已修改的对象保留当前 SVG fallback,最终模板不包含 IR 专用 ref。@@ -219,7 +223,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 只在“重复制作已知固定成果、且新内容适配现有页面角色与文字拓扑”时推荐 `mirror`;结构应延续但内容需要重排时用 `layout`;只需身份语言或论证必须换结构时用 `style`。确认 `mirror` 后,Strategist 为每个项目页选择一张原型,Executor 复制完整 SVG,只修改允许变更的可见文字,同时保留装饰、精灵图裁剪、几何坐标和规范化结构声明;这仍不要求沿用来源页数或页序。Mirror 保留受支持的画面外观,不承诺保留来源 PPTX 的分组编辑层级。+**按 mirror 创建的工作区怎么消费**:从来源到工作区的 `replication_mode: mirror` 是能力,不是项目选择。开放式沟通契约确认后,Stage 2 先把 Deck 保存的应用契约与当前受众、结果和内容角色对照;只在“重复制作已知固定成果、且新内容适配现有页面角色与文字拓扑”时推荐 `mirror`。结构兼容、但内容需要重排时用 `layout`;只需身份语言或论证必须换结构时用 `style`。确认 `mirror` 后,Strategist 为每个项目页选择一张原型,Executor 复制完整 SVG,只修改允许变更的可见文字,同时保留装饰、精灵图裁剪、几何坐标和规范化结构声明;这仍不要求沿用来源页数或页序。Mirror 保留受支持的画面外观,不承诺保留来源 PPTX 的分组编辑层级。### 第四步:验证、预览导出、注册与发现diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.mdindex e916fc00..5c1b4d0b 100644--- a/skills/ppt-master/SKILL.md+++ b/skills/ppt-master/SKILL.md@@ -292,16 +292,22 @@ Summary:| Kind | Physical dir | Contains | Frontmatter ||---|---|---|---|| **brand** | `templates/brands/<id>/templates/` inside a complete workspace | identity-only segment: color / typography / logo / voice / icon style | `kind: brand` |-| **layout** | `templates/layouts/<id>/templates/` inside a complete workspace | structure-only segment: canvas / page structure / page types / SVG roster | `kind: layout` |-| **deck** | `templates/decks/<id>/templates/` inside a complete workspace | full identity + structure reference with the middle (template overview) segment | `kind: deck` |+| **layout** | `templates/layouts/<id>/templates/` inside a complete workspace | brand-neutral structure: canvas / page structure / semantic text roles / page types / SVG roster | `kind: layout` |+| **deck** | `templates/decks/<id>/templates/` inside a complete workspace | recurring presentation application + integrated identity + structure | `kind: deck` |++Creation-mode eligibility does not weaken kind ownership: a Layout may be+created with `mirror` only when the source contract is already brand-neutral+and application-neutral. A branded or application-bearing source must be+re-authored as Layout through `standard` / `fidelity` or retained as a Deck;+removing identity or application rules is not mirror.**Segment ownership** (governs fusion override priority):| Segment | Sections | Owner kind on fusion ||---|---|---|| Identity | Color Scheme / Typography / Logo / Voice & Tone / Icon Style | brand |-| Structure | Canvas / Page Structure / Page Types / SVG Roster | layout |-| Middle | Template Overview (use cases / design intent) | deck (no other kind writes this) |+| Structure | Canvas / Page Structure / semantic text roles and spatial behavior / Page Types / SVG Roster | layout |+| Application | Template Overview (recurring situations, audiences/outcomes, stable narrative/page roles, content reuse policy) | deck (no other kind writes this) |#### Single-path dispatch@@ -309,7 +315,7 @@ Summary:|---|---|| `kind: brand` | Install `templates/` plus any existing `images/` and `icons/` into the matching project roots; ignore `exports/`. Identity is constrained by the brand; structure stays free. || `kind: layout` | Install `templates/` plus any existing `images/` and `icons/` into the matching project roots; ignore `exports/`. The workspace exposes reusable structure; Stage 2 decides from scenario fit whether to consume it as `mirror` / `layout` / `style` where legal, then confirms the complete visual system. |-| `kind: deck` | Install `templates/` plus any existing `images/` and `icons/` into the matching project roots; ignore `exports/`. The workspace exposes both identity and structure; Stage 2 still decides the legal reuse scope from the confirmed communication contract. |+| `kind: deck` | Install `templates/` plus any existing `images/` and `icons/` into the matching project roots; ignore `exports/`. The workspace exposes an application contract with integrated identity and structure; Stage 1 independently confirms the current communication contract, then Stage 2 derivation compares the two and decides the legal reuse scope. |Normalize every explicit path before any write:@@ -334,19 +340,26 @@ The Strategist confirmation stage first decides the selected deck/layout templat#### Multi-path fusion-When the user gives two or more paths of **different kinds**, Step 3 fuses them into a single `<project>/templates/design_spec.md`. **Default granularity is segment-level integer replacement** — entire identity / structure / middle segments are taken from the highest-priority source for that segment, no implicit field-level mixing.+When the user gives two or more paths of **different kinds**, Step 3 fuses them into a single `<project>/templates/design_spec.md`. **Default granularity is segment-level integer replacement** — entire identity / structure / application segments are taken from the highest-priority source for that segment, no implicit field-level mixing.Override priority by segment:-| Combination | Identity from | Structure from | Middle from |+| Combination | Identity from | Structure from | Application from ||---|---|---|---|| brand only | brand | (free design) | (none) || layout only | (free design) | layout | (none) || deck only | deck | deck | deck |-| brand + layout | brand | layout | (none) |+| brand + layout | brand | layout | current project's Stage-1 communication contract; no reusable Deck application is invented || brand + deck | brand (overrides deck) | deck | deck |-| layout + deck | deck | layout (overrides deck) | deck |-| brand + layout + deck | brand | layout | deck |+| layout + deck | deck | compatible layout (overrides deck) | deck |+| brand + layout + deck | brand | compatible layout | deck |++Before a Layout overrides a Deck's structure, compare the Deck application+contract with the Layout's page roles, slot types, and capacity. If any required+narrative/content role cannot be represented, stop the fusion and surface a+conflict: retain the Deck structure, select another Layout, or explicitly+revise the application contract. Never keep an application promise that the+installed structure cannot satisfy.Field-level micro-adjustment (e.g. "use anthropic brand but primary changed to #FF0000") is **not** part of Step 3 fusion — it flows into Strategist confirmation stage e–g as a normal user request.@@ -385,7 +398,7 @@ When fusion happens (any multi-path case), the resulting `<project>/templates/deSingle-path Step 3 does **not** add provenance (the source is self-evident from the copied files).-The fused frontmatter `kind` describes the resulting bundle: `deck` when both identity and structure are present, `layout` when only structure is present, and `brand` when only identity is present. Keep this field accurate; the Strategist confirmation server uses it to show template adherence only for bundles that actually own page structure.+The fused frontmatter `kind` describes the resulting project capability bundle: `deck` when both identity and structure are present, `layout` when only structure is present, and `brand` when only identity is present. A project-local Brand + Layout fusion uses `kind: deck` for routing but is not thereby promoted into a reusable library Deck; Stage 1 supplies the current project's application context. Keep this field accurate; the Strategist confirmation server uses it to show template adherence only for bundles that actually own page structure.**✅ Checkpoint — Default path proceeds to Step 4 without user interaction. If the user supplied one or more explicit template paths, those have been copied, staged in place, or fused into `<project_path>/templates/` before advancing.**@@ -440,7 +453,7 @@ Steps:Page opens at the launch-log URL such as `http://127.0.0.1:5050` — the **same port as the Step 6 live preview** (they never run at once: this page shuts down at the end of Step 4). If 5050 is held, the launcher **auto-advances** (5051, …) — read the actual URL from the launch log and report it. The page does **not** close after Stage 1: it shows a "deriving…" state and polls for Stage 2. **Launch or wait failure is non-fatal**: if it fails or times out (flask missing, port blocked, no GUI / remote / web host), do **NOT** troubleshoot — **on any non-zero exit, re-check `result.json` once** for a fresh `status: stage1-confirmed` before dropping to the chat fallback. **On success (exit 0 with a stage-1 result), do not pause or report — go straight to step 3 in the same turn.**3. **Derive Stage 2 once from the confirmed communication contract, write it, then wait for the solution handoff — immediately, same turn (the page is polling for it).** Read the stage-1 `result.json` (`status: stage1-confirmed`). Using the user's **actual** contract (not your originals), **overwrite** `recommendations.json` with `"stage": "stage2"` and author the complete deck solution:- Recommend PPT-only reading mode through the compatibility key `recommend.delivery_purpose` (`text` / `balanced` / `presentation`) from the confirmed audience, delivery context, and artifact afterlife. `text` makes the page self-contained with complete prose and detail; `balanced` shares meaning between page and presenter; `presentation` uses one idea, concise claims, and visual evidence per page while speech / notes carry explanation. Then recommend one narrative `mode` and page count from source volume × desired audience outcome × reading mode. Reading mode governs content grammar and page granularity as well as the body baseline; it is not a font-size preset. The page applies `reading mode → body baseline → unpinned role sizes` as a deterministic browser-only dependency. This never calls the backend, and a manually edited size is pinned against later reading-mode changes.- - When Step 3 loaded a deck/layout template, recommend `template_reuse_scope` now: `mirror`, `layout`, or `style`; `mirror` is legal only for `replication_mode: mirror`. Include `template_adherence: strict|adaptive` only for `mirror|layout`; `style` hides it and later writes `pptx_structure.mode: flat`. Select from scenario fit: literal recurring artifact → consider `mirror`; reusable structure with new content → `layout`; identity only or a contract that needs a different structure → `style`. Omit both fields for free design and brand-only templates.+ - When Step 3 loaded a deck/layout template, recommend `template_reuse_scope` now: `mirror`, `layout`, or `style`; `mirror` is legal only for `replication_mode: mirror`. Include `template_adherence: strict|adaptive` only for `mirror|layout`; `style` hides it and later writes `pptx_structure.mode: flat`. For a Deck, first compare its application contract—situations, audiences/outcomes, required narrative/page roles, and content policy—with the confirmed Stage-1 contract; do not treat the stored application as truth when the current request differs. Select from scenario fit: literal recurring artifact → consider `mirror`; compatible reusable structure with new content → `layout`; identity only or a contract that needs a different structure → `style`. Omit both fields for free design and brand-only templates.- Author `design_directions` with ≥3 coordinated candidates (safe / shifted / bold; honest-shortfall exception unchanged). Each candidate carries one compatible `visual_style`, color object, typography object, icon id, and—when `image_usage` includes `ai`—one generated-image **rendering** object. The page applies a candidate as one coherent starting point and then exposes the component fields for deliberate override. Do not generate Cartesian combinations or random mix-and-match defaults.- Color candidates carry background / secondary_bg / primary / accent / secondary_accent / body_text. Typography splits CJK + Latin for heading/body, includes topic-matched sample text, and uses one fixed body baseline per reading mode (`text` 20 / `balanced` 24 / `presentation` 32 on PPT). Font and direction cards change font character while preserving the current reading-mode sizing state. Recommend one or more `image_usage` source ids (`["ai"]`, `["ai","provided"]`, `["web","placeholder"]`, or `["none"]`; `none` is exclusive) and keep mixed-source / page-role guidance in `image_notes`. When AI is included, each direction's `image_strategy` contains rendering / visual / mood only; **never offer or submit a separate image palette**. Image HEX and role behavior come directly from that direction's deck color object. Spot-illustration lean remains rationale, not a field.diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.mdindex 603ae0e4..689317f4 100644--- a/skills/ppt-master/references/strategist.md+++ b/skills/ppt-master/references/strategist.md@@ -154,6 +154,8 @@ For `mirror` / `layout`, surface the second closed Stage-2 choice, `template_adh**Default — layout + adaptive**: When the user supplied only a template path, 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 as `template_reuse_scope` under `spec_lock.md pptx_structure`; record adherence only for `mirror` / `layout`.+**Mandatory — consume the stored contract at the decision point**: Immediately before authoring the Stage-2 reuse recommendation for an installed `kind: deck`, re-read `<project_path>/templates/design_spec.md`. Compare the five application-contract rows in `## I. Template Overview` with the confirmed Stage-1 audience, intent, outcome, delivery context, artifact afterlife, and source obligations. Then compare every `## V. Page Roster` content-policy value with the narrative/page roles the current artifact needs, including required / optional / repeatable status and fixed / replaceable / example-only content. Treat the stored 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 the current contract only with the roster's structural roles, slots, and capacity.+**Scenario fit comes before template capability.** A workspace advertising `mirror` does not mean the project should consume it in mirror mode. Recommend from the confirmed communication contract:| Scope | Appropriate when |diff --git a/skills/ppt-master/references/template-designer.md b/skills/ppt-master/references/template-designer.mdindex 619ac457..7d21eca4 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 basic norms that make the template reusable.+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.> 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, applicable scenarios, 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 contract, 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`.@@ -51,6 +51,17 @@ Use the compact facts in `manifest.json` for orientation. Open screenshots or th**Native structure output**: Always set `native_structure_mode: structured`.+**Hard rule — native objects are compiled output**: Treat Theme, Master,+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+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+the applicable rules into the same native graph without merging their source+ownership.+| Mode | Output structure contract ||---|---|| `standard` / `fidelity` | Author project-canonical SVG prototypes and an intentional new Master/Layout/slot system. Source visual language and assets may guide the design, but source ownership, keys, picker names, parent relationships, placeholders, and repeated Slide-local elements do not define or seed the output topology. Use the compact authored-preset group only for exact registered preset matches. |@@ -84,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**: The Strategist confirmation stage selects `strict` or `adaptive` when a project consumes this package. Both 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. 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.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.@@ -112,7 +123,7 @@ The output page set is determined by **replication mode**, declared in the final| 04 | `04_ending.svg` | Ending page | Fixed structure: thank-you message, contact info || -- | `02_toc.svg` | Table of contents | Optional: TOC title, chapter list (number + title) |-**Design philosophy**: Templates define visual consistency and structural pages; content pages maintain maximum flexibility.+**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.@@ -145,6 +156,7 @@ Extension page types beyond the canonical four (transition / appendix / disclaimWhen the brief sets `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.- Precondition: the import evidence identifies every source Master/Layout, parent relationship, picker name, placeholder contract, and fixed visual layer. Stop only when required facts or supported geometry are missing; unused identities are not a stop condition.- Output: `<template_workspace>/templates/<NNN>_<page_type>.svg` for every source slide, plus `layout_<layout_key>.svg` for every source Layout unused by all source slides. `<NNN>` is the zero-padded source slide index (3 digits) and `<page_type>` is derived from `manifest.json` `pageTypeCandidates` — `cover` / `toc` / `chapter` / `content` / `ending`. When the page-type heuristic is ambiguous, fall back to `content`. Preserve source slide order via the numeric prefix; definition-only files are not generated pages.@@ -153,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. 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 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.**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.@@ -163,7 +175,7 @@ When the brief sets `Replication mode: mirror`, materialize a new template works### 1. Must Generate design_spec.md-**Scope rule — personality only.** A deck `design_spec.md` describes the identity and structure that make the complete template recognizable. A layout spec describes only its distinctive reusable structure. Neither restates generic constraints — those live in the canonical references and are already loaded by every downstream role:+**Scope rule — package-specific rules only.** A Deck `design_spec.md` describes its recurring application plus integrated identity and structure. A Layout spec describes only brand-neutral reusable structure and may state supported content shapes/delivery settings without owning a communication objective or narrative. Neither restates generic constraints — those live in the canonical references and are already loaded by every downstream role:- General SVG required / forbidden / conditional interfaces → [`shared-standards.md`](shared-standards.md)- Generic layout pattern library, spacing bands, font-size ratio bands → [`templates/design_spec_reference.md`](../templates/design_spec_reference.md) (read by Strategist when authoring the **project** design_spec)@@ -186,7 +198,7 @@ field that the registrar cannot bind to its library kind.deck_id: <id>kind: deckcategory: brand | general | scenario | government | special-summary: <one-line tone & use case>+summary: <one-line recurring presentation family and intended outcome>keywords: [tag1, tag2, tag3]primary_color: "#......"canvas_format: ppt169@@ -211,8 +223,15 @@ page_count: <N># [Template Name] — Design Specification## I. Template Overview-- Use cases, design tone, theme mode (light / dark / mixed)-- One paragraph: what visually identifies this template at a glance+| Application contract | 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> |++- Design tone, theme mode (light / dark / mixed), and the visual identity visible at a glance## II. Color Scheme- HEX values with role labels (primary / accent / background / text / etc.)@@ -229,7 +248,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). 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 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.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.@@ -269,11 +288,11 @@ page_types: [cover, toc, chapter, content, ending]# [Layout Name] — Design Specification## IV. Signature Design Elements-- Structure-specific grid, zones, page chrome, image behavior, density rhythm, and slot conventions-- Neutral preview paint may expose hierarchy, but it is not a color or typography identity+- Structure-specific grid, zones, page chrome, image behavior, density rhythm, semantic text roles, alignment/wrapping/capacity behavior, and slot conventions+- Neutral preview paint/font/size may expose hierarchy, but it is not a color, typeface, or final type-scale identity## V. Page Roster-One row per emitted SVG with Layout key, picker name, intended content, and slot behavior. Roster entries must match the actual files on disk.+One row per emitted SVG with Layout key, picker name, supported content shape, and slot behavior. Roster entries must match the actual files on disk.For `mirror`, append the same `### Source Preservation Map` required above.@@ -282,9 +301,14 @@ Reference the `placeholders:` frontmatter declaration and explain the structural```**Layout boundary**: Omit Template Overview, Color Scheme, Typography, Logo,-Voice & Tone, and Icon Style. The frontmatter `summary` carries concise-selection context; the deck-only Template Overview remains the middle segment-used during fusion.+Voice & Tone, and Icon Style. A scenario category records geometric fit only.+Structural text roles, alignment, wrapping, and capacity remain valid Layout+rules; final font families, weights, colors, and absolute sizes do not.+Do not prescribe communication objectives, audience outcomes, required+narrative order, fixed boilerplate, or example-content retention. The+frontmatter `summary` carries concise structural selection context; the+deck-only Template Overview remains the application segment used during+fusion.Sections to **omit** from template `design_spec.md` (sourced elsewhere — listing them here is noise):@@ -301,7 +325,7 @@ Sections to **omit** from template `design_spec.md` (sourced elsewhere — listiWhen rewriting an existing template that contains an omitted generic section,delete it rather than leaving a pointer. Keep a template-specific boundary only-inside the personality section it qualifies (asset system, motif, image+inside the package-owned section it qualifies (asset system, motif, imagetreatment, or page roster); do not preserve a generic technical-rules heading.### 2. Inherit Design Specification@@ -313,6 +337,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 boundaryIf PPTX import output exists:- Prefer imported theme colors and fonts over visually guessed values@@ -561,7 +586,7 @@ If suitable template resources already exist, use them directly instead of generThis section describes downstream reuse of an existing workspace. Library and project scopes carry the same portable template contract.-**Example library structure** (query the appropriate kind's index — `templates/layouts/layouts_index.json` for structure-only templates, `templates/decks/decks_index.json` for complete identity + structure templates, `templates/brands/brands_index.json` for identity-only presets):+**Example library structure** (query the appropriate kind's index — `templates/layouts/layouts_index.json` for brand-neutral structure templates, `templates/decks/decks_index.json` for recurring applications with integrated identity/structure, `templates/brands/brands_index.json` for identity-only presets):```templates/@@ -584,10 +609,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`+- [x] Replication mode confirmed: `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] `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 atomsdiff --git a/skills/ppt-master/scripts/docs/svg-pipeline.md b/skills/ppt-master/scripts/docs/svg-pipeline.mdindex 24c40812..623fff26 100644--- a/skills/ppt-master/scripts/docs/svg-pipeline.md+++ b/skills/ppt-master/scripts/docs/svg-pipeline.md@@ -169,8 +169,8 @@ The output routes reusable vectors once to `icons/imported/`, bitmaps to`images/`, and other referenced files to `templates/assets/`. The JSON reportreports payload occurrence, native-record, unique-byte, and compressed-storecounts and is written to stdout only. The command intentionally does not create-`templates/design_spec.md`; Template_Designer writes that personality and page-roster after materialization. This compiler is for Type A mirror materialization,+`templates/design_spec.md`; Template_Designer writes the package-specific rules+and page roster after materialization. This compiler is for Type A mirror materialization,not `standard` / `fidelity`, loose Type B SVGs, ordinary generation, finalize,or export.diff --git a/skills/ppt-master/templates/README.md b/skills/ppt-master/templates/README.mdindex dd5ecb9c..b8bc77bf 100644--- a/skills/ppt-master/templates/README.md+++ b/skills/ppt-master/templates/README.md@@ -8,12 +8,25 @@ inheritance hierarchy.| Kind | Owns | Does not own | Discovery index ||---|---|---|---|| [`brands/`](./brands/) | Identity: color, typography, logo, voice, icon style | Page structure or SVG roster | [`brands_index.json`](./brands/brands_index.json) |-| [`layouts/`](./layouts/) | Structure: canvas, Master/Layout graph, page types, slots, SVG roster | Brand identity | [`layouts_index.json`](./layouts/layouts_index.json) |-| [`decks/`](./decks/) | Complete identity + structure reference | — | [`decks_index.json`](./decks/decks_index.json) |+| [`layouts/`](./layouts/) | Brand-neutral structure: canvas, Master/Layout graph, page types, slots, SVG roster | Brand identity or a recurring communication application | [`layouts_index.json`](./layouts/layouts_index.json) |+| [`decks/`](./decks/) | A recurring presentation family: application contract + integrated identity + structure | — | [`decks_index.json`](./decks/decks_index.json) |A brand is not “a layout minus its pages”: it owns a different segment. Use a-brand for identity with free page composition, a layout for fixed reusable-structure with downstream identity, and a deck for a coherent complete system.+brand for identity with free page composition, a layout for brand-neutral+structure whose identity and communication purpose remain downstream+decisions, and a deck for a recurring presentation family with an explicit+application contract.++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+structural geometry and brand visuals even though their source rules remain+separately owned.New workspaces always enter [`Create Template`](../workflows/create-template.md),which keeps the fixed route name and dispatches exactly one child workflow:@@ -28,10 +41,10 @@ explicit workspace-root path supplied by the user.| Axis | Values | Meaning ||---|---|---|-| Template kind | `brand` / `layout` / `deck` | Which design segments the package owns |-| 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; Create Brand is N/A |+| 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 content stays Slide-local; layout/deck routes compile declared Masters and Layouts |+| 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 deckis still an ordinary reusable `deck` package after creation; it does not force@@ -62,8 +75,9 @@ indicate legacy Master/Layout semantics.[`design_spec_reference.md`](./design_spec_reference.md) is the project-levelStrategist reference for the generated presentation's full specification andcontent outline. Reusable template `design_spec.md` files are deliberately-smaller: they contain portable metadata and only the personality or structure-that distinguishes that package. General SVG/PPT rules remain centralized in+smaller: they contain portable metadata and only the identity, structure, or+application rules owned by that package. General SVG/PPT rules remain+centralized in[`shared-standards.md`](../references/shared-standards.md).## Visualization Templatesdiff --git a/skills/ppt-master/templates/brands/README.md b/skills/ppt-master/templates/brands/README.mdindex 9afb23ed..36f04033 100644--- a/skills/ppt-master/templates/brands/README.md+++ b/skills/ppt-master/templates/brands/README.md@@ -3,9 +3,9 @@This directory holds **brand-only templates**: identity bundles (color / typography / logo / voice / icon style) without an SVG page roster. Strategist locks the brand's identity segment as truth; Executor designs pages freely under those constraints.Brand is one of three template kinds in the library — alongside-[`layouts/`](../layouts/) (structure-only) and [`decks/`](../decks/) (complete-identity + structure). The shared kind and workspace model lives in the-parent [`README.md`](../README.md).+[`layouts/`](../layouts/) (brand-neutral structure) and [`decks/`](../decks/)+(a recurring application with integrated identity and structure). The shared+kind and workspace model lives in the parent [`README.md`](../README.md).## How brands are consumed@@ -16,8 +16,8 @@ Brand application follows the **same explicit-path rule and workspace routing as| An explicit brand workspace path (e.g. `templates/brands/anthropic/`) | Resolve `templates/design_spec.md`; stage `templates/` plus any existing `images/` and `icons/` into the matching project directories; Strategist locks the identity segment || Bare brand name only ("use anthropic brand"), brand mention without path, or silence | Skip — same mechanical rule as all template kinds: bare names never trigger || Brand path + layout path | Fuse into one `design_spec.md` — brand owns identity segment (color / typography / logo / voice / icon style); layout owns structure segment (canvas / page roster). See `SKILL.md` Step 3. |-| Brand path + deck path | Fuse — brand identity overrides deck identity; structure + middle segments come from deck |-| Brand path + layout path + deck path | Three-way fuse — brand=identity, layout=structure, deck=middle |+| Brand path + deck path | Fuse — brand identity overrides deck identity; structure + application segments come from deck |+| Brand path + layout path + deck path | Three-way fuse — brand=identity, layout=structure, deck=application, subject to application/structure compatibility || Two brand paths | Conflict resolution prompt before fusion — user picks per-segment source |`brands_index.json` is discovery-only; listing brands never advances the pipeline.diff --git a/skills/ppt-master/templates/decks/README.md b/skills/ppt-master/templates/decks/README.mdindex 29badfc0..a8b10879 100644--- a/skills/ppt-master/templates/decks/README.md+++ b/skills/ppt-master/templates/decks/README.md@@ -1,16 +1,20 @@# Deck Templates-**Deck = a complete reusable template bundle.** It owns both presentation-identity and reusable page structure. 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.+**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.+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`: identity + structure + deck-specific overview |+| 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 | Always `structured`; `flat` is reserved for free design and brand-only routes |+| PPTX structure | Workspace is `structured`; downstream `mirror` / `layout` use it, while confirmed `style` intentionally retains only visual language and generates `flat` |The discovery source of truth is [`decks_index.json`](./decks_index.json)(`deck_id → { summary, canvas_format, page_count, primary_color }`). This README@@ -18,6 +22,10 @@ defines the kind and intentionally does not enumerate installed decks. Theshared kind and workspace model lives in the parent[`README.md`](../README.md).+Index `summary` values lead with the recurring presentation family and intended+outcome. Visual tone alone is not enough to select a Deck; open its Template+Overview when application fit must be judged in detail.+---## Trigger and fusion@@ -30,24 +38,28 @@ may resolve `design_spec.md` directly. Semantic-legacy packages must be replacedthrough Create Template rather than upgraded in place. See [`SKILL.md`](../../SKILL.md) Step 3.A deck path alone supplies the complete reference. When combined with a brand-or layout path, brand replaces the identity segment and layout replaces the-structure segment; the deck remains the source of deck-specific overview-context. Fusion never changes the package's stored SVGs in place.+or layout path, brand replaces the identity segment and layout may replace the+structure segment; the deck remains the source of the application contract.+Before a Layout override is accepted, its page roles and slot capabilities must+support the Deck's required narrative/content roles. Treat an incompatibility+as a fusion conflict instead of retaining an application promise the new+structure cannot satisfy. Fusion never changes the package's stored SVGs in+place.---## `design_spec.md` contract-The spec stores portable metadata plus template-specific personality. It does-not repeat generic SVG rules, spacing libraries, font-ratio bands, or the-canonical placeholder table.+The spec stores portable metadata plus package-owned application, identity,+and structure rules. It does not repeat generic SVG rules, spacing libraries,+font-ratio bands, or the canonical placeholder table.```markdown---deck_id: <slug>kind: deckcategory: brand | general | scenario | government | special-summary: <one-line use case and tone>+summary: <one-line recurring presentation family and intended outcome>primary_color: "#XXXXXX"canvas_format: ppt169canvas_width: 1280@@ -69,7 +81,19 @@ page_count: <N>## VII. Placeholder Overrides # omit when none```-`Page Roster` must list every SVG and its declared Master/Layout identity.+`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.++`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.+Every additional authored Master represents a distinct reusable design family,not one Layout or an organizational duplicate.@@ -108,7 +132,7 @@ Library scope writes `skills/ppt-master/templates/decks/<deck_id>/` and updatesthe index. Project scope uses an initialized `projects/<name>/` workspace anddoes not register globally. Empty optional directories are omitted.-1. Enter [`workflows/create-template.md`](../../workflows/create-template.md), which dispatches integrated identity-and-structure output to [`create-deck.md`](../../workflows/create-template/create-deck.md).+1. Enter [`workflows/create-template.md`](../../workflows/create-template.md), which dispatches recurring-application output with integrated identity and structure to [`create-deck.md`](../../workflows/create-template/create-deck.md).2. Validate with `svg_quality_checker.py --template-mode`.3. Run `template_preview_pptx.py` when review is requested and always when the roster declares multiple Masters.4. In library scope, register with `register_template.py <id> --kind deck`.diff --git a/skills/ppt-master/templates/decks/decks_index.json b/skills/ppt-master/templates/decks/decks_index.jsonindex 29aefa83..2fc466ed 100644--- a/skills/ppt-master/templates/decks/decks_index.json+++ b/skills/ppt-master/templates/decks/decks_index.json@@ -1,12 +1,12 @@{"中国电信": {- "summary": "中国电信政企数字化、转型规划与内部汇报的克制红灰品牌模板。",+ "summary": "中国电信政企数字化方案、转型规划与内部评审,用于说明方案并对齐决策和下一步;采用克制的红灰品牌视觉。","canvas_format": "ppt169","page_count": 5,"primary_color": "#C00000"},"中汽研": {- "summary": "中汽研认证展示、技术交流与业务来访场景的深蓝专业模板。",+ "summary": "中汽研认证展示、评测汇报与技术交流,用于建立可信理解并推进评审或合作;采用专业的深蓝工程视觉。","canvas_format": "ppt169","page_count": 5,"primary_color": "#004098"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 10d8a960..7e65bcea 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"@@ -2,7 +2,7 @@deck_id: 中国电信kind: deckcategory: brand-summary: 中国电信政企数字化、转型规划与内部汇报的克制红灰品牌模板。+summary: 中国电信政企数字化方案、转型规划与内部评审,用于说明方案并对齐决策和下一步;采用克制的红灰品牌视觉。keywords: [中国电信, 政企, 数字化, 企业汇报]primary_color: "#C00000"canvas_format: ppt169@@ -21,7 +21,14 @@ page_count: 5## I. Template Overview-- 适用于政企数字化方案、转型规划、内部评审和客户汇报。+| Application contract | Definition |+| --- | --- |+| Recurring presentation family | 政企数字化方案、转型规划、内部评审和客户汇报 |+| Intended audiences and outcomes | 面向政企客户决策者、项目干系人与内部评审者;帮助受众理解背景与方案、形成判断,并明确下一步 |+| Delivery and reading assumptions | 以会议讲解为主,同时需要会后流转和复核;页面应保留关键结论与必要证据,不依赖口头说明才能辨认主题 |+| Stable narrative/page roles | 必需封面;可选目录与章节页;正文页可重复;需要正式收束时使用结束页。具体论证顺序由当前项目的沟通契约决定 |+| Content reuse boundary | Logo、品牌口号与固定品牌图形可保留;项目标题、目录、章节名、正文、数据、来源和联系信息必须替换;原型中的示例文字不得进入成品 |+- 视觉基调为白底、通信红结构条、银灰内容承载区与少量城市线稿,强调权威、清晰和克制。- 结构上分为两个可复用 Master 家族:China Telecom Brand 服务封面、章节与收尾,China Telecom Content 服务目录与正文;它们按视觉体系分工,不是按单个 Layout 拆分出的重复 Master。@@ -55,13 +62,13 @@ page_count: 5## V. Page Roster-| 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 | 左侧结束语、右侧品牌卡片、底部飘带 | 结束标题、副标题、联系信息、页码 |+| 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 | 左侧结束语、右侧品牌卡片、底部飘带 | 结束标题、副标题、联系信息、页码 | 可选收束页;品牌图形固定,结束语与联系信息按项目替换 |## VI. Assetsdiff --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 09081da3..ece4dbd8 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"@@ -2,7 +2,7 @@deck_id: 中汽研kind: deckcategory: brand-summary: 中汽研认证展示、技术交流与业务来访场景的深蓝专业模板。+summary: 中汽研认证展示、评测汇报与技术交流,用于建立可信理解并推进评审或合作;采用专业的深蓝工程视觉。keywords: [中汽研, 认证, 评测, 技术交流]primary_color: "#004098"canvas_format: ppt169@@ -21,7 +21,14 @@ page_count: 5## I. Template Overview-- 适用于产品认证展示、评测汇报、技术推广和业务来访。+| Application contract | Definition |+| --- | --- |+| Recurring presentation family | 产品认证展示、评测汇报、技术推广和业务来访 |+| Intended audiences and outcomes | 面向客户、技术评审者、合作伙伴与来访团队;帮助受众理解认证或评测能力、信任证据,并推进评审、交流或合作下一步 |+| Delivery and reading assumptions | 以现场讲解和技术交流为主,同时允许会后独立阅读;页面需保留关键结论、证据标签与必要上下文 |+| Stable narrative/page roles | 必需封面;可选目录与章节页;正文页可重复;正式交流可使用结束页。具体论证顺序由当前项目的沟通契约决定 |+| Content reuse boundary | Logo、机构英文名与固定结构图形可保留;项目标题、目录、章节名、正文、数据、案例和联系信息必须替换;原型示例不得作为事实复用 |+- 视觉以中汽研深蓝、白底内容页、方形章节编号和简洁网格为识别核心,强调专业、可信和工程秩序。- 结构上分为两个可复用 Master 家族:CATARC Dark 服务封面、章节与收尾,CATARC Light 服务目录与正文;它们按深浅视觉体系分工,不是按单个 Layout 拆分出的重复 Master。@@ -55,13 +62,13 @@ page_count: 5## V. Page Roster-| 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 与结束语 | 结束标题、英文副标题、联系信息、页脚 |+| 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 与结束语 | 结束标题、英文副标题、联系信息、页脚 | 可选收束页;机构视觉固定,结束语与联系信息按项目替换 |## VI. Assetsdiff --git a/skills/ppt-master/templates/layouts/README.md b/skills/ppt-master/templates/layouts/README.mdindex d42e1aba..6486c735 100644--- a/skills/ppt-master/templates/layouts/README.md+++ b/skills/ppt-master/templates/layouts/README.md@@ -1,21 +1,33 @@# Layout Templates**Layout = a structure-only reusable template bundle.** It owns canvas,-Master/Layout structure, page types, slot geometry, and the SVG roster. It does-not own color, typography, logo, voice, or icon style. Those identity decisions-come from an explicit brand/deck source or from the Strategist confirmation-stage.--Neutral colors and safe fonts may appear in SVG prototypes so the structure is-reviewable. They are preview paint, not a locked identity segment. Non-mirror-projects repaint and retype the selected structure from the project lock.+Master/Layout structure, page types, slot geometry, semantic text roles,+alignment/wrapping/capacity behavior, and the SVG roster. It does not own+brand color, typeface/weight identity, the final resolved type scale, logo,+voice, or icon style. Those identity decisions come from an explicit+brand/deck source or from the Strategist confirmation stage.++A layout may describe the content shapes and delivery conditions its geometry+can support. It must not own a communication objective, audience outcome,+scenario-specific narrative sequence, fixed boilerplate, or example content+that downstream generation is expected to preserve. Those application rules+belong to a Deck. A structurally useful “board update” page can remain a+Layout; a board-update sequence with required decision, risk, and action roles+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.| 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 | Always `structured`; `flat` is reserved for free design and brand-only routes |+| PPTX structure | Workspace is `structured`; downstream `mirror` / `layout` use it, while confirmed `style` intentionally discards structure and generates `flat` |The discovery source of truth is [`layouts_index.json`](./layouts_index.json)(`layout_id → { summary, canvas_format, page_count, page_types }`). This README@@ -23,6 +35,13 @@ defines the kind and intentionally does not enumerate installed layouts. Theshared kind and workspace model lives in the parent[`README.md`](../README.md).+Layout mirror has one additional eligibility rule: the validated source+contract must already be brand-neutral and application-neutral. A source+outside that boundary can become a Layout only through `standard` or+`fidelity`, which deliberately authors a new neutral system. If its identity or+application rules must remain literal, create a Deck instead. Removing either+kind of rule is never a mirror operation.+---## Trigger and identity boundary@@ -43,8 +62,9 @@ place. See [`SKILL.md`](../../SKILL.md) Step 3.## `design_spec.md` contractThe spec stores portable structural metadata plus rules unique to this layout.-It omits the deck-only Template Overview and every identity section. The-frontmatter `summary` carries the concise selection context.+It omits the deck-only Template Overview/application contract and every+identity section. The frontmatter `summary` carries the concise selection+context.```markdown---@@ -70,9 +90,11 @@ page_types: [cover, toc, chapter, content, ending]````Signature Design Elements` describes only reusable structure: grids, zones,-image behavior, density rhythm, and slot conventions. It must not introduce a-brand palette or typography system. `Page Roster` lists every SVG with its-Layout key, PowerPoint picker name, intended content, and slot behavior.+image behavior, density rhythm, semantic text roles, alignment/wrapping/+capacity behavior, and slot conventions. It must not introduce a brand+palette, typeface identity, final type scale, communication objective, or+required narrative sequence. `Page Roster` lists every SVG with its Layout+key, PowerPoint picker name, supported content shape, and slot behavior.---diff --git a/skills/ppt-master/workflows/create-template.md b/skills/ppt-master/workflows/create-template.mdindex d601357c..13284f7f 100644--- a/skills/ppt-master/workflows/create-template.md+++ b/skills/ppt-master/workflows/create-template.md@@ -25,10 +25,10 @@ Create Template is the fixed user-facing entry and common contract. It selects o| Child workflow | Select when | Library-scope output | Exclusive responsibility ||---|---|---|---|| [`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 | `templates/layouts/<layout_id>/` | Canvas, page grammar, Master/Layout/slot contract, and SVG roster; no brand identity |-| [`Create Deck`](./create-template/create-deck.md) | Reuse identity and structure together, including a specific organization's presentation system | `templates/decks/<deck_id>/` | Integrated identity, structure, template overview, and 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 |-Select Create Brand only for identity-only intent. Select Create Layout only when identity must remain downstream-selectable. Otherwise select Create Deck. 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.+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.See [`templates/README.md`](../templates/README.md) for the shared kind andworkspace model. Downstream template application and fusion remain owned by@@ -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. 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.+**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.### 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 context: use cases, design intent, presentation rhythm, examples, and negative requirements.+- Deck application: recurring situations, intended audiences/outcomes, delivery or reading assumptions, stable narrative/page roles, content reuse boundaries, examples, and negative requirements.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.@@ -377,10 +377,11 @@ Compose a single message that surfaces every Required brief item to the user, **| 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. |+| 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. Create Brand has no replication mode. |+| 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 || Asset bundling | Recommended included assets, plus excluded candidate assets with a one-line reason when reference assets exist |@@ -394,18 +395,20 @@ Items to surface:| 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` |-| Applicable scenarios | Yes | `[suggested]` from analysis; user confirms |+| 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. || 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. 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. |+| 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. || 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. || 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. |-| Fonts | Create Brand/Create Deck only | A: `[fact]` from `manifest.json`. B: `[fact]` from SVG `font-family`. C: font family is not derivable — use `[decision]` if the user supplies one. D: `[fact]` from an independently identified external authority or `[decision]` from user-authored text in any carrier. E: `[decision]` when a custom stack is wanted. Create Layout stores no typography system. |+| Fonts | Create Brand/Create Deck only | A: `[fact]` from `manifest.json`. B: `[fact]` from SVG `font-family`. C: font family is not derivable — use `[decision]` if the user supplies one. D: `[fact]` from an independently identified external authority or `[decision]` from user-authored text in any carrier. E: `[decision]` when a custom stack is wanted. Create Layout stores no typeface identity or final type scale; its structural text roles, alignment, wrapping, and capacity remain part of page grammar. || Design style | Optional | `[suggested]` from analysis || Assets list | Optional | A: `[fact]` from `assets/` listing; user picks which to bundle. B/C/D: retain each file's source and let the user confirm adoption. E: none. || Keywords | Yes | `[suggested]` from analysis (3–5 short tags); user confirms |@@ -418,7 +421,7 @@ When the bundle includes Type A for Create Layout/Create Deck, also include in tThe 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.). 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.). 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.---@@ -439,11 +442,12 @@ Skipping this gate — including silently inferring values from reference files,- [ ] User has replied with values or explicit acceptance of suggested defaults- [ ] 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`)+- [ ] 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- [ ] 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+- [ ] 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 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@@ -600,7 +604,7 @@ Mirror mode does not simplify the visual target or synthesize layer ownership. T**Expected outputs from this step** (full spec → [template-designer.md](../references/template-designer.md)):-1. `design_spec.md` — **personality only**. A deck writes Template Overview, Color Scheme, Signature Design Elements, and 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. 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.md` / `design_spec_reference.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 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.md` / `design_spec_reference.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 handling3. 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.@@ -669,7 +673,7 @@ This checker validates the authoring contract, not the compiled OOXML package. T**Checklist**:-- [ ] `design_spec.md` follows the kind-specific personality-only skeleton: deck = Overview / Color / Signature / Page Roster plus conditional sections; layout = structure-owned Signature / Page Roster with no Overview 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. §V Page Roster lists every emitted page+- [ ] `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- [ ] 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@@ -749,7 +753,7 @@ Run the unified registrar with the kind flag; it derives the corresponding index# For brandpython3 skills/ppt-master/scripts/register_template.py <template_id> --kind brand-# For deck (default)+# For deckpython3 skills/ppt-master/scripts/register_template.py <template_id> --kind deck# For layout@@ -876,8 +880,9 @@ The next Generate PPTX Step 3 input is the exact `<template_workspace>/` root in1. **SVG technical constraints**: See [shared-standards.md](../references/shared-standards.md) — do not restate them 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. **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.-4. **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.-5. **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.+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.+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.> **Full role specification**: [template-designer.md](../references/template-designer.md)diff --git a/skills/ppt-master/workflows/create-template/create-deck.md b/skills/ppt-master/workflows/create-template/create-deck.mdindex 20089af1..149c5bbc 100644--- a/skills/ppt-master/workflows/create-template/create-deck.md+++ b/skills/ppt-master/workflows/create-template/create-deck.md@@ -1,5 +1,5 @@----description: Create Deck child workflow for a complete reusable identity-and-structure workspace.+description: Create Deck child workflow for a recurring presentation application with integrated identity and structure.---# Create Deck Workflow@@ -11,11 +11,11 @@ Enter this child workflow only after [`Create Template`](../create-template.md)| Owner | Responsibilities ||---|---|| Create Template | Child-workflow dispatch plus the shared source taxonomy, `library` / `project` scope, confirmation gate, collision preflight, structured authoring contract, validation commands, registration, completion, and Generate PPTX handoff |-| Create Deck | Integrated identity-and-structure interpretation, deck-specific brief fields, complete `design_spec.md`, SVG roster, and deck-specific validation |+| Create Deck | Recurring-application interpretation, integrated identity/structure, complete `design_spec.md`, SVG roster, and deck-specific validation |**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 — complete reusable system**: A deck owns the identity segment, the structure segment, and the deck-only Template Overview. It is a reusable template workspace, not the user's finished content deck.+**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.## Invocation Points@@ -25,16 +25,16 @@ 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 both segments:+Use Create Template Step 1 for source ingestion and replication-mode eligibility. 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, page types, image behavior, and density rhythm.-- Middle: use cases, design intent, presentation rhythm, and other deck-specific overview context.+- 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.-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 middle 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.+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.-Create Deck is the default child when identity and structure are both requested or when the source is a specific organization's branded presentation system. If the user explicitly wants identity-only or brand-neutral structure, return to Create Template dispatch before the shared confirmation marker is emitted.+Create Deck is selected when identity and structure must travel together, when the source is a specific organization's branded presentation system, or when reusable scenario/content semantics are requested. A complete PPTX source alone does not make the output a Deck. If only identity is stable, use Create Brand; if the reusable structure is brand-neutral and the communication application remains downstream-defined, use Create Layout. Return to Create Template dispatch before the shared confirmation marker is emitted when the evidence supports a different kind.## 2. Deck Brief and Schema@@ -43,7 +43,11 @@ Add these child-owned requirements to Create Template Step 2:| Field | Requirement ||---|---|| Deck ID and display name | Required; `deck_id` is a filesystem-safe ASCII slug |-| Use cases and design intent | Required; becomes the Template Overview |+| 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 || 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 |@@ -57,7 +61,7 @@ Write this complete schema:deck_id: <confirmed slug>kind: deckcategory: brand | general | scenario | government | special-summary: <one-line use case and tone>+summary: <one-line recurring presentation family and intended outcome>keywords: [<three-to-five tags>]primary_color: "#XXXXXX"canvas_format: ppt169@@ -82,6 +86,12 @@ page_count: <N>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.+## 3. Author or Materialize the DeckFollow Create Template Step 4 and the shared Template_Designer contract with `kind: deck`, `kind_dir: decks`, and `id_key: deck_id` fixed. Do not ask the user to choose the kind again.@@ -103,9 +113,9 @@ Every SVG is a complete preview and declares one root Master and Layout under thIn 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`.+- `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; conditional sections match real choices/assets.+- 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.- 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.mdindex 7e67c77b..ad8e2626 100644--- a/skills/ppt-master/workflows/create-template/create-layout.md+++ b/skills/ppt-master/workflows/create-template/create-layout.md@@ -15,9 +15,9 @@ Enter this child workflow only after [`Create Template`](../create-template.md)**Hard rule — child workflow, not a top-level route**: Create Layout 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 — structure only**: A layout owns canvas, page grammar, Master/Layout families, slot geometry, page types, image behavior, density rhythm, and the SVG prototype roster. It owns no brand palette, typography system, logo, voice, or icon identity.+**Hard rule — brand-neutral structure only**: A layout owns canvas, page grammar, Master/Layout families, slot geometry, semantic text roles, alignment/wrapping/capacity behavior, page types, image behavior, density rhythm, and the SVG prototype roster. It owns no brand palette, typeface/weight identity, final resolved type scale, logo, voice, icon identity, communication objective, audience outcome, required narrative sequence, fixed scenario copy, or example content that downstream generation is expected to preserve.-Neutral colors and safe fonts may appear in SVG prototypes so the structure is reviewable. They are preview paint, not a locked identity segment, and must not be written as brand truth in `design_spec.md`.+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 project type scale, and must not be written as brand truth in `design_spec.md`. The reusable rule is the text role and its spatial behavior. Downstream `layout` scope resolves actual appearance from Brand, reading mode, and confirmed project typography; explicit `mirror` scope preserves the literal source formatting instead.## Invocation Points@@ -29,10 +29,11 @@ Neutral colors and safe fonts may appear in SVG prototypes so the structure is rUse Create Template Step 1 for source ingestion and replication-mode eligibility. Interpret source evidence only for reusable structure:-- Canvas dimensions, grid, zones, page taxonomy, repeated chrome, image placement, density rhythm, and placeholder geometry may become layout facts or suggestions.-- Colors, fonts, logos, voice, and icon style remain source context only. Do not copy them into the layout identity because a layout has no identity segment.-- When the source is branded, explicitly confirm that Create Layout will strip that identity. 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 source contains a complete current structure contract and preserves validated structure facts in a new workspace without modifying the source.+- 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.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.@@ -43,11 +44,11 @@ Add these child-owned requirements to Create Template Step 2:| Field | Requirement ||---|---|| Layout ID and display name | Required; `layout_id` is a filesystem-safe ASCII slug |-| Structural use cases | Required; describe content shapes and presentation contexts, not brand tone |+| Structural use cases | Required; describe content shapes and delivery settings the geometry can support, not communication objectives, audience outcomes, narrative sequence, or brand tone || Canvas | Required; exact format, dimensions, and `viewBox` |-| Page grammar | Required; page types, variants, grids, zones, density rhythm, and image behavior |+| 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 eligible `mirror` under Create Template Step 1 |+| Replication mode | Required; `standard`, eligible `fidelity`, or `mirror` only when the complete source contract is already brand-neutral and application-neutral || Identity stripping | Required when branded reference material exists; list the identity facts intentionally excluded |Write this structure-only schema:@@ -78,7 +79,10 @@ page_types: [cover, toc, chapter, content, ending]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. `Page Roster` lists every SVG with its Master/Layout identity, picker name, intended content shape, and slot behavior.+`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.++`category: scenario` is a discovery-fit label only. It does not authorize a+Template Overview or scenario-specific content policy.## 3. Author or Materialize the Layout@@ -95,7 +99,7 @@ The output is:└── exports/ # conditional review evidence```-Every SVG is a complete preview and declares one root Master and Layout under the shared structured contract. For authored modes, neutral preview paint must remain replaceable downstream. For mirror, preserve source structure and supported visuals exactly as allowed by Create Template, while keeping identity fields out of the layout spec.+Every SVG is a complete preview and declares one root Master and Layout under the shared structured contract. For authored modes, neutral preview paint must remain replaceable downstream. For mirror, first prove the source contract already satisfies the complete Layout boundary, then preserve its structure and supported visuals exactly as allowed by Create Template. Never call removal or replacement of source identity or application rules “mirror”.## 4. Layout Validation@@ -103,10 +107,11 @@ In addition to Create Template Steps 5–6, verify:- `templates/design_spec.md` contains `layout_id`, `kind: layout`, `summary`, canvas fields, `replication_mode`, `native_structure_mode: structured`, `page_count`, and `page_types`.- `layout_id` matches the confirmed workspace ID in library scope.-- Signature Design Elements and Page Roster exist; Template Overview and all identity sections do not.-- `primary_color`, brand palette, brand typography, logo, voice, and icon-identity claims are absent.+- Signature Design Elements and Page Roster exist; Template Overview, application-contract language, and all identity sections do not.+- `primary_color`, brand palette, brand typeface/weight claims, final project type-scale claims, logo, voice, and icon-identity claims are absent; structural text roles and capacity rules may remain.- Every SVG in the roster satisfies the shared Master/Layout/slot contract and the roster is bidirectionally complete.- Neutral prototype paint is not described as a locked brand identity.+- `replication_mode: mirror` is rejected for any source that retains organization-specific identity or reusable application rules; use authored Layout mode or Create Deck instead.For library scope, Create Template validates and registers with:diff --git a/skills/ppt-master/workflows/index.md b/skills/ppt-master/workflows/index.mdindex 728a1e1b..83d49a9c 100644--- a/skills/ppt-master/workflows/index.md+++ b/skills/ppt-master/workflows/index.md@@ -27,8 +27,8 @@ Registry for the route authorities and supporting runbooks referenced by [`SKILL|---|---|---|---|| Generation profile | `beautify-pptx` | [`profiles/beautify-pptx.md`](./profiles/beautify-pptx.md) | Generate PPTX route when wording, page count, and page order are frozen 1:1 || Template child workflow | `create-brand` | [`create-template/create-brand.md`](./create-template/create-brand.md) | Create Template after identity-only intent is selected |-| Template child workflow | `create-layout` | [`create-template/create-layout.md`](./create-template/create-layout.md) | Create Template after brand-neutral structure-only intent is selected |-| Template child workflow | `create-deck` | [`create-template/create-deck.md`](./create-template/create-deck.md) | Create Template after integrated identity-and-structure intent is selected or defaulted |+| Template child workflow | `create-layout` | [`create-template/create-layout.md`](./create-template/create-layout.md) | Create Template after brand-neutral, application-neutral structure intent is selected |+| Template child workflow | `create-deck` | [`create-template/create-deck.md`](./create-template/create-deck.md) | Create Template after a branded structural system or recurring presentation application is selected || Intake stage | `topic-research` | [`stages/topic-research.md`](./stages/topic-research.md) | Generate PPTX route before Step 1 for topic-only requests || Control stage | `resume-execute` | [`stages/resume-execute.md`](./stages/resume-execute.md) | Generate PPTX route when a planned project resumes in a fresh chat || Planning stage | `refine-spec` | [`stages/refine-spec.md`](./stages/refine-spec.md) | Generate PPTX route after confirmation when the user explicitly requests spec review |diff --git a/skills/ppt-master/workflows/routing.md b/skills/ppt-master/workflows/routing.mdindex a5a3fe20..9dfc01ed 100644--- a/skills/ppt-master/workflows/routing.md+++ b/skills/ppt-master/workflows/routing.md@@ -86,11 +86,17 @@ When a PPTX already contains native Master/Layout parts, `create-template` mirro| Selected kind | Behavior ||---|---|| `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 structure and an SVG roster |-| `deck` | Dispatch to [`create-deck`](./create-template/create-deck.md); author identity, structure, template overview, and an 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 |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.+**Hard rule — classify reusable rules, not source completeness**: A complete+PPTX does not automatically select Deck. Use Brand when only identity is+stable; use Layout when structure is brand-neutral and the communication+application stays downstream-defined; use Deck when structure carries identity+or reusable scenario/content semantics.+---## 6. Native and Shared Post-Processing Boundary