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
feat(templates): add reusable style workspaces
hugohe37987664e91cb
diff --git a/AGENTS.md b/AGENTS.mdindex fbd2db92..ee8e79b8 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -20,7 +20,7 @@ PPT Master turns source material into natively editable DrawingML PPTX. Generate## Execution Requirements-- For any `brand`, `layout`, or `deck` workspace creation from PPTX/SVG, images/PDFs, documents/websites, brand assets, direct text, or mixed references, enter [`skills/ppt-master/workflows/create-template.md`](skills/ppt-master/workflows/create-template.md); it keeps the fixed Create Template name and dispatches exactly one of [`create-brand`](skills/ppt-master/workflows/create-template/create-brand.md), [`create-layout`](skills/ppt-master/workflows/create-template/create-layout.md), or [`create-deck`](skills/ppt-master/workflows/create-template/create-deck.md).+- For any `brand`, `style`, `layout`, or `deck` workspace creation from PPTX/SVG, images/PDFs, documents/websites, brand assets, direct text, or mixed references, enter [`skills/ppt-master/workflows/create-template.md`](skills/ppt-master/workflows/create-template.md); it keeps the fixed Create Template name and dispatches exactly one of [`create-brand`](skills/ppt-master/workflows/create-template/create-brand.md), [`create-style`](skills/ppt-master/workflows/create-template/create-style.md), [`create-layout`](skills/ppt-master/workflows/create-template/create-layout.md), or [`create-deck`](skills/ppt-master/workflows/create-template/create-deck.md).- Always-on SVG constraints live in [`skills/ppt-master/references/shared-standards-core.md`](skills/ppt-master/references/shared-standards-core.md). Load [`svg-effects.md`](skills/ppt-master/references/svg-effects.md), [`native-data-interface.md`](skills/ppt-master/references/native-data-interface.md), and [`pptx-structure-interface.md`](skills/ppt-master/references/pptx-structure-interface.md) only when their documented execution triggers apply.- Canvas choices live in [`skills/ppt-master/references/canvas-formats.md`](skills/ppt-master/references/canvas-formats.md).- Icon library details live in [`skills/ppt-master/templates/icons/README.md`](skills/ppt-master/templates/icons/README.md).diff --git a/README.md b/README.mdindex 4f41cbaa..027e0d09 100644--- a/README.md+++ b/README.md@@ -110,7 +110,7 @@ And that depth is a **direction of travel, not a fixed checklist.** PPT Master'sIn form, it's a workflow (a "skill") that runs inside any agent-capable AI tool: tell it in chat — "make a deck from this PDF" — and it runs the workflow on your machine and exports a natively editable `.pptx`. No coding on your side; you do exactly three things — install Python, install an AI tool, drop in your material.-Generating a new deck from source documents is the main pipeline, but not the only route. PPT Master can also distill reusable brand / layout / deck templates from your references, fill an existing `.pptx` with new content while preserving its design, and add native transitions, animations, and narration to a finished deck — each route with an explicit contract for what gets preserved.+Generating a new deck from source documents is the main pipeline, but not the only route. PPT Master can also distill reusable brand / style / layout / deck templates from your references, fill an existing `.pptx` with new content while preserving its design, and add native transitions, animations, and narration to a finished deck — each route with an explicit contract for what gets preserved.On top of that native depth, this form comes with three promises:diff --git a/README_CN.md b/README_CN.mdindex 22851962..93e1a699 100644--- a/README_CN.md+++ b/README_CN.md@@ -114,7 +114,7 @@形态上,它是一套在有 Agent 能力的 AI 工具里运行的工作流(一个 "skill"):你在对话框里说"用这份 PDF 做一份 PPT",它就按流程在你本机生成、导出原生可编辑的 `.pptx`。你不写任何代码,只做三件事——装 Python、装一个 AI 工具、把材料放进来。-从源材料生成新 deck 是主管线,但不是唯一路线:PPT Master 还能从你的参考资料中提炼可复用的品牌 / 版式 / 成品模板,把新内容填进你已有的 `.pptx` 并保留其设计,或为成品 deck 追加原生转场、动画和旁白——每条路线都有明确的保留契约。+从源材料生成新 deck 是主管线,但不是唯一路线:PPT Master 还能从你的参考资料中提炼可复用的品牌 / 风格 / 版式 / 成品模板,把新内容填进你已有的 `.pptx` 并保留其设计,或为成品 deck 追加原生转场、动画和旁白——每条路线都有明确的保留契约。在这份原生深度之上,这个形态还带来三个承诺:diff --git a/docs/README.md b/docs/README.mdindex 62609f5c..7ae4e164 100644--- a/docs/README.md+++ b/docs/README.md@@ -20,7 +20,7 @@ User-facing documentation lives in this directory: English files are the canonic|---|---|| [Audio Narration](./audio-narration.md) | Speaker notes to per-slide narration: providers, voice cloning, timing, PPTX embedding || [Transitions & Animations](./animations.md) | Default behavior and customization for page transitions and per-element object animations |-| [Templates Guide](./templates-guide.md) | Creating and applying brand / layout / deck templates |+| [Templates Guide](./templates-guide.md) | Creating and applying brand / style / layout / deck templates |## Architecture & Internals@@ -28,7 +28,7 @@ User-facing documentation lives in this directory: English files are the canonic|---|---|| [Technical Design](./technical-design.md) | Architecture, design philosophy, why SVG → DrawingML || [PowerPoint–SVG Mapping](./powerpoint-svg-mapping.md) | Feature-by-feature mapping between PowerPoint constructs and the pipeline |-| [Templates Architecture](./templates-architecture.md) | Design of the brand / layout / deck template system |+| [Templates Architecture](./templates-architecture.md) | Design of the brand / style / layout / deck template system |## Project Directiondiff --git a/docs/faq.md b/docs/faq.mdindex 06cee78f..c52b4ca8 100644--- a/docs/faq.md+++ b/docs/faq.md@@ -313,7 +313,7 @@ You don't need to supply every detail upfront — the AI agent will ask follow-u**Step 3 — Wait for the Result**-The AI agent will handle the rest — analyzing your references, building the layout definitions, and validating the template. If you request PowerPoint review, it also generates `exports/<id>_template_preview.pptx` on demand. Both scopes require `templates/` and use optional `images/`, `icons/`, and `exports/`: library scope writes `skills/ppt-master/templates/<kind>/<id>/` and registers it; project scope writes `projects/<name>/` and skips registration. Empty optional directories are omitted. Give that workspace root to Step 3; it never copies `exports/`, and library review exports are Git-ignored. A flat workspace with `design_spec.md` at the root remains compatible only when its SVGs already satisfy the current contract; semantic-legacy packages must be replaced through `create-template` rather than upgraded in place.+The AI agent will handle the rest — analyzing your references, writing the kind-specific specification, building structured layout definitions only for Layout/Deck, and validating the workspace. Brand/Style never create a preview PPTX; Layout/Deck generate `exports/<id>_template_preview.pptx` on request and require it for multiple Masters. Both scopes require `templates/`; Brand/Layout/Deck may use package-owned `images/` and `icons/`, while Style contains only `templates/design_spec.md`. Library scope writes `skills/ppt-master/templates/<kind>/<id>/` and registers it; project scope writes `projects/<name>/` and skips registration. Empty optional directories are omitted. Give that workspace root to Step 3; it never copies `exports/`, and library review exports are Git-ignored. A compatible legacy-flat Brand/Layout/Deck workspace remains readable only when it satisfies the current kind contract; Layout/Deck also require current structured SVGs. Style has no legacy-flat form, and semantic-legacy packages must be replaced through `create-template` rather than upgraded in place.> **Tip**: The more specific you are about the style and use case, the better the generated template will match your expectations.diff --git a/docs/getting-started.md b/docs/getting-started.mdindex 2b4d747e..cda920f8 100644--- a/docs/getting-started.md+++ b/docs/getting-started.md@@ -18,14 +18,14 @@ The short path to your first deck, how to use everything around it — templates## Start from a template-**Optional.** By default PPT Master uses **free design** — you don't need a template, and you can skip to the next section. Reach for one only when a deck must reuse a fixed layout set or brand identity.+**Optional.** By default PPT Master uses **free design** — you don't need a template, and you can skip to the next section. Reach for one when a deck must reuse a brand identity, a communication/design method, a fixed layout set, or a recurring deck application.**Two ways to reuse an existing `.pptx`, depending on what you want back:**| You want… | Route | What happens ||---|---|---|| **Use this deck's native slide shells with new content** | Fill Native PPTX | Clones the selected source slides and patches text / table / chart data directly in OOXML. The source design remains native; output is a new filled deck bound to the available slide shells. |-| **Build a reusable design system, then generate a new deck** | Create Template → Generate PPTX | Creates a validated Brand, Layout, or Deck workspace from the reference, then authors a fresh deck. The new story, structure, and page count can differ from the source. |+| **Build a reusable design system, then generate a new deck** | Create Template → Generate PPTX | Creates a validated Brand, Style, Layout, or Deck workspace from the reference, then authors a fresh deck. The new story, structure, and page count can differ from the source. |For the first, give the AI your `.pptx` plus your material (or a topic) and ask it to "fill this deck with the new content" — see the [template-fill workflow](../skills/ppt-master/workflows/template-fill-pptx.md). The rest of this section covers create-template.@@ -35,7 +35,7 @@ For the first, give the AI your `.pptx` plus your material (or a topic) and askYou: Create a reusable Deck template from projects/brand/our_deck.pptx via /create-template```-Create Template analyzes the reference, confirms whether the result is a Brand, Layout, or Deck, and then authors or materializes a new validated workspace. The importer supplies source evidence; the final workspace owns `templates/design_spec.md`, any required SVG prototypes, and matching assets. If you want a PowerPoint review file, run the optional preview export; it creates `exports/<id>_template_preview.pptx` on demand. The workspace root is what you point to at generation time.+Create Template analyzes the reference, confirms whether the result is a Brand, Style, Layout, or Deck, and then authors or materializes a new validated workspace. The importer supplies source evidence; the final workspace owns `templates/design_spec.md` plus any prototypes and assets required by its kind. Brand and Style are roster-free; Layout and Deck own structured SVG prototypes. If you want a PowerPoint review file for Layout or Deck, run the optional preview export; it creates `exports/<id>_template_preview.pptx` on demand. The workspace root is what you point to at generation time.During the create-template brief, choose `library` (the existing default) or `project`. Both require `templates/` and use optional `images/`, `icons/`, and on-demand `exports/`; empty optional directories are omitted. Project scope requires an initialized target project; library scope alone adds global registration.@@ -46,7 +46,7 @@ A created template lives in one of two places:| **Registered in the skill library** | `skills/ppt-master/templates/<kind>/<id>/` | Portable workspace plus global registration, so it appears when you ask "what templates are available?" || **Under projects** | `projects/<name>/` | The same portable workspace without global registration |-Invoke either result by giving its **workspace-root path** in chat. Step 3 resolves `templates/design_spec.md`; for directory-shape compatibility it also accepts a flat root whose direct `design_spec.md` and SVGs already satisfy the current contract. A create-template run may hand its exact validated workspace root directly to Step 3 in the same conversation. Both cases stay path-based; a bare template name never triggers. The complete workspace can be copied or migrated between the library and `projects/` without restructuring it; only library registration changes.+Invoke either result by giving its **workspace-root path** in chat. Step 3 resolves `templates/design_spec.md`; for directory-shape compatibility it also accepts a legacy-flat Brand/Layout/Deck root that satisfies its current kind contract. Layout/Deck additionally require current structured SVGs; Style has no flat form. A create-template run may hand its exact validated workspace root directly to Step 3 in the same conversation. Both cases stay path-based; a bare template name never triggers. The complete workspace can be copied or migrated between the library and `projects/` without restructuring it; only library registration changes.```You: Make a deck from sources/report.pdf with template skills/ppt-master/templates/layouts/presentation_core/diff --git a/docs/project-positioning.md b/docs/project-positioning.mdindex 10b41930..7f7e4cee 100644--- a/docs/project-positioning.md+++ b/docs/project-positioning.md@@ -14,7 +14,7 @@ This English file is the canonical policy source. The [Chinese version](./zh/pro> **PPT Master is an open-source, chat-driven workflow that lets AI reason the argument into shape first, then design and produce a real, editable PowerPoint — not slide images or a thin editable skin. Its defining axis is native depth: author or preserve more of PowerPoint's own object model, behavior, and reusable structure, release after release.**-The input may be a topic, source material, data, design references, brand assets, or an existing `.pptx`. The main pipeline creates a new deck; other explicit routes and profiles can distill reusable Brand / Layout / Deck workspaces, fill an existing PowerPoint with new content, redesign it, or add native presentation behavior while preserving what their contracts promise to keep.+The input may be a topic, source material, data, design references, brand assets, or an existing `.pptx`. The main pipeline creates a new deck; other explicit routes and profiles can distill reusable Brand / Style / Layout / Deck workspaces, fill an existing PowerPoint with new content, redesign it, or add native presentation behavior while preserving what their contracts promise to keep.That native depth is a direction of travel, not a fixed checklist. PPT Master's north star is to keep converging with PowerPoint itself, narrowing the gap between what an AI can generate and what a skilled user can build by hand. The [PowerPoint ↔ SVG Mapping Guide](./powerpoint-svg-mapping.md) records the current boundary honestly, feature by feature.@@ -72,7 +72,7 @@ The capability model is broader than one generation pipeline, but deliberately n|---|---|| Presentation reasoning | Turn a topic or source bundle into an audience-aware message, narrative mode, outline, page plan, and explicit design direction || Native presentation authoring | Create new slide visuals and compile them into a real, natively editable PowerPoint deck |-| Reusable presentation design | Distill, create, combine, validate, and apply Brand, Layout, and Deck workspaces |+| Reusable presentation design | Distill, create, combine, validate, and apply Brand, Style, Layout, and Deck workspaces || Existing-deck adaptation | Redesign an existing deck, fill native slide shells with new content, or add native behaviors under distinct preservation contracts || PowerPoint expression | Use images, diagrams, charts, tables, formulas, notes, narration, transitions, and animation when they serve the communication goal || Review and delivery | Preview, inspect, validate, repair, export, read back, and retain enough local project state for later refinement or re-export |@@ -160,7 +160,7 @@ Future work should improve this outcome in the following priority order:1. Native depth, output correctness, and delivery reliability.2. Content reasoning, narrative quality, and visual coherence.-3. Reuse of brands, layouts, decks, and existing PowerPoint assets.+3. Reuse of brands, styles, layouts, decks, and existing PowerPoint assets.4. Human review, correction, and controlled iteration.5. Additional formats, providers, and convenience features that strengthen the first four priorities.diff --git a/docs/roadmap.md b/docs/roadmap.mdindex 9c803670..51a0e23b 100644--- a/docs/roadmap.md+++ b/docs/roadmap.md@@ -12,7 +12,7 @@The defining axis is **native depth**: author or preserve more of PowerPoint's own object model, behavior, and reusable structure, release after release — converging with PowerPoint itself. The [positioning charter](./project-positioning.md) states the full thesis; the [PowerPoint ↔ SVG Mapping Guide](./powerpoint-svg-mapping.md) records the current boundary honestly, feature by feature.-Today that axis is expressed through four explicit artifact routes: **Generate PPTX** authors newly designed slides through constrained SVG → DrawingML; **Create Template** produces reusable Brand / Layout / Deck workspaces; **Fill Native PPTX** and **Enhance Native PPTX** preserve existing packages through scoped OOXML operations.+Today that axis is expressed through four explicit artifact routes: **Generate PPTX** authors newly designed slides through constrained SVG → DrawingML; **Create Template** produces reusable Brand / Style / Layout / Deck workspaces; **Fill Native PPTX** and **Enhance Native PPTX** preserve existing packages through scoped OOXML operations.---diff --git a/docs/technical-design.md b/docs/technical-design.mdindex 0feae64f..705560a9 100644--- a/docs/technical-design.md+++ b/docs/technical-design.md@@ -59,8 +59,8 @@ User Input (PDF/DOCX/XLSX/PPTX/URL/Markdown/topic text)├── If canonical same-stem Markdown is absent, run ppt_to_md.py against that archived PPTX└── Content-type files in sources/ become the content contract↓-[Template / Brand / Layout (optional)] — default: skip, proceed with free design- Trigger only on an explicit current-contract Brand/Layout/Deck workspace-root path: either a global-library entry root or a project workspace root+[Template / Brand / Style / Layout (optional)] — default: skip, proceed with free design+ Trigger only on an explicit current-contract Brand/Style/Layout/Deck workspace-root path: either a global-library entry root or a project workspace rootRaw PPTX template requests route to template-fill; reusable SVG templates are created by create-template first↓[Strategist] - three-stage Strategist confirmation stage & Design Specifications → design_spec.md + spec_lock.md@@ -165,8 +165,8 @@ Use this table before reasoning about implementation details. Most failed runs s| Raw PPTX template plus new material/topic | Fill Native PPTX (`template-fill-pptx`) | clone/fill native slides; no SVG generation || Existing PPTX, preserve page count/order/wording 1:1, improve layout | Generate PPTX + `beautify-pptx` profile | regenerate through SVG; content and pagination are locked || Finished PPTX, keep content/layout stable, add notes/audio/timings/transitions | Enhance Native PPTX (`native-enhance-pptx`) | direct OOXML patch; no design regeneration |-| User wants a reusable template workspace from one or more PPTX/SVG files, images/PDFs, documents/websites, brand assets, direct text, or a mixed reference bundle | Create Template (`create-template`) | the fixed entry reads every applicable evidence channel, dispatches one Create Brand, Create Layout, or Create Deck child workflow, then returns a workspace root for Generate Step 3; structured children may export a review PPTX |-| User supplies an explicit current-contract template path | Generate PPTX Step 3 | Brand/Layout/Deck workspaces resolve `templates/design_spec.md`; flat roots may resolve direct `design_spec.md`; semantic-legacy packages are rejected and replaced through Create Template |+| User wants a reusable template workspace from one or more PPTX/SVG files, images/PDFs, documents/websites, brand assets, direct text, or a mixed reference bundle | Create Template (`create-template`) | the fixed entry reads every applicable evidence channel, dispatches one Create Brand, Create Style, Create Layout, or Create Deck child workflow, then returns a workspace root for Generate Step 3; structured children may export a review PPTX |+| User supplies an explicit current-contract template path | Generate PPTX Step 3 | Current Brand/Style/Layout/Deck workspaces resolve `templates/design_spec.md`; only compatible legacy-flat Brand/Layout/Deck roots may resolve direct `design_spec.md`; semantic-legacy packages are rejected and replaced through Create Template || User asks to tune object-level animation order/effect/timing | Generate PPTX + `customize-animations` stage | optional export policy via `animations.json` || User asks to preview, select, annotate, or re-export browser edits | Generate PPTX + `live-preview` stage | annotations apply only at defined handoff points |@@ -367,9 +367,9 @@ Templates are **opt-in, not default**. The default Strategist flow is free desig**Why default to free design.** Templates are floors that easily become ceilings: they lock the deck into the template's visual idioms regardless of how the content actually wants to be presented. Free-design layouts derive structure from the source content rather than imposing it from a fixed grammar, so the visual rhythm tracks the content rather than fighting it. Constrained mode is genuinely better in narrow cases (brand-locked decks, strongly-typed scenarios like academic defense or government report), so it stays available — but the AI doesn't proactively reach for it; the user does.-**Mechanical trigger, not semantic matching.** A bare name like `presentation_core`, a brand mention, or a style phrase such as "McKinsey style" does not trigger Step 3 even if a matching library directory exists. Step 3 consumes an explicit path. Current Brand/Layout/Deck workspaces resolve `templates/design_spec.md`; compatible flat-directory packages resolve direct `design_spec.md` only when their SVGs already satisfy the current contract. Directory shape never authorizes structure migration. A package with legacy Master/Layout/placeholder semantics must be replaced by a newly created template workspace before Step 3. Discoverability is handled by template indexes and explicit Q&A ("what templates are available?"), not by runtime fuzzy matching.+**Mechanical trigger, not semantic matching.** A bare name like `presentation_core`, a brand mention, or a style phrase such as "McKinsey style" does not trigger Step 3 even if a matching library directory exists. Step 3 consumes an explicit path. Current Brand/Style/Layout/Deck workspaces resolve `templates/design_spec.md`; compatible flat Brand/Layout/Deck packages may resolve direct `design_spec.md` only when they satisfy the current kind contract, including current structured SVGs for Layout/Deck. Style has no legacy-flat form. A free-form style brief remains ordinary Stage-2 input; only an explicit `kind: style` workspace path activates the reusable Style contract. Directory shape never authorizes structure migration. A package with legacy Master/Layout/placeholder semantics must be replaced by a newly created template workspace before Step 3. Discoverability is handled by template indexes and explicit Q&A ("what templates are available?"), not by runtime fuzzy matching.-All current Brand/Layout/Deck packages use one workspace routing contract. Brand workspaces omit the SVG roster; empty optional directories are omitted:+All current Brand/Style/Layout/Deck packages use one workspace routing contract. Brand and Style workspaces omit the SVG roster; empty optional directories are omitted:```text<template_workspace>/@@ -380,15 +380,20 @@ All current Brand/Layout/Deck packages use one workspace routing contract. Brand└── exports/ # optional, on-demand review files; Git-ignored in the library```+Style narrows this routing shape to `templates/design_spec.md` only; it does+not carry asset or review payloads. Existing project scaffolding is not Style+input.+`<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/`.-For Create Layout / Create Deck, `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. Create Brand analyzes and materializes identity fragments only; it does not enter these structural replication strategies or produce an SVG roster.+For Create Layout / Create Deck, `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. Create Brand analyzes identity fragments only; Create Style extracts portable method/direction only. Neither enters structural replication strategies or produces an SVG roster.-The three template kinds own different segments of the design contract:+The four 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 |+| `style` | direction / method | communication method, open page roles, evidence/data rules, visual defaults, image/icon direction, advisory review focus | seeds Stage 2; Style-only stays flat, while fusion follows the selected Layout/Deck structure; never becomes identity truth or triggers visual review || `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, representative page roles, identity, and actual SVG roster | contributes descriptive context and prototypes that Strategist compares with the independently confirmed Stage-1 contract and current content before deriving the application plan |@@ -400,11 +405,11 @@ formatting from those rules plus the confirmed reading mode/type scale;`mirror` preserves literal source formatting and text topology. Export mayplace 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.+When several paths are supplied, fusion is segment-level, not field-level. Brand owns identity, Style owns direction/method defaults, Layout owns compatible structure, and Deck supplies descriptive recurring-application context plus fallback identity/structure under the current Stage-1 communication contract. User confirmation remains highest. Style palette/type defaults never override Brand/Deck identity; its method/composition expectations must be compatible with the selected Deck application and Layout/Deck structure or 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 files cannot be Step 3 workspaces.** Normal Generate may use a PPTX as source material, and `beautify-pptx` may redesign it while preserving page count, order, and per-page wording 1:1; neither treats the source PPTX as a Step 3 template. When a raw PPTX is used as a template or native slide shell and filled with new material, the default route is Fill Native PPTX. If the request permits splitting, merging, dropping, reordering, or narrative restructuring, it remains Generate. Only a request to create a reusable template workspace and reuse that design system in SVG-route Step 3 first runs Create Template and then supplies the generated workspace root.-**Layouts are opt-in; charts and icons are not.** The asymmetry isn't an inconsistency — *layout* is what locks visual idiom (the floor/ceiling problem above), while charts and icons are reusable primitives that don't impose deck-wide style. Same `templates/` directory, different role in the visual contract.+**Template contracts are opt-in; charts and icons are not.** The asymmetry is intentional: Layout locks reusable structure, Style locks direction/method defaults, Brand locks identity, and Deck combines a recurring application with identity and structure. Charts and icons are reusable primitives that do not by themselves impose a deck-wide contract. Same `templates/` directory, different ownership.---@@ -770,7 +775,7 @@ Supporting files stay separate only to keep route contracts focused and load opt| Class | Runbooks | Owning route ||---|---|---|| Generation profiles | `beautify-pptx`, `quick-generate` | Generate PPTX with either wording/page invariants or the explicit direct SVG-to-PPTX short circuit |-| 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 |+| Template child workflows | `create-brand`, `create-style`, `create-layout`, `create-deck` | Create Template dispatches exactly one for identity-only, roster-free direction/method, brand-neutral/application-neutral structure, or a recurring application with integrated identity/structure || Template-input stage | `apply-template-workspace` | Generate PPTX Step 3; loaded only when an explicit workspace-root path triggers it || 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 |diff --git a/docs/templates-architecture.md b/docs/templates-architecture.mdindex 7137f0cf..c2636c78 100644--- a/docs/templates-architecture.md+++ b/docs/templates-architecture.md@@ -1,28 +1,29 @@-# Template Architecture: Brand / Layout / Deck+# Template Architecture: Brand / Style / Layout / Deck[English](./templates-architecture.md) | [Chinese](./zh/templates-architecture.md)----> This is the **architecture alignment document**. It defines the three template kinds at the data-model layer, the field sets of each `design_spec.md`, and the multi-path fusion + conflict resolution rules. Audience: contributors and AI workflows; answers "what should / shouldn't a template directory contain; how do they combine when multiple are supplied".+> This is the **architecture alignment document**. It defines the four template kinds at the data-model layer, the field sets of each `design_spec.md`, and the multi-path fusion + conflict resolution rules. Audience: contributors and AI workflows; answers "what should / shouldn't a template directory contain; how do they combine when multiple are supplied".>> For user-facing usage (how to trigger, how to pick), see [`templates-guide.md`](./templates-guide.md); not repeated here.----## 1. The three kinds+## 1. The four kinds| 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` |+| **Style** | `templates/styles/<id>/` | Portable direction/method: communication method, page-role vocabulary, evidence/data expression, visual defaults, image/icon direction, advisory review focus | No identity truth, application contract, canvas, page structure, or SVG roster | `workflows/create-template/create-style.md` || **Layout** | `templates/layouts/<id>/` | Brand-neutral structure segment only: canvas / page structure / semantic text roles / page types / SVG roster | No brand identity and no recurring communication application | `workflows/create-template/create-layout.md` || **Deck** | `templates/decks/<id>/` | A recurring presentation family: descriptive application context + integrated identity + structure | — | `workflows/create-template/create-deck.md` |-Every newly created Layout/Deck SVG is a complete preview with root Master/Layout key and picker names, direct atomic Master/Layout elements, and top-level semantic slot groups. A normal slot has positive design-zone bounds and exactly one compatible carrier; composite `object` regions use explicit proxy binding, and zero-slot Layouts are valid. These specialized markers are authoritative; minimal `data-pptx-role` hints are added only for structural page-frame behavior they cannot express. Create Template derives `standard` / `fidelity` / `mirror` internally from the natural-language intent and source evidence. Authored strategies create new SVGs and structure; mirror materializes validated source facts. Strategist later derives strict/adaptive exporter behavior from the actual prototypes and current content. None of these implementation values is a required user choice. A flat directory with `design_spec.md` at its root remains a supported compatibility shape only when its SVGs satisfy the current contract. Semantic-legacy packages must be replaced by a newly created template workspace; they are never upgraded in place.+Every newly created Layout/Deck SVG is a complete preview with root Master/Layout key and picker names, direct atomic Master/Layout elements, and top-level semantic slot groups. A normal slot has positive design-zone bounds and exactly one compatible carrier; composite `object` regions use explicit proxy binding, and zero-slot Layouts are valid. These specialized markers are authoritative; minimal `data-pptx-role` hints are added only for structural page-frame behavior they cannot express. Create Template derives `standard` / `fidelity` / `mirror` internally from the natural-language intent and source evidence. Authored strategies create new SVGs and structure; mirror materializes validated source facts. Strategist later derives strict/adaptive exporter behavior from the actual prototypes and current content. None of these implementation values is a required user choice. A legacy-flat Brand/Layout/Deck directory with `design_spec.md` at its root remains readable only when it satisfies the current kind contract; Style has no legacy-flat form. Semantic-legacy packages must be replaced by a newly created template workspace; they are never upgraded in place.-The three are **parallel reusable-rule bundles**, not PowerPoint package-object types. In library scope, the physical directory and the frontmatter `kind` field correspond one-to-one:+The four are **parallel reusable-rule bundles**, not PowerPoint package-object types. In library scope, the physical directory and the frontmatter `kind` field correspond one-to-one:-The fused project-level `design_spec.md` retains the existing routing `kind`: `deck` when both identity and structure are present, `layout` when only structure is present, and `brand` when only identity is present. For a project-local Brand + Layout composition, this label means “both capabilities are installed”; it does not promote that composition into a reusable library Deck or invent application context. The current project's Stage-1 communication contract supplies that context. Strategist derives the template application plan internally; the confirmation page exposes no template mode controls.+The fused project-level `design_spec.md` retains the existing capability label: `deck` when both identity and structure are present, `layout` when structure is present without identity, `brand` when identity is present without structure, and `style` only when direction/method is the sole reusable segment. Style combined with another kind does not change that kind label. For a project-local Brand + Layout composition, `kind: deck` means “both capabilities are installed”; it does not promote that composition into a reusable library Deck or invent application context. The current project's Stage-1 communication contract supplies that context. Strategist derives the template application plan internally; the confirmation page exposes no template mode controls.```yaml# templates/brands/anthropic/templates/design_spec.md@@ -31,6 +32,12 @@ kind: brand...---+# templates/styles/consulting_analytical/templates/design_spec.md+---+kind: style+...+---+# templates/layouts/presentation_core/templates/design_spec.md---kind: layout@@ -53,6 +60,7 @@ 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 |+| **Style** | No reusable package structure; confirmed method and visual defaults guide flat Slide-local authoring || **Layout** | Master/Layout/Placeholder topology, reusable geometry, semantic text roles, and spatial slot behavior || **Deck** | The Brand and Layout projections plus descriptive recurring-application context and actual prototypes |@@ -64,11 +72,12 @@ those rules plus the confirmed reading mode/type scale; `mirror` preservesliteral source formatting and text topology. Export then compiles theapplicable rules into the same native Master/Layout graph. Theme is thereforean implementation projection of resolved identity—whether supplied by Brand,-Deck, or the current project—not a fourth template kind.+Deck, or the current project—not another template kind. Style fallback colors+and fonts are proposal seeds, not Theme identity truth.### 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:+`create-template` confirms where a workspace is placed. This execution choice does not add another kind and does not add a PPTX structure mode:| Scope | Workspace root | Core workspace | Discovery ||---|---|---|---|@@ -97,7 +106,7 @@ that root path directly; `templates/icons/` is not part of the package shape.PPTX import uses a two-level metadata model. The temporary lossless SVG keeps native-shape metadata, hidden carriers, and preview evidence as immutable payload backing; `svg_authoring_view.py` creates the editable authoring IR bundle, whose lightweight SVGs carry document-local source refs and whose manifest stores only paths and initial hashes. Authored modes use project-canonical SVG and compact authored-preset groups only for exact registered preset matches. Mirror materializes templates from the IR and reuses converter-supported payload only for unchanged Slide-local/slot refs; fixed structural layers remain direct atoms, unsupported or edited objects keep their SVG fallback, and final templates contain no IR-only refs. Export compiles only the declared SVG structure and never infers ownership.-Both scopes retain `kind: layout` or `kind: deck` in portable frontmatter. `output_scope` and `target_project` stay in the workflow brief and are not persisted into `design_spec.md`.+Both scopes retain their selected `kind` in portable frontmatter. `output_scope` and `target_project` stay in the workflow brief and are not persisted into `design_spec.md`.Before any final write, resolve the selected workspace root, require an empty `templates/` root, and check all planned image and icon destination filenames for conflicts. Check a preview-PPTX destination when review was requested or the confirmed roster contains multiple Masters. Project scope additionally requires an initialized target project. Fail before writing anything; never merge or overwrite.@@ -108,6 +117,7 @@ To make multi-path fusion override cleanly, every field belongs to a named segme| Segment | Sections it contains | Override owner ||---|---|---|| **Identity** | Color Scheme / Typography / Logo / Voice & Tone / Icon Style | brand |+| **Direction / method** | Communication Method / Page Role Vocabulary / Evidence & Data Expression / Visual System Defaults / Image & Icon Direction / Review Focus | style; defaults remain subordinate to user-confirmed choices and owning identity/structure segments || **Structure** | Portable canvas/page-type metadata, structure-owned Signature rules, SVG Page Roster, and the SVG Master/Layout/slot contract | layout || **Application** | Template Overview: recurring situations, audiences/outcomes, delivery assumptions, and representative narrative/page roles | deck only; brand / layout don't write this |@@ -123,9 +133,10 @@ current Strategist decides which prototypes and content to use.mirror maps validated source identities and parentage one-to-one into a newworkspace. Mirror preserves source facts but does not prove that the source isa 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.+A source that yields only identity becomes Brand; reusable method and visual+direction without prototypes becomes Style; 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 sourcecontract is already brand-neutral and application-neutral. Removing brand@@ -165,6 +176,39 @@ primary_color: "<HEX>"**Forbidden**: canvas viewBox, page types, SVG roster — those are layout's responsibility.+### Style schema++**Frontmatter**++```yaml+---+style_id: <slug>+kind: style+summary: <one-line portable method and visual direction>+keywords: [tag1, tag2, tag3]+---+```++**Body sections** (direction/method segment)++| § | Title | Required content |+|---|---|---|+| I | Style Overview | Name, broad best fit, reusable intent, and sources; no bound audience/outcome |+| II | Communication Method | Preferred mode seed, argument flow, page-message discipline, and evidence discipline |+| III | Page Role Vocabulary | Open roles with communication jobs, evidence obligations, and composition tendencies; no order/count |+| IV | Evidence & Data Expression | Claim/evidence rules, fact/assumption/implication/recommendation distinction, chart/table/source guidance |+| V | Visual System Defaults | Visual-style seed, composition, density, decoration, rhythm, and optional fallback palette/type defaults |+| VI | Image & Icon Direction | Rendering, usage, and treatment guidance without an inventory or page mapping |+| VII | Review Focus | Extra checks used only when the user separately enables visual review |++Style writes no SVG and never owns official Brand identity, Deck application,+canvas, page count/order, Master/Layout/placeholder structure, or page-specific+resources. Its palette and typography values are overrideable fallbacks:+user-confirmed choices and Brand/Deck identity values take precedence. Review+Focus cannot activate visual review. `kind: style` identifies this reusable+package; it is distinct from the Stage-2 `visual_style` choice and from the+internal `template_reuse_scope: style` flat-export value.+### Layout schema**Frontmatter**@@ -260,11 +304,11 @@ kind owns this segment”.----## 3. The three index files+## 3. The four index filesEach index maps one-to-one with its physical directory; fields are trimmed to what Strategist actually needs to pick, following the compact "meta + summary" pattern used by [`charts_index.json`](../skills/ppt-master/templates/charts/charts_index.json) while preserving structured metadata that helps selection.-These indexes cover library scope only. A project-root workspace is intentionally absent from all three indexes and remains usable through its explicit `projects/<name>/` path. Because both scopes use the same workspace shape, moving or copying the complete core workspace between them does not require asset-path rewriting; only library registration changes.+These indexes cover library scope only. A project-root workspace is intentionally absent from all four indexes and remains usable through its explicit `projects/<name>/` path. Because both scopes use the same workspace shape, moving or copying the complete core workspace between them does not require asset-path rewriting; only library registration changes.### `templates/brands/brands_index.json`@@ -280,6 +324,20 @@ These indexes cover library scope only. A project-root workspace is intentionall- Keep `primary_color` — Strategist needs the dominant color at first glance when picking a brand- Drop `keywords` — summary already carries the English equivalents; AI matches via natural language (same approach as the charts library)+### `templates/styles/styles_index.json`++```json+{+ "<style_id>": {+ "summary": "Answer-first, evidence-led decision-document defaults without page prototypes or brand identity",+ "keywords": ["consulting", "decision-support", "evidence"]+ }+}+```++- Keep `keywords` because method/direction discovery is semantic and has no structural roster to summarize+- Do not add canvas, page count, or primary color; Style owns neither structure nor identity truth+### `templates/layouts/layouts_index.json````json@@ -317,27 +375,30 @@ These indexes cover library scope only. A project-root workspace is intentionall## 4. Multi-path fusion and conflict resolution-### Override priority (implicit dispatch)+### Segment ownership (implicit dispatch)-When the user supplies a set of explicit workspace-root paths, Step 3 fuses them into `<project>/templates/design_spec.md` per the table below:+When the user supplies explicit workspace-root paths, Step 3 resolves each+segment independently and writes one `<project>/templates/design_spec.md`:-| User paths | Fusion behavior |+| Segment | Starting owner ||---|---|-| (none) | Skip Step 3, free design |-| 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; 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 |+| Identity | Brand, otherwise Deck, otherwise the current project; Style supplies fallback candidates only |+| Direction / method | Style, otherwise the current Stage-2 recommendation; actual Deck prototypes and Signature facts inform compatibility only |+| Structure | Compatible Layout, otherwise Deck, otherwise free design |+| Application context | The current Stage-1 communication contract, informed by Deck's descriptive recurring-application context |++Current user instructions and final confirmation override every starting+owner. Brand identity remains authoritative over Style palette/type fallbacks.+Style alone, or Style with Brand, uses flat page authoring. Style with a Layout+or Deck follows the selected structural source. A Style never upgrades or+downgrades structure by itself.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.+contract against the Layout's page roles, slot types, and capacity. Before+combining Style with Layout/Deck, verify that its communication method and+composition expectations can be realized by the selected application and+structure. On mismatch, surface the conflicting segments; do not silently mix+fields or retain a promise that the selected structure cannot satisfy.### Whole-segment replacement (default granularity)@@ -364,7 +425,7 @@ Rules:- No implicit ordering — every cross-source segment difference is reported as a conflict- Only when the user picks `(c)` does AI walk through each segment- Field-level conflict resolution is out of scope — segment-level only-- `layout × 2`, `deck × 2`, `brand × 2` handled the same way+- `style × 2`, `layout × 2`, `deck × 2`, `brand × 2` handled the same way- Max two of any one kind (more than that — ask the user to converge in chat first)### Provenance@@ -375,6 +436,7 @@ When fusion happens (any multi-path case), the resulting `<project>/templates/de> **Fused from:**> - deck: `templates/decks/中国电信/` (base)> - brand: `templates/brands/anthropic/` (identity override)+> - style: `templates/styles/consulting_analytical/` (direction/method)> - layout: `templates/layouts/presentation_core/` (structure override)> - conflicts resolved: Color Scheme from anthropic (user picked a)```@@ -385,11 +447,12 @@ This lets both AI and humans trace which segment came from where.## 5. Relationship with Generate PPTX Step 3-**Trigger rule stays path-based** — an explicit workspace-root path is still required (see [Generate PPTX Step 3](../skills/ppt-master/workflows/generate-pptx.md#step-3-template-option)), and bare names never trigger. Step 3 first resolves `<workspace>/templates/design_spec.md`; for directory-shape compatibility, it also accepts a flat root containing `<workspace>/design_spec.md` when the SVGs already satisfy the current contract. Packages using legacy semantics such as `native_structure_mode: template`, missing Master identity, direct atomic placeholders, or distillation-era markers are rejected; `create-template` must produce a new workspace before generation continues. The only narrow handoff exception is a `create-template` run in the current conversation: after validation, it may pass its exact workspace root directly into Step 3. The `kind` field decides **how AI handles the path after triggering**:+**Trigger rule stays path-based** — an explicit workspace-root path is still required (see [Generate PPTX Step 3](../skills/ppt-master/workflows/generate-pptx.md#step-3-template-option)), and bare names never trigger. Step 3 first resolves `<workspace>/templates/design_spec.md`; for directory-shape compatibility, it also accepts a legacy-flat Brand/Layout/Deck root containing `<workspace>/design_spec.md` when the package satisfies its current kind contract. Layout/Deck additionally require current structured SVGs; Style has no flat form. Packages using legacy semantics such as `native_structure_mode: template`, missing Master identity, direct atomic placeholders, or distillation-era markers are rejected; `create-template` must produce a new workspace before generation continues. The only narrow handoff exception is a `create-template` run in the current conversation: after validation, it may pass its exact workspace root directly into Step 3. The `kind` field decides **how AI handles the path after triggering**:| User path's `kind` | Step 3 action (per-kind branch) ||---|---|| `kind: brand` | Map workspace `templates/` plus existing `images/` and `icons/` to the matching project peers; ignore `exports/` |+| `kind: style` | Install the spec-only direction/method workspace; require no SVG roster and keep generated pages flat || `kind: layout` | Map workspace `templates/` plus existing `images/` and `icons/` to the matching project peers; ignore `exports/` || `kind: deck` | Map workspace `templates/` plus existing `images/` and `icons/` to the matching project peers; ignore `exports/` || Multi-path | Fuse one `design_spec.md` per the table above, then merge the existing portable roots after resolving collisions |@@ -399,7 +462,7 @@ Bitmaps share the workspace `images/` pool and template SVGs reference them thro### Strategist confirmation stage behavior per kind-Installing a template does not narrow away the communication question. Stage 1 always confirms the same open communication contract independently of the template. Brand supplies identity constraints while structure stays free; Layout exposes structural capability; Deck also contributes descriptive application context. After Stage 1, Strategist inspects the actual prototypes and current content, then authors one page/prototype plan and records `mirror`, `layout`, or `style` only as internal exporter values. A mirror-authored workspace therefore enables literal reuse but never forces it. The Confirm UI exposes no template-mode fields. Planning semantics live in `references/strategist.md` and `references/strategist-template.md`; `templates/schemas/spec_lock.schema.json` owns the machine structure.+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; Style supplies method and visual-default seeds while remaining flat; Layout exposes structural capability; Deck also contributes descriptive application context. For Style-only use, Strategist does not look for prototypes and deterministically records `template_reuse_scope: style` with flat structure. For Layout/Deck, it inspects the actual prototypes and current content, then authors one page/prototype plan and records `mirror`, `layout`, or `style` only as internal exporter values. A mirror-authored workspace therefore enables literal reuse but never forces it. The Confirm UI exposes no template-mode fields. Planning semantics live in `references/strategist.md` and `references/strategist-template.md`; `templates/schemas/spec_lock.schema.json` owns the machine structure.---@@ -409,10 +472,11 @@ 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-style.md` | Direction/method-only Style workspace; no SVG roster, identity truth, application contract, native structure, or preview PPTX || `workflows/create-template/create-layout.md` | Brand-neutral structural Layout workspace with a structured SVG roster || `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.+In library scope, the frontmatter `kind` field determines which workspace parent is used under `templates/brands/` / `templates/styles/` / `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.---@@ -421,6 +485,7 @@ In library scope, the frontmatter `kind` field determines which workspace parent- **No field-level override syntax in the fusion layer** — field-level adjustment uses the existing Strategist confirmation stage path- **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 output-scope structure fork or CLI flag** — output scope is a `create-template` brief decision; both layout/deck scopes declare `native_structure_mode: structured`, while Brand/Style remain roster-free+- **No Theme kind** — Theme projects resolved identity from Brand, Deck, or the current project; Style fallback values are not identity truth+- **No automatic visual review from Style** — Review Focus supplements an already-enabled review pass and never triggers it- **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 9e6af270..895be7dc 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 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.+A PPT Master template is a reusable workspace with one of four explicit kinds: **Brand** owns identity, **Style** owns portable communication method and visual defaults, **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 and Style intentionally have no SVG roster. Each workspace's `design_spec.md` declares exactly what that kind contributes.This guide answers three questions:@@ -19,7 +19,7 @@ Choose the route by the artifact you already have and the result you want:| Starting point and goal | Route | Copy-ready request ||---|---|---|| A raw `.pptx`; keep its existing slide shells and replace content | **Fill Native PPTX** | `Fill projects/source/template.pptx with projects/source/content.md.` |-| A reusable Brand/Layout/Deck workspace; generate a fresh deck | **Generate PPTX with an explicit workspace path** | `Make a deck from sources/report.pdf with template skills/ppt-master/templates/layouts/presentation_core/.` |+| A reusable Brand/Style/Layout/Deck workspace; generate a fresh deck | **Generate PPTX with an explicit workspace path** | `Make a deck from sources/report.pdf with template skills/ppt-master/templates/layouts/presentation_core/.` || A PPTX, SVG set, brand guide, website, images, or mixed references; first build a reusable system | **Create Template → Generate PPTX** | `Use /create-template to create a reusable Deck workspace from projects/brand/our_deck.pptx.` |Do not pass a raw `.pptx` as a Generate PPTX template path. Fill it directly when you want its existing pages, or run Create Template first when you want a reusable system.@@ -29,6 +29,7 @@ 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. |+| **Style** | Communication method, open page-role vocabulary, evidence/data rules, visual defaults, image/icon direction, and advisory review focus | Flat Slide-local pages. Style values seed Stage 2 but do not become brand identity or reusable Layouts. || **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: descriptive application context, identity, page structure, and actual prototypes | A deck whose page/prototype application plan is derived by AI from the template and current content. |@@ -55,15 +56,15 @@ The workflow **defaults to free design** — it will not ask whether you want a### How to enter the template flow-Send the Brand/Layout/Deck workspace root in chat before Generate PPTX reaches Step 3. Anywhere in the sentence is fine; the path just has to be unambiguous:+Send the Brand/Style/Layout/Deck workspace root in chat before Generate PPTX reaches Step 3. Anywhere in the sentence is fine; the path just has to be unambiguous:> "use this template: `skills/ppt-master/templates/layouts/presentation_core/`" ✅> "use last deck's template: `projects/last_deck/`" ✅> "make a product introduction with `/Users/me/Desktop/our_brand_v3/`" ✅-For every current template kind, the path is the **template workspace root**. Step 3 resolves `templates/design_spec.md`, then installs `templates/` plus any existing `images/` and `icons/` into the target project or consumes them in place when the workspace is already that project. It never copies `exports/`. Deck/Layout workspaces additionally validate the structured SVG contract. The path may point to a built-in library workspace under `skills/ppt-master/templates/<kind>/<id>/`, a project workspace under `projects/<name>/`, or another workspace with the same routing. A create-template run may hand its exact validated workspace root directly to Step 3 in the same conversation; user-supplied paths and current-conversation Create Template handoffs are the two valid triggers.+For every current template kind, the path is the **template workspace root**. Step 3 resolves `templates/design_spec.md`; Brand/Layout/Deck install their package-owned `templates/` plus any real `images/` and `icons/`, while Style installs only its spec and ignores unrelated project scaffolding. It never copies `exports/`. Deck/Layout workspaces additionally validate the structured SVG contract; Brand/Style validate their roster-free specs. The path may point to a built-in library workspace under `skills/ppt-master/templates/<kind>/<id>/`, a project workspace under `projects/<name>/`, or another workspace with the same routing. A create-template run may hand its exact validated workspace root directly to Step 3 in the same conversation; user-supplied paths and current-conversation Create Template handoffs are the two valid triggers.-> **Compatibility preflight:** Step 3 also accepts a flat-directory workspace with `design_spec.md` and SVGs directly at the supplied root, but only when those SVGs already satisfy the current contract. Flat placement by itself is harmless. Former atomic-placeholder, unmapped Master/Layout, and other semantic-legacy packages are rejected; run `create-template` to create a new workspace, then generate new structured pages from that workspace. Nothing upgrades the old package in place.+> **Compatibility preflight:** Step 3 also accepts a legacy-flat Brand/Layout/Deck workspace with `design_spec.md` directly at the supplied root when it satisfies the current kind contract. Layout/Deck additionally require current structured SVGs; Style has no flat form. Former atomic-placeholder, unmapped Master/Layout, and other semantic-legacy packages are rejected; run `create-template` to create a new workspace, then generate new structured pages from that workspace. Nothing upgrades the old package in place.### What does NOT trigger the template flow@@ -101,13 +102,14 @@ Template workspace: projects/acme_template/The path labels are optional; the paths themselves are mandatory. If two paths have the same kind, the workflow stops at the existing conflict-resolution gate instead of choosing one silently.-You do not need to choose a template-use mode. By default, Strategist reads the actual Master/Layout/prototype roster and current content, then decides which pages to select, repeat, skip, reorder, or reorganize. If you care about a specific boundary, state it in ordinary language in the same request—for example, “keep the cover and closing page exactly, choose suitable middle pages yourself” or “use only the visual language”. That explicit sentence wins over AI judgment.+You do not need to choose a template-use mode. For Layout/Deck, Strategist reads the actual Master/Layout/prototype roster and current content, then decides which pages to select, repeat, skip, reorder, or reorganize. Brand instead supplies identity constraints, while Style supplies direction/method defaults; both leave pages freely composed unless another workspace supplies structure. If you care about a specific boundary, state it in ordinary language in the same request—for example, “keep the cover and closing page exactly, choose suitable middle pages yourself” or “use only the visual language”. That explicit sentence wins over AI judgment.### Template catalog-Templates are organized into three kinds, each with a discovery index:+Templates are organized into four 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+- [`styles_index.json`](../skills/ppt-master/templates/styles/styles_index.json) — direction/method workspaces: communication method, evidence/data expression, visual defaults, and advisory review focus, with no SVG page roster- [`layouts_index.json`](../skills/ppt-master/templates/layouts/layouts_index.json) — structure-only workspaces: canvas / page grammar / page types / SVG roster, with identity selected downstream- [`decks_index.json`](../skills/ppt-master/templates/decks/decks_index.json) — recurring presentation applications with integrated identity, structure, and factual prototype descriptions@@ -115,22 +117,22 @@ Ask "what templates are available?" for a readable list with workspace paths. Th### Free design vs template-Free design is **not** "no structure" or "no style" — the Strategist still plans the narrative, hierarchy, and visual system for that specific deck. Its generated pages use `pptx_structure.mode: flat`, so every visible object remains Slide-local. A Brand-only workspace also stays `flat` while supplying identity constraints. Layout and Deck workspaces expose a reusable Master / Layout / slot contract. Strategist inspects the real prototypes and current content, then automatically decides whether to use that structure or only its visual language.+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. Brand-only and Style-only workspaces also stay `flat`; Brand supplies identity constraints, while Style supplies reusable method and visual-default seeds. Layout and Deck workspaces expose a reusable Master / Layout / slot contract. Strategist inspects the real prototypes and current content, then automatically decides whether to use that structure or only its visual language.-> Rule of thumb: use a Brand workspace when identity must be fixed; use a Layout workspace when brand-neutral structure should be reused while purpose remains open; use a Deck when a branded structural system or recurring communication application should travel as one contract. Use free design when composition should grow from the current content.+> Rule of thumb: use a Brand workspace when identity must be fixed; use a Style workspace when a repeatable method and visual direction should travel without page prototypes; 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 only from the current content.-### Styles are not templates+### A style brief is not a Style workspace-A **style brief** is interpretive language ("minimalist" / "Keynote-style" / "editorial") that the Strategist turns into concrete design choices. A **template** is a real Brand / Layout / Deck workspace that the workflow consumes only when you provide its explicit directory path.+A **style brief** is interpretive language ("minimalist" / "Keynote-style" / "editorial") that the Strategist turns into concrete design choices for one deck. A **Style workspace** is a real `kind: style` template with pre-authored communication method and visual defaults, consumed only from an explicit directory path.-| | Template | Style |+| | Style workspace | Style brief ||---|---|---|| How invoked | Explicit directory path in your message | Free-form description in your message |-| What it supplies | The segments declared by its kind: identity, structure, or both | Intent that the Strategist interprets into mode, visual style, color, typography, icons, and imagery |-| Confirmation | Template-owned values become the starting contract; user-confirmed choices remain authoritative | No pre-authored values; the Strategist proposes concrete candidates and the user confirms them |-| Best for | Reusing an existing identity and/or page system | Expressing a desired feel without adopting a stored workspace |+| What it supplies | Reusable method, role/evidence discipline, and visual defaults; no identity truth or page prototypes | Intent that the Strategist interprets into mode, visual style, color, typography, icons, and imagery |+| Confirmation | Stored values seed Stage 2; Brand/Deck identity and user-confirmed choices remain authoritative | No pre-authored values; the Strategist proposes concrete candidates and the user confirms them |+| Best for | Repeating a design/argument approach across projects without freezing pages | Expressing a desired feel for the current project only |-A style description and a template name still go through different machinery: "minimalist" is interpretive language, while `presentation_core/` is a real template directory that requires an explicit path.+A style description and a Style workspace still go through different machinery: "minimalist" is interpretive language, while `templates/styles/<id>/` is a real template directory that requires an explicit path. `kind: style`, Stage-2 `visual_style`, and internal `template_reuse_scope: style` are separate axes.### How style briefs are interpreted@@ -157,7 +159,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 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.+The entry name always remains **Create Template**. It dispatches exactly one child workflow: Create Brand for identity only, Create Style for portable method/direction without prototypes, 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@@ -177,29 +179,34 @@ Before generation, the workflow writes one concise natural-language proposal and|-------|-------|| **Output scope** | `library` (default) or `project`; both use the same portable workspace routing, while only library scope registers it globally || **Target project** | Required only for `project`; give the exact initialized project path |-| **Selected child workflow** | Create Brand / Create Layout / Create Deck, fixed by the entry dispatch |+| **Selected child workflow** | Create Brand / Create Style / Create Layout / Create Deck, fixed by the entry dispatch || **Template ID** | Portable template identity; in library scope it is also the directory / index key. Prefer ASCII slug like `acme_consulting`; non-ASCII names work but must be filesystem-safe || **Display name** | Human-readable name for documentation |-| **Template context** | One proposed category, use case, display name, tone summary, and index keywords; you may correct the prose directly |-| **Canvas and visual direction** | Create Layout/Create Deck only: the proposed canvas, light/dark behavior, identity, and source-derived visual rules |-| **Creation plan** | What the AI will preserve, rebuild, simplify, or extract; how broad the prototype set will be; and how native structure will be handled—all described in ordinary language |-| **Source facts and assets** | Observable Master/Layout facts, supported native features, adopted assets, exclusions, and any material limitation |+| **Kind-specific context** | Brand: identity use cases and tone. Style: broad best fit plus discovery keywords. Layout: structure-compatible situations plus category/keywords. Deck: recurring application plus category/keywords. You may correct the prose directly |+| **Method and visual defaults** | Create Style only: communication method, open page-role vocabulary, evidence/data expression, visual defaults, image/icon direction, and advisory review focus; no audience/page/structure contract |+| **Identity** | Create Brand/Create Deck only: palette, typography, logo, voice, and icon identity |+| **Canvas and structure** | Create Layout/Create Deck only: canvas, page grammar, Master/Layout/slot plan, density behavior, and source-derived structural rules |+| **Source treatment** | Every child states what it extracts inside its owned segment. Only Layout/Deck describe prototype breadth, preservation/rebuild strategy, and native structure |+| **Source facts and assets** | Brand/Layout/Deck list adopted or excluded assets; Layout/Deck also report observable Master/Layout facts and supported native features. Style retains textual provenance only |After confirmation the workflow echoes the finalized brief and emits the marker `[TEMPLATE_BRIEF_CONFIRMED]`. Subsequent steps only run after that marker. **This is a hard gate — no brief, no generation.**Before either scope writes final files, one hard preflight resolves the required `templates/` destination and any optional asset destinations, requires an empty `templates/` root, and rejects bitmap or imported-vector filename collisions in `images/` and `icons/imported/`. It checks `exports/` only when a review PPTX was requested. Project scope additionally requires an initialized target project. Existing empty scaffolding created by project initialization is allowed and left untouched; Create Template does not create optional directories merely to keep empty paths. A failed check stops before partial output; the workflow does not merge or overwrite.-> Why so strict? A template is a structural contract, whether it is reused globally or only inside the current project. Confirming ownership and geometry first avoids partial or misplaced output.+> Why so strict? A template is a reusable ownership contract, whether it is global or project-scoped. Confirming the owned segment and destination first—and geometry only for Layout/Deck—avoids partial or misplaced output.### Step 3 — The AI derives the implementation-You do not select a creation mode. The AI translates the confirmed prose into one internal strategy so deterministic tools can run:+Create Style writes its confirmed direction/method spec directly and does not+enter an SVG creation mode. For Create Layout/Create Deck, you do not select a+creation mode. The AI translates the confirmed prose into one internal+strategy so deterministic tools can run:- a compact reusable system when the request calls for distillation;- broader source-aligned coverage when the source itself contains useful variants;- literal materialization when the request calls for preservation and the source has a complete supported structure contract.-The resulting frontmatter still records `replication_mode: standard|fidelity|mirror` for tool compatibility and audit. It is an implementation record, not a user-facing choice. A brand-neutral Layout cannot literally preserve brand/application facts; the AI either re-authors it as a Layout or keeps those facts in a Deck according to the requested result.+Layout/Deck frontmatter still records `replication_mode: standard|fidelity|mirror` for tool compatibility and audit. It is an implementation record, not a user-facing choice. Style frontmatter intentionally has no replication/native-structure fields. A brand-neutral Layout cannot literally preserve brand/application facts; the AI either re-authors it as a Layout or keeps those facts in a Deck according to the requested result.**About sprite sheets**: PPTX-exported assets are often a single large image referenced from multiple slides, each cropping a different region via nested `<svg viewBox=...>` wrappers. In `fidelity` and `mirror` modes this nesting must be preserved — you cannot flatten it to a bare `<image>`, or the crop is lost and the page misaligns. The workflow validates this automatically.@@ -225,11 +232,11 @@ the designer writes that brief against the published roster.### Step 4 — Validation, review export, registration, and discovery-After generation, both scopes run [`svg_quality_checker.py`](../skills/ppt-master/scripts/svg_quality_checker.py) as a hard gate: Brand validates its identity-only spec and asset references, while Layout/Deck validate the SVG roster and structured contract. If you want a PowerPoint review file, run the optional preview export; it creates `exports/<id>_template_preview.pptx` on demand. Authored templates use concise preview-only placeholder samples so long canonical markers stay readable without changing the source SVGs. The only scope-specific action is library registration:+After generation, both scopes run [`svg_quality_checker.py`](../skills/ppt-master/scripts/svg_quality_checker.py) as a hard gate: Brand validates its identity-only spec, Style validates its method/direction-only spec, and Layout/Deck validate the SVG roster and structured contract. Brand/Style never create a preview PPTX. Layout/Deck may create `exports/<id>_template_preview.pptx` on request, and must do so for multiple Masters. Authored templates use concise preview-only placeholder samples so long canonical markers stay readable without changing the source SVGs. The only scope-specific action is library registration:| Scope | Workspace root | Preview | Discovery behavior ||---|---|---|---|-| `library` (default) | `skills/ppt-master/templates/<kind>/<id>/` | Create Brand: N/A; Create Layout/Create Deck: optional for one Master, mandatory for multiple Masters | Register in the matching `brands_index.json`, `layouts_index.json`, or `decks_index.json` after validation |+| `library` (default) | `skills/ppt-master/templates/<kind>/<id>/` | Create Brand/Create Style: N/A; Create Layout/Create Deck: optional for one Master, mandatory for multiple Masters | Register in the matching `brands_index.json`, `styles_index.json`, `layouts_index.json`, or `decks_index.json` after validation || `project` | `projects/<name>/` | Same kind-specific review behavior | Skip global index registration |Library registration makes the template **discoverable** — when someone asks "what templates are available?", the AI lists it from the index. To use either scope, follow [Generate PPTX Step 3](../skills/ppt-master/workflows/generate-pptx.md#step-3-template-option): provide the workspace root before Step 3 runs, for example `use this template: skills/ppt-master/templates/layouts/<your_template_id>/` or `use this template: projects/<name>/`. A project workspace can also be migrated or reused elsewhere because its core shape is identical; register it only if it is placed in the library and should appear in discovery.@@ -248,7 +255,7 @@ For a generated deck that used a Layout or Deck workspace, verify the release ar| Click a reusable content region | Template slots behave as native placeholders with the declared type and frame. || Add a new slide from one of the emitted Layouts | Master/Layout visuals and placeholder geometry appear without copying a finished content slide. |-Brand-only use is intentionally different: it applies identity while keeping authored content Slide-local, so do not expect a reusable template Layout roster beyond the clean package scaffold.+Brand/Style use is intentionally different: both keep authored content Slide-local, so do not expect a reusable template Layout roster beyond the clean package scaffold. Brand supplies identity; Style supplies method/direction defaults.`exports/<id>_template_preview.pptx` is review evidence created by Create Template when requested or required. It is not the template input; generation always consumes the workspace root.@@ -258,6 +265,9 @@ Microsoft PowerPoint is the acceptance target for Master/Layout behavior. KeynotLibrary and project scopes use the same core structure; substitute either `skills/ppt-master/templates/<kind>/<id>/` or `projects/<name>/` for `<template_workspace>`:+Brand and Style stop at `templates/design_spec.md` (plus real Brand assets when+present); they do not create the SVG or `exports/` rows shown above.+```<template_workspace>/├── templates/@@ -290,7 +300,7 @@ nor allowed.- **Library scope (`library`, default)** writes the workspace under `skills/ppt-master/templates/<kind>/<id>/` and registers it globally.- **Project scope (`project`)** writes the same portable workspace at `projects/<name>/` and skips registration.-The result is not a private or reduced project-only format. You can point Step 3 at either workspace root, copy `templates/` plus any existing `images/` and `icons/` between roots, or migrate a project result into the library without restructuring it. If it moves into the library, run registration so discovery reflects its new location.+The result is not a private or reduced project-only format. You can point Step 3 at either workspace root. Brand/Layout/Deck migrate with `templates/` plus any real package-owned `images/` and `icons/`; Style migrates only `templates/design_spec.md`, and unrelated project scaffolding is ignored. If a workspace moves into the library, run its kind-specific registration so discovery reflects the new location.---@@ -298,8 +308,8 @@ The result is not a private or reduced project-only format. You can point Step 3Common misconceptions to avoid:-- **A reusable template is an explicit workspace, not a packaged source PPTX.** Brand workspaces may contain identity only; Layout and Deck workspaces add the structured SVG contract. Authored modes create that contract, while mirror maps validated source ownership facts into it. Export compiles only declared structure-- **A template is not one undifferentiated "style skin".** Brand, Layout, and Deck deliberately separate identity from structure so each segment can be reused or fused under an explicit ownership rule+- **A reusable template is an explicit workspace, not a packaged source PPTX.** Brand and Style workspaces are roster-free; Layout and Deck workspaces add the structured SVG contract. Authored modes create that contract, while mirror maps validated source ownership facts into it. Export compiles only declared structure+- **A template is not one undifferentiated "style skin".** Brand, Style, Layout, and Deck deliberately separate identity, direction/method, structure, and application so each segment can be reused or fused under an explicit ownership rule- **A template does not make content decisions for you.** The Strategist still decides per-page which layout to use and whether to extend a variant. Templates offer candidates, not predetermined results- **`fidelity` mode is not pixel-perfect copying.** Even with `literal` fidelity, the AI still strips noise and unnecessary repetition — geometry stays, redundancy goes- **`mirror` targets literal supported appearance and source topology, not byte-identical OOXML.** It inherits source import limitations and permits only mechanical normalization such as fixed-layer group expansion. Unsupported native objects keep their available SVG fallback or are reported; mirror never synthesizes replacement ownership.@@ -309,6 +319,6 @@ Common misconceptions to avoid:## Related docs- [`workflows/create-template.md`](../skills/ppt-master/workflows/create-template.md) — full workflow spec (AI-facing)-- [`templates/layouts/README.md`](../skills/ppt-master/templates/layouts/README.md) — current template catalog+- [`templates/README.md`](../skills/ppt-master/templates/README.md) — four template kinds and their discovery indexes- [`references/template-designer.md`](../skills/ppt-master/references/template-designer.md) — Template_Designer role definition and SVG technical constraints- [FAQ: how do I create a custom template?](./faq.md) — short FAQ versiondiff --git a/docs/why-ppt-master.md b/docs/why-ppt-master.mdindex 6a3d3526..0129baaa 100644--- a/docs/why-ppt-master.md+++ b/docs/why-ppt-master.md@@ -25,7 +25,7 @@ Editable is already table stakes — exporting each slide as an editable `.pptx`- **Native charts & tables, on demand** — data-backed chart and table objects with an Edit-Data workbook when you want them (trade-off note below)- **The full text, picture, fill, and effect model** — run/paragraph formatting, picture crop and shape-clip, gradients, patterns, outer shadow, glow- **Transitions, entrance / emphasis / path / exit animation, and speaker notes → voice narration** — real OOXML timing and package parts, not baked-in video-- **Template distillation on top** — hand it an existing deck and it extracts a reusable brand / layout / deck template; a layer of reuse built *above* the native primitives+- **Template distillation on top** — hand it reference material and it extracts a reusable brand / style / layout / deck template; a layer of reuse built *above* the native primitivesAnd this depth is a **direction of travel, not a fixed list.** The project's north star is to keep converging with PowerPoint itself — an ongoing effort to build and integrate more of its native capabilities, release after release, narrowing the gap between what an AI can generate for you and what you could build by hand in PowerPoint.diff --git a/docs/zh/README.md b/docs/zh/README.mdindex 3e95ff7f..0c2dbb07 100644--- a/docs/zh/README.md+++ b/docs/zh/README.md@@ -20,7 +20,7 @@|---|---|| [音频旁白](./audio-narration.md) | 从演讲者备注到逐页旁白:服务商、声音复刻、时序、PPTX 嵌入 || [转场与动画](./animations.md) | 页间转场与页内元素动画的默认行为和自定义方式 |-| [模板使用指南](./templates-guide.md) | 品牌 / 版式 / 成品模板的创建与套用 |+| [模板使用指南](./templates-guide.md) | 品牌 / 风格 / 版式 / 成品模板的创建与套用 |## 架构与原理@@ -28,7 +28,7 @@|---|---|| [技术路线](./technical-design.md) | 架构、设计哲学、为什么选 SVG → DrawingML || [PowerPoint–SVG 能力映射](./powerpoint-svg-mapping.md) | PowerPoint 构造与管线之间逐项能力映射 |-| [模板体系架构](./templates-architecture.md) | 品牌 / 版式 / 成品模板体系的设计 |+| [模板体系架构](./templates-architecture.md) | 品牌 / 风格 / 版式 / 成品模板体系的设计 |## 项目方向diff --git a/docs/zh/faq.md b/docs/zh/faq.mdindex c5fe3dd8..1cb21787 100644--- a/docs/zh/faq.md+++ b/docs/zh/faq.md@@ -287,7 +287,7 @@ beautify 和主管线的一句话判别:**原来的分页是要保留的信息**第三步 — 等待完成**-AI 代理会自动完成后续工作——分析参考、构建布局定义并验证模板。如果你明确需要 PowerPoint 审阅文件,它还会按需生成 `exports/<id>_template_preview.pptx`。两种范围都要求 `templates/`,并使用可选的 `images/`、`icons/` 与 `exports/`:`library` 写入 `skills/ppt-master/templates/<kind>/<id>/` 并完成全局注册;`project` 写入 `projects/<name>/` 并跳过注册;空的可选目录直接省略。把这个工作区根目录交给 Step 3 即可,Step 3 不会复制 `exports/`,全局库的预览导出也由 Git 忽略。根目录平铺 `design_spec.md` 的工作区只有在 SVG 已满足当前合同时才兼容;语义旧包必须通过 `create-template` 替换,不能原地升级。+AI 代理会自动完成后续工作——分析参考、写入 kind 专属规范,仅为 Layout/Deck 构建结构定义,并验证工作区。Brand/Style 不生成预览 PPTX;Layout/Deck 可按请求生成 `exports/<id>_template_preview.pptx`,多 Master 时必须生成。两种范围都要求 `templates/`;Brand/Layout/Deck 可使用包自有 `images/` 和 `icons/`,Style 则只包含 `templates/design_spec.md`。`library` 写入 `skills/ppt-master/templates/<kind>/<id>/` 并完成全局注册;`project` 写入 `projects/<name>/` 并跳过注册;空的可选目录直接省略。把这个工作区根目录交给 Step 3 即可,Step 3 不会复制 `exports/`,全局库的预览导出也由 Git 忽略。兼容的旧平铺 Brand/Layout/Deck 工作区只有在满足当前 kind 合同时才可读取,Layout/Deck 还必须满足当前 structured SVG 合同;Style 不存在旧平铺形态,语义旧包必须通过 `create-template` 替换,不能原地升级。> **提示**:对风格和使用场景描述得越具体,生成的模板就越符合你的预期。diff --git a/docs/zh/getting-started.md b/docs/zh/getting-started.mdindex 32174964..c4f60688 100644--- a/docs/zh/getting-started.md+++ b/docs/zh/getting-started.md@@ -18,14 +18,14 @@## 用模板-**可选。** 默认走**自由设计**——不需要模板,可以直接跳到下一节。只有当 deck 必须复用一套固定版式或品牌时,才需要模板。+**可选。** 默认走**自由设计**——不需要模板,可以直接跳到下一节。只有当 deck 必须复用品牌身份、沟通与设计方法、固定版式或重复使用的 Deck 应用时,才需要模板。**复用现成 `.pptx` 有两条路,取决于你想要什么结果:**| 你想要… | 路径 | 会发生什么 ||---|---|---|| **用这份 deck 的原生页面壳承载新内容** | Fill Native PPTX | 克隆选中的源页面,并在 OOXML 中直接改写文字 / 表格 / 图表数据。来源设计保持原生;输出是受现有页面壳约束的新回填 deck。 |-| **先建立可复用设计系统,再生成新 deck** | Create Template → Generate PPTX | 从参考材料创建经过验证的 Brand、Layout 或 Deck 工作区,再创作一份新 deck。新故事、结构与页数都可以不同于来源。 |+| **先建立可复用设计系统,再生成新 deck** | Create Template → Generate PPTX | 从参考材料创建经过验证的 Brand、Style、Layout 或 Deck 工作区,再创作一份新 deck。新故事、结构与页数都可以不同于来源。 |前者:把 `.pptx` 连同素材(或一个主题)给 AI,说「套模板」——见 [套模板工作流](../../skills/ppt-master/workflows/template-fill-pptx.md)。本节其余部分讲 create-template。@@ -35,7 +35,7 @@你:用 /create-template 从 projects/brand/our_deck.pptx 创建一个可复用 Deck 模板```-Create Template 会分析参考材料,确认结果属于 Brand、Layout 还是 Deck,再创作或物化一个经过验证的新工作区。导入器只提供来源证据;最终工作区拥有 `templates/design_spec.md`、所需 SVG 原型与配套素材。如果需要 PowerPoint 评审文件,再显式运行可选预览导出;它会按需创建 `exports/<id>_template_preview.pptx`。生成时引用的是工作区根目录。+Create Template 会分析参考材料,确认结果属于 Brand、Style、Layout 还是 Deck,再创作或物化一个经过验证的新工作区。导入器只提供来源证据;最终工作区拥有 `templates/design_spec.md`,以及该 kind 真正需要的原型和素材。Brand 与 Style 不含 roster;Layout 与 Deck 拥有 structured SVG 原型。如果需要 Layout 或 Deck 的 PowerPoint 评审文件,再显式运行可选预览导出;它会按需创建 `exports/<id>_template_preview.pptx`。生成时引用的是工作区根目录。在 create-template 简报中选择 `library`(沿用原默认)或 `project`。两种范围都要求 `templates/`,并使用可选的 `images/`、`icons/` 和按需生成的 `exports/`;空的可选目录直接省略。项目范围要求给出已初始化的目标项目;只有全局库范围会执行注册。@@ -46,7 +46,7 @@ Create Template 会分析参考材料,确认结果属于 Brand、Layout 还是| **注册进 skill 库** | `skills/ppt-master/templates/<kind>/<id>/` | 可移植工作区并执行全局注册;问“有哪些模板”时会被列出来 || **放在 projects 下** | `projects/<name>/` | 相同的可移植工作区,不执行全局注册 |-两种结果都通过对话里给出**工作区根目录路径**来引用。Step 3 会解析 `templates/design_spec.md`;为兼容目录形态,也接受 `design_spec.md` 直接位于所给根目录、且 SVG 已满足当前合同的平铺工作区。create-template 可在同一对话里把已验证的精确工作区根目录直接交给 Step 3。两种情况都以路径为准,绝不认裸模板名。完整工作区可以在全局库与 `projects/` 之间复制或迁移,无需调整目录结构;只有全局库注册不同。+两种结果都通过对话里给出**工作区根目录路径**来引用。Step 3 会解析 `templates/design_spec.md`;为兼容目录形态,也接受满足当前 kind 合同的旧式平铺 Brand/Layout/Deck 根目录,Layout/Deck 还必须带有当前 structured SVG;Style 没有平铺形态。create-template 可在同一对话里把已验证的精确工作区根目录直接交给 Step 3。两种情况都以路径为准,绝不认裸模板名。完整工作区可以在全局库与 `projects/` 之间复制或迁移,无需调整目录结构;只有全局库注册不同。```你:用 sources/report.pdf 做 deck,模板用 skills/ppt-master/templates/layouts/presentation_core/diff --git a/docs/zh/project-positioning.md b/docs/zh/project-positioning.mdindex 8bfe9427..abb91bc3 100644--- a/docs/zh/project-positioning.md+++ b/docs/zh/project-positioning.md@@ -14,7 +14,7 @@> **PPT Master 是一套开源、对话驱动的工作流,让 AI 先把论证推理成形,再设计并产出真正可编辑的 PowerPoint——不是整页图片,也不是一层能改的表皮。它的核心轴线是原生深度:随着版本迭代,持续创作或保留更多 PowerPoint 自身的对象模型、演示行为和可复用结构。**-输入可以是一个主题、源材料、数据、设计参考、品牌资产或已有 `.pptx`。主管线负责生成新 deck;其他明确路线和 profile 可以提炼可复用的 Brand / Layout / Deck 工作区,向现有 PowerPoint 填入新内容、重新设计它,或在保留各自契约所承诺内容的前提下追加原生演示行为。+输入可以是一个主题、源材料、数据、设计参考、品牌资产或已有 `.pptx`。主管线负责生成新 deck;其他明确路线和 profile 可以提炼可复用的 Brand / Style / Layout / Deck 工作区,向现有 PowerPoint 填入新内容、重新设计它,或在保留各自契约所承诺内容的前提下追加原生演示行为。原生深度是一条持续推进的方向,不是一张固定功能清单。PPT Master 的北极星是不断向 PowerPoint 自身靠拢,缩小 AI 能生成的内容与熟练用户可以在 PowerPoint 中手工完成的内容之间的差距。[PowerPoint ↔ SVG 能力映射](../powerpoint-svg-mapping.md)逐项、诚实地记录当前边界。@@ -72,7 +72,7 @@ PPT Master 的能力范围比单一生成管线更宽,但有意窄于通用办|---|---|| 演示推理 | 把主题或材料包转化为面向受众的核心信息、叙事模式、提纲、页面规划和明确设计方向 || 原生演示创作 | 创作新的页面视觉,并编译为真正原生可编辑的 PowerPoint deck |-| 可复用演示设计 | 提炼、创建、组合、校验并应用 Brand、Layout 和 Deck 工作区 |+| 可复用演示设计 | 提炼、创建、组合、校验并应用 Brand、Style、Layout 和 Deck 工作区 || 已有 deck 改编 | 在不同保留契约下重做已有 deck、向原生页面壳填入新内容,或追加原生演示行为 || PowerPoint 表达 | 在沟通目标需要时使用图片、图示、图表、表格、公式、讲稿、旁白、转场和动画 || 审阅与交付 | 预览、检查、校验、修复、导出、回读,并保留足够的本地项目状态供后续精修或重新导出 |@@ -160,7 +160,7 @@ PPT Master 不以成为以下产品为目标:1. 原生深度、输出正确性和交付可靠性。2. 内容推理、叙事质量和视觉一致性。-3. 品牌、版式、Deck 和已有 PowerPoint 资产的复用。+3. 品牌、风格、版式、Deck 和已有 PowerPoint 资产的复用。4. 人工审阅、修正和可控迭代。5. 能够强化前四项的额外格式、provider 和便利能力。diff --git a/docs/zh/roadmap.md b/docs/zh/roadmap.mdindex a850e50c..39caaf72 100644--- a/docs/zh/roadmap.md+++ b/docs/zh/roadmap.md@@ -12,7 +12,7 @@项目的主轴是**原生深度**:逐版本创作或保留更多 PowerPoint 自身的对象模型、行为与可复用结构——持续向 PowerPoint 本身靠拢。完整论述见[项目定位章程](./project-positioning.md);[PowerPoint ↔ SVG 映射指南](./powerpoint-svg-mapping.md)逐特性诚实记录当前边界。-这条主轴今天体现为四条显式产物路线:**Generate PPTX** 通过受约束的 SVG → DrawingML 创作全新设计的页面;**Create Template** 产出可复用的 Brand / Layout / Deck 模板工作区;**Fill Native PPTX** 与 **Enhance Native PPTX** 通过限定范围的 OOXML 操作保留既有文件包。+这条主轴今天体现为四条显式产物路线:**Generate PPTX** 通过受约束的 SVG → DrawingML 创作全新设计的页面;**Create Template** 产出可复用的 Brand / Style / Layout / Deck 模板工作区;**Fill Native PPTX** 与 **Enhance Native PPTX** 通过限定范围的 OOXML 操作保留既有文件包。---diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.mdindex 04118eba..33c8a67a 100644--- a/docs/zh/technical-design.md+++ b/docs/zh/technical-design.md@@ -52,8 +52,8 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使├── 若缺少同 stem 的规范 Markdown,再对该归档 PPTX 运行 ppt_to_md.py└── sources/ 内容型文件成为内容契约↓-[模板 / 品牌 / 布局(可选)] — 默认跳过,直接自由设计- 仅在用户明确提供符合当前合同的 Brand/Layout/Deck 工作区根路径时触发:可以是全局模板库条目根,也可以是项目工作区根+[模板 / 品牌 / Style / 布局(可选)] — 默认跳过,直接自由设计+ 仅在用户明确提供符合当前合同的 Brand/Style/Layout/Deck 工作区根路径时触发:可以是全局模板库条目根,也可以是项目工作区根原生 PPTX 模板请求进入 template-fill;可复用 SVG 模板需先通过 create-template 创建↓[Strategist] 策略师 - 三阶段策略师确认与设计规范 → design_spec.md + spec_lock.md@@ -156,8 +156,8 @@ narration 标记。| 原生 PPTX 模板 + 新材料 / 新主题 | Fill Native PPTX(`template-fill-pptx`) | 克隆并填充原生页面;不生成 SVG || 现有 PPTX,页数 / 页序 / 措辞 1:1 保留,只改善排版 | Generate PPTX + `beautify-pptx` profile | 通过 SVG 重新生成;内容和分页锁定 || 已完成 PPTX,保持内容 / 布局稳定,只加讲稿、音频、计时、转场 | Enhance Native PPTX(`native-enhance-pptx`) | 直接 OOXML patch;不重新设计 |-| 用户想从一个或多个 PPTX/SVG、图片/PDF、文档/网站、品牌资产、直接文字或混合参考材料包构建可复用模板工作区 | Create Template(`create-template`) | 固定入口读取每个适用证据通道,只分派一个 Create Brand、Create Layout 或 Create Deck 子工作流,再返回供 Generate Step 3 使用的工作区根目录;结构型子工作流可导出审阅 PPTX |-| 用户提供符合当前合同的明确模板路径 | Generate PPTX Step 3 | Brand/Layout/Deck 工作区解析 `templates/design_spec.md`;平铺根目录可解析直接 `design_spec.md`;语义旧包会被拒绝,并通过 Create Template 替换 |+| 用户想从一个或多个 PPTX/SVG、图片/PDF、文档/网站、品牌资产、直接文字或混合参考材料包构建可复用模板工作区 | Create Template(`create-template`) | 固定入口读取每个适用证据通道,只分派一个 Create Brand、Create Style、Create Layout 或 Create Deck 子工作流,再返回供 Generate Step 3 使用的工作区根目录;结构型子工作流可导出审阅 PPTX |+| 用户提供符合当前合同的明确模板路径 | Generate PPTX Step 3 | 当前 Brand/Style/Layout/Deck 工作区解析 `templates/design_spec.md`;只有兼容的旧平铺 Brand/Layout/Deck 根目录可解析直接 `design_spec.md`;语义旧包会被拒绝,并通过 Create Template 替换 || 用户要求调整对象级动画顺序 / 效果 / 计时 | Generate PPTX + `customize-animations` 阶段 | 通过 `animations.json` 控制可选导出策略 || 用户要求预览、选择、注解或重导出浏览器编辑 | Generate PPTX + `live-preview` 阶段 | 注解只在规定交接点应用 |@@ -350,9 +350,9 @@ PPT Master 不只服务 PPT——同一套 SVG → DrawingML 流水线还能产**为什么默认自由设计。** 模板是地板,但很容易变成天花板:它会把整个 deck 锁进模板自有的视觉惯用语,无视内容本身想要怎样被呈现。自由设计的布局从源内容的结构推导而来,而不是从一套固定语法套上去——视觉节奏跟着内容走,而不是跟内容打架。约束模式在窄场景里确实更好(品牌锁定的 deck、强类型场景如学术答辩或政府报告),所以它一直在;但 AI 不主动去抓,是用户去抓。-**机械触发,不做语义匹配。** 像 `presentation_core` 这样的裸名字、品牌提及,或“麦肯锡风格”这类风格短语,即使库里存在相似目录,也不会触发 Step 3。Step 3 只消费显式路径。当前 Brand/Layout/Deck 工作区均解析 `templates/design_spec.md`;平铺目录只有在 SVG 已满足当前合同时,才兼容从根目录读取 `design_spec.md`。目录形态从不授权结构迁移;带旧 Master/Layout/placeholder 语义的包必须先替换为新建的模板工作区,才能进入 Step 3。发现性交给模板索引和显式问答(“有哪些模板可以用?”),不交给运行时 fuzzy matching。+**机械触发,不做语义匹配。** 像 `presentation_core` 这样的裸名字、品牌提及,或“麦肯锡风格”这类风格短语,即使库里存在相似目录,也不会触发 Step 3。Step 3 只消费显式路径。当前 Brand/Style/Layout/Deck 工作区均解析 `templates/design_spec.md`;自由文字风格说明仍只是 Stage 2 输入,只有显式 `kind: style` 工作区路径才启用可复用 Style 合同。旧平铺 Brand/Layout/Deck 目录只有在满足当前 kind 合同时,才兼容从根目录读取 `design_spec.md`;Layout/Deck 还必须满足当前 structured SVG 合同。Style 不存在旧平铺形态。目录形态从不授权结构迁移;带旧 Master/Layout/placeholder 语义的包必须先替换为新建的模板工作区,才能进入 Step 3。发现性交给模板索引和显式问答(“有哪些模板可以用?”),不交给运行时 fuzzy matching。-当前 Brand/Layout/Deck 都采用同一工作区路由合同;Brand 不含 SVG roster,空的可选目录直接省略:+当前 Brand/Style/Layout/Deck 都采用同一工作区路由合同;Brand 与 Style 不含 SVG roster,空的可选目录直接省略:```text<template_workspace>/@@ -363,25 +363,29 @@ PPT Master 不只服务 PPT——同一套 SVG → DrawingML 流水线还能产└── exports/ # 可选、按需生成的审阅文件;全局库下由 Git 忽略```+Style 将这一路由形态收窄为仅 `templates/design_spec.md`,不携带素材或+审阅 payload;项目中既有的脚手架也不属于 Style 输入。+`<template_workspace>` 可以是 `skills/ppt-master/templates/<kind>/<id>/`,也可以是 `projects/<name>/`。Step 3 接收这个根目录。工作区可在两个位置之间迁移而不改形;唯一的范围差异是全局索引注册。空的可选目录不创建,`exports/` 也不会复制进新项目。-对 Create Layout / Create Deck,`standard` 与 `fidelity` 会重新创作 SVG 和新的 Master/Layout/slot 系统;来源拓扑只作为视觉证据,不保留、也不蒸馏。`mirror` 把来源包内实际存在且已验证的页序、Master/Layout 身份与父子关系、placeholder 事实和受支持视觉物化到新工作区,不做语义归纳或缺口补造。只有被保留的来源本身已经品牌中立且应用中立时,Layout mirror 才合法;否则应重新创作 Layout,或把这些事实保留为 Deck。由于结构层不能是 `<g>`,固定结构层的来源 group wrapper 只允许机械展开成直接原子,同时保持归属、paint order 和视觉一致。Create Brand 只分析并物化身份片段,不进入这些结构复制策略,也不生成 SVG roster。+对 Create Layout / Create Deck,`standard` 与 `fidelity` 会重新创作 SVG 和新的 Master/Layout/slot 系统;来源拓扑只作为视觉证据,不保留、也不蒸馏。`mirror` 把来源包内实际存在且已验证的页序、Master/Layout 身份与父子关系、placeholder 事实和受支持视觉物化到新工作区,不做语义归纳或缺口补造。只有被保留的来源本身已经品牌中立且应用中立时,Layout mirror 才合法;否则应重新创作 Layout,或把这些事实保留为 Deck。由于结构层不能是 `<g>`,固定结构层的来源 group wrapper 只允许机械展开成直接原子,同时保持归属、paint order 和视觉一致。Create Brand 只提取身份片段,Create Style 只提取可移植方法/方向;两者都不进入结构复制策略,也不生成 SVG roster。-三类模板拥有不同的设计契约片段:+四类模板拥有不同的设计契约片段:| Kind | 拥有的片段 | 典型内容 | 对 Strategist 的影响 ||---|---|---|---|| `brand` | 身份片段 | 配色、字体、logo、语气、图标风格 | 锁定身份;结构保持自由 |+| `style` | 方向/方法片段 | 沟通方法、开放页面角色、证据/数据规则、视觉默认值、图片/图标方向、审阅关注点 | 作为 Stage 2 起点;Style-only 保持 flat,与 Layout/Deck 合成时沿用所选结构;不升级为身份真值,也不触发 visual review || `layout` | 品牌中立的结构片段 | 画布、页面结构、语义文字角色/空间行为、页面类型、SVG roster | 提供结构能力;身份与沟通应用仍由下游决定 || `deck` | 应用段 + 一体化身份/结构 | 重复场景、受众与结果、代表性页面角色、身份和真实 SVG roster | 提供描述性语境和原型;Strategist 将其与独立确认的 Stage-1 契约及当前内容对照,再推导应用计划 |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 能明确说明每个片段来自哪里,便于审计和复现。+当用户提供多个路径时,融合是**片段级**而不是字段级:Brand 拥有身份,Style 拥有方向/方法默认值,Layout 拥有兼容结构,Deck 在当前 Stage 1 沟通契约下提供描述性的重复应用语境及兜底身份/结构;用户最终确认最高。Style 的色彩/字体 fallback 不覆盖 Brand/Deck 身份,其方法与构图预期必须兼容所选 Deck 应用和 Layout/Deck 结构,否则显式提出冲突。项目内 Brand + Layout 组合的应用语境来自 Stage 1,不会自动升级成可注册的 Deck。同类冲突也会显式列出,而不是按输入顺序默默决定。这样融合后的 spec 能明确说明每个片段来自哪里,便于审计和复现。**原生 PPTX 不能直接作为 Step 3 工作区。** 普通 Generate 可以把 PPTX 作为源材料使用,`beautify-pptx` 也可以在页数、页序和逐页措辞 1:1 的边界下重新设计;这两种情况都不会把原始 PPTX 当作 Step 3 模板。把原生 PPTX 作为模板或页面壳、再用新材料填充时,默认进入 Fill Native PPTX;若请求允许拆分、合并、删页、重排或叙事重构,则仍属于 Generate。只有当目标是创建可复用模板工作区、并在 SVG 路线的 Step 3 中重复使用其设计系统时,才先运行 Create Template,再传入生成的工作区根目录。-**布局是 opt-in,图表和图标不是。** 这种不对称不是矛盾——*布局*正是锁定视觉惯用语的那一层(地板/天花板问题),而图表和图标是不会施加 deck 级风格约束的复用原语。同一个 `templates/` 目录,但在视觉契约里扮演的角色不同。+**模板合同是 opt-in,图表和图标不是。** 这种不对称是有意的:Layout 锁定可复用结构,Style 锁定方向/方法默认值,Brand 锁定身份,Deck 则把重复应用与身份、结构组合起来;图表和图标只是不会单独施加 deck 级合同的复用原语。同一个 `templates/` 目录,但 ownership 不同。---@@ -724,7 +728,7 @@ ChartEx 导入被有意限制为 7 个已验证数据模型:`treemap`、`sunbu| 分类 | 文档 | 归属路线 ||---|---|---|| 生成 profile | `beautify-pptx`、`quick-generate` | Generate PPTX;分别负责逐字措辞 / 页数 / 页序不变量与显式 SVG→PPTX 直接短路 |-| 模板子工作流 | `create-brand`、`create-layout`、`create-deck` | Create Template 在“仅身份 / 品牌中立且应用中立的结构 / 应用契约与身份结构一体化”中只分派一个 |+| 模板子工作流 | `create-brand`、`create-style`、`create-layout`、`create-deck` | Create Template 在“仅身份 / 无 roster 的方向与方法 / 品牌中立且应用中立的结构 / 应用语境与身份结构一体化”中只分派一个 || 模板输入阶段 | `apply-template-workspace` | Generate PPTX Step 3;只在显式工作区根目录触发时加载 || 生成阶段 | `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 的旁白集成 |diff --git a/docs/zh/templates-architecture.md b/docs/zh/templates-architecture.mdindex fefe8097..5c56fc34 100644--- a/docs/zh/templates-architecture.md+++ b/docs/zh/templates-architecture.md@@ -1,28 +1,29 @@-# 模板架构:Brand / Layout / Deck 三分类+# 模板架构:Brand / Style / Layout / Deck 四分类[English](../templates-architecture.md) | [Chinese](./templates-architecture.md)----> 本文是**架构对齐文档**,定义"模板"在数据模型层面的三种身份、各自的 `design_spec.md` 字段集、以及多路径合成与冲突解决规则。面向贡献者与 AI 工作流,回答"一个模板目录里应该写什么、不写什么;多个模板同时给时怎么合成"。+> 本文是**架构对齐文档**,定义“模板”在数据模型层面的四种身份、各自的 `design_spec.md` 字段集、以及多路径合成与冲突解决规则。面向贡献者与 AI 工作流,回答“一个模板目录里应该写什么、不写什么;多个模板同时给时怎么合成”。>> 用户视角的用法(怎么触发、怎么选)见 [`templates-guide.md`](./templates-guide.md);本文不重复。----## 一、三分类+## 一、四分类| 分类 | 全局库工作区根目录 | 写什么 | 不写什么 | 出处工作流 ||---|---|---|---|---|| **Brand** | `templates/brands/<id>/` | 仅身份段:color / typography / logo / voice / icon style | 不写 canvas、page structure、SVG roster | `workflows/create-template/create-brand.md` |+| **Style** | `templates/styles/<id>/` | 可移植方向/方法段:沟通方法、页面角色词汇、证据/数据表达、视觉默认值、图片/图标方向、审阅关注点 | 不写身份真值、应用契约、canvas、页面结构或 SVG roster | `workflows/create-template/create-style.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` 只补充它们无法表达的页面框架行为。Create Template 根据自然语言意图与来源证据在内部推导 `standard` / `fidelity` / `mirror`;Strategist 再根据真实原型与当前内容推导 strict/adaptive 导出行为。这些实现值都不是用户必选项。根目录平铺 `design_spec.md` 的目录只有在 SVG 已满足当前合同时才兼容;带旧结构语义的包必须替换为新建模板工作区,不能原地升级。+每张新建的 Layout/Deck SVG 都是完整预览,并在根节点声明 Master/Layout key 与选择器名称;固定 Master/Layout 视觉是直接原子元素;语义槽位是顶层 group。普通槽位必须有正数设计区域 bounds 和恰好一个兼容 carrier;复合 `object` 区域走显式 proxy 绑定,零槽 Layout 也合法。这些专用标记具有最高优先级;最小 `data-pptx-role` 只补充它们无法表达的页面框架行为。Create Template 根据自然语言意图与来源证据在内部推导 `standard` / `fidelity` / `mirror`;Strategist 再根据真实原型与当前内容推导 strict/adaptive 导出行为。这些实现值都不是用户必选项。仅 Brand/Layout/Deck 的旧式平铺目录可在满足当前 kind 合同时继续读取;Style 没有平铺兼容形态。带旧结构语义的包必须替换为新建模板工作区,不能原地升级。-三者是**三种并列的可复用规则包**,不是 PowerPoint 包对象类型。在全局库范围内,物理目录与 frontmatter `kind` 字段双向对齐:+四者是**四种并列的可复用规则包**,不是 PowerPoint 包对象类型。在全局库范围内,物理目录与 frontmatter `kind` 字段双向对齐:-多路径合成后的项目级 `design_spec.md` 沿用现有路由 `kind`:同时具备身份段和结构段时为 `deck`,只有结构段时为 `layout`,只有身份段时为 `brand`。对于项目内临时组合的 Brand + Layout,这个标签只表示“已安装两种能力”,不会把组合自动提升为可注册的 Deck,也不会凭空生成应用语境;当前项目的 Stage 1 沟通契约负责提供场景。Strategist 在内部生成模板应用计划,确认页不显示模板模式控件。+多路径合成后的项目级 `design_spec.md` 沿用能力标签:同时具备身份段和结构段时为 `deck`,只有结构段时为 `layout`,只有身份段时为 `brand`,只有方向/方法段时才为 `style`。Style 与其他 kind 合成时不改变原有能力标签。对于项目内临时组合的 Brand + Layout,`kind: deck` 只表示“已安装两种能力”,不会把组合自动提升为可注册的 Deck,也不会凭空生成应用语境;当前项目的 Stage 1 沟通契约负责提供场景。Strategist 在内部生成模板应用计划,确认页不显示模板模式控件。```yaml# templates/brands/anthropic/templates/design_spec.md@@ -31,6 +32,12 @@ kind: brand...---+# templates/styles/consulting_analytical/templates/design_spec.md+---+kind: style+...+---+# templates/layouts/presentation_core/templates/design_spec.md---kind: layout@@ -53,14 +60,15 @@ native_structure_mode: structured| 项目合同 | 原生投影 ||---|---|| **Brand** | Theme 的颜色、字体与效果,以及 Logo 等固定身份资产规则 |+| **Style** | 不提供可复用包结构;已确认的方法和视觉默认值指导 flat Slide-local 创作 || **Layout** | Master/Layout/Placeholder 拓扑、可复用几何、语义文字角色与槽位空间行为 || **Deck** | Brand 与 Layout 的投影,再加描述性重复应用语境和真实原型 |-一个 Slide Master 可以同时包含结构几何和品牌视觉。来源规则仍分开归属:Layout 决定拓扑、位置、语义文字角色与空间行为,Brand 决定身份值与资产。下游选择 `layout` 时,导出结合已确认的阅读模式和字号体系解析最终 placeholder 格式;选择 `mirror` 时则保留来源的字面格式与文字拓扑。最后再把适用规则编译进同一套 Master/Layout 图谱。因此 Theme 是已解析身份的实现投影——身份可以来自 Brand、Deck 或当前项目——而不是第四种模板 kind。+一个 Slide Master 可以同时包含结构几何和品牌视觉。来源规则仍分开归属:Layout 决定拓扑、位置、语义文字角色与空间行为,Brand 决定身份值与资产。下游选择 `layout` 时,导出结合已确认的阅读模式和字号体系解析最终 placeholder 格式;选择 `mirror` 时则保留来源的字面格式与文字拓扑。最后再把适用规则编译进同一套 Master/Layout 图谱。因此 Theme 是已解析身份的实现投影——身份可以来自 Brand、Deck 或当前项目——而不是另一种模板 kind;Style 的色彩/字体 fallback 也不是 Theme 身份真值。### 输出范围与 kind 相互独立-`create-template` 会确认 Layout/Deck 工作区放在哪里。这个执行选择不会增加第四种 kind,也不会增加新的 PPTX 结构模式:+`create-template` 会确认工作区放在哪里。这个执行选择不会增加另一种 kind,也不会增加新的 PPTX 结构模式:| 范围 | 工作区根目录 | 核心结构 | 发现行为 ||---|---|---|---|@@ -87,17 +95,18 @@ native_structure_mode: structured原生形状 metadata 采用两级模型。完整导入 SVG 保存 native metadata、隐藏 carrier 和预览证据,并作为不可变原生载荷后备;`svg_authoring_view.py` 生成可编辑 authoring IR,其中轻量 SVG 使用文档内 source ref 标识对象,manifest 只保存路径和初始 hash。创作模式使用项目规范化 SVG,只有精确匹配已登记 preset 时才使用 compact authored-preset 组。Mirror 从 IR 物化模板,仅为未改且 hash 匹配的 Slide-local/slot ref 重新接入转换器已支持的载荷;固定结构层保持直接原子,不支持或已修改的对象保留 SVG fallback,最终模板不包含 IR 专用 ref。导出只编译声明的结构,不推断归属。-两种范围都在可移植 frontmatter 中保留 `kind: layout` 或 `kind: deck`。`output_scope` 与 `target_project` 只属于工作流简报,不写入 `design_spec.md`。+两种范围都在可移植 frontmatter 中保留所选 `kind`。`output_scope` 与 `target_project` 只属于工作流简报,不写入 `design_spec.md`。任何范围第一次写最终文件前,都必须解析工作区根目录、确认 `templates/` 为空,并检查全部计划写入的图片与图标文件名无冲突;用户要求预览或已确认 roster 含多个 Master 时检查预览 PPTX 目标。项目范围还必须确认目标项目已初始化。任一失败都在写入前停止,不合并、不覆盖。-### 三段的字段切分+### 四段的字段切分为了让多路径合成能干净覆盖,所有字段按段归属,**段级整段替换是默认粒度**:| 段 | 包含的章节 | 归属(覆盖优先级)||---|---|---|| **身份段** | Color Scheme / Typography / Logo / Voice & Tone / Icon Style | brand 覆盖 |+| **方向/方法段** | Communication Method / Page Role Vocabulary / Evidence & Data Expression / Visual System Defaults / Image & Icon Direction / Review Focus | style;默认值低于用户确认及身份/结构所有者 || **结构段** | 可移植 canvas/page-type 元数据、结构归属的 Signature 规则、SVG Page Roster,以及 SVG Master/Layout/slot 合同 | layout 覆盖 || **应用段** | Template Overview:重复场景、受众与结果、交付假设及代表性叙事/页面角色 | deck 独有;brand / layout 不写 |@@ -105,7 +114,7 @@ native_structure_mode: structuredDeck 编码的是**一类可重复演示**,而不只是预先组合好的 Brand 和 Layout。它描述模板服务哪些沟通场景、支持哪些受众结果,以及常见的叙事或页面角色。身份与结构围绕这份语境形成一个整体;具体选哪些原型、如何处理内容,由当前 Strategist 决定。-`standard` / `fidelity` 根据已确认的证据创作新完整系统;mirror 把已验证的来源身份与父子关系一对一映射进新工作区。Mirror 能保留来源事实,但不能单独证明来源就是可复用 Deck:创建时仍要识别稳定的应用规则。只得到身份时创建 Brand;得到品牌中立的可复用结构时创建 Layout;结构带品牌身份,或者包含场景叙事与内容语法时创建 Deck。+`standard` / `fidelity` 根据已确认的证据创作新完整系统;mirror 把已验证的来源身份与父子关系一对一映射进新工作区。Mirror 能保留来源事实,但不能单独证明来源就是可复用 Deck:创建时仍要识别稳定的应用规则。只得到身份时创建 Brand;方法与视觉方向需要脱离原型复用时创建 Style;得到品牌中立的可复用结构时创建 Layout;结构带品牌身份,或者包含场景叙事与内容语法时创建 Deck。这也约束创建模式:只有来源合同本身已经品牌中立且应用中立时,Layout mirror 才成立。删除品牌色、字体、Logo、固定身份对象或可复用应用规则都属于重新创作;越过这条边界的来源要么使用 `standard` / `fidelity` 创作新的 Layout,要么保留这些事实并创建 Deck mirror。@@ -141,6 +150,37 @@ primary_color: "<HEX>"**不允许出现**:canvas viewBox、page types、SVG roster——这些是 layout 的职责。+### Style schema++**Frontmatter**++```yaml+---+style_id: <slug>+kind: style+summary: <一句话描述可移植方法与视觉方向>+keywords: [tag1, tag2, tag3]+---+```++**正文章节**(方向/方法段)++| 节 | 标题 | 必写内容 |+|---|---|---|+| I | Style Overview | 名称、宽泛适用语境、复用意图与来源;不绑定受众/结果 |+| II | Communication Method | mode 候选、论证流、页面信息纪律与证据纪律 |+| III | Page Role Vocabulary | 开放角色及其沟通任务、证据义务和构图倾向;不规定顺序/页数 |+| IV | Evidence & Data Expression | 主张/证据、事实/假设/含义/建议区分,以及图表/表格/来源规则 |+| V | Visual System Defaults | visual-style 候选、构图、密度、装饰、节奏及可选色彩/字体 fallback |+| VI | Image & Icon Direction | 渲染、使用与处理方向;不写 inventory 或逐页映射 |+| VII | Review Focus | 仅在用户另行开启 visual review 后追加的检查点 |++Style 不写 SVG,也不拥有 Brand 官方身份、Deck 应用契约、canvas、页数/+顺序、Master/Layout/placeholder 结构或逐页资源。其色彩与字体只是可覆盖+fallback:用户最终确认及 Brand/Deck 身份优先。Review Focus 不能启动+visual review。`kind: style` 表示可复用包类型,区别于 Stage 2 的+`visual_style` 选择和内部 flat 导出值 `template_reuse_scope: style`。+### Layout schema**Frontmatter**@@ -223,11 +263,11 @@ Template Overview 写明可重复演示类型、目标受众与结果、交付/----## 三、三套 index 文件+## 三、四套 index 文件每个 index 跟物理目录一一对应,字段按需精简,沿用 [`charts_index.json`](../../skills/ppt-master/templates/charts/charts_index.json) 的紧凑“meta + summary”模式,同时保留对 Strategist 选型有用的结构化元数据。-三套索引只覆盖全局库范围。项目根工作区有意不进入任何索引,仍可通过显式 `projects/<name>/` 路径使用。因为两种范围采用相同工作区形态,完整核心工作区可在两者之间移动或复制,不需要重写素材路径;只有全局库注册不同。+四套索引只覆盖全局库范围。项目根工作区有意不进入任何索引,仍可通过显式 `projects/<name>/` 路径使用。因为两种范围采用相同工作区形态,完整核心工作区可在两者之间移动或复制,不需要重写素材路径;只有全局库注册不同。### `templates/brands/brands_index.json`@@ -243,6 +283,20 @@ Template Overview 写明可重复演示类型、目标受众与结果、交付/- 保留 `primary_color` —— Strategist 选 brand 时第一眼就要知道主色- 去掉 keywords —— summary 自带英文等价词,AI 用自然语言匹配(沿用 charts 经验)+### `templates/styles/styles_index.json`++```json+{+ "<style_id>": {+ "summary": "Answer-first、证据驱动的决策文档默认值,不含页面原型或品牌身份",+ "keywords": ["consulting", "decision-support", "evidence"]+ }+}+```++- 保留 `keywords`:方法/方向没有结构 roster,发现主要依赖语义+- 不写 canvas、page count 或 primary color;Style 不拥有结构或身份真值+### `templates/layouts/layouts_index.json````json@@ -280,22 +334,26 @@ Template Overview 写明可重复演示类型、目标受众与结果、交付/## 四、多路径合成与冲突解决-### 合成优先级(隐式触发)+### 片段所有权(隐式触发)-用户给出一组显式工作区根目录路径后,Step 3 按以下表合成 `<project>/templates/design_spec.md`:+用户给出显式工作区根目录路径后,Step 3 分片段解析并写入一份+`<project>/templates/design_spec.md`:-| 用户路径 | 合成行为 |+| 片段 | 起始所有者 ||---|---|-| 无 | 跳过 Step 3,走自由设计 |-| 只 brand | 复制 brand 全部,结构走自由设计 |-| 只 layout | 复制 layout 全部,身份走自由设计(策略师确认阶段 e/f/g 决策) |-| 只 deck | 复制 deck 全部 |-| brand + layout | brand 提供身份段 + layout 提供结构段;这是项目内组合输入,不是可复用 Deck 应用契约 |-| brand + deck | brand 段级覆盖 deck 的身份段,结构段与应用段从 deck 拿 |-| layout + deck | 只有 layout 能表达 Deck 的必需叙事/内容角色时才覆盖结构段;身份段与应用段从 deck 拿 |-| brand + layout + deck | brand 覆盖身份 + 兼容的 layout 覆盖结构 + deck 提供应用段;身份/结构段的 deck 原值整段丢弃 |+| 身份 | Brand,其次 Deck,再其次当前项目;Style 只提供 fallback 候选 |+| 方向/方法 | Style,否则为当前 Stage 2 推荐;Deck 的真实原型与 Signature 事实只提供兼容性依据 |+| 结构 | 兼容 Layout,其次 Deck,再其次自由设计 |+| 应用语境 | 当前 Stage 1 沟通契约;如有 Deck,则吸收其描述性的重复应用语境 |++用户当前明确指令和最终确认高于所有起始所有者。Brand 身份高于 Style+的色彩/字体 fallback。Style-only 或 Style + Brand 使用 flat 创作;Style+与 Layout/Deck 合成时沿用所选结构源。Style 自身不升级或降级结构。-Layout 覆盖 Deck 前,必须把 Deck 应用契约与 Layout 的页面角色、槽位类型和容量对照。如果必需角色无法表达,就把它作为合成冲突交给用户:保留 Deck 结构、改选 Layout,或明确修改应用契约。不能保留一份当前结构无法兑现的场景承诺。+Layout 覆盖 Deck 前,必须把 Deck 应用契约与 Layout 的页面角色、槽位+类型和容量对照;Style 与 Layout/Deck 合成前,也要确认其沟通方法和+构图预期能够被应用语境与结构兑现。不兼容时显式报告冲突,不能静默+混合字段或保留一份当前结构无法兑现的承诺。### 段级整段替换(默认粒度)@@ -320,8 +378,8 @@ AI: 你给了两个 brand,检测到段级冲突:- 默认无隐式顺序,所有冲突都问- 仅在用户选 (c) 才进入逐段问答;不做字段级冲突解决-- `layout × 2`、`deck × 2`、`brand × 2` 同处理-- 三类各最多两份(再多让用户先在 chat 里收敛)+- `style × 2`、`layout × 2`、`deck × 2`、`brand × 2` 同处理+- 每类最多两份(再多让用户先在 chat 里收敛)### Provenance 记录@@ -331,6 +389,7 @@ AI: 你给了两个 brand,检测到段级冲突:> **Fused from:**> - deck: `templates/decks/中国电信/` (base)> - brand: `templates/brands/anthropic/` (identity 段覆盖)+> - style: `templates/styles/consulting_analytical/` (方向/方法)> - layout: `templates/layouts/presentation_core/` (structure 段覆盖)> - conflicts resolved: Color Scheme from anthropic(用户选 a)```@@ -341,11 +400,12 @@ AI: 你给了两个 brand,检测到段级冲突:## 五、与 Generate PPTX Step 3 的关系-**触发规则仍以路径为准**——仍需显式工作区根目录路径(见 [Generate PPTX Step 3](../../skills/ppt-master/workflows/generate-pptx.md#step-3-template-option)),裸名称绝不触发。Step 3 先解析 `<workspace>/templates/design_spec.md`;为兼容目录形态,也接受根目录直接包含 `<workspace>/design_spec.md` 的平铺工作区,但其中 SVG 必须已经满足当前合同。若包仍使用 `native_structure_mode: template`、缺 Master 身份、原子 placeholder 或蒸馏时代标记等旧语义,Step 3 必须拒绝;先由 `create-template` 产出新工作区,再继续生成。唯一的窄例外是当前对话刚完成 `create-template`:验证通过后可把精确的工作区根目录直接交给 Step 3。`kind` 字段决定**触发后 AI 怎么处理**:+**触发规则仍以路径为准**——仍需显式工作区根目录路径(见 [Generate PPTX Step 3](../../skills/ppt-master/workflows/generate-pptx.md#step-3-template-option)),裸名称绝不触发。Step 3 先解析 `<workspace>/templates/design_spec.md`;为兼容目录形态,也接受根目录直接包含 `<workspace>/design_spec.md`、且满足当前 kind 合同的旧式平铺 Brand/Layout/Deck 工作区。Layout/Deck 还必须带有当前 structured SVG;Style 没有平铺形态。若包仍使用 `native_structure_mode: template`、缺 Master 身份、原子 placeholder 或蒸馏时代标记等旧语义,Step 3 必须拒绝;先由 `create-template` 产出新工作区,再继续生成。唯一的窄例外是当前对话刚完成 `create-template`:验证通过后可把精确的工作区根目录直接交给 Step 3。`kind` 字段决定**触发后 AI 怎么处理**:| 用户路径指向 | Step 3 行为(按 kind 分支)||---|---|| `kind: brand` | 把工作区 `templates/` 及实际存在的 `images/`、`icons/` 映射到项目同名目录;忽略 `exports/` |+| `kind: style` | 安装仅含 spec 的方向/方法工作区;要求无 SVG roster,并保持生成页面为 flat || `kind: layout` | 把工作区 `templates/` 及实际存在的 `images/`、`icons/` 映射到项目同名目录;忽略 `exports/` || `kind: deck` | 把工作区 `templates/` 及实际存在的 `images/`、`icons/` 映射到项目同名目录;忽略 `exports/` || 多路径 | 按上表合成单份 `design_spec.md`,解决冲突后再合并实际存在的可移植目录 |@@ -355,7 +415,7 @@ AI: 你给了两个 brand,检测到段级冲突:### 策略师确认阶段在不同 kind 下的行为-安装模板不会让沟通问题消失。Stage 1 始终独立确认同一份开放式沟通契约。Brand 提供身份约束、结构仍然自由;Layout 提供结构能力;Deck 还提供描述性应用语境。Stage 1 之后,Strategist 会读取真实原型和当前内容,生成一份页面/原型计划,只把 `mirror`、`layout` 或 `style` 记录为内部导出值。按 mirror 创建的工作区因此只提供原样复用能力,不会强制使用;Confirm UI 不显示模板模式字段。规划语义由 `references/strategist.md` 与 `references/strategist-template.md` 负责,机器结构由 `templates/schemas/spec_lock.schema.json` 负责。+安装模板不会让沟通问题消失。Stage 1 始终独立确认同一份开放式沟通契约。Brand 提供身份约束、结构仍然自由;Style 提供方法和视觉默认值候选并保持 flat;Layout 提供结构能力;Deck 还提供描述性应用语境。Style-only 时 Strategist 不读取原型,固定写入 `template_reuse_scope: style` 与 flat 结构;Layout/Deck 才读取真实原型和当前内容,生成页面/原型计划,并把 `mirror`、`layout` 或 `style` 记录为内部导出值。按 mirror 创建的工作区因此只提供原样复用能力,不会强制使用;Confirm UI 不显示模板模式字段。规划语义由 `references/strategist.md` 与 `references/strategist-template.md` 负责,机器结构由 `templates/schemas/spec_lock.schema.json` 负责。---@@ -365,10 +425,11 @@ AI: 你给了两个 brand,检测到段级冲突:|---|---|| `workflows/create-template.md` | 固定 Create Template 入口,以及范围、确认、预检、结构创作、注册、完成和交接的共享合同;只分派一个子工作流 || `workflows/create-template/create-brand.md` | 仅身份的 Brand 工作区;无 SVG roster,空的可选目录省略 |+| `workflows/create-template/create-style.md` | 仅方向/方法的 Style 工作区;无 SVG roster、身份真值、应用契约、原生结构或预览 PPTX || `workflows/create-template/create-layout.md` | 品牌中立、带结构化 SVG roster 的 Layout 工作区 || `workflows/create-template/create-deck.md` | 应用契约与身份/结构一体化、带结构化 SVG roster 的 Deck 工作区;可复用成果带品牌身份或场景语义时选择,不能只因来源是一份完整 PPTX 就默认选择 |-在全局库范围,frontmatter `kind` 字段决定工作区父目录位于 `templates/brands/` / `templates/layouts/` / `templates/decks/`。项目范围在项目工作区根目录保留同一 kind 语义。完整工作区可在两种范围之间移动而不改形,只需增加或移除全局索引注册。+在全局库范围,frontmatter `kind` 字段决定工作区父目录位于 `templates/brands/` / `templates/styles/` / `templates/layouts/` / `templates/decks/`。项目范围在项目工作区根目录保留同一 kind 语义。完整工作区可在两种范围之间移动而不改形,只需增加或移除全局索引注册。---@@ -377,6 +438,7 @@ AI: 你给了两个 brand,检测到段级冲突:- **不在 fusion 层支持字段级覆盖语法** —— 字段级微调走 策略师确认阶段这条已有路径- **不为同类三份及以上设计批量冲突解决** —— 用户先在 chat 里收敛到两份- **不引入双名映射表** —— 模板命名按其品牌/场景母语(中文模板用中文名,英文模板用 snake_case),不强制统一-- **不为输出范围新增结构分支或 CLI flag** —— 输出范围是 `create-template` 简报里的执行选择;两种范围的 Layout/Deck 都声明 `native_structure_mode: structured`-- **不增加第四种 Theme kind** —— Theme 投影 Brand、Deck 或当前项目解析后的身份,不是新的用户侧复用合同+- **不为输出范围新增结构分支或 CLI flag** —— 输出范围是 `create-template` 简报里的执行选择;两种范围的 Layout/Deck 都声明 `native_structure_mode: structured`,Brand/Style 均无 roster+- **不增加 Theme kind** —— Theme 投影 Brand、Deck 或当前项目解析后的身份;Style fallback 不是身份真值+- **不让 Style 自动触发 visual review** —— Review Focus 只补充已启用的审阅阶段- **不把 Brand + Layout 自动提升成可注册的 Deck** —— 项目内组合可以按同时具备身份/结构能力来路由,但可复用 Deck 仍必须包含应用契约diff --git a/docs/zh/templates-guide.md b/docs/zh/templates-guide.mdindex f14a5542..f3908b67 100644--- a/docs/zh/templates-guide.md+++ b/docs/zh/templates-guide.md@@ -4,7 +4,7 @@----PPT Master 模板是一种可复用工作区,明确分为三类:**Brand** 只拥有身份系统,**Layout** 只拥有品牌中立的可复用页面结构,**Deck** 拥有一类可重复演示的描述性应用语境及一体化身份与结构。Layout 与 Deck 工作区包含声明 Master / Layout / slot 合同的完整 SVG 原型;Brand 工作区则有意不包含 SVG roster。每个工作区的 `design_spec.md` 与配套素材共同声明该 kind 实际提供什么。+PPT Master 模板是一种可复用工作区,明确分为四类:**Brand** 只拥有身份系统,**Style** 只拥有可移植沟通方法和视觉默认值,**Layout** 只拥有品牌中立的可复用页面结构,**Deck** 拥有一类可重复演示的描述性应用语境及一体化身份与结构。Layout 与 Deck 工作区包含声明 Master / Layout / slot 合同的完整 SVG 原型;Brand 与 Style 则有意不包含 SVG roster。每个工作区的 `design_spec.md` 声明该 kind 实际提供什么。本文回答三个问题:@@ -19,7 +19,7 @@ PPT Master 模板是一种可复用工作区,明确分为三类:**Brand**| 起点与目标 | 路线 | 可直接复制的请求 ||---|---|---|| 手里是原始 `.pptx`,想保留现有页面壳并替换内容 | **Fill Native PPTX** | `用 projects/source/template.pptx 套入 projects/source/content.md 的内容。` |-| 已有可复用 Brand/Layout/Deck 工作区,想生成一份全新 deck | **Generate PPTX + 显式工作区路径** | `用 sources/report.pdf 做 deck,模板用 skills/ppt-master/templates/layouts/presentation_core/。` |+| 已有可复用 Brand/Style/Layout/Deck 工作区,想生成一份全新 deck | **Generate PPTX + 显式工作区路径** | `用 sources/report.pdf 做 deck,模板用 skills/ppt-master/templates/layouts/presentation_core/。` || 手里是 PPTX、SVG、品牌手册、网站、图片或混合参考,想先建立可复用系统 | **Create Template → Generate PPTX** | `用 /create-template 从 projects/brand/our_deck.pptx 创建一个可复用 Deck 工作区。` |不要把原始 `.pptx` 当作 Generate PPTX 的模板路径。想沿用它的现有页面就直接回填;想建立可复用系统,就先运行 Create Template。@@ -29,6 +29,7 @@ PPT Master 模板是一种可复用工作区,明确分为三类:**Brand**| Kind | 复用什么 | 原生 PowerPoint 结果 ||---|---|---|| **Brand** | 颜色、字体、Logo、语调、图标风格 | 只提供身份约束。生成页面保持 Slide 本地,文件只有干净的项目 Master 与 Blank Layout 脚手架。 |+| **Style** | 沟通方法、开放页面角色词汇、证据/数据规则、视觉默认值、图片/图标方向及审阅关注点 | 生成 flat Slide-local 页面;这些值只作为 Stage 2 起点,不升级为品牌身份或可复用 Layout。 || **Layout** | 品牌中立的页面语法、Master/Layout 身份、语义文字角色、槽位与版式 roster | 结构化 deck,包含可复用原生 Master、具名 Layout 与 placeholder;身份、阅读模式字号和沟通应用另行解析。 || **Deck** | 一类可重复演示:描述性应用语境、身份、页面结构与真实原型 | AI 根据模板实物与当前内容自动生成页面/原型应用计划。 |@@ -49,15 +50,15 @@ Theme、Slide Master、Slide Layout 与 Placeholder 是 PowerPoint 原生对象### 怎么触发模板流程-在 Generate PPTX 进入 Step 3 前,于对话里写出 Brand/Layout/Deck 工作区根目录(位置不重要,只要明确即可):+在 Generate PPTX 进入 Step 3 前,于对话里写出 Brand/Style/Layout/Deck 工作区根目录(位置不重要,只要明确即可):> "用这个模板做:`skills/ppt-master/templates/layouts/presentation_core/`" ✅> "用上次那个模板:`projects/last_deck/`" ✅> "做一份产品介绍,模板用 `/Users/me/Desktop/our_brand_v3/`" ✅-对于当前所有模板类型,这里给的都是**模板工作区根目录**。Step 3 会解析其中的 `templates/design_spec.md`,然后把 `templates/` 及实际存在的 `images/`、`icons/` 安装进目标项目;如果工作区本来就是该项目根目录,则原地消费,并且始终不复制 `exports/`。Deck/Layout 还会校验 structured SVG 合同。路径可以指向 `skills/ppt-master/templates/<kind>/<id>/` 下的内置库工作区、`projects/<name>/` 下的项目工作区,或其他保持同样路由的工作区。当前对话刚完成 create-template 时,可把精确的已验证工作区根目录直接交给 Step 3;用户显式提供路径与当前对话的 Create Template 交接是两种合法触发方式。+对于当前所有模板类型,这里给的都是**模板工作区根目录**。Step 3 会解析其中的 `templates/design_spec.md`;Brand/Layout/Deck 安装其包自有 `templates/` 及真实存在的 `images/`、`icons/`,Style 只安装 spec,并忽略项目中无关的脚手架。如果工作区本来就是该项目根目录,则原地消费,并且始终不复制 `exports/`。Deck/Layout 还会校验 structured SVG 合同;Brand/Style 校验各自无 roster 的 spec。路径可以指向 `skills/ppt-master/templates/<kind>/<id>/` 下的内置库工作区、`projects/<name>/` 下的项目工作区,或其他保持同样路由的工作区。当前对话刚完成 create-template 时,可把精确的已验证工作区根目录直接交给 Step 3;用户显式提供路径与当前对话的 Create Template 交接是两种合法触发方式。-> **兼容性预检:** Step 3 也接受 `design_spec.md` 与 SVG 直接位于所给根目录的平铺工作区,但这些 SVG 必须已经满足当前合同。目录平铺本身没有问题;旧的原子 placeholder、未映射 Master/Layout 等语义旧包会被拒绝。先运行 `create-template` 创建新工作区,再从该工作区生成新的 structured 页面;不会原地升级旧包。+> **兼容性预检:** Step 3 也接受 `design_spec.md` 直接位于所给根目录、且满足当前 kind 合同的旧式平铺 Brand/Layout/Deck 工作区。Layout/Deck 还必须带有当前 structured SVG;Style 没有平铺形态。旧的原子 placeholder、未映射 Master/Layout 等语义旧包会被拒绝。先运行 `create-template` 创建新工作区,再从该工作区生成新的 structured 页面;不会原地升级旧包。### 什么**不会**触发模板流程@@ -95,36 +96,37 @@ Layout 工作区:skills/ppt-master/templates/layouts/presentation_core/“模板工作区”这些标签可以不写,但路径本身必须明确。如果给出两个相同 kind 的路径,工作流会进入既有冲突解决门,不会静默替你选一个。-你不需要选择模板使用模式。默认由 Strategist 读取真实的 Master/Layout/原型集合和当前内容,决定选哪些页、哪些重复/跳过/重排,以及是否重组。如果你在意某个边界,直接在同一句请求里用普通语言说明即可,例如“封面和结束页原样保留,中间页由你选择”或“只参考视觉语言”;明确文字优先于 AI 判断。+你不需要选择模板使用模式。对 Layout/Deck,Strategist 会读取真实的 Master/Layout/原型集合和当前内容,决定选哪些页、哪些重复/跳过/重排,以及是否重组。Brand 只提供身份约束,Style 只提供方向/方法默认值;除非另一个工作区提供结构,否则两者都保持页面自由编排。如果你在意某个边界,直接在同一句请求里用普通语言说明即可,例如“封面和结束页原样保留,中间页由你选择”或“只参考视觉语言”;明确文字优先于 AI 判断。### 现有模板一览-模板按三种 kind 分目录,并分别由发现索引维护:+模板按四种 kind 分目录,并分别由发现索引维护:- [`brands_index.json`](../../skills/ppt-master/templates/brands/brands_index.json) — 仅身份工作区:color / typography / logo / voice / icon style,不含 SVG 页面 roster+- [`styles_index.json`](../../skills/ppt-master/templates/styles/styles_index.json) — 仅方向/方法工作区:沟通方法、证据/数据表达、视觉默认值与审阅关注点,不含 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) — 可重复演示应用,包含一体化身份、结构与原型事实描述-直接问“有哪些模板可以用?”即可得到带工作区路径的可读清单。索引是当前安装内容的真值,三类 README 负责定义合同。完整数据模型与三类的合成 / 冲突解决规则见 [`templates-architecture.md`](./templates-architecture.md)。+直接问“有哪些模板可以用?”即可得到带工作区路径的可读清单。索引是当前安装内容的真值,四类 README 负责定义合同。完整数据模型与四类的合成 / 冲突解决规则见 [`templates-architecture.md`](./templates-architecture.md)。### 自由设计 vs 模板-自由设计不是“没有结构”或“没有风格”——Strategist 仍会为这份 deck 规划叙事、层级与视觉系统,但生成页面使用 `pptx_structure.mode: flat`,所有可见对象都保留在 Slide 本地。仅使用 Brand 工作区时同样保持 `flat`,只是由 Brand 提供身份约束。Layout 与 Deck 工作区提供可复用 Master / Layout / slot 合同;Strategist 会读取真实原型和当前内容,自动判断是复用结构,还是只参考视觉语言。+自由设计不是“没有结构”或“没有风格”——Strategist 仍会为这份 deck 规划叙事、层级与视觉系统,但生成页面使用 `pptx_structure.mode: flat`,所有可见对象都保留在 Slide 本地。仅使用 Brand 或 Style 工作区时同样保持 `flat`:Brand 提供身份约束,Style 提供可复用方法与视觉默认值候选。Layout 与 Deck 工作区提供可复用 Master / Layout / slot 合同;Strategist 会读取真实原型和当前内容,自动判断是复用结构,还是只参考视觉语言。-> 经验:需要锁定身份系统时用 Brand;需要复用品牌中立结构、但让用途保持开放时用 Layout;需要把品牌化结构或可重复沟通场景作为一份契约复用时用 Deck;希望版式从当前内容出发重新生长时走自由设计。+> 经验:需要锁定身份系统时用 Brand;需要复用方法和视觉方向、但不固定页面时用 Style;需要复用品牌中立结构、但让用途保持开放时用 Layout;需要把品牌化结构或可重复沟通场景作为一份契约复用时用 Deck;希望全部从当前内容出发时走自由设计。-### 风格不是模板+### 风格说明不是 Style 工作区-**风格说明**是解释性语言(“极简风” / “Keynote 风” / “杂志风”),由 Strategist 转化为具体设计选择。**模板**则是真实存在的 Brand / Layout / Deck 工作区,只有在你给出**显式目录路径**时才会被工作流消费。+**风格说明**是解释性语言(“极简风” / “Keynote 风” / “杂志风”),由 Strategist 转化为当前 deck 的具体设计选择。**Style 工作区**则是真实存在的 `kind: style` 模板,预写可复用沟通方法与视觉默认值,只有在你给出**显式目录路径**时才会被消费。-| | 模板 | 风格 |+| | Style 工作区 | 风格说明 ||---|---|---|| 怎么触发 | 消息里给出明确的目录路径 | 消息里写自由描述 |-| 提供什么 | 由 kind 声明的身份段、结构段或两者 | 由 Strategist 解释为 mode、visual style、色彩、字体、图标与图片方向 |-| 如何确认 | 模板拥有的值构成起始合同;用户最终确认的选择仍然权威 | 没有预写数值;Strategist 给出具体候选,由用户确认 |-| 适用场景 | 复用已有身份系统和 / 或页面系统 | 只表达想要的感觉,不采用已存工作区 |+| 提供什么 | 可复用方法、角色/证据纪律和视觉默认值;无身份真值或页面原型 | 由 Strategist 解释为 mode、visual style、色彩、字体、图标与图片方向 |+| 如何确认 | 已存值作为 Stage 2 起点;Brand/Deck 身份和用户最终确认仍然权威 | 没有预写数值;Strategist 给出具体候选,由用户确认 |+| 适用场景 | 跨项目复用论证与设计方法,但不锁页面 | 只表达当前项目想要的感觉 |-风格描述和模板名仍走**两套机制**:“极简风”是解释性语言,`presentation_core/` 则是真实模板目录,必须提供显式路径。+风格描述和 Style 工作区仍走**两套机制**:“极简风”是解释性语言,`templates/styles/<id>/` 则是真实模板目录,必须提供显式路径。`kind: style`、Stage 2 `visual_style` 与内部 `template_reuse_scope: style` 是三条不同轴。### 风格说明如何被解释@@ -151,7 +153,7 @@ Strategist 会把方向拆成两个彼此独立的选择:接下来工作流会**强制**先和你确认一份模板简报(不允许跳过)。-入口名称始终保持 **Create Template**。它只分派一个子工作流:仅复用身份走 Create Brand;复用品牌中立结构、且沟通应用保持开放时走 Create Layout;复用品牌化结构或可重复演示应用时走 Create Deck。来源是一份完整 PPTX 并不会自动决定 kind,工作流只按真正稳定、值得重复使用的规则分类。子工作流一旦选定,不会在简报里再次选 kind。+入口名称始终保持 **Create Template**。它只分派一个子工作流:仅复用身份走 Create Brand;复用无页面原型的可移植方法/方向走 Create Style;复用品牌中立结构、且沟通应用保持开放时走 Create Layout;复用品牌化结构或可重复演示应用时走 Create Deck。来源是一份完整 PPTX 并不会自动决定 kind,工作流只按真正稳定、值得重复使用的规则分类。子工作流一旦选定,不会在简报里再次选 kind。### 第一步:准备参考材料包或简报@@ -171,29 +173,31 @@ Strategist 会把方向拆成两个彼此独立的选择:|------|------|| **输出范围** | `library`(默认)或 `project`;两者使用相同的可移植工作区路由,只有 library 会进入全局索引 || **目标项目** | 仅 `project` 必填;必须给出已初始化项目的精确路径 |-| **已选子工作流** | Create Brand / Create Layout / Create Deck,由入口分派后固定 |+| **已选子工作流** | Create Brand / Create Style / Create Layout / Create Deck,由入口分派后固定 || **模板 ID** | 模板的可移植身份;在 `library` 下同时也是目录名 / 索引键。优先 ASCII slug,如 `acme_consulting`;中文品牌名也行,但要文件系统安全 || **显示名称** | 文档中的人类可读名 |-| **模板语境** | AI 提议一个类别、适用场景、显示名称、调性概要和索引关键词;你可直接修改文字 |-| **画布与视觉方向** | 仅 Create Layout/Create Deck:建议画布、明暗关系、身份和从来源观察到的视觉规则 |-| **创建方案** | AI 将保留、重建、简化或提取什么;原型范围多大;如何处理原生结构——全部用普通语言说明 |-| **来源事实与素材** | 可观察的 Master/Layout 事实、受支持原生能力、采用/排除的素材及重要限制 |+| **kind 专属语境** | Brand:身份适用场景和调性。Style:宽泛 best fit 与发现关键词。Layout:结构可承载场景及 category/keywords。Deck:重复应用场景及 category/keywords。你可直接修改文字 |+| **方法与视觉默认值** | 仅 Create Style:沟通方法、开放页面角色词汇、证据/数据表达、视觉默认值、图片/图标方向和审阅关注点;不写受众/页序/结构契约 |+| **身份** | 仅 Create Brand/Create Deck:色板、字体、Logo、voice 与 icon identity |+| **画布与结构** | 仅 Create Layout/Create Deck:画布、页面语法、Master/Layout/slot 方案、密度行为和来源结构规则 |+| **来源处理** | 每个 child 只说明如何提取自己拥有的片段;仅 Layout/Deck 描述原型覆盖范围、保留/重建策略和原生结构 |+| **来源事实与素材** | Brand/Layout/Deck 列出采用或排除的素材;Layout/Deck 另报告可观察的 Master/Layout 事实和受支持原生能力。Style 只保留文字 provenance |确认后,工作流会回显一份完整简报并写入标记 `[TEMPLATE_BRIEF_CONFIRMED]`,从这一刻起后续步骤才会启动。**这是一个硬门——简报没确认,不会开始生成**。无论选择哪种范围,第一次写最终文件前都会做一次完整预检:解析必需的 `templates/` 和实际需要的可选素材目录,要求 `templates/` 为空,并检查 `images/` 与 `icons/imported/` 中计划写入的位图和导入向量文件名没有冲突;只有明确要求审阅 PPTX 时才检查 `exports/`。项目范围还要求目标项目已经初始化。项目初始化时已存在的空脚手架目录可以保留且不会被算作模板产物;Create Template 不会为了保留空路径而新建可选目录。任一检查失败都会在写入前停止,不合并、不覆盖,也不会留下半套输出。-> 为什么这么严?无论模板进入全局库,还是只服务当前项目,它都是结构契约。先确认归属和几何,可避免半成品或资产落错目录。+> 为什么这么严?无论模板进入全局库,还是只服务当前项目,它都是可复用的 ownership contract。先确认所拥有的片段和目标位置,并且只为 Layout/Deck 确认几何,可避免半成品或资产落错目录。### 第三步:AI 推导内部实现-你不需要选择创建模式。AI 会把已确认的自然语言方案转换成一个内部策略,供确定性工具执行:+Create Style 会直接写入已确认的方向/方法 spec,不进入 SVG 创建模式。对 Create Layout/Create Deck,你不需要选择创建模式;AI 会把已确认的自然语言方案转换成一个内部策略,供确定性工具执行:- 需要精炼时,创建紧凑的可复用系统;- 来源本身包含有价值的多种版式时,创建更广的来源对齐原型;- 明确要求原样保留、且来源结构完整受支持时,进行字面物化。-frontmatter 仍会记录 `replication_mode: standard|fidelity|mirror` 以兼容工具并保留审计信息;它是实现记录,不是用户选项。品牌中立的 Layout 不能同时字面保留品牌/应用事实,AI 会按目标重新创作 Layout,或把这些事实留在 Deck 中。+Layout/Deck frontmatter 仍会记录 `replication_mode: standard|fidelity|mirror` 以兼容工具并保留审计信息;它是实现记录,不是用户选项。Style frontmatter 有意不写 replication/native-structure 字段。品牌中立的 Layout 不能同时字面保留品牌/应用事实,AI 会按目标重新创作 Layout,或把这些事实留在 Deck 中。**关于精灵图**:PPTX 导出的素材常常是**一张大图 + 多页通过 viewBox 裁剪不同区域**。`fidelity` 和 `mirror` 模式下必须保留这层嵌套 `<svg viewBox=...>` 包装,不能扁平化为单张 `<image>`——否则裁剪信息丢失,画面会错位。工作流会自动校验这一点。@@ -217,11 +221,11 @@ python3 skills/ppt-master/scripts/mirror_template_materialize.py \### 第四步:验证、预览导出、注册与发现-模板生成完,两种范围都会先跑 [`svg_quality_checker.py`](../../skills/ppt-master/scripts/svg_quality_checker.py) 作为硬门:Brand 校验 identity-only 规范与素材引用,Layout/Deck 校验 SVG roster 和 structured 合同。如果需要 PowerPoint 审阅文件,再运行可选预览导出;它会按需创建 `exports/<id>_template_preview.pptx`。创作型模板会只在临时预览副本中使用简短占位示例,避免较长的 canonical marker 换行,不会修改源 SVG。唯一按范围分流的动作是全局注册:+模板生成完,两种范围都会先跑 [`svg_quality_checker.py`](../../skills/ppt-master/scripts/svg_quality_checker.py) 作为硬门:Brand 校验 identity-only 规范,Style 校验 method/direction-only 规范,Layout/Deck 校验 SVG roster 和 structured 合同。Brand/Style 不生成预览 PPTX;Layout/Deck 可按需创建 `exports/<id>_template_preview.pptx`,多 Master 时必须创建。创作型模板只在临时预览副本中使用简短占位示例,避免较长的 canonical marker 换行,不会修改源 SVG。唯一按范围分流的动作是全局注册:| 范围 | 工作区根目录 | 预览 | 发现行为 ||---|---|---|---|-| `library`(默认) | `skills/ppt-master/templates/<kind>/<id>/` | Create Brand:不适用;Create Layout/Create Deck:单 Master 可选、多 Master 必须 | 校验后注册到对应 `brands_index.json`、`layouts_index.json` 或 `decks_index.json` |+| `library`(默认) | `skills/ppt-master/templates/<kind>/<id>/` | Create Brand/Create Style:不适用;Create Layout/Create Deck:单 Master 可选、多 Master 必须 | 校验后注册到对应 `brands_index.json`、`styles_index.json`、`layouts_index.json` 或 `decks_index.json` || `project` | `projects/<name>/` | 沿用同一套 kind-specific 审阅规则 | 跳过全局索引注册 |全局注册让模板**可被发现**——下次有人问“有哪些模板可用?”时,AI 会从索引里把它列出来。两种范围的用法相同:按 [Generate PPTX Step 3](../../skills/ppt-master/workflows/generate-pptx.md#step-3-template-option) 的规则,在 Step 3 运行前给出工作区根目录,例如 `用这个模板:skills/ppt-master/templates/layouts/<your_template_id>/` 或 `用这个模板:projects/<name>/`。项目工作区也可以迁移或被其他工作区复用,因为核心结构完全一致;只有放进全局库并需要被发现时才执行注册。@@ -240,7 +244,7 @@ python3 skills/ppt-master/scripts/mirror_template_materialize.py \| 点击可复用内容区域 | 模板槽位表现为带声明类型与边界的原生 placeholder。 || 从某个已导出 Layout 新建一页 | 不复制成品内容页,也能得到该 Master/Layout 的固定视觉与 placeholder 几何。 |-Brand-only 的目标不同:它只施加身份约束,创作内容仍保持 Slide 本地,因此不应期待除干净包脚手架之外的可复用 Layout roster。+Brand/Style 的目标不同:两者都让创作内容保持 Slide 本地,因此不应期待除干净包脚手架之外的可复用 Layout roster;Brand 提供身份,Style 提供方法/方向默认值。`exports/<id>_template_preview.pptx` 是 Create Template 按需或按规则生成的审阅证据,不是模板输入;真正生成时始终传工作区根目录。@@ -250,6 +254,9 @@ Master/Layout 行为以 Microsoft PowerPoint 为验收目标。Keynote、WPS 与全局库与项目范围使用相同的核心结构。把下面的 `<template_workspace>` 替换为 `skills/ppt-master/templates/<kind>/<id>/` 或 `projects/<name>/` 即可:+Brand 与 Style 只写 `templates/design_spec.md`(Brand 可带真实身份资产),+不会生成下面的 SVG 或 `exports/` 行。+```<template_workspace>/├── templates/@@ -279,7 +286,7 @@ Master/Layout 行为以 Microsoft PowerPoint 为验收目标。Keynote、WPS 与- **全局库范围(`library`,默认)**把工作区写入 `skills/ppt-master/templates/<kind>/<id>/`,并完成全局注册。- **项目范围(`project`)**把同一份可移植工作区写入 `projects/<name>/`,并跳过注册。-项目范围不是私有或缩减格式。Step 3 可以直接接收任一工作区根目录;`templates/` 及实际存在的 `images/`、`icons/` 可以在两类根目录之间复制或迁移,无需改形。如果迁入全局库,再执行注册,让发现索引反映新位置。+项目范围不是私有或缩减格式。Step 3 可以直接接收任一工作区根目录。Brand/Layout/Deck 迁移 `templates/` 及真实的包自有 `images/`、`icons/`;Style 只迁移 `templates/design_spec.md`,并忽略无关的项目脚手架。迁入全局库后,再按对应 kind 执行注册,让发现索引反映新位置。---@@ -287,8 +294,8 @@ Master/Layout 行为以 Microsoft PowerPoint 为验收目标。Keynote、WPS 与避免常见误解:-- **可复用模板是一份显式工作区,不是打包后的源 PPTX。** Brand 可以只有身份系统;Layout 与 Deck 才增加 structured SVG 合同。创作模式建立这份合同,mirror 则把经过验证的来源归属事实映射进去;导出只编译已声明的结构-- **模板不是一张不可拆分的“风格皮肤”。** Brand、Layout 与 Deck 有意把身份和结构拆开,使每一段都能按明确所有权单独复用或参与合成+- **可复用模板是一份显式工作区,不是打包后的源 PPTX。** Brand 与 Style 无 roster;Layout 与 Deck 才增加 structured SVG 合同。创作模式建立这份合同,mirror 则把经过验证的来源归属事实映射进去;导出只编译已声明的结构+- **模板不是一张不可拆分的“风格皮肤”。** Brand、Style、Layout 与 Deck 有意拆开身份、方向/方法、结构和应用,使每一段都能按明确所有权单独复用或参与合成- **模板不会替你做内容决策**。策略师仍然会按内容判断每页用哪个版式、要不要扩展为变体,模板提供候选,不预设结果- **`fidelity` 模式不等于像素级搬运**。即便是 `literal` 保真,AI 仍会把杂质和不必要的重复结构清理掉——载体保留几何,但不照抄冗余- **`mirror` 的目标是受支持范围内的视觉与来源拓扑忠实,不是字节级 OOXML**。它继承源 PPT 的导入限制,只允许固定结构层 group 展开等机械归一化。不支持的原生对象保留可用 SVG fallback 或明确报告;mirror 不归纳替代 ownership。@@ -298,6 +305,6 @@ Master/Layout 行为以 Microsoft PowerPoint 为验收目标。Keynote、WPS 与## 相关文档- [`workflows/create-template.md`](../../skills/ppt-master/workflows/create-template.md) — 完整工作流规范(面向 AI 执行)-- [`templates/layouts/README.md`](../../skills/ppt-master/templates/layouts/README.md) — 现有模板一览+- [`templates/README.md`](../../skills/ppt-master/templates/README.md) — 四类模板及其发现索引- [`references/template-designer.md`](../../skills/ppt-master/references/template-designer.md) — 模板设计师角色定义和 SVG 技术约束- [常见问题:如何制作自定义模板](./faq.md#q-如何制作自定义模板) — FAQ 简版diff --git a/docs/zh/why-ppt-master.md b/docs/zh/why-ppt-master.mdindex d955f5e7..549542f9 100644--- a/docs/zh/why-ppt-master.md+++ b/docs/zh/why-ppt-master.md@@ -25,7 +25,7 @@- **按需的原生图表与表格** —— 需要时就是带「编辑数据」工作簿的数据驱动图表 / 表格对象(取舍见下)- **完整的文本 / 图片 / 填充 / 效果模型** —— 段落与文本级格式、图片裁剪与形状裁切、渐变、图案、外阴影、发光- **转场、进入 / 强调 / 动作路径 / 退出动画、演讲者备注 → 语音旁白** —— 都是真正的 OOXML 计时与包内部件,不是烤进去的视频-- **在这之上的模板提炼** —— 把一份现成的 deck 交给它,它能提炼出可复用的 brand / layout / deck 模板;这是建立在原生原语**之上**的一层复用能力+- **在这之上的模板提炼** —— 把参考材料交给它,它能提炼出可复用的 brand / style / layout / deck 模板;这是建立在原生原语**之上**的一层复用能力而这份深度是**一个前进方向,不是一张固定清单。** 项目的北极星是持续向 PowerPoint 本身靠拢——不断开发、集成更多它的原生能力,一个版本接一个版本,缩小「AI 能替你生成的」和「你在 PowerPoint 里手工能做出的」之间的差距。diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.mdindex 98f5b893..f735d60d 100644--- a/skills/ppt-master/SKILL.md+++ b/skills/ppt-master/SKILL.md@@ -2,7 +2,7 @@name: ppt-masterdescription: >AI-driven presentation workflow for generating editable PPTX decks, creating- reusable Brand/Layout/Deck workspaces, filling native PPTX templates, and+ reusable Brand/Style/Layout/Deck workspaces, filling native PPTX templates, andenhancing finished PPTX files. Use when the user asks to create, regenerate,template, fill, or enhance a presentation, or mentions ppt-master.metadata:diff --git a/skills/ppt-master/references/artifact-ownership.md b/skills/ppt-master/references/artifact-ownership.mdindex 99d3470a..58aed74e 100644--- a/skills/ppt-master/references/artifact-ownership.md+++ b/skills/ppt-master/references/artifact-ownership.md@@ -33,7 +33,7 @@ the default profile, but it does not create `svg_final/`.| `images/` | Runtime image pool | User, extracted, AI, web, formula, slice, EMF/WMF assets | Default Step 5 or Quick Generate resource preparation writes here; `analysis/image_analysis.csv` derives from current contents || `images/image_prompts.json`, `image_queries.json`, `image_sources.json`, `formula_manifest.json` | Conditional resource contracts | AI/web/formula execution status and provenance | Create only for a triggered path, including Quick. They guide preparation/attribution, never page design. || `icons/` | Prepared project icon pool | Bundled icons copied by `icon_sync.py` plus user-provided, template, imported, or custom icon SVGs | SVG authoring may use any icon in this project-local pool; `spec_lock.icons.inventory` records the default plan's bundled choices rather than an exhaustive whitelist. Exporter global fallback is legacy compatibility only. |-| `templates/` | Project template reference | Step 3 imported specs, template SVGs, and non-image assets | Strategist reads the template Design Spec and actual SVG roster during planning. Continuous Executor reuses that context; fresh Executor reads the Design Spec once and each selected complete SVG only before first use or after its SHA changes. |+| `templates/` | Project template reference | Step 3 imported specs, optional Layout/Deck SVG prototypes, and non-image assets | Strategist reads every installed template Design Spec. It reads an actual SVG roster only for Layout/Deck; Brand and Style are intentionally roster-free. Continuous Executor reuses that context; fresh Executor reads the Design Spec once and each selected complete SVG, when any, only before first use or after its SHA changes. || `templates/template_execution_manifest.json` (`v1`) + `templates/template_execution/*.text-slots.json` (`v2-min`) | Derived template index | Compact prototype/source-import summary plus per-prototype text-slot diagnostics; the sidecar integrity hash is tool-only | Materialization may publish these deterministic records, but page-context does not inject or require them and models do not read them during page authoring. The complete prototype SVG is the sole visual/template authority; never author from either JSON artifact. || `<import_workspace>/svg/` | Imported native-payload backing | Complete PPTX-derived metadata, hidden carriers, fallback evidence, and source structure | Keep immutable; create-template materialization may resolve a validated source ref against these files, but models do not edit or bulk-read them || `<import_workspace>/svg-flat/` | Optional complete-page verification backing | Self-contained visual composition generated only by explicit `--inheritance-mode both` | Keep immutable when requested; never use as authoring or materialization input |@@ -64,11 +64,11 @@ the default profile, but it does not create `svg_final/`.| Sources read policy | In `sources/`, read content-type files (`.md` / `.markdown` / `.txt` / `.csv` / `.tsv` / `.json` / `.jsonl` / `.yaml` / `.yml`) and judge by content — a `.json` / `.csv` may be core content or just data. Exclude known sidecars: `*.conversion_profile.json` and `*_files/image_manifest.json`. `analysis/` facts (`source_profile.json`, `<stem>.slide_library.json`) are read per Step 4 / direct-PPTX workflow, not in the `sources/` content scan. || PPTX structure | `slide_library.json` owns native geometry, slot facts, and SmartArt layout/relationships for direct PPTX workflows. || Design contract | Final confirmation once → audited `design_spec.md` → optional same-file refinement/approval → context-authored lock. Never maintain a parallel draft/lock. Executor may apply `Template Application` prose but never replace identity. Repair divergence from the approved Design Spec/context unless it fails active-decision fidelity. |-| Flat packaging authority | Free-design, brand-only, and `template_reuse_scope: style` declare `pptx_structure.mode: flat` and omit `pptx_masters`, `pptx_layouts`, `page_pptx_layouts`, and `page_layouts`. `svg_output/` owns the complete Slide-local visual design without root Master/Layout identity, fixed-layer ownership, or placeholder metadata. Export materializes one clean project-owned Master plus one Blank Layout, applies the locked theme defaults, removes stock content placeholders/Layout inventory, and retains only the standard date/footer/slide-number capability hooks. |+| Flat packaging authority | Free-design, brand-only, Style-only, and every plan with `template_reuse_scope: style` declare `pptx_structure.mode: flat` and omit `pptx_masters`, `pptx_layouts`, `page_pptx_layouts`, and `page_layouts`. A Style fused with Layout/Deck changes only Direction / method and does not force the non-Style structure plan to flat. `svg_output/` owns the complete Slide-local visual design without root Master/Layout identity, fixed-layer ownership, or placeholder metadata. Export materializes one clean project-owned Master plus one Blank Layout, applies the locked theme defaults, removes stock content placeholders/Layout inventory, and retains only the standard date/footer/slide-number capability hooks. || Template structure authority | `template_reuse_scope: mirror|layout` uses `page_layouts` for each page's authoring-input prototype. `pptx_masters` / `pptx_layouts` own the unique reusable output definitions, while `page_pptx_layouts` owns page assignment. Strict keeps the prototype contract; adaptive may use a current or new Layout already declared by Strategist. A construction-discovered structural change returns upstream for definition and assignment repair before authoring resumes. Mirror additionally preserves literal visuals/text topology; layout allows project-controlled reflow/re-skinning. Unused definitions may register without a published Slide. Templates validate provenance but never add missing visible page objects during export. || Fact classes | External facts resolve through `sources/*.facts.json`; invented demo KPIs/targets/internal ratios are labeled `scenario` in `design_spec.md §IX` and visibly in the page. Never promote scenario data into the external fact registry. || Imported-template authoring | Editable SVGs under `authoring-svg/` own create-template edits, `authoring_summary.json` owns model-facing orientation, and `authoring_manifest.json` owns tool-only source-object identity. Lossless `svg/` owns immutable native payload and fallback evidence; optional `svg-flat/` owns only complete-page verification. Materialized `templates/*.svg` own the validated deliverable contract and contain no IR-only source refs. |-| Legacy template input | Old unmapped/distilled/preserve structured projects and incomplete template packages are not migrated in place. [`create-template`](../workflows/create-template.md) authors a new current workspace: original PPTX Type A may preserve existing native topology in mirror; legacy SVG-only Type B is visual reference for `standard` / `fidelity`. An intentional free-design or brand-only `flat` project is already current. The exporter does not migrate or visually cluster legacy structure. |+| Legacy template input | Old unmapped/distilled/preserve structured projects and incomplete template packages are not migrated in place. [`create-template`](../workflows/create-template.md) authors a new current workspace: original PPTX Type A may preserve existing native topology in mirror; legacy SVG-only Type B is visual reference for `standard` / `fidelity`. Intentional free-design, Brand-only, and Style-only `flat` projects are already current. The exporter does not migrate or visually cluster legacy structure. || Image facts | `images/` is live state; `analysis/image_analysis.csv` is a regenerated view, not a durable cache. || SVG source | `svg_output/` is the only author source for generated pages. || Page-design closure | On SVG-authoring routes, every visible exported-slide object exists in the corresponding page SVG or an explicitly referenced visual asset. |diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.mdindex d41beb11..b7ee2b80 100644--- a/skills/ppt-master/references/executor-base.md+++ b/skills/ppt-master/references/executor-base.md@@ -17,7 +17,7 @@ Always-loaded Executor authority for flat SVG page authoring and behavior shared**Hard rule — complete page SVG**: Every visible object intended for the exported slide MUST exist in the final page SVG or be explicitly referenced by it. Templates and `spec_lock.md` guide construction; they are not export-time overlays for missing visible content.-**Hard rule — flat PowerPoint structure**: Free-design, brand-only, and `template_reuse_scope: style` projects use `pptx_structure.mode: flat`: write no root Master/Layout identity, `data-pptx-layer`, or `data-pptx-placeholder`; every visible object remains Slide-local, and the root declares exactly one canonical `data-pptx-page-role` (`cover` / `toc` / `section` / `content` / `ending`). A `style` template supplies colors, typography, decoration, and rhythm as style input without creating per-page prototype mappings. Export materializes one clean project-owned Master plus one Blank Layout from the current lock. Add `data-pptx-role` only to structural page-frame objects whose package, page-number, or animation behavior is not already expressed by specialized metadata; the marked element uses a stable unique `id`. See [`semantic-svg.md`](./semantic-svg.md).+**Hard rule — flat PowerPoint structure**: Free-design, brand-only, Style-only, and every `template_reuse_scope: style` project use `pptx_structure.mode: flat`: write no root Master/Layout identity, `data-pptx-layer`, or `data-pptx-placeholder`; every visible object remains Slide-local, and the root declares exactly one canonical `data-pptx-page-role` (`cover` / `toc` / `section` / `content` / `ending`). A Style workspace supplies reusable communication/design direction, composition rhythm, and information-expression defaults without page prototypes. Its identity-adjacent color, typography, icon, and image defaults yield to the final Brand/Deck identity and confirmed project lock. When Style is fused with Layout/Deck, it changes only Direction / method and follows the resolved non-Style structure route. Export materializes one clean project-owned Master plus one Blank Layout from the current lock. Add `data-pptx-role` only to structural page-frame objects whose package, page-number, or animation behavior is not already expressed by specialized metadata; the marked element uses a stable unique `id`. See [`semantic-svg.md`](./semantic-svg.md).**Hard rule — supported PPTX route**: The only supported generated-PPTX path is `svg_output/` through the project SVG-to-DrawingML converter. Step 7.2 still generates `svg_final/` as a mandatory self-contained visual preview that may be inserted as an SVG picture. Do not treat PowerPoint's manual Convert-to-Shape operation as an authoring target or compatibility requirement.diff --git a/skills/ppt-master/references/strategist-template.md b/skills/ppt-master/references/strategist-template.mdindex f67eefcb..e1023b56 100644--- a/skills/ppt-master/references/strategist-template.md+++ b/skills/ppt-master/references/strategist-template.md@@ -2,35 +2,37 @@# Strategist Template Planning-Conditional extension for applying an installed Brand/Layout/Deck workspace to Stage 2 recommendations and the execution lock.+Conditional extension for applying an installed Brand/Style/Layout/Deck workspace to Stage 2 recommendations and the execution lock.-**Trigger**: Load only when Generate Step 3 copied an explicit workspace path into `<project_path>/templates/`. Bare template names, style words, and free-design projects do not trigger this module.+**Trigger**: Load only when Generate Step 3 validated an explicit workspace path and either installed it into `<project_path>/templates/` or confirmed that the target project is consuming it in place. Bare template names, style words, and free-design projects do not trigger this module.---## 1. AI-Authored Template Application Plan-**Template vs preset**: A style mention and a template directory are different inputs. Bare names and style words map to a visual-style preset; only the installed workspace activates the rules below. Its fused `<project_path>/templates/design_spec.md` is the template-design source.+**Template vs preset**: A style mention and a Style workspace are different inputs. Bare names and style words remain interpretive input and never resolve to a local path; only an explicitly installed workspace activates the rules below. Its fused `<project_path>/templates/design_spec.md` is the template-design source. Treat `kind: style` or a fused provenance entry for `style` as an active Direction / method segment.-**Legacy template boundary**: A template containing `native_structure.json`, `source_template.pptx`, missing root Master identity, direct atomic placeholders, or old `baseline` / `preserve` / distillation metadata is not a Generate Step 3 input. Create a current workspace through [`create-template`](../workflows/create-template.md), preferably from the original PPTX when native topology matters. Do not mutate the input in place.+**Legacy template boundary**: A Layout/Deck template containing `native_structure.json`, `source_template.pptx`, missing root Master identity, direct atomic placeholders, or old `baseline` / `preserve` / distillation metadata is not a Generate Step 3 input. Create a current workspace through [`create-template`](../workflows/create-template.md), preferably from the original PPTX when native topology matters. Brand and Style are intentionally roster-free; never reject either for omitting SVG or Master identity. Do not mutate the input in place.**No template-mode confirmation**: Never ask the user to select `template_reuse_scope`, `template_adherence`, `mirror`, `layout`, `style`, `strict`, or `adaptive`. These are internal execution values for the current exporter. The user communicates intent in natural language; explicit instructions such as “全部原样保留”, “从中选合适的页面”, “可以重组”, or “只参考视觉” are authoritative. Without an explicit instruction, Strategist decides.Immediately before authoring the Stage-2 solution, load each relevant templateresource once per path + SHA and inspect:-- the installed `design_spec.md`, actual Page Roster, and relevant SVG prototypes;+- every installed `design_spec.md`; for Layout/Deck only, also inspect the actual Page Roster and relevant SVG prototypes;+- the resolved Identity, Structure, Application, and Direction / method segment owners from the Step-3 fusion receipt;- the current communication contract, source obligations, planned page count, and content shape of every planned page;- the user's natural-language instructions, including any page names/numbers or elements they explicitly require.Then author one plan that decides all of the following without presenting an option menu:-- whether the full prototype set, a relevant subset, or only the design language is useful;-- which prototype each generated page starts from, which template pages are skipped, and which prototypes are repeated or reordered;-- whether content is inserted directly, reorganized inside the existing structure, or rebuilt while retaining only visual language;+- for Layout/Deck, whether the full prototype set, a relevant subset, or only the design language is useful;+- for Layout/Deck, which prototype each generated page starts from, which template pages are skipped, and which prototypes are repeated or reordered;+- whether content is inserted directly, reorganized inside existing structure, or rebuilt under the resolved Direction / method segment;+- for Style, which communication method, visual language, composition rhythm, and information-expression defaults are adopted or adapted without inventing page prototypes;- which visible elements must remain literal because the user said so, and which may change to serve the current content.-Template size is evidence, not policy. A short template may use every prototype when the content genuinely fits; a 20–30 page source may contribute only a few suitable pages, or several pages may be reorganized into a new sequence. Never infer that all pages must be kept or that visible sample content is protected merely because it exists in the template.+For Layout/Deck, template size is evidence, not policy. A short template may use every prototype when the content genuinely fits; a 20–30 page source may contribute only a few suitable pages, or several pages may be reorganized into a new sequence. Never infer that all pages must be kept or that visible sample content is protected merely because it exists in the template. Style and Brand have no prototype set.Record the resulting exporter plan internally:@@ -38,13 +40,13 @@ Record the resulting exporter plan internally:|---|---|| `template_reuse_scope: mirror` | The workspace has `replication_mode: mirror`, the plan calls for literal page reuse, and each page changes only allowed visible text values while preserving visual and text-node topology. || `template_reuse_scope: layout` | The plan reuses the template Master/Layout system and prototypes while allowing current-project content and appearance decisions. |-| `template_reuse_scope: style` | The plan uses only color, typography, decoration language, or rhythm and intentionally creates flat free-design pages. |+| `template_reuse_scope: style` | A Style-only workspace is active, or the plan uses only communication/design direction, color, typography, decoration language, composition, or rhythm and intentionally creates flat free-design pages. || `template_adherence: strict` | Every structured page fits an existing prototype contract without changing its Layout identity or slot topology. Mandatory for `template_reuse_scope: mirror`. || `template_adherence: adaptive` | Structured reuse remains useful, but at least one page needs a new explicit Layout under the selected Master. |Write only the derived values to `spec_lock.md pptx_structure`; omit `template_adherence` for `style`. Do not put these internal values in `design_spec.md`, recommendation stage files, the Confirm UI, or `result.json`.-**Mandatory — natural-language Stage-2 plan**: Summarize which prototypes are used/skipped/repeated/reordered, what stays literal, and what may be replaced or reorganized. Write it to top-level `template_application.value` in `recommendations.stage2.json`; omit it without an active template. After Stage 2, re-read the confirmed `result.json` value (or exact chat answer), never the initial recommendation. Blank returns the decision to Strategist. Persist the effective plan on one line as `- **Template Application**: <prose>` in `design_spec.md §I`, then derive internal reuse/adherence values and mappings; never copy the prose to `spec_lock.md`. Do not add a questionnaire, internal controls, or fixed template-use options.+**Mandatory — natural-language Stage-2 plan**: For Layout/Deck, summarize which prototypes are used/skipped/repeated/reordered, what stays literal, and what may be replaced or reorganized. For Brand/Style, summarize the installed identity or Direction / method constraints and state that pages remain freely composed unless another workspace supplies structure. Write the result to top-level `template_application.value` in `recommendations.stage2.json`; omit it without an active template. After Stage 2, re-read the confirmed `result.json` value (or exact chat answer), never the initial recommendation. Blank returns the decision to Strategist. Persist the effective plan on one line as `- **Template Application**: <prose>` in `design_spec.md §I`, then derive internal reuse/adherence values and mappings; never copy the prose to `spec_lock.md`. Do not add a questionnaire, internal controls, or fixed template-use options.**Three-stage boundary**: An installed template changes the content of Stage 2, never the confirmation sequence. Run Stage 1 → Stage 2 → Stage 3 in order in both Confirm UI and chat fallback; do not skip a stage or treat template inspection as user confirmation. On browser timeout, return to the same stage in chat.@@ -52,24 +54,26 @@ Write only the derived values to `spec_lock.md pptx_structure`; omit `template_a## 2. Scenario Fit and Inherited Design-**Mandatory — decide from the §1 inspection**: For an installed `kind: deck`, compare the retained Template Overview with the confirmed audience, intent, outcome, delivery context, artifact afterlife, and source obligations. Compare the retained Page Roster/relevant SVG prototypes with required narrative roles, content shapes, slots, and capacity. Reopen a resource only when its path + SHA changed. The template describes what exists; it never overrides the current project or own required/optional/repeatable or fixed/replaceable/example-only policy. For `kind: layout`, compare only structural roles, slots, and capacity.+**Mandatory — decide from the §1 inspection**: For an installed `kind: deck`, compare the retained Template Overview with the confirmed audience, intent, outcome, delivery context, artifact afterlife, and source obligations. Compare the retained Page Roster/relevant SVG prototypes with required narrative roles, content shapes, slots, and capacity. Reopen a resource only when its path + SHA changed. The template describes what exists; it never overrides the current project or own required/optional/repeatable or fixed/replaceable/example-only policy. For `kind: layout`, compare only structural roles, slots, and capacity. For an active Style segment, compare its communication method with the current contract and its composition requirements with any selected Layout/Deck structure. Surface a material incompatibility; never silently weaken one segment to make it fit.| Internal scope | Appropriate when ||---|---|| `mirror` | The artifact repeats a known form; literal appearance and text topology are requirements; new content fits existing roles and slots. || `layout` | The structural system and brand continue, but the communication outcome requires reflow, new emphasis, or an adaptive Layout. |-| `style` | Only visual identity is reusable, or the outcome requires a different sequence, density, or composition system. |+| `style` | Only communication/design direction is reused, a Style-only workspace is active, or the outcome requires a different sequence, density, or composition system. |When the communication contract conflicts with the workspace, choose and state the best-fit application plan in the complete Stage-2 solution. Surface the mismatch only when it materially limits the result; do not respond with a mode questionnaire. Template capability constrains what is legal; scenario fit decides what is useful.> Internal note: `content_divergence` controls source reorganization; the AI-derived `template_reuse_scope` records the reused layer; `template_adherence` records whether a structured plan keeps or extends existing Layout identities.-**Template design precedence**: User overrides win. Otherwise template colors and title/body stacks are fixed anchors, not industry defaults. Each of ≥3 directions carries six palette roles and complete fonts: repeat fixed values with `typography.fixed: true`; vary only template-open roles. Bundles differ overall; fonts may repeat. Keep declared icon and image constraints.+**Template design precedence**: Explicit current user instructions and final confirmation win. Brand identity overrides Deck identity, and either is fixed starting truth rather than an industry default. Style owns Direction / method only: its color, typography, icon, and image values are candidate defaults and never override resolved Brand/Deck identity or become official facts. Preferred Mode / Visual Style values seed Stage 2; the Style overlay must resolve into the final single `mode` and `visual_style` lock rather than create a parallel narrative or aesthetic authority. Style takes this segment ahead of ordinary Stage-2 defaults; actual Deck prototypes and Signature facts remain compatibility constraints, not a second method owner. Each of ≥3 directions still carries six palette roles and complete fonts: repeat fixed Brand/Deck values with `typography.fixed: true`; adapt Style candidates to that identity and vary only open roles. Keep resolved icon and image constraints. Style Review Focus never activates [`visual-review`](../workflows/stages/visual-review.md); only an explicit user request does.---## 3. Structured Lock Planning+For Style-only or Style + Brand, write `pptx_structure.mode: flat` plus `template_reuse_scope: style`; omit `template_adherence` and every structured mapping section. When Style is fused with Layout or Deck, it changes only Direction / method and does not change the non-Style capability label or force flat/structured routing. Derive reuse scope from the selected Layout/Deck application plan; a literal `mirror` plan is compatible only when the Style segment requires no visual or topology change.+For `mirror` / `layout`, write `pptx_structure.mode: structured` plus `template_adherence: strict|adaptive`; mirror always writes `strict`. Do not write legacy `baseline`, `template`, `preserve`, `layout_strategy`, or Layout-kind rows.- **Master roster**: Write one `pptx_masters` row per Master as `<master_key>: <picker name>` and copy the workspace's prototype roster. Keys use 1–64 ASCII letters, digits, dots, underscores, or hyphens, start with a letter/digit, and contain no spaces; human-readable spaces belong only in the picker name. Master visuals are root-level atomic elements and may never be `<g>`.diff --git a/skills/ppt-master/references/template-designer.md b/skills/ppt-master/references/template-designer.mdindex 801276e4..502654f6 100644--- a/skills/ppt-master/references/template-designer.md+++ b/skills/ppt-master/references/template-designer.md@@ -589,13 +589,15 @@ 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 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):+**Example library structure** (query the appropriate kind's index — `templates/brands/brands_index.json` for identity, `templates/styles/styles_index.json` for roster-free direction/method, `templates/layouts/layouts_index.json` for brand-neutral structure, and `templates/decks/decks_index.json` for recurring applications with integrated identity/structure):```templates/├── brands/│ ├── anthropic/ # Anthropic brand identity (logo + colors + typography)│ └── google/ # Google brand identity+├── styles/+│ └── <style_id>/ # Communication method and design direction; no SVG roster├── layouts/│ └── presentation_core/ # General structure system (no identity)└── decks/diff --git a/skills/ppt-master/references/visual-review.md b/skills/ppt-master/references/visual-review.mdindex acdc58f5..e5ed21cc 100644--- a/skills/ppt-master/references/visual-review.md+++ b/skills/ppt-master/references/visual-review.md@@ -25,9 +25,12 @@ Each review subagent processes a **batch** of pages (see §6.1 for batch sizing)2. **Path to this rubric file**3. **`<project>/design_spec.md`** (read-only) — §IX outline is the source of truth for "what should this page deliver"4. **`<project>/spec_lock.md`** (read-only) — brand-locked values-5. **`<project>/.review/`** (writable) — where backups and findings JSON go+5. **Style Review Focus excerpt** (conditional, read-only) — supplied by the orchestrator only when `<project>/templates/design_spec.md` contains an active Style segment; it retains the source path and exact §VII wording+6. **`<project>/.review/`** (writable) — where backups and findings JSON go-The subagent reads inputs 2–4 **once** at the start of its turn, then iterates over the page batch sequentially (one page at a time): apply the rubric → write `<project>/.review/<page>.json` → move on. This is the core token-saving move — three fixed documents are read N/K times instead of N times.+The subagent reads inputs 2–5 **once** at the start of its turn (input 5 may be absent), then iterates over the page batch sequentially (one page at a time): apply the rubric → apply any Style supplement → write `<project>/.review/<page>.json` → move on. This is the core token-saving move — fixed context is read N/K times instead of N times.++Style Review Focus is supplemental acceptance context, not a second rubric. It cannot create new Hard rules, weaken §§1–3, or authorize content, identity, or structural edits. Record a clearly unmet focus item as `rule: "STYLE"`: apply a fix only when the existing rubric already permits that atomic edit; otherwise add a `needs_human_items` entry with a concise suggested fix.## §1 Hard rules (fix every hit)diff --git a/skills/ppt-master/scripts/README.md b/skills/ppt-master/scripts/README.mdindex b7abbcea..a9ba9e5d 100644--- a/skills/ppt-master/scripts/README.md+++ b/skills/ppt-master/scripts/README.md@@ -272,13 +272,13 @@ embedded.For SVG-authoring routes, `svg_output/` is the complete visible page-design source: every exported text, image, shape, background, and template-derived layout element is present in the page SVG or explicitly referenced by it. Export may translate represented content into Master/Layout/Slide parts or native objects, but it does not retrieve missing visible content from templates or planning files. Speaker notes, animation, narration, transitions, `template-fill-pptx`, and `native-enhance-pptx` remain separately owned capabilities.-Native `svg_to_pptx.py` release export reads the project's explicit structure mode. Free-design and brand-only projects use `flat`, omit Master/Layout mappings and SVG structure metadata, keep every represented object Slide-local, and materialize one clean project-owned Master plus one Blank Layout from the current color/typography lock. Stock content placeholders and unused built-in Layouts are removed; only the standard date/footer/slide-number capability hooks remain. Deck/layout template projects use `structured`: each project supplies unique Master/Layout definitions and one Layout assignment per generated page before SVG generation, and every SVG root repeats its assigned identity. A template-backed definition may remain unused and still register without a published carrier slide. Fixed Master/Layout visuals are direct semantic atoms; ordinary groups are invalid there, while one validated compact authored-preset `<g>` is the sole group exception because it compiles to one native shape. Reusable slots are top-level groups with positive design-zone bounds plus one compatible carrier. Composite `object` regions use explicit proxy binding, and zero-slot Layouts are valid.+Native `svg_to_pptx.py` release export reads the project's explicit structure mode. Free-design, Brand-only, Style-only, and other `template_reuse_scope: style` projects use `flat`, omit Master/Layout mappings and SVG structure metadata, keep every represented object Slide-local, and materialize one clean project-owned Master plus one Blank Layout from the current color/typography lock. Stock content placeholders and unused built-in Layouts are removed; only the standard date/footer/slide-number capability hooks remain. A Deck/Layout application uses `structured` only when Strategist derives `template_reuse_scope: mirror|layout`: each project supplies unique Master/Layout definitions and one Layout assignment per generated page before SVG generation, and every SVG root repeats its assigned identity. A template-backed definition may remain unused and still register without a published carrier slide. Fixed Master/Layout visuals are direct semantic atoms; ordinary groups are invalid there, while one validated compact authored-preset `<g>` is the sole group exception because it compiles to one native shape. Reusable slots are top-level groups with positive design-zone bounds plus one compatible carrier. Composite `object` regions use explicit proxy binding, and zero-slot Layouts are valid.-Structured template export compiles only the declared structure, maps locked typography/colors into PowerPoint defaults, creates the named Master/Layout parts, and reads the package back before publication. It never clusters pages, promotes repeated chrome heuristically, or invents placeholders. Flat export is the normal free-design/brand-only route: it creates only the clean project-owned shell and performs no promotion or deduplication of Slide content.+Structured template export compiles only the declared structure, maps locked typography/colors into PowerPoint defaults, creates the named Master/Layout parts, and reads the package back before publication. It never clusters pages, promotes repeated chrome heuristically, or invents placeholders. Flat export is the normal free-design/Brand-only/Style-only/style-scope route: it creates only the clean project-owned shell and performs no promotion or deduplication of Slide content.Template `page_layouts` records authoring-input provenance, `pptx_masters` / `pptx_layouts` own unique reusable definitions, and `page_pptx_layouts` owns page assignment. Strict preserves its Master/Layout/slot contract; adaptive retains its Master and may use a new Layout key only when fixed Layout atoms or slot topology/bounds change. `standard` / `fidelity` author new SVGs and a new Master/Layout/slot contract. `mirror` materializes a new workspace from the complete validated source identity graph—including unused Layout definitions—without semantic synthesis or gap filling, while mechanically expanding fixed-layer group wrappers into the direct atoms required by the structured contract.-Legacy structured/template contracts using `baseline`, `template`, `preserve`, `layout_strategy`, `data-pptx-layout-kind`, `distilled`/`utility`, direct atomic placeholders, or incomplete root Master identity must be replaced by a new workspace created through [`create-template`](../workflows/create-template.md). Generate new structured SVG pages from that workspace; do not upgrade the existing PPTX/SVG in place. Explicit flat free-design/brand-only projects intentionally omit root Master identity.+Legacy structured/template contracts using `baseline`, `template`, `preserve`, `layout_strategy`, `data-pptx-layout-kind`, `distilled`/`utility`, direct atomic placeholders, or incomplete root Master identity must be replaced by a new workspace created through [`create-template`](../workflows/create-template.md). Generate new structured SVG pages from that workspace; do not upgrade the existing PPTX/SVG in place. Explicit flat free-design/Brand-only/Style-only projects intentionally omit root Master identity.`pptx_to_svg.py` annotates verified text-grid tables and conservative chart data with `data-pptx-replace-with` beside the visible SVG fallback and places the payload in `<metadata type="application/json">`; the parent claim selects the chart or table schema. Imported table/chart groups under this contract carry `data-pptx-import-source="pptx"`, whether active or fallback-only. Table import covers exact physical row/grid topology, canonical rectangular merges, safe solid/no-fill per-side borders, plain multi-paragraph cells, and a closed run-rich paragraph schema. Each rich run requires `text` and may use only `bold`, `italic`, `underline`, `strike`, `color`, `font_size`, one `font_family`, `lang`, and `alt_lang`. A merge must use the exact `rowSpan` / `gridSpan` / `hMerge` / `vMerge` physical topology with empty merge slaves. Presentation-only source run XML without a non-empty `effectLst` / `effectDag` normalizes; a table-cell run effect disables native replacement and adds a blocking effect diagnostic. Relationship-bearing text, extensions, line breaks, fields, tabs, bullets, broken text topology, unsafe border XML, non-solid fills, and other merge encodings remain fallback-only. For table style `{5C22544A-7EE6-4342-B048-85BDC9FD1C3A}`, the normalized SVG fallback resolves `wholeTbl`, `firstRow`, horizontal banding, theme colors/fonts, and direct cell/run overrides; other built-in/custom style families are not implied.diff --git a/skills/ppt-master/scripts/register_template.py b/skills/ppt-master/scripts/register_template.pyindex a3f726ac..b6d3ed1a 100644--- a/skills/ppt-master/scripts/register_template.py+++ b/skills/ppt-master/scripts/register_template.py@@ -1,25 +1,28 @@#!/usr/bin/env python3-"""Register a brand / layout / deck template into the global template index.+"""Register a brand / style / layout / deck template in the global index.-Three kinds, three workspace roots, three index files. The shared model lives+Four kinds, four workspace roots, four index files. The shared model livesin ``templates/README.md``; each kind's schema lives in its directory README:| --kind | Workspace roots | Index file ||---------|-------------------------|-------------------------------|| brand | ``templates/brands/`` | ``brands_index.json`` |+| style | ``templates/styles/`` | ``styles_index.json`` || layout | ``templates/layouts/`` | ``layouts_index.json`` || deck | ``templates/decks/`` | ``decks_index.json`` |Current workspaces keep ``design_spec.md`` and any SVG roster under``<workspace>/templates/``. Assets live in optional ``images/`` / ``icons/``directories. Explicitly generated review artifacts go to the optional, ignored-``exports/`` directory. Legacy flat roots remain readable.+``exports/`` directory. Legacy flat roots remain readable for Brand/Layout/Deck;+Style uses only the current nested one-file contract.Index entry schemas (the JSON file is the single source of truth — READMEfiles describe the kind and usage in prose but do **not** enumerate templates;discovery happens exclusively against the index file):- brand: ``{ summary, primary_color }``+- style: ``{ summary, keywords[] }``- layout: ``{ summary, canvas_format, page_count, page_types[] }``- deck: ``{ summary, canvas_format, page_count, primary_color }``@@ -28,15 +31,17 @@ Usage::python3 scripts/register_template.py <id> --kind deck # default kind=deckpython3 scripts/register_template.py <id> --kind layoutpython3 scripts/register_template.py <id> --kind brand+ python3 scripts/register_template.py <id> --kind stylepython3 scripts/register_template.py --rebuild-all --kind deckpython3 scripts/register_template.py <id> --dry-run``--rebuild-all`` rebuilds every entry from scratch within the chosen kind;recommended for repairing index drift across many templates at once.-Project-scoped Brand workspaces are validated, not registered, through-``svg_quality_checker.py <workspace>/templates --template-mode``. That entry-reuses :func:`validate_brand_workspace`, so the Brand schema has one authority.+Project-scoped Brand and Style workspaces are validated, not registered,+through ``svg_quality_checker.py <workspace>/templates --template-mode``. That+entry reuses :func:`validate_brand_workspace` or+:func:`validate_style_workspace`, so each schema has one authority."""from __future__ import annotations@@ -73,6 +78,12 @@ KIND_CONFIG = {"id_key": "brand_id","needs_svg_roster": False,},+ "style": {+ "dir": TEMPLATES_DIR / "styles",+ "index": TEMPLATES_DIR / "styles" / "styles_index.json",+ "id_key": "style_id",+ "needs_svg_roster": False,+ },"layout": {"dir": TEMPLATES_DIR / "layouts","index": TEMPLATES_DIR / "layouts" / "layouts_index.json",@@ -109,7 +120,130 @@ _BRAND_PROVENANCE_VALUES = {"fact", "approx", "user"}_BRAND_ASSET_REF_RE = re.compile(r"`((?:\.\./)+(?:images|icons)/[^`]+)`")+_STYLE_REQUIRED_SECTIONS = (+ ("I", "Style Overview"),+ ("II", "Communication Method"),+ ("III", "Page Role Vocabulary"),+ ("IV", "Evidence & Data Expression"),+ ("V", "Visual System Defaults"),+ ("VI", "Image & Icon Direction"),+ ("VII", "Review Focus"),+)+_STYLE_FORBIDDEN_SECTIONS = (+ "Brand Overview",+ "Template Overview",+ "Color Scheme",+ "Typography",+ "Logo",+ "Voice & Tone",+ "Icon Style",+ "Assets",+ "Signature Design Elements",+ "Page Roster",+ "Placeholder Overrides",+)+_STYLE_REQUIRED_FIELDS = {+ "I. Style Overview": (+ "Style Name",+ "Best Fit",+ "Reusable Intent",+ "Sources",+ ),+ "II. Communication Method": (+ "Argument Flow",+ "Page Message Discipline",+ "Claim Discipline",+ ),+ "IV. Evidence & Data Expression": (+ "Argument Trace",+ "Charts",+ "Tables",+ "Sources",+ "Native Editability",+ ),+ "V. Visual System Defaults": (+ "Composition",+ "Density",+ "Decoration",+ "Color Behavior",+ "Typography Character",+ ),+ "VI. Image & Icon Direction": (+ "Image Usage",+ "Image Treatment",+ "Icon Treatment",+ ),+}+_STYLE_CUSTOM_FIELDS = (+ (+ "II. Communication Method",+ "Preferred Mode",+ "Mode Behavior",+ "Mode References",+ SKILL_DIR / "references" / "modes",+ ),+ (+ "V. Visual System Defaults",+ "Preferred Visual Style",+ "Visual Style Behavior",+ "Visual Style References",+ SKILL_DIR / "references" / "visual-styles",+ ),+ (+ "VI. Image & Icon Direction",+ "Preferred Image Rendering",+ "Image Rendering Behavior",+ "Image Rendering References",+ SKILL_DIR / "references" / "image-renderings",+ ),+)+_STYLE_FORBIDDEN_FIELDS = (+ "Brand Overview",+ "Template Overview",+ "Color Scheme",+ "Typography",+ "Signature Design Elements",+ "Page Roster",+ "Placeholder Overrides",+ "Target Audience",+ "Communication Objective",+ "Desired Outcome",+ "Core Message",+ "Delivery Context",+ "Artifact Afterlife",+ "Application Context",+ "Content Outline",+ "Page Count",+ "Page Types",+ "Page Order",+ "Page Sequence",+ "Canvas Format",+ "Canvas Width",+ "Canvas Height",+ "Canvas ViewBox",+ "Replication Mode",+ "Native Structure Mode",+ "Master",+ "Layout",+ "Placeholders",+ "Page Assignment",+ "Icon Inventory",+ "Image Resources",+ "Primary Color",+ "Logo",+ "Voice & Tone",+ "Icon Style",+ "Assets",+)+_STYLE_ALLOWED_FRONTMATTER_FIELDS = frozenset({+ "style_id",+ "kind",+ "summary",+ "keywords",+})+_STYLE_REVIEW_TRIGGER_MARKER = "<!-- visual-review-trigger: explicit-user-only -->"_HEX_COLOR_RE = re.compile(r"#[0-9A-Fa-f]{6}")+_PORTABLE_STYLE_ID_RE = re.compile(r"^\w[\w.-]*$")# ---------------------------------------------------------------------------@@ -240,6 +374,53 @@ def _numbered_section(body: str, title: str) -> str | None:return match.group(0) if match else None+def _markdown_subsection(body: str, title: str) -> str | None:+ match = re.search(+ rf"^###\s+{re.escape(title)}\s*$.*?(?=^#{{2,3}}\s+|\Z)",+ body,+ re.MULTILINE | re.DOTALL,+ )+ return match.group(0) if match else None+++def _markdown_table_rows(section: str) -> list[list[str]]:+ rows: list[list[str]] = []+ for line in section.splitlines():+ if not line.lstrip().startswith("|"):+ continue+ cells = [cell.strip() for cell in line.strip().strip("|").split("|")]+ if not cells or all(re.fullmatch(r":?-{3,}:?", cell) for cell in cells):+ continue+ rows.append(cells)+ return rows+++def _style_value_is_substantive(value: str | None) -> bool:+ if value is None:+ return False+ cleaned = _clean_field_value(value)+ if not cleaned or re.fullmatch(r"<[^>]+>", cleaned):+ return False+ return cleaned.casefold() not in {"tbd", "todo", "n/a", "none", "-", "—"}+++def _style_field_is_declared(body: str, label: str) -> bool:+ escaped = re.escape(label)+ return bool(+ re.search(+ rf"^\s*(?:>\s*)?(?:[-*]\s*)?"+ rf"\*{{0,2}}{escaped}\*{{0,2}}\s*[::]",+ body,+ re.MULTILINE | re.IGNORECASE,+ )+ or re.search(+ rf"^\|\s*\*{{0,2}}{escaped}\*{{0,2}}\s*\|",+ body,+ re.MULTILINE | re.IGNORECASE,+ )+ )++def _validate_brand_spec(expected_template_id: str | None,template_root: Path,@@ -376,6 +557,327 @@ def _validate_brand_spec(raise SpecParseError(f"invalid brand specification:\n{details}")+def _validate_style_spec(+ expected_template_id: str | None,+ template_root: Path,+ template_dir: Path,+ frontmatter: dict,+ body: str,+) -> None:+ """Reject Style workspaces outside the roster-free method contract."""+ errors: list[str] = []++ raw_style_id = frontmatter.get("style_id")+ declared_id = raw_style_id.strip() if isinstance(raw_style_id, str) else ""+ if not declared_id:+ errors.append("frontmatter style_id must be a non-empty string")+ else:+ if (+ _PORTABLE_STYLE_ID_RE.fullmatch(declared_id) is None+ or declared_id in {".", ".."}+ or declared_id.endswith(".")+ ):+ errors.append(+ "frontmatter style_id must be a filesystem-safe portable slug"+ )+ if (+ expected_template_id is not None+ and declared_id != expected_template_id+ ):+ errors.append(+ "frontmatter style_id must match directory "+ f"{expected_template_id!r}, got {declared_id!r}"+ )++ raw_kind = frontmatter.get("kind")+ declared_kind = raw_kind.strip() if isinstance(raw_kind, str) else ""+ if declared_kind != "style":+ errors.append(+ "frontmatter kind must be 'style', "+ f"got {declared_kind!r}"+ )++ raw_summary = frontmatter.get("summary")+ if not isinstance(raw_summary, str) or not _style_value_is_substantive(+ raw_summary+ ):+ errors.append("frontmatter summary must be a non-empty string")++ non_string_fields = [key for key in frontmatter if not isinstance(key, str)]+ if non_string_fields:+ errors.append("style frontmatter field names must be strings")+ unexpected_fields = sorted(+ key+ for key in frontmatter+ if isinstance(key, str) and key not in _STYLE_ALLOWED_FRONTMATTER_FIELDS+ )+ if unexpected_fields:+ errors.append(+ "style frontmatter contains unsupported field(s): "+ + ", ".join(unexpected_fields)+ )++ keywords = frontmatter.get("keywords")+ if (+ not isinstance(keywords, list)+ or not 3 <= len(keywords) <= 5+ or not all(+ isinstance(item, str) and _style_value_is_substantive(item)+ for item in keywords+ )+ ):+ errors.append(+ "frontmatter keywords must contain 3-5 non-empty strings"+ )+ elif len({item.strip().casefold() for item in keywords}) != len(keywords):+ errors.append("frontmatter keywords must be unique")++ unexpected_source_entries = sorted(+ path.relative_to(template_dir).as_posix()+ + ("/" if path.is_dir() else "")+ for path in template_dir.rglob("*")+ if path.relative_to(template_dir).as_posix() != "design_spec.md"+ )+ if unexpected_source_entries:+ errors.append(+ "style workspaces must contain only templates/design_spec.md; "+ "unexpected template entry(s): "+ + ", ".join(unexpected_source_entries)+ )++ if expected_template_id is not None:+ unexpected_workspace_entries = sorted(+ path.relative_to(template_root).as_posix()+ + ("/" if path.is_dir() else "")+ for path in template_root.rglob("*")+ if path.relative_to(template_root).as_posix()+ not in {"templates", "templates/design_spec.md"}+ )+ if unexpected_workspace_entries:+ errors.append(+ "library Style workspaces must contain only "+ "templates/design_spec.md; unexpected workspace entry(s): "+ + ", ".join(unexpected_workspace_entries)+ )++ h1_headings = re.findall(r"^#\s+(.+?)\s*$", body, re.MULTILINE)+ if len(h1_headings) != 1:+ errors.append(+ "style body must contain exactly one document-title H1; got "+ f"{len(h1_headings)}"+ )++ expected_headings = [+ f"{numeral}. {title}" for numeral, title in _STYLE_REQUIRED_SECTIONS+ ]+ actual_headings = re.findall(r"^##\s+(.+?)\s*$", body, re.MULTILINE)+ if actual_headings != expected_headings:+ errors.append(+ "style body must contain exactly the required I-VII sections in "+ "order; got: " + (", ".join(actual_headings) or "none")+ )++ nested_headings = re.findall(+ r"^(#{3,6})\s+(.+?)\s*$",+ body,+ re.MULTILINE,+ )+ unexpected_nested_headings = [+ f"{marks} {title}"+ for marks, title in nested_headings+ if len(marks) != 3+ or title not in {"Fallback Color Scheme", "Fallback Typography"}+ ]+ if unexpected_nested_headings:+ errors.append(+ "style body contains unsupported nested heading(s): "+ + ", ".join(unexpected_nested_headings)+ )+ allowed_h3 = [title for marks, title in nested_headings if len(marks) == 3]+ if len(allowed_h3) != len(set(allowed_h3)):+ errors.append("style fallback subsections must not be repeated")++ for title in _STYLE_FORBIDDEN_SECTIONS:+ if re.search(+ rf"^#{{1,6}}\s+(?:[IVX]+\.\s+)?{re.escape(title)}\s*$",+ body,+ re.MULTILINE,+ ):+ errors.append(f"style scope must not declare section: {title}")++ for section_title, labels in _STYLE_REQUIRED_FIELDS.items():+ section_name = section_title.split(". ", 1)[1]+ if _numbered_section(body, section_name) is None:+ continue+ for label in labels:+ value = _extract_section_field(body, section_title, [label])+ if not _style_value_is_substantive(value):+ errors.append(+ f"{section_title} must declare a non-empty {label} field"+ )++ role_section = _numbered_section(body, "Page Role Vocabulary") or ""+ role_rows = [+ row+ for row in _markdown_table_rows(role_section)+ if row and row[0].casefold() != "role"+ ]+ if not any(+ len(row) >= 4+ and all(_style_value_is_substantive(cell) for cell in row[:4])+ for row in role_rows+ ):+ errors.append(+ "III. Page Role Vocabulary must contain at least one complete "+ "four-column role row"+ )++ for (+ section_title,+ preferred_label,+ behavior_label,+ references_label,+ catalog_dir,+ ) in _STYLE_CUSTOM_FIELDS:+ preferred = _extract_section_field(+ body,+ section_title,+ [preferred_label],+ )+ behavior = _extract_section_field(+ body,+ section_title,+ [behavior_label],+ )+ references = _extract_section_field(+ body,+ section_title,+ [references_label],+ )+ preferred_text = _clean_field_value(preferred or "")+ catalog_ids = {+ path.stem+ for path in catalog_dir.glob("*.md")+ if not path.stem.startswith("_")+ }+ is_custom = bool(+ re.match(r"^custom(?:\b|\s*[:—-])", preferred_text, re.IGNORECASE)+ )+ if is_custom and not _style_value_is_substantive(behavior):+ errors.append(+ f"{behavior_label} is required when {preferred_label} is custom"+ )+ if not is_custom and _style_value_is_substantive(behavior):+ errors.append(+ f"{behavior_label} is allowed only when {preferred_label} is custom"+ )+ if not is_custom and _style_value_is_substantive(references):+ errors.append(+ f"{references_label} is allowed only when "+ f"{preferred_label} is custom"+ )+ if (+ _style_value_is_substantive(preferred)+ and not is_custom+ and preferred_text not in catalog_ids+ ):+ errors.append(+ f"{preferred_label} references unknown catalog id "+ f"{preferred_text!r}"+ )+ if is_custom and _style_value_is_substantive(references):+ catalog_references = [+ _clean_field_value(item)+ for item in (references or "").split(",")+ ]+ if any(not item for item in catalog_references):+ errors.append(+ f"{references_label} must be a comma-separated list of "+ "catalog ids"+ )+ duplicates = sorted(+ item+ for item in set(catalog_references)+ if catalog_references.count(item) > 1+ )+ if duplicates:+ errors.append(+ f"{references_label} repeats catalog id(s): "+ + ", ".join(duplicates)+ )+ unknown_references = sorted(+ item+ for item in set(catalog_references)+ if item == "custom" or item not in catalog_ids+ )+ if unknown_references:+ errors.append(+ f"{references_label} references unknown catalog id(s): "+ + ", ".join(unknown_references)+ )++ visual_section = _numbered_section(body, "Visual System Defaults") or ""+ fallback_colors = _markdown_subsection(body, "Fallback Color Scheme")+ if fallback_colors is not None:+ if "### Fallback Color Scheme" not in visual_section:+ errors.append("Fallback Color Scheme must appear under section V")+ color_rows = [+ row+ for row in _markdown_table_rows(fallback_colors)+ if row and row[0].casefold() != "role"+ ]+ if not color_rows:+ errors.append("Fallback Color Scheme must contain at least one row")+ for row in color_rows:+ if (+ len(row) < 3+ or not _style_value_is_substantive(row[0])+ or _HEX_COLOR_RE.fullmatch(row[1].strip("` ")) is None+ or not _style_value_is_substantive(row[2])+ ):+ errors.append(+ "Fallback Color Scheme rows must be Role | #RRGGBB | Purpose"+ )+ break++ fallback_typography = _markdown_subsection(body, "Fallback Typography")+ if fallback_typography is not None:+ if "### Fallback Typography" not in visual_section:+ errors.append("Fallback Typography must appear under section V")+ typography_rows = [+ row+ for row in _markdown_table_rows(fallback_typography)+ if row and row[0].casefold() != "role"+ ]+ if not any(+ len(row) >= 4+ and all(_style_value_is_substantive(cell) for cell in row[:4])+ for row in typography_rows+ ):+ errors.append(+ "Fallback Typography must contain at least one complete "+ "four-column row"+ )++ review_section = _numbered_section(body, "Review Focus") or ""+ if review_section.count(_STYLE_REVIEW_TRIGGER_MARKER) != 1:+ errors.append(+ "VII. Review Focus must contain exactly one "+ f"{_STYLE_REVIEW_TRIGGER_MARKER} marker"+ )+ review_items = re.findall(r"^[-*]\s+(.+?)\s*$", review_section, re.MULTILINE)+ if not any(_style_value_is_substantive(item) for item in review_items):+ errors.append("VII. Review Focus must contain at least one check")++ for label in _STYLE_FORBIDDEN_FIELDS:+ if _style_field_is_declared(body, label):+ errors.append(f"style scope must not declare field: {label}")++ if errors:+ details = "\n".join(f" - {error}" for error in errors)+ raise SpecParseError(f"invalid style specification:\n{details}")++def _validate_svg_template_spec(kind: str,template_id: str,@@ -522,6 +1024,11 @@ def _extract_entry("""Build the index entry + extras for a single template."""template_root = template_dirtemplate_dir = _template_content_dir(template_root)+ if kind == "style" and template_dir == template_root:+ raise SpecParseError(+ "Style workspaces require templates/design_spec.md; "+ "legacy-flat design_spec.md is not supported"+ )spec_path = template_dir / "design_spec.md"frontmatter, body = _read_spec(spec_path)@@ -534,7 +1041,8 @@ def _extract_entry(f"expected kind={kind!r} — use --kind {declared_kind} instead")- summary = (fm.get("summary") or "").strip()+ raw_summary = fm.get("summary")+ summary = raw_summary.strip() if isinstance(raw_summary, str) else ""if not summary:section_title = ("I. Brand Overview" if kind == "brand" else "I. Template Overview"@@ -564,6 +1072,18 @@ def _extract_entry(summary=summary,primary_color=str(primary_color),)+ elif kind == "style":+ _validate_style_spec(+ template_id,+ template_root,+ template_dir,+ fm,+ body,+ )+ entry = OrderedDict(+ summary=summary,+ keywords=[item.strip() for item in fm["keywords"]],+ )elif kind == "layout":if template_id is None:raise SpecParseError("layout validation requires an expected layout_id")@@ -627,6 +1147,22 @@ def validate_brand_workspace(template_root: str | Path) -> dict:return _extract_entry("brand", None, Path(template_root))+def validate_style_workspace(template_root: str | Path) -> dict:+ """Validate a portable Style workspace without registering it.++ Global library roots also enforce directory identity and the one-file+ package boundary. Project roots keep their unrelated initialized-project+ scaffolding out of the Style contract.+ """+ root = Path(template_root)+ expected_id = (+ root.name+ if root.resolve().parent == KIND_CONFIG["style"]["dir"].resolve()+ else None+ )+ return _extract_entry("style", expected_id, root)++# ---------------------------------------------------------------------------# Index / README writers# ---------------------------------------------------------------------------@@ -664,8 +1200,18 @@ def _enumerate_ids(kind: str) -> list[str]:def _print_completion_card(kind: str, template_id: str, entry: dict, extras: dict) -> None:- pretty_kind = {"layout": "Layout", "deck": "Deck", "brand": "Brand"}[kind]- dir_name = {"layout": "layouts", "deck": "decks", "brand": "brands"}[kind]+ pretty_kind = {+ "layout": "Layout",+ "deck": "Deck",+ "brand": "Brand",+ "style": "Style",+ }[kind]+ dir_name = {+ "layout": "layouts",+ "deck": "decks",+ "brand": "brands",+ "style": "styles",+ }[kind]print()print(f"## {pretty_kind} Registration Complete")print()@@ -682,7 +1228,7 @@ def _print_completion_card(kind: str, template_id: str, entry: dict, extras: dicprint(f"**Summary**: {entry.get('summary') or '—'}")print("**Index Registration**: Done")print()- if kind != "brand":+ if KIND_CONFIG[kind]["needs_svg_roster"]:pages = extras.get("pages") or []page_prefix = extras.get("page_prefix") or ""preview = extras.get("preview") or ""@@ -708,7 +1254,10 @@ def _print_completion_card(kind: str, template_id: str, entry: dict, extras: dicdef main() -> int:require_skill_integrity()parser = argparse.ArgumentParser(- description="Register / refresh templates (brand / layout / deck) in the index."+ description=(+ "Register / refresh templates (brand / style / layout / deck) "+ "in the index."+ ))parser.add_argument("template_id", nargs="?",diff --git a/skills/ppt-master/scripts/svg_quality/checker.py b/skills/ppt-master/scripts/svg_quality/checker.pyindex 9123ca00..8d389421 100644--- a/skills/ppt-master/scripts/svg_quality/checker.py+++ b/skills/ppt-master/scripts/svg_quality/checker.py@@ -771,30 +771,34 @@ SPARSE_UNDECLARED_FONT_SIZE_MAX_OCCURRENCES = 2IMAGE_DOWNSIZE_WARN_RATIO = 4.0IMAGE_DOWNSIZE_WARN_MIN_BYTES = 1024 * 1024-def _design_spec_is_brand(spec_path: Path) -> bool:- """Return True when a design_spec.md frontmatter declares ``kind: brand``.+def _design_spec_kind(spec_path: Path) -> str | None:+ """Return a roster-free ``kind`` declared in design_spec.md frontmatter.Lightweight detector that does not require PyYAML — scans only the- frontmatter block (``---`` delimited) for a ``kind:`` line whose value- contains ``brand``. Used by ``check_directory`` to select Brand schema- validation instead of SVG-roster validation.+ frontmatter block (``---`` delimited). Used by ``check_directory`` to+ select schema-only validation for Brand and Style workspaces instead of+ SVG-roster validation."""try:text = spec_path.read_text(encoding='utf-8')except OSError:- return False+ return Noneif not text.startswith('---\n'):- return False+ return Noneend = text.find('\n---\n', 4)if end == -1:- return False+ return Nonefm_block = text[4:end]for line in fm_block.splitlines():stripped = line.strip()- if stripped.startswith('kind:'):- value = stripped.split(':', 1)[1].strip().strip('"\'')- return value == 'brand'- return False+ match = re.fullmatch(+ r'''kind\s*:\s*(?:(['"])(brand|style)\1|(brand|style))'''+ r'''(?:\s+#.*)?\s*''',+ stripped,+ )+ if match:+ return match.group(2) or match.group(3)+ return Nonedef _declared_template_structure_mode(target_path: Path) -> str | None:@@ -1038,7 +1042,7 @@ class SVGQualityChecker:# template_mode=True). Each entry is (severity, kind, message) where# severity is 'error' or 'warning'. Printed in print_summary.self._template_issues: List[Tuple[str, str, str]] = []- self._brand_template_checked = False+ self._spec_only_template_kind: str | None = Noneself._animation_issues: List[Tuple[str, str]] = []self._illustration_issues: List[Tuple[str, str, str]] = []self._communication_trace_issues: List[Tuple[str, str]] = []@@ -4719,20 +4723,23 @@ class SVGQualityChecker:self.issue_types['Input issues'] += 1return []- # Brand-only workspaces have no SVG roster. Validate their portable- # identity schema through the same authority used by library+ # Brand and Style workspaces have no SVG roster. Validate their+ # portable contracts through the same authority used by library# registration, while keeping project scope independent of global# indexes and directory names.if self.template_mode and dir_path.is_dir():nested_spec = dir_path / 'templates' / 'design_spec.md'spec = nested_spec if nested_spec.is_file() else dir_path / 'design_spec.md'- if spec.exists() and _design_spec_is_brand(spec):- self._brand_template_checked = True+ spec_kind = _design_spec_kind(spec) if spec.exists() else None+ if spec_kind in {'brand', 'style'}:+ self._spec_only_template_kind = spec_kindself.summary['total'] += 1- brand_valid = True+ spec_valid = True+ pretty_kind = spec_kind.title()print(- f"[INFO] Brand directory detected (kind: brand) — "- f"validating design_spec.md and referenced assets."+ f"[INFO] {pretty_kind} directory detected "+ f"(kind: {spec_kind}) — "+ f"validating its portable workspace contract.")workspace_root = (spec.parent.parent@@ -4743,23 +4750,28 @@ class SVGQualityChecker:from register_template import (SpecParseError,validate_brand_workspace,+ validate_style_workspace,)- validate_brand_workspace(workspace_root)+ validator = {+ 'brand': validate_brand_workspace,+ 'style': validate_style_workspace,+ }[spec_kind]+ validator(workspace_root)except ImportError as exc:- brand_valid = False+ spec_valid = Falseself._template_issues.append(('error',- 'brand_contract',- f"Brand schema validator could not be imported: {exc}",+ f'{spec_kind}_contract',+ f"{pretty_kind} schema validator could not be imported: {exc}",))except (OSError, SpecParseError) as exc:- brand_valid = False+ spec_valid = Falseself._template_issues.append(('error',- 'brand_contract',+ f'{spec_kind}_contract',str(exc),))- if brand_valid:+ if spec_valid:self.summary['passed'] += 1return self.results@@ -6747,7 +6759,7 @@ class SVGQualityChecker:from ``main`` agrees), warnings under ``warnings``. Both are listedper file so the user can act on them directly."""- if not self._template_issues and not self._brand_template_checked:+ if not self._template_issues and self._spec_only_template_kind is None:returnerrors = [item for item in self._template_issues if item[0] == 'error']@@ -6762,10 +6774,11 @@ class SVGQualityChecker:print(f" Warnings ({len(warnings)}):")for _sev, kind, msg in warnings:print(f" [{kind}] {msg}")- if self._brand_template_checked and not errors:- print(" Brand design_spec.md schema and asset references passed.")+ if self._spec_only_template_kind is not None and not errors:+ pretty_kind = self._spec_only_template_kind.title()+ print(f" {pretty_kind} design_spec.md contract passed.")if not errors:- if not self._brand_template_checked:+ if self._spec_only_template_kind is None:print(" No structural roster issues.")print(" Conventional placeholder-name hints may be declared through ""'placeholders:' frontmatter. Placeholder bounds are mandatory "diff --git a/skills/ppt-master/scripts/svg_quality/cli.py b/skills/ppt-master/scripts/svg_quality/cli.pyindex 18ec329a..a367d177 100644--- a/skills/ppt-master/scripts/svg_quality/cli.py+++ b/skills/ppt-master/scripts/svg_quality/cli.py@@ -78,7 +78,7 @@ def print_usage() -> None:print(" --quick-generate Validate lockless flat Quick Generate SVGs;")print(" ignore design_spec.md and spec_lock.md.")print(" --template-mode Validate a template workspace's templates/ directory:")- print(" Brand validates design_spec.md and referenced assets;")+ print(" Brand/Style validate their portable workspace contracts;")print(" Layout/Deck glob *.svg directly, skip spec_lock checks,")print(" enforce roster consistency, and emit placeholder hints.")print(" native_structure_mode: structured also enables complete")diff --git a/skills/ppt-master/templates/README.md b/skills/ppt-master/templates/README.mdindex 73927437..5674be12 100644--- a/skills/ppt-master/templates/README.md+++ b/skills/ppt-master/templates/README.md@@ -2,27 +2,31 @@## Reusable template kinds-Brand, Layout, and Deck are independent template kinds, not stages of one+Brand, Style, Layout, and Deck are independent template kinds, not stages of oneinheritance 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) |+| [`styles/`](./styles/) | Direction/method: reusable communication method, visual language, composition rhythm, and information-expression defaults | Official brand identity, current-project application, page structure, or SVG roster | [`styles_index.json`](./styles/styles_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 brand-neutral-structure whose identity and communication purpose remain downstream-decisions, and a deck for a recurring presentation family with an explicit-application contract.+A brand is not “a layout minus its pages”, and a Style is not a roster-free+Deck: each owns a different segment. Use a brand for identity with free page+composition, a Style for reusable direction/method without identity truth or+page prototypes, 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 templatekinds. Theme values and identity assets are projected from resolved identityrules supplied by Brand, Deck, or the current project; Layout rules projectinto Master/Layout/Placeholder topology, semantic text roles, andspatial behavior; Deck combines both with descriptive recurring-application-context and actual prototype examples. Downstream AI planning decides which+context and actual prototype examples. Style rules guide communication method,+visual language, composition, and information expression; they do not create a+PowerPoint package object or override resolved Brand/Deck identity. Downstream AI planning decides whichprototypes and content to use, then records the required exporter values.A compiled Slide Master may therefore contain bothstructural geometry and brand visuals even though their source rules remain@@ -31,6 +35,7 @@ separately owned.New workspaces always enter [`Create Template`](../workflows/create-template.md),which keeps the fixed route name and dispatches exactly one child workflow:[`Create Brand`](../workflows/create-template/create-brand.md),+[`Create Style`](../workflows/create-template/create-style.md),[`Create Layout`](../workflows/create-template/create-layout.md), or[`Create Deck`](../workflows/create-template/create-deck.md).@@ -42,10 +47,10 @@ by the user or an exact validated Create Template handoff.| Axis | Values | Meaning ||---|---|---|-| Template kind | `brand` / `layout` / `deck` | Which reusable contract the package owns: identity, brand-neutral structure, or a complete recurring application |+| Template kind | `brand` / `style` / `layout` / `deck` | Which reusable contract the package owns: identity, direction/method, brand-neutral structure, or a complete recurring application || Internal creation strategy | `standard` / `fidelity` / `mirror` | AI-derived Create Layout/Create Deck implementation: newly author a compact or broad roster, or materialize validated source-package facts into a new workspace; persisted for tools, never presented as a required user choice || Internal application plan | `template_reuse_scope` plus optional `template_adherence` | Strategist derives literal, structural, or style-only use and any strict/adaptive exporter behavior after inspecting the installed template and current content |-| PPTX structure | `flat` / `structured` | Derived application plans that use template structure compile declared Masters and Layouts; style-only, brand-only, and free design remain Slide-local |+| PPTX structure | `flat` / `structured` | Derived application plans that use template structure compile declared Masters and Layouts; Style-only, style-scope, brand-only, and free design remain Slide-local. Style fused with Layout/Deck does not change the non-Style structure plan. |These axes must not be used as synonyms or exposed as a user mode matrix. Inparticular, a mirror-created deck is still an ordinary reusable `deck` package@@ -59,7 +64,7 @@ initialized project:```text<template_workspace>/-├── templates/ # design_spec.md, SVG prototypes, optional native_payloads.json.gz store+├── templates/ # design_spec.md; optional Layout/Deck SVG prototypes and native_payloads.json.gz store├── images/ # optional bitmaps├── icons/│ └── imported/ # optional imported vectors, one canonical copy@@ -68,10 +73,16 @@ initialized project:Empty optional directories are omitted. Template SVGs reference bitmaps through`../images/<name>` and imported vectors through `data-icon="imported/<name>"`.+Style narrows this shared routing shape to `templates/design_spec.md` only and+does not carry asset or review payloads; initialized-project sibling scaffolding+may exist but is not Style input.The conditional [`apply-template-workspace`](../workflows/stages/apply-template-workspace.md)-stage owns installation and fusion: it consumes `templates/`, `images/`, and-`icons/` and ignores `exports/`. Compatible legacy-flat packages remain-readable; directory shape alone does not indicate legacy Master/Layout semantics.+stage owns installation and fusion. Brand/Layout/Deck consume package-owned+`templates/`, `images/`, and `icons/`; Style consumes only+`templates/design_spec.md` and ignores sibling project scaffolding. Every kind+ignores `exports/`. Compatible legacy-flat Brand/Layout/Deck packages remain+readable; Style has no legacy-flat form, and directory shape alone does not+indicate legacy Master/Layout semantics.## Design specification references@@ -81,7 +92,7 @@ authoring; their schemas own machine validation. Files under `scaffolds/` areoptional overwrite-safe CLI conveniences, not Generate-route starting artifacts.Reusable template `design_spec.md` files aredeliberately smaller: they contain portable metadata and only the identity,-structure, or application rules owned by that package. General SVG rules live+direction/method, structure, or application rules owned by that package. General SVG rules livein [`shared-standards-core.md`](../references/shared-standards-core.md), witheffects and PowerPoint interfaces loaded only when triggered.diff --git a/skills/ppt-master/templates/brands/README.md b/skills/ppt-master/templates/brands/README.mdindex b4c054cc..d1aab020 100644--- a/skills/ppt-master/templates/brands/README.md+++ b/skills/ppt-master/templates/brands/README.md@@ -2,10 +2,11 @@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/) (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).+Brand is one of four template kinds in the library — alongside+[`styles/`](../styles/) (direction/method defaults), [`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 consumeddiff --git a/skills/ppt-master/templates/decks/README.md b/skills/ppt-master/templates/decks/README.mdindex 108b0933..9e7b0aa7 100644--- a/skills/ppt-master/templates/decks/README.md+++ b/skills/ppt-master/templates/decks/README.md@@ -133,5 +133,6 @@ does not register globally. Empty optional directories are omitted.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`.-See also [`layouts/`](../layouts/) for structure-only packages and+See also [`styles/`](../styles/) for direction/method packages,+[`layouts/`](../layouts/) for structure-only packages, and[`brands/`](../brands/) for identity-only packages.diff --git a/skills/ppt-master/templates/layouts/README.md b/skills/ppt-master/templates/layouts/README.mdindex 21847770..99f7420e 100644--- a/skills/ppt-master/templates/layouts/README.md+++ b/skills/ppt-master/templates/layouts/README.md@@ -146,3 +146,5 @@ omitted.General SVG/PPT rules remain authoritative in[`shared-standards-core.md`](../../references/shared-standards-core.md) and[`pptx-structure-interface.md`](../../references/pptx-structure-interface.md).+See [`styles/`](../styles/) when reusable method and visual direction should be+combined with this structure without becoming identity truth.diff --git a/skills/ppt-master/templates/styles/README.md b/skills/ppt-master/templates/styles/README.mdnew file mode 100644index 00000000..d4acf035--- /dev/null+++ b/skills/ppt-master/templates/styles/README.md@@ -0,0 +1,83 @@+# Style Workspaces++**Style = a roster-free reusable communication method plus coordinated design defaults.** It can carry argument flow, page-role vocabulary, evidence and data-expression discipline, visual-system defaults, image/icon direction, and additional review focus. It does not own a current project's communication contract, reusable brand identity, page geometry, SVG prototypes, or a recurring application contract.++Style is a fourth independent template kind alongside [`brands/`](../brands/), [`layouts/`](../layouts/), and [`decks/`](../decks/). It is not a replacement for the mode or visual-style catalogs.++## Axis Separation++| Axis | Meaning |+|---|---|+| Template `kind: style` | A portable workspace that coordinates reusable method and non-binding design defaults |+| Stage-2 `mode` | The current deck's confirmed narrative and persuasion skeleton |+| Stage-2 `visual_style` | The current deck's confirmed shape, composition, whitespace, typography-character, and texture lock |+| Internal `template_reuse_scope: style` | A flat current-project export plan that reuses no Master/Layout structure |++These names are separate contracts. Style-only and Style + Brand naturally produce a flat application plan, while Style fused with a Layout or Deck may use structured reuse. `kind: style` therefore never forces the internal reuse scope when another workspace supplies structure.++## Trigger, Precedence, and Fusion++Selection uses the common explicit-path trigger in [`generate-pptx`](../../workflows/generate-pptx.md) Step 3. A bare Style name, consulting label, or ordinary visual description remains a brief or catalog signal and does not activate this workspace. `styles_index.json` is discovery-only.++| Decision | Precedence |+|---|---|+| Current project communication contract, mode, visual style, palette, typography, images, and icons | Latest explicit user instruction and confirmed project values |+| Exact identity values | Brand, then Deck identity; both override overlapping Style fallback values |+| Reusable communication method and evidence discipline | Style, applied only where compatible with the current project contract |+| Reusable structure | Compatible Layout, then Deck structure; Style never supplies structure |+| Recurring application context | Deck, subordinate to the current project's Stage-1 communication contract |++Style fallback values seed the normal Stage-2 solution when the corresponding decision remains open. They are not identity truth and do not bypass confirmation. If a Style method and a Deck application contract materially conflict, surface the mismatch; do not silently weaken either one.++## `design_spec.md` Contract++The frontmatter is intentionally small:++```markdown+---+style_id: <slug>+kind: style+summary: <one-line reusable method and design-default fit>+keywords: [<three-to-five discovery tags>]+---+```++The seven required body sections are:++| § | Title | Owned content |+|---|---|---|+| I | Style Overview | Display name, best fit, reusable intent, and provenance |+| II | Communication Method | Argument flow, page-message discipline, claim treatment, and an optional mode seed |+| III | Page Role Vocabulary | Semantic roles with communication jobs, evidence obligations, and non-geometric composition tendencies |+| IV | Evidence & Data Expression | Claim/evidence trace, chart/table/source behavior, and native-editability preference |+| V | Visual System Defaults | Composition, density, decoration, color behavior, typography character, and optional visual-style/fallback seeds |+| VI | Image & Icon Direction | Rendering, usage, framing, and icon treatment without asset selection |+| VII | Review Focus | Extra checks used only after the user explicitly activates visual review |++`Fallback Color Scheme` and `Fallback Typography` are optional subsections under §V. They remain lower-priority defaults, never Brand identity. A preset mode, visual style, or image rendering resolves to a real ID in its matching catalog. A custom seed includes its behavior prose and lists only catalog references actually used as comma-separated IDs; use `Mode References`, `Visual Style References`, or `Image Rendering References` respectively.++Section VII contains exactly one non-localized `<!-- visual-review-trigger: explicit-user-only -->` marker. Its surrounding explanation and checks may use the user's language; the marker lets validation enforce that Review Focus is advisory and never activates visual review.++**Forbidden — identity, structure, or application ownership**:++- Do not write `primary_color`, official color provenance, Logo, Voice & Tone, Icon Style, canvas fields, page count/types, `replication_mode`, `native_structure_mode`, or placeholder fields.+- Do not write Template Overview, Signature Design Elements, Page Roster, SVG filenames, Master/Layout identities, slot geometry, fixed page sequences, or reusable application audience/outcome rules.+- Do not write the current project's audience, objective, outcome, core message, delivery context, artifact afterlife, content outline, page assignments, icon inventory, or image-resource list.++## Workspace and Creation++Every Style workspace contains one portable source file and no page or asset payload:++```text+<template_workspace>/+└── templates/+ └── design_spec.md+```++Do not create empty `images/`, `icons/`, or `exports/` directories. Existing initialized-project scaffolding may remain untouched but is not Style output.++1. Enter [`workflows/create-template.md`](../../workflows/create-template.md), which dispatches method/default output to [`create-style.md`](../../workflows/create-template/create-style.md).+2. Validate with `svg_quality_checker.py --template-mode`.+3. In library scope, register with `register_template.py <id> --kind style`.++The discovery source of truth is [`styles_index.json`](./styles_index.json). Each entry is `style_id → { summary, keywords }`; the index never duplicates the full method or defaults and never activates Generate Step 3.diff --git a/skills/ppt-master/templates/styles/styles_index.json b/skills/ppt-master/templates/styles/styles_index.jsonnew file mode 100644index 00000000..0967ef42--- /dev/null+++ b/skills/ppt-master/templates/styles/styles_index.json@@ -0,0 +1 @@+{}diff --git a/skills/ppt-master/workflows/create-template.md b/skills/ppt-master/workflows/create-template.mdindex a975a9e4..feb425bc 100644--- a/skills/ppt-master/workflows/create-template.md+++ b/skills/ppt-master/workflows/create-template.md@@ -1,10 +1,10 @@----description: Create Template entry workflow and shared contract for the Create Brand, Create Layout, and Create Deck sub-workflows.+description: Create Template entry workflow and shared contract for the Create Brand, Create Style, Create Layout, and Create Deck sub-workflows.---# Create Template Workflow-> **Fixed entry name**: user-facing template creation always enters **Create Template**. This workflow selects exactly one child workflow — [`create-brand.md`](./create-template/create-brand.md), [`create-layout.md`](./create-template/create-layout.md), or [`create-deck.md`](./create-template/create-deck.md) — and owns their shared execution contract.+> **Fixed entry name**: user-facing template creation always enters **Create Template**. This workflow selects exactly one child workflow — [`create-brand.md`](./create-template/create-brand.md), [`create-style.md`](./create-template/create-style.md), [`create-layout.md`](./create-template/create-layout.md), or [`create-deck.md`](./create-template/create-deck.md) — and owns their shared execution contract.>> **Role invoked for Create Layout/Create Deck**: [Template_Designer](../references/template-designer.md)@@ -25,10 +25,11 @@ 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 Style`](./create-template/create-style.md) | Reuse a communication method and visual direction without identity truth or page prototypes | `templates/styles/<style_id>/` | Method, page-role vocabulary, evidence/data expression, visual defaults, image/icon direction, and advisory review focus; no SVG roster || [`Create Layout`](./create-template/create-layout.md) | Reuse a brand-neutral structural skeleton without a recurring communication application | `templates/layouts/<layout_id>/` | Canvas, page grammar, semantic text roles, Master/Layout/slot contract, and SVG roster; no brand identity or application contract || [`Create Deck`](./create-template/create-deck.md) | Reuse a branded structural system or a recurring presentation application | `templates/decks/<deck_id>/` | Descriptive application context, integrated identity/structure, and SVG roster |-Select Create Brand only for identity-only intent. Select Create Layout only when identity remains downstream-selectable and the reusable artifact does not prescribe communication objectives, audience outcomes, a required narrative sequence, or scenario-specific starting content. Select Create Deck when structure carries brand identity or reusable application semantics. A complete source PPTX alone does not determine the kind: classify only the stable rules worth reusing. Ask one discriminator question only when the user's requested reusable artifact is genuinely ambiguous; once selected, enter that child workflow and do not repeat route selection inside its confirmation gate.+Select Create Brand only for identity-only intent. Select Create Style when the portable value is a communication method, evidence discipline, and visual direction but there is no official identity, page geometry, or prototype roster to retain. 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@@ -54,7 +55,12 @@ Both scopes write this contract:└── exports/ # conditional; required package evidence for multi-Master templates```-The review PPTX is derived evidence, not a source template asset. Create `exports/` only when a review deck is requested or the template declares more than one Master; multi-Master templates require the package-level gate in Step 6. Template application reads `templates/` plus any existing `images/` and `icons/`; it never copies or consumes `exports/`. Library `exports/` directories are Git-ignored.+Create Style narrows the shared root to `templates/design_spec.md` only. It+does not write or adopt images, icons, native payloads, or review exports;+pre-existing empty project scaffolding remains untouched and is not Style+output.++The review PPTX is derived evidence, not a source template asset. Create `exports/` only when a review deck is requested or the template declares more than one Master; multi-Master templates require the package-level gate in Step 6. Brand/Layout/Deck application reads `templates/` plus any package-owned `images/` and `icons/`; Style reads only `templates/design_spec.md`. No kind copies or consumes `exports/`. Library `exports/` directories are Git-ignored.For `project`, `target_project` is required and must be an existing project initialized by `project_manager.py init`. Before the first final-output write, run one complete preflight. Apply the same collision checks to a library workspace; the only difference is that its root is under the global kind directory:@@ -78,11 +84,11 @@ After dispatch, the selected child workflow executes these shared steps with its## Step 1: Reference Bundle Intake & Analysis-Run every applicable input branch for the reference bundle the user supplied. A bundle may contain one source, several files of one type, multiple source types, direct text in the conversation, or no external file. This step produces analysis artefacts only — it does **not** create the final template directory, write `design_spec.md`, or touch any template index. When Create Brand was selected, follow that child workflow's analysis rules and do not run page-topology analysis merely because the reference is a PPTX/PDF.+Run every applicable input branch for the reference bundle the user supplied. A bundle may contain one source, several files of one type, multiple source types, direct text in the conversation, or no external file. This step produces analysis artefacts only — it does **not** create the final template directory, write `design_spec.md`, or touch any template index. When Create Brand or Create Style was selected, follow that child workflow's analysis rules and do not run page-topology analysis merely because the reference is a PPTX/PDF.### Input source taxonomy-The rows are evidence channels, not mutually exclusive routes. Run every matching row and retain source-level provenance. The internal-strategy column applies to Create Layout/Create Deck. Create Brand uses the same reference formats for identity evidence but has no replication strategy, SVG roster, or native-structure path.+The rows are evidence channels, not mutually exclusive routes. Run every matching row and retain source-level provenance. The internal-strategy column applies to Create Layout/Create Deck. Create Brand uses the same reference formats for identity evidence, while Create Style extracts portable method and direction; neither has a replication strategy, SVG roster, or native-structure path.| Type | What the user supplied | Tool / read path | Internal strategies supported by the evidence ||------|-------------------------|------------------|-----------------------------------------------|@@ -92,6 +98,15 @@ The rows are evidence channels, not mutually exclusive routes. Run every matchin| **D** Text / document / website / asset references | Direct conversation text, pasted requirements, Markdown/TXT, DOCX/PDF/HTML/URL, brand/design manuals, or supplied logo/icon/font assets | Use direct text as-is; read plain text/Markdown; convert supported documents/URLs with `source_to_md.py` into a temporary analysis workspace; inventory explicit assets | `standard` only by itself || **E** No reference material | A template request with no external source and no substantive brief yet | Skip analysis; collect every required value in Steps 2–3 | `standard` only |+**Roster-free child boundary**: Create Brand and Create Style do not enter the+structured import/materialization path below. Their child workflows may inspect+PPTX/PDF pages, extracted text, screenshots, or other sources as evidence, but+they do not preserve or derive canvas, page count/order, Master/Layout identity,+placeholder geometry, or an SVG roster. Create Brand extracts identity truth;+Create Style extracts only portable communication method and visual defaults.+The Type A/Type B authoring-IR and `standard` / `fidelity` / `mirror` mechanics+below are Create Layout/Create Deck concerns.+| Bundle rule | Behavior ||---|---|| Combine channels | `standard` may use every confirmed visual, textual, documentary, web, and asset source together. Do not force the user to choose one source type. |@@ -269,6 +284,13 @@ checks from `authoring_manifest.json`.Before composing Step 2, extract the template's reusable norms from the previous content. These norms are not generic design advice; they are the source deck's observable operating rules, and they must flow into `design_spec.md`.+This table applies to Create Layout/Create Deck. Create Brand extracts only the+identity subset defined by its child workflow. Create Style instead extracts+argument flow, page-message/evidence discipline, open page-role vocabulary,+data-expression rules, composition/density rhythm, visual defaults, and+image/icon direction. It must discard source-specific audience, objective,+page order/count, page mappings, canvas, and native structure.+| Norm area | Extract from | Record as ||---|---|---|| Canvas / page geometry | `manifest.json` slide size, SVG `width` / `height` / `viewBox` | `[fact]` canvas format, pixel dimensions, source `viewBox`, and aspect ratio |@@ -349,6 +371,7 @@ Inventory explicitly supplied logo, icon, font, and other brand/design assets. RExtract only what the source actually states:- Identity rules: colors, typography, logo usage, voice, icon style, and explicit exclusions.+- Style method: argument flow, evidence discipline, reusable page-role vocabulary, information hierarchy, composition/density rhythm, visual defaults, image/icon direction, and optional review focus. Do not retain the source's audience, objective, page sequence, page count, or page-specific resource choices as Style rules.- Structure rules: canvas, page types, grids, zones, placeholders, density, image behavior, and requested variants.- Deck application: recurring situations, intended audiences/outcomes, delivery or reading assumptions, representative narrative/page roles, examples, and negative requirements. Do not convert these observations into mandatory future-use policy.@@ -356,7 +379,7 @@ Treat an explicit value authored by the user as `[decision]` regardless of carri### 1E. No reference material-Skip the analysis. Step 2 will list every Required item as `[decision]`; nothing is fact-derivable from a non-existent source. Create Brand may emit an incomplete empty skeleton only under its explicit child-workflow rule; Create Layout/Create Deck still require the shared confirmation gate before authoring a `standard` workspace.+Skip the analysis. Step 2 will list every Required item as `[decision]`; nothing is fact-derivable from a non-existent source. Create Brand may emit an incomplete empty skeleton only under its explicit child-workflow rule. Create Style, Create Layout, and Create Deck still require the shared confirmation gate before authoring their workspace.---@@ -377,14 +400,15 @@ Compose one concise natural-language proposal that states the template the AI in|---|---|| 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 |+| Selected child workflow | Echo the already-dispatched Create Brand, Create Style, Create Layout, or Create Deck workflow; do not reopen kind selection inside the brief |+| Method and direction | Create Style only. Summarize the portable communication method, evidence discipline, page-role vocabulary, information design, visual defaults, image/icon direction, and advisory review focus. Do not include a current audience/outcome, page order/count, canvas, or prototype plan. || Category | Create Layout/Create Deck only. State the one discovery category inferred from the intended artifact. For Layout, a scenario category records geometric fit only and never grants application ownership. || Application context | Create Deck only. Summarize the recurring presentation family, likely audiences/outcomes, delivery/reading assumptions, and representative page roles. This is descriptive selection context, not a rule saying which template pages or visible content future projects must keep. || Theme direction | Create Layout/Create Deck only. Describe the intended light/dark/mixed behavior in plain language. Create Brand records identity colors instead and does not own a page theme mode. || Canvas | Create Layout/Create Deck only. State the recommended canvas with exact pixel size and `viewBox`; do not enumerate same-ratio alternatives unless the user asks or the evidence is genuinely ambiguous. || Creation plan | Create Layout/Create Deck only. Describe what will be preserved, what will be rebuilt, how broad the prototype roster will be, and how native structure will be handled. The AI derives the internal `replication_mode` from this prose after confirmation; never ask the user to select `standard`, `fidelity`, or `mirror`. || Native structure plan | Create Layout/Create Deck only. State the planned Master/Layout/slot result. For newly authored output, show the planned Master families and reject one-Master-per-Layout organization or equivalent duplicate Masters. For literal preservation, summarize the exact supported source facts that will be mapped into the new workspace. |-| Asset bundling | Recommended included assets, plus excluded candidate assets with a one-line reason when reference assets exist |+| Asset bundling | Create Brand/Create Layout/Create Deck only. Recommend included assets, plus excluded candidate assets with a one-line reason when reference assets exist. Create Style records textual provenance only and writes no asset payload. |Items to surface:@@ -395,22 +419,25 @@ Items to surface:| New template ID | Yes | `[decision]` when supplied; otherwise propose a filesystem-safe ASCII slug as `[suggested]`. In library scope it also becomes the matching index key || Template display name | Yes | `[decision]` when supplied; otherwise `[suggested]`, often from `manifest.json.source.name` for type A || Category | Create Layout/Create Deck only | `[decision]` when explicit; otherwise `[derived]` for indexing — Create Deck: `brand` / `general` / `scenario` / `government` / `special`; Create Layout: `general` / `scenario` / `government` / `special` |-| Applicable scenarios | Yes | Create Brand: identity use cases. Create Layout: content shapes and delivery settings its geometry can support, without communication or narrative ownership. Create Deck: recurring presentation situations inside the application contract. `[suggested]` from analysis unless explicitly authored or externally sourced; user confirms. |+| Applicable scenarios | Yes | Create Brand: identity use cases. Create Style: broad best-fit discovery context only, without binding a target audience, outcome, or recurring application. 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. || Application context and representative page roles | Create Deck only | `[decision]` when supplied explicitly; otherwise `[suggested]` from recurring source patterns. Describe the source and intended family without assigning required/optional/repeatable status or fixed/replaceable/example-only policy. |-| Identity tone or structural summary | Yes | Create Brand/Create Deck: identity tone. Create Layout: structural use case and density/rhythm summary only. |+| Identity, method, or structural summary | Yes | Create Brand/Create Deck: identity tone. Create Style: communication method and visual-default summary. Create Layout: structural use case and density/rhythm summary only. |+| Communication method and evidence discipline | Create Style only | `[decision]` when explicit; otherwise `[suggested]` from repeated source behavior. State argument flow, message/evidence discipline, page-role vocabulary, and data-expression rules without fixing a page sequence. |+| Visual-system defaults | Create Style only | `[decision]` when explicit; otherwise `[suggested]` from evidence. Palette, typography, mode, and visual-style values remain overrideable seeds, never Brand identity truth or direct Stage-2 locks. |+| Review focus | Create Style only | `[decision]` when explicit; otherwise `[suggested]`. These checks apply only if the user separately enables visual review; the Style cannot trigger that stage. || 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`). || Internal creation strategy | Create Layout/Create Deck only | `[derived]` from the confirmed natural-language plan and evidence. `standard` is the compact authored implementation, `fidelity` requires A/B page evidence for broader source-aligned coverage, and `mirror` requires A or B with a complete explicit structure contract for literal materialization. Create Layout mirror additionally requires a brand-neutral and application-neutral source. Persist `replication_mode` for tools, not as a user-facing mode. || Native structure facts | Create Layout/Create Deck with Type A or structured Type B | `[fact]` from `native_structure.json` / source SVG contract: master/layout counts, parentage, page assignments, placeholder identities, and multi-master status. Mirror preserves these validated facts in the new workspace; authored modes do not use them as output topology. || Structure ownership plan | Create Layout/Create Deck only | `[derived]` from the requested result. Authored output creates new Master/Layout ownership, including the reusable-family reason for every additional Master; literal preservation maps source ownership without synthesis. Every Master must own at least one emitted Layout and every Layout must have at least one emitted prototype. || Reference treatment | Create Layout/Create Deck when a reference exists | `[derived]` per page from the user's prose: closely reproduce geometry/decoration where requested, otherwise adapt the reference into the newly authored system. Literal materialization preserves supported source facts mechanically. |-| Basic template norms | Yes when reference exists | Create Brand uses the identity fields and provenance rules from its child workflow. Create Layout/Create Deck use `[fact]` / `[suggested]` layout grammar, image system, density rhythm, page roster semantics, and asset policy from Step 1. |+| Basic template norms | Yes when reference exists | Create Brand uses the identity fields and provenance rules from its child workflow. Create Style uses portable method, page-role, evidence/data, composition/density, visual-default, and image/icon rules while discarding project-specific context. 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 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 |+| Design style | Required for Create Style; optional otherwise | `[decision]` when explicit; otherwise `[suggested]` from analysis. For Style this is an overrideable visual-direction seed, not an exact lookup token or identity lock. |+| Assets list | Optional for Create Brand/Create Layout/Create Deck; N/A for Create Style | 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. Style may cite the reference textually but never adopts an asset. |+| Keywords | Create Style/Create Layout/Create Deck only | `[suggested]` from analysis (3–5 short tags); user confirms. Create Brand has no keywords field or keyword index payload. |When the bundle includes Type A for Create Layout/Create Deck, also include in this message:@@ -420,7 +447,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.). `replication_mode` is the AI-derived implementation record, not a user selection. A Deck writes descriptive application context in Template Overview and factual prototype descriptions in Page Roster rather than duplicating that prose into frontmatter. Do not persist a generic `template_id` field: it is the parent workflow's cross-kind name, not a registrar schema key. Do not persist the execution-only `output_scope` or `target_project` fields. In library scope, `register_template.py` reads this frontmatter in Step 7 so the brief flows directly into the index without the AI re-deriving it from prose.+> **Persist the portable brief into `design_spec.md`**. In Step 4, declare a YAML frontmatter block with the child-specific ID key (`brand_id`, `style_id`, `deck_id`, or `layout_id`) and only fields owned by that child. Create Brand follows its identity schema. Create Style persists only `style_id`, `kind`, `summary`, and `keywords`; its method and direction live in the required body sections, and it writes no canvas, category, identity, application, replication, native-structure, page-count, or roster fields. Create Layout/Create Deck persist the confirmed portable fields (`kind`, `category`, `summary`, `keywords`, `primary_color` for deck, `page_types` for layout, `canvas_format`, `canvas_width`, `canvas_height`, `canvas_viewbox`, `source_viewbox`, `replication_mode`, `native_structure_mode`, etc.). `replication_mode` is the AI-derived implementation record, not a user selection. A Deck writes descriptive application context in Template Overview and factual prototype descriptions in Page Roster rather than duplicating that prose into frontmatter. Do not persist a generic `template_id` field: it is the parent workflow's cross-kind name, not a registrar schema key. Do not persist the execution-only `output_scope` or `target_project` fields. In library scope, `register_template.py` reads this frontmatter in Step 7 so the brief flows directly into the index without the AI re-deriving it from prose.---@@ -444,7 +471,8 @@ Skipping this gate — including silently inferring values from reference files,- [ ] For Create Layout/Create Deck, the AI-derived internal strategy is consistent with the bundle evidence (`fidelity` requires A/B page evidence; `mirror` requires A or structured B; C/D/E channels alone permit only `standard`); Create Layout mirror evidence is already brand-neutral and application-neutral- [ ] Every supplied visual, textual, documentary, web, and asset channel has been analyzed or explicitly excluded; mixed-input conflicts are surfaced rather than silently resolved- [ ] For Create Layout/Create Deck mirror, the source graph and supported geometry are complete; every source Layout absent from the source-slide roster is planned as a definition-only prototype, and any genuinely missing/unsupported facts were reported; Create Layout mirror contains no retained brand identity or reusable application policy-- [ ] Child-specific norms from prior content have been surfaced and accepted, or explicitly marked N/A when no reference exists: identity/provenance for Create Brand; layout/image/density/asset behavior for Create Layout/Create Deck+- [ ] 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; communication/evidence/visual-direction behavior for Create Style; layout/image/density/asset behavior for Create Layout/Create Deck+- [ ] For Create Style, the portable communication method, open page-role vocabulary, evidence/data rules, visual defaults, image/icon direction, and advisory review focus are confirmed; project-specific audience/outcome/page sequence and all identity/structure fields remain N/A- [ ] For Create Layout/Create Deck, the plan makes structure ownership explicit: authored output creates a new structure without source-topology distillation; literal materialization maps validated source ownership one-to-one into a new workspace- [ ] For Create Deck, the recurring presentation family, intended audiences/outcomes, and representative page roles are understood without turning them into mandatory page/content policies; for Create Layout, no application contract or brand identity has leaked into the structure brief- [ ] For Create Brand, all required identity fields from its child workflow are confirmed and canvas/replication/native-structure fields remain N/A@@ -481,6 +509,8 @@ The preflight is atomic at the Create Template parent level: discover and settle**Create Brand branch**: continue in [`create-brand.md`](./create-template/create-brand.md) §3 with the confirmed identity brief and resolved `<template_workspace>`. Then return to the Create Brand branch in Step 5. Do not invoke Template_Designer, create SVGs, or apply the Create Layout/Create Deck-only material below.+**Create Style branch**: continue in [`create-style.md`](./create-template/create-style.md) §3 with the confirmed method/direction brief and resolved `<template_workspace>`. Then return to the Create Style branch in Step 5. Do not invoke Template_Designer, create SVGs, retain source page topology, or apply the Create Layout/Create Deck-only material below.+**Create Layout/Create Deck branch**: continue in the selected child workflow, switch to the Template_Designer role, and generate per role definition. The role input is the finalized brief from Step 3 plus the analysis bundle from Step 1, including the accepted basic template norms.When the bundle includes Type A, pass the following internal package to the role:@@ -650,6 +680,27 @@ python3 skills/ppt-master/scripts/register_template.py <brand_id> --kind brand -After Create Brand validation passes, skip the Create Layout/Create Deck-only remainder of this step and all of Step 6; continue at Step 7.+**Create Style branch**: run the child workflow's §4 semantic checklist, then+the shared validator in both scopes. The validator detects `kind: style` and+mechanically enforces the frontmatter, section/field shape, conditional custom+and fallback values, portable ID, and one-file roster-free package boundary.+The child checklist remains authoritative for semantic scope and provenance.++```bash+python3 skills/ppt-master/scripts/svg_quality_checker.py "<template_workspace>/templates" --template-mode+```++In `library` scope, additionally run the registrar dry-run so `style_id` is+checked against the library directory/index key:++```bash+python3 skills/ppt-master/scripts/register_template.py <style_id> --kind style --dry-run+```++After Create Style validation passes, skip the Create Layout/Create Deck-only+remainder of this step and all of Step 6; continue at Step 7. Review Focus is+advisory content only and never activates the Generate visual-review stage.+**Create Layout/Create Deck branch**: set `<template_source>` to `<template_workspace>/templates/` in both scopes.```bash@@ -713,7 +764,7 @@ This step is a **hard gate**. Do not generate a review PPTX, register, or hand t## Step 6: Template Review PPTX and Multi-Master Package Gate-**Trigger — Create Layout/Create Deck only**: Run when the user requests a PowerPoint review file **or** when the validated SVG roster declares more than one unique Master key. A multi-Master template requires this step even when no review artifact was requested. A one-Master template may skip directly to Step 7 when the user did not request a review file. Create Brand always skips this step because it owns no SVG roster or native structure.+**Trigger — Create Layout/Create Deck only**: Run when the user requests a PowerPoint review file **or** when the validated SVG roster declares more than one unique Master key. A multi-Master template requires this step even when no review artifact was requested. A one-Master template may skip directly to Step 7 when the user did not request a review file. Create Brand and Create Style always skip this step because they own no SVG roster or native structure.Export the complete SVG roster, one prototype per slide, from the workspace root:@@ -753,7 +804,7 @@ Branch on the confirmed output scope:| Scope | Action ||---|---|| `library` | Run the registrar below after Step 5 passes and Step 6 also passes whenever it was requested or required by a multi-Master roster |-| `project` | Skip the registrar entirely. Do not edit `decks_index.json`, `layouts_index.json`, or any library README; continue to Step 8 with index status `Not registered (project workspace)` |+| `project` | Skip the registrar entirely. Do not edit any global template index or library README; continue to Step 8 with index status `Not registered (project workspace)` |Run the unified registrar with the kind flag; it derives the corresponding index entry from `templates/design_spec.md` (frontmatter when present, prose fallback otherwise) plus the actual `templates/*.svg` file list. The registrar retains read compatibility with old flat library packages; new creation never writes that shape:@@ -761,6 +812,9 @@ 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 style+python3 skills/ppt-master/scripts/register_template.py <template_id> --kind style+# For deckpython3 skills/ppt-master/scripts/register_template.py <template_id> --kind deck@@ -775,14 +829,25 @@ Outputs by kind (the JSON index is the single source of truth — READMEs descri| `deck` | `templates/decks/decks_index.json` || `layout` | `templates/layouts/layouts_index.json` || `brand` | `templates/brands/brands_index.json` |+| `style` | `templates/styles/styles_index.json` |-The completion card's file roster is collected by globbing `templates/*.svg` in the workspace. Legacy flat packages still use their root `*.svg` roster.+The Layout/Deck completion card's file roster is collected by globbing+`templates/*.svg` in the workspace. Brand/Style cards are spec-only. Legacy+flat Layout/Deck packages still use their root `*.svg` roster.The index file is a **discovery index** — it lets the AI answer "what templates are available?" by listing names and workspace-root paths. It is **not** consulted to trigger [`generate-pptx`](./generate-pptx.md) Step 3. Step 3 triggers on an explicit workspace-root path supplied by the user, regardless of whether that path is registered. An unregistered workspace still works when the user gives its path; it just will not appear in discovery listings.> **Recommended for new templates**: declare a YAML frontmatter block at the top of `design_spec.md`. The registrar prefers it over prose extraction:>> ```yaml+> # style example+> ---+> style_id: consulting_analytical+> kind: style+> summary: Answer-first, evidence-led decision-document defaults without page prototypes or brand identity.+> keywords: [consulting, decision-support, evidence, analytical]+> ---+>> # deck example> ---> deck_id: my_deck@@ -829,6 +894,7 @@ The index file is a **discovery index** — it lets the AI answer "what template> To rebuild every entry at once (e.g. after editing many specs), run:>> ```bash+> python3 skills/ppt-master/scripts/register_template.py --kind style --rebuild-all> python3 skills/ppt-master/scripts/register_template.py --kind deck --rebuild-all> python3 skills/ppt-master/scripts/register_template.py --kind layout --rebuild-all> ```@@ -845,14 +911,14 @@ Produce one scope-aware, evidence-driven completion card for either location:## Template Creation Complete**Template Name**: <template_id> (<display_name>)-**Kind**: brand | layout | deck+**Kind**: brand | style | layout | deck**Output Scope**: library | project**Workspace Path**: `<template_workspace>/`**Template Source**: `<template_workspace>/templates/`**Bitmap Path**: `<template_workspace>/images/` ← omit when no bitmap was written or adopted**Imported Vector Path**: `<template_workspace>/icons/imported/` ← omit when no imported vector was written or adopted-**Review PPTX**: `<template_workspace>/exports/<template_id>_template_preview.pptx` ← Create Layout/Create Deck only; omit for Create Brand and when an optional one-Master review was not requested-**Primary Color**: <hex> ← Create Brand/Create Deck only; omit for Create Layout+**Review PPTX**: `<template_workspace>/exports/<template_id>_template_preview.pptx` ← Create Layout/Create Deck only; omit for Create Brand/Create Style and when an optional one-Master review was not requested+**Primary Color**: <hex> ← Create Brand/Create Deck only; omit for Create Style/Create Layout**Index Registration**: Done | Not registered (project workspace)### Files Included@@ -867,9 +933,13 @@ Produce one scope-aware, evidence-driven completion card for either location:| `exports/<template_id>_template_preview.pptx` | Verified, when requested or required for multi-Master |```-For Create Brand, replace the SVG/review rows with `templates/design_spec.md` plus only the real `images/*` / `icons/*` assets. Its completion card must explicitly state `SVG roster: N/A` and `Native structure: N/A`.+For Create Brand, replace the SVG/review rows with+`templates/design_spec.md` plus only real identity assets. For Create Style,+list only `templates/design_spec.md`. Both completion cards must explicitly+state `SVG roster: N/A` and `Native structure: N/A`; Style must also state+`Visual review trigger: N/A (advisory focus only)`.-The next Generate PPTX Step 3 input is the exact `<template_workspace>/` root in either scope. Step 3 resolves its `templates/design_spec.md`, ignores `exports/`, and copies or consumes `templates/` plus any existing `images/` and `icons/` as one unit. It then authors new `svg_output/` pages under the template contract and exports a new PPTX. Neither the reference PPTX/SVG nor the template prototypes are upgraded in place. A legacy-flat package root remains readable only when its semantic SVG contract is current; otherwise create a new workspace through this route.+The next Generate PPTX Step 3 input is the exact `<template_workspace>/` root in either scope. Step 3 resolves its `templates/design_spec.md` and always ignores `exports/`. Brand/Layout/Deck copy or consume package-owned `templates/` plus any existing `images/` and `icons/`; Style consumes only `templates/design_spec.md` and ignores sibling project scaffolding. It then authors new `svg_output/` pages under the template contract and exports a new PPTX. Neither the reference PPTX/SVG nor the template prototypes are upgraded in place. A legacy-flat Brand/Layout/Deck package root remains readable only when it satisfies its current kind contract; for Layout/Deck that includes the structured SVG contract. Style has no legacy-flat form. Otherwise create a new workspace through this route.---@@ -886,11 +956,11 @@ The next Generate PPTX Step 3 input is the exact `<template_workspace>/` root in## Notes-1. **SVG technical constraints**: Create Layout/Create Deck load [shared-standards-core.md](../references/shared-standards-core.md) plus [pptx-structure-interface.md](../references/pptx-structure-interface.md), and load [svg-effects.md](../references/svg-effects.md) only when the authored design uses those effects. Create Brand authors no SVG and loads none of these SVG modules. Do not restate the contracts in the template's `design_spec.md`.-2. **Color consistency**: Create Deck SVG files must use the same color scheme as `design_spec.md §II Color Scheme`; Create Layout owns no identity colors, and Create Brand owns no SVG files-3. **Native-object mapping**: Treat Theme/Master/Layout/Placeholder as compiled PowerPoint objects, not template kinds. Layout owns topology and placement, Brand owns identity values/assets, and Deck adds descriptive recurring-application context.+1. **SVG technical constraints**: Create Layout/Create Deck load [shared-standards-core.md](../references/shared-standards-core.md) plus [pptx-structure-interface.md](../references/pptx-structure-interface.md), and load [svg-effects.md](../references/svg-effects.md) only when the authored design uses those effects. Create Brand and Create Style author no SVG and load none of these SVG modules. Do not restate the contracts in the template's `design_spec.md`.+2. **Color consistency**: Create Deck SVG files must use the same color scheme as `design_spec.md §II Color Scheme`; Create Layout owns no identity colors, Create Style owns only overrideable visual defaults, and Create Brand/Create Style own no SVG files+3. **Native-object mapping**: Treat Theme/Master/Layout/Placeholder as compiled PowerPoint objects, not template kinds. Layout owns topology and placement, Brand owns identity values/assets, Style owns portable direction/method defaults, and Deck adds descriptive recurring-application context.4. **Placeholder convention**: `{{}}` format only; default names listed in [Placeholder Reference](../references/template-designer.md#4-placeholder-reference-canonical-convention-overridable-per-template). Override per template via `placeholders:` frontmatter when needed.5. **Discovery requirement**: A library template is discoverable only after `register_template.py` has been run against it (Step 7). A project-scoped workspace intentionally stays out of global discovery and is consumed by its explicit workspace-root path.-6. **Review output**: Generate `exports/<template_id>_template_preview.pptx` on request and always for a multi-Master template. It is derived local evidence, never a source input during template application, and library exports stay Git-ignored.+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. Brand and Style never generate this preview; Style Review Focus cannot activate visual review.> **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 2c18668a..236d347c 100644--- a/skills/ppt-master/workflows/create-template/create-deck.md+++ b/skills/ppt-master/workflows/create-template/create-deck.md@@ -127,4 +127,4 @@ python3 skills/ppt-master/scripts/register_template.py <deck_id> --kind deck --dpython3 skills/ppt-master/scripts/register_template.py <deck_id> --kind deck```-For project scope, skip both commands. The exact workspace root becomes the next Generate PPTX Step 3 input; any separately supplied Brand or Layout workspace overrides the corresponding complete segment downstream without mutating this deck workspace.+For project scope, skip both commands. The exact workspace root becomes the next Generate PPTX Step 3 input; any separately supplied Brand, Style, or Layout workspace overrides the corresponding complete segment downstream without mutating this deck workspace.diff --git a/skills/ppt-master/workflows/create-template/create-style.md b/skills/ppt-master/workflows/create-template/create-style.mdnew file mode 100644index 00000000..37482218--- /dev/null+++ b/skills/ppt-master/workflows/create-template/create-style.md@@ -0,0 +1,185 @@+---+description: Create Style child workflow for a reusable communication method and visual-default workspace without page prototypes.+---++# Create Style Workflow++Enter this child workflow only after [`Create Template`](../create-template.md) dispatches `kind: style`.++## Responsibility Boundary++| Owner | Responsibilities |+|---|---|+| Create Template | Child-workflow dispatch plus the shared `library` / `project` scope, confirmation gate, collision preflight, registration, completion, and Generate PPTX handoff contract |+| Create Style | Reusable communication method, page-role vocabulary, evidence discipline, visual-system defaults, image/icon direction, review focus, and the roster-free `design_spec.md` |++**Hard rule — child workflow, not a top-level route**: Create Style executes only inside Create Template. It uses the parent workflow's single shared confirmation/preflight/registration contract and never creates a competing entry route or second confirmation gate.++**Hard rule — method and defaults only**: A Style owns a reusable way to argue, express evidence, and coordinate non-binding design defaults. It owns no current-project communication contract, reusable brand identity, page geometry, canvas, SVG prototype, Master/Layout graph, placeholder contract, application contract, or visible asset inventory.++**Hard rule — no page prototypes**: A Style workspace contains only `templates/design_spec.md`. Do not create page SVGs, a review PPTX, or empty `images/`, `icons/`, or `exports/` directories.++## Invocation Points++1. Use §1–2 below for Style analysis and brief fields, then execute Create Template Steps 2–3 with those child-owned fields.+2. After Create Template Step 4 resolves and preflights `<template_workspace>`, use §3 to materialize the confirmed Style.+3. Run §4, then return its evidence to Create Template Steps 5, 7, and 8. Create Style always skips the shared structured-preview step.++## 1. Style Input Interpretation++Use every supplied reference only as evidence for reusable method and design defaults:++| Evidence | May inform | Must not become |+|---|---|---|+| Direct brief, text, document, or website | Argument flow, claim discipline, page-role vocabulary, data-expression rules, and review focus | The current project's audience, objective, outline, page count, or source claims |+| PPTX, PDF, image, or SVG reference | Visual-system tendencies, density, decoration, image treatment, and icon treatment | A copied page roster, canvas contract, Master/Layout graph, or fixed geometry |+| Brand or organization material | A lower-priority fallback direction when the user explicitly wants it generalized | Official identity truth, logos, proprietary palettes, brand voice, or trademarked presentation rules |+| Existing mode, visual-style, or image-rendering catalog entry | A preferred catalog seed plus a concise Style-owned overlay | A duplicated copy of the catalog file |++Preserve source provenance in `Style Overview`. Keep exact user-authored method decisions distinct from AI-derived defaults. Reject organization-confidential examples and do not generalize proprietary frameworks into a reusable Style.++**Reference — not a constraint**: A Style may prefer a catalog mode, visual style, image rendering, fallback palette, or fallback font stack. These values seed the normal Stage-2 solution; they are not execution locks and never bypass user confirmation.++## 2. Style Brief and Schema++Add these child-owned requirements to Create Template Step 2:++| Field | Requirement |+|---|---|+| Style ID and display name | Required; `style_id` is a filesystem-safe portable slug (prefer ASCII for interoperability) |+| Best fit | Required; describe reusable decision, explanation, or expression situations without binding a target audience or outcome |+| Reusable intent | Required; state what the method and design defaults should consistently achieve |+| Communication method | Required; argument flow, page-message discipline, and claim/evidence treatment; a preferred mode is optional |+| Page-role vocabulary | Required; reusable semantic roles and their jobs, evidence obligations, and composition tendencies; no order or inclusion policy |+| Evidence and data expression | Required; chart, table, source, and editability guidance without numeric content quotas |+| Visual-system defaults | Required; composition, density, decoration, color behavior, and typography character; catalog seeds and literal fallbacks are optional |+| Image and icon direction | Required; rendering, usage, and treatment defaults without asset inventory or page mapping |+| Review focus | Required; extra checks to apply only if the user explicitly activates visual review |++Write this roster-free schema:++```markdown+---+style_id: <confirmed slug>+kind: style+summary: <one-line reusable method and design-default fit>+keywords: [<three-to-five discovery tags>]+---++# <Style Name> — Style Specification++> Method and design defaults only. No project communication contract, brand identity, page structure, or SVG prototypes.++## I. Style Overview+| Property | Value |+|---|---|+| Style Name | <display name> |+| Best Fit | <reusable selection context> |+| Reusable Intent | <stable method/design outcome> |+| Sources | <source URLs, bundled references, or user brief; include date/version when known> |++## II. Communication Method+- **Preferred Mode**: <catalog id or custom; omit when none>+- **Mode References**: <catalog ids actually used by a custom seed; omit when none>+- **Mode Behavior**: <required for custom; omit for a preset>+- **Argument Flow**: <reusable reasoning progression>+- **Page Message Discipline**: <relationship among question, title, message, and proof>+- **Claim Discipline**: <treatment of facts, assumptions, implications, and recommendations>++## III. Page Role Vocabulary+| Role | Communication Job | Evidence Obligation | Composition Tendency |+|---|---|---|---|+| <semantic role> | <job> | <proof requirement> | <non-geometric tendency> |++## IV. Evidence & Data Expression+- **Argument Trace**: <claim-to-evidence relationship>+- **Charts**: <selection, labeling, annotation, and decoration behavior>+- **Tables**: <comparison, hierarchy, and emphasis behavior>+- **Sources**: <citation and uncertainty treatment>+- **Native Editability**: <when editable data/native shapes are preferred>++## V. Visual System Defaults+- **Preferred Visual Style**: <catalog id or custom; omit when none>+- **Visual Style References**: <catalog ids actually used by a custom seed; omit when none>+- **Visual Style Behavior**: <required for custom; omit for a preset>+- **Composition**: <page-scale relationships without fixed geometry>+- **Density**: <information and whitespace rhythm>+- **Decoration**: <shape, rule, elevation, and ornament behavior>+- **Color Behavior**: <role and contrast behavior; no identity claim>+- **Typography Character**: <hierarchy and register; no identity claim>++### Fallback Color Scheme+| Role | HEX | Purpose |+|---|---|---|+| <role> | #RRGGBB | <fallback use> |++### Fallback Typography+| Role | Primary | Fallback Tail | Character |+|---|---|---|---|+| <role> | <family> | <ordered fallbacks> | <typographic job> |++## VI. Image & Icon Direction+- **Preferred Image Rendering**: <catalog id or custom; omit when none>+- **Image Rendering References**: <catalog ids actually used by a custom seed; omit when none>+- **Image Rendering Behavior**: <required for custom; omit for a preset>+- **Image Usage**: <semantic role and frequency tendency>+- **Image Treatment**: <crop, framing, overlay, and caption behavior>+- **Icon Treatment**: <shape/stroke/fill behavior; actual library and inventory remain Stage-2 decisions>++## VII. Review Focus+<!-- visual-review-trigger: explicit-user-only -->+> Apply this section only after the user explicitly activates visual review. It never triggers that stage.++- <style-specific answer, evidence, hierarchy, legibility, or scan-path check>+```++`Fallback Color Scheme` and `Fallback Typography` are conditional; omit either subsection when the Style has no literal fallback values. Exact fallback colors use `#RRGGBB`. A supplied Brand or Deck identity replaces overlapping fallback colors, font families, voice, and icon identity as one identity decision; it does not erase the Style's communication method or evidence discipline.++`Preferred Mode`, `Preferred Visual Style`, and `Preferred Image Rendering` are recommendation seeds. The current project's confirmed Stage-2 values remain authoritative. A preset value must be a real ID in its matching catalog. For `custom`, retain only real catalog references actually used as a comma-separated ID list and include the matching behavior prose.++`Page Role Vocabulary` is a semantic vocabulary, not a Page Roster. Do not assign order, required/optional/repeatable status, page count, filenames, Master/Layout identities, slots, or fixed/replaceable/example-only content policy.++## 3. Materialize the Confirmed Style++Create Template supplies an already resolved and collision-checked `<template_workspace>`. Write only:++```text+<template_workspace>/+└── templates/+ └── design_spec.md+```++Do not create or adopt images, icons, SVGs, native payloads, or review exports. References remain textual provenance; they are not portable Style assets.++## 4. Style Validation++Return these facts to Create Template:++- `templates/design_spec.md` contains non-empty `style_id`, `kind: style`, `summary`, and three-to-five `keywords`; no other frontmatter field exists.+- `style_id` matches the confirmed workspace ID in library scope.+- Required sections I–VII exist; preset seeds resolve to real catalog IDs, while custom seeds include behavior prose and only real comma-separated catalog references.+- No `*.svg`, optional asset directory, review export, or native payload was created.+- No `primary_color`, canvas, page-count, page-type, replication, native-structure, Master/Layout, placeholder, Page Roster, or Signature Design Elements field exists.+- No current-project target audience, communication objective/outcome, delivery context, artifact afterlife, content outline, page assignment, icon inventory, or image-resource mapping exists.+- Brand-only identity sections (`Brand Overview`, `Color Scheme`, `Typography`, `Logo`, `Voice & Tone`, and `Icon Style`) and Deck-only `Template Overview` are absent. Conditional fallback subsections remain explicitly named `Fallback Color Scheme` and `Fallback Typography`.+- `Review Focus` contains exactly one `<!-- visual-review-trigger: explicit-user-only -->` marker; its localized prose explains the same boundary, and the section cannot activate visual review by itself.++For both scopes, Create Template Step 5 validates the portable Style contract without registration:++```bash+python3 skills/ppt-master/scripts/svg_quality_checker.py "<template_workspace>/templates" --template-mode+```++For `library` scope, additionally validate the directory/index identity with:++```bash+python3 skills/ppt-master/scripts/register_template.py <style_id> --kind style --dry-run+```++After that gate passes, Create Template Step 7 registers with:++```bash+python3 skills/ppt-master/scripts/register_template.py <style_id> --kind style+```++For `project` scope, run only the shared validator, skip both registrar commands, and report `Not registered (project workspace)`. Downstream consumption always uses the explicit workspace root through Generate PPTX Step 3; a bare Style name or ordinary style description never activates it.diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.mdindex 6097560d..c5165b24 100644--- a/skills/ppt-master/workflows/generate-pptx.md+++ b/skills/ppt-master/workflows/generate-pptx.md@@ -175,7 +175,7 @@ Read references/strategist.md| Deterministic trigger | Additional Strategist reference ||---|---|-| Step 3 installed an explicit Brand/Layout/Deck workspace | `references/strategist-template.md` |+| Step 3 installed an explicit Brand/Style/Layout/Deck workspace | `references/strategist-template.md` || The core's proposed Stage 2 `image_usage` contains a source other than `none`, the user supplied an explicit non-`none` image constraint, or formula-worthy content activates formula planning | `references/strategist-image.md` + `references/image-layout-spec.md` + `references/image-layout-patterns.md` before authoring image renderings, production detail, formula resources, or §VIII |Core chooses Stage-2 sources. Load it before Stage 2 for non-`none`, or after confirmation if `none` changes; do not backfill candidates. Retain for confirmed non-`none` or formulas; otherwise write no image rows. Bare template/style names do not load the template module.@@ -464,7 +464,7 @@ group on both pages.`template_reuse_scope: mirror|layout` pages MUST start from the complete `page_layouts` SVG, keep inherited visible objects, and preserve root Master/Layout identity plus stable atoms/slots. Strict preserves that reusable contract; under `layout`, the once-loaded Design Spec's `Template Application` may still authorize carrier text/tspan reflow inside unchanged slot bounds. Adaptive uses the current or new Layout key/name already declared by Strategist. If construction proves that fixed atoms or slot topology/bounds must change, stop and return upstream for Strategist to repair the owning plan and lock, validate and read back the affected fragments, then resume; Executor never mutates `spec_lock.md`. `mirror` changes only visible text values while preserving text/tspan topology and attributes. `style` follows the flat paragraph below without structure metadata.-`template_reuse_scope: style`, free-design, and brand-only pages use `pptx_structure.mode: flat`. Draw the complete page directly: keep backgrounds, repeated chrome, headings, text, images, and decoration as ordinary Slide-local SVG content. Do not plan `pptx_masters` / `pptx_layouts` / `page_pptx_layouts`, do not add root Master/Layout identity, and do not add `data-pptx-layer` or `data-pptx-placeholder` metadata. Group logical content normally with top-level `<g id>` elements. Export materializes one clean project-owned Master plus one Blank Layout, applies the locked theme colors/fonts/title-body defaults, removes stock content placeholders and unused built-in Layouts, and retains only the standard date/footer/slide-number capability hooks. It does not promote or deduplicate page content.+`template_reuse_scope: style`, Style-only, free-design, and brand-only pages use `pptx_structure.mode: flat`. A Style-only workspace always derives `template_reuse_scope: style`; Style never supplies prototype mappings. When fused with Layout/Deck, Style changes only Direction / method and follows the selected non-Style structure plan. On a flat page, draw the complete page directly: keep backgrounds, repeated chrome, headings, text, images, and decoration as ordinary Slide-local SVG content. Do not plan `pptx_masters` / `pptx_layouts` / `page_pptx_layouts`, do not add root Master/Layout identity, and do not add `data-pptx-layer` or `data-pptx-placeholder` metadata. Group logical content normally with top-level `<g id>` elements. Export materializes one clean project-owned Master plus one Blank Layout, applies the locked theme colors/fonts/title-body defaults, removes stock content placeholders and unused built-in Layouts, and retains only the standard date/footer/slide-number capability hooks. It does not promote or deduplicate page content.Do not duplicate specialized identity with `data-pptx-role`. Add it only to structural page-frame objects whose package, page-number, or animation behavior is not already expressed by `data-pptx-layer`, `data-pptx-placeholder`, or `data-pptx-replace-with`; such an element needs a stable unique `id`. Do not add generic content roles to ordinary titles, body text, cards, KPIs, diagrams, charts, icons, or images. Full contract: [`references/semantic-svg.md`](../references/semantic-svg.md).diff --git a/skills/ppt-master/workflows/index.md b/skills/ppt-master/workflows/index.mdindex 7413cacf..c77bf329 100644--- a/skills/ppt-master/workflows/index.md+++ b/skills/ppt-master/workflows/index.md@@ -23,6 +23,7 @@ Maintainer-only inventory for adding, moving, or removing workflow documents. Ru| `quick-generate` | Generation profile | [`profiles/quick-generate.md`](./profiles/quick-generate.md) | Generate PPTX direct SVG-to-PPTX short circuit || `apply-template-workspace` | Template-input stage | [`stages/apply-template-workspace.md`](./stages/apply-template-workspace.md) | Generate Step 3 || `create-brand` | Template child workflow | [`create-template/create-brand.md`](./create-template/create-brand.md) | Create Template |+| `create-style` | Template child workflow | [`create-template/create-style.md`](./create-template/create-style.md) | Create Template || `create-layout` | Template child workflow | [`create-template/create-layout.md`](./create-template/create-layout.md) | Create Template || `create-deck` | Template child workflow | [`create-template/create-deck.md`](./create-template/create-deck.md) | Create Template || `topic-research` | Factual-preparation stage | [`stages/topic-research.md`](./stages/topic-research.md) | Inside Generate Step 1 |diff --git a/skills/ppt-master/workflows/routing.md b/skills/ppt-master/workflows/routing.mdindex ab47723f..dd903aec 100644--- a/skills/ppt-master/workflows/routing.md+++ b/skills/ppt-master/workflows/routing.md@@ -31,7 +31,7 @@ route selection. After selection, the route authority owns execution.| Route | Request shape | Authority | Preconditions | Mutation model | Output contract ||---|---|---|---|---|---|| Generate PPTX | Create a new presentation; regenerate an existing deck visually; use source material or a topic; optionally apply an explicit template workspace | [`generate-pptx`](./generate-pptx.md) | Source facts exist or research can gather them; explicit quick intent activates its profile | Author new SVG pages and export a new PPTX | Default: spec, lock, SVG, validation, and PPTX; Quick: optional source/resource artifacts, no spec/lock, SVG, and one PPTX |-| Create Template | Create a reusable brand/layout/deck template from one or more PPTX/SVG files, images/PDFs, direct or file-based text, documents/websites, brand assets, or a mixed reference bundle | [`create-template`](./create-template.md) | A reusable-template request exists; reference material is optional, and project scope additionally requires an initialized target project | Author a new portable workspace; never modify any reference file in place | Workspace with required `templates/`, optional `images/` / `icons/`, and optional review `exports/` |+| Create Template | Create a reusable brand/style/layout/deck template from one or more PPTX/SVG files, images/PDFs, direct or file-based text, documents/websites, brand assets, or a mixed reference bundle | [`create-template`](./create-template.md) | A reusable-template request exists; reference material is optional, and project scope additionally requires an initialized target project | Author a new portable workspace; never modify any reference file in place | Workspace with required `templates/`, optional `images/` / `icons/`, and optional review `exports/` || Fill Native PPTX | Use a raw PPTX's native slide shells and replace/fill content | [`template-fill-pptx`](./template-fill-pptx.md) | Source PPTX plus new material/topic | Clone and patch PPTX through OOXML; no SVG pipeline | New filled PPTX in project `exports/` || Enhance Native PPTX | Keep a finished PPTX's visible slides stable while adding notes, audio, timings, or transitions | [`native-enhance-pptx`](./native-enhance-pptx.md) | Finished source PPTX exists | Append/update scoped OOXML parts; no slide regeneration | New enhanced PPTX in project `exports/` |@@ -45,7 +45,7 @@ route selection. After selection, the route authority owns execution.| Topic only, or supplied sources leave planning-critical factual gaps | Run [`topic-research`](./stages/topic-research.md) inside the selected Generate profile's source preparation: immediately for topic-only input, or after conversion and reading for source-backed input; research only the identified gaps || Existing PPTX may be split, merged, dropped, reordered, or re-outlined | Treat the PPTX as source content through [`generate-pptx`](./generate-pptx.md) Step 1 and its PPTX intake; continue the default pipeline unless explicit Quick Generate intent selected that profile || Existing PPTX must preserve wording, page count, and page order 1:1 | Activate the [`beautify-pptx`](./profiles/beautify-pptx.md) profile inside the main pipeline |-| Explicit current brand/layout/deck workspace root | Enter [`generate-pptx`](./generate-pptx.md) Step 3 and conditionally load [`apply-template-workspace`](./stages/apply-template-workspace.md); consume the workspace root, never only its inner `templates/` directory |+| Explicit current brand/style/layout/deck workspace root | Enter [`generate-pptx`](./generate-pptx.md) Step 3 and conditionally load [`apply-template-workspace`](./stages/apply-template-workspace.md); consume the workspace root, never only its inner `templates/` directory || Split-mode project resumes in a fresh chat | Run [`resume-execute`](./stages/resume-execute.md) inside the active Generate route || Existing generated project needs a deck-wide `colors.*` or universal `typography.font_family` substitution | Stay in Generate; load [`update_spec.py`](../scripts/docs/update_spec.md), honor its supported-key boundary, then rerun the final quality gate and Step 7 export || User explicitly requests spec refinement | Run [`refine-spec`](./stages/refine-spec.md) after Design Spec Gate 1 and before lock Gate 2 |@@ -78,14 +78,14 @@ Generate pipeline.When a PPTX already contains native Master/Layout parts, `create-template` mirror may read and preserve those existing package facts in the new workspace. It does not infer missing historical intent. An incomplete or legacy SVG package may guide `standard` / `fidelity` visually, but it is not mutated into a structured template and cannot claim source-topology recovery.-**Hard rule — no automatic structure upgrade**: Free-design and brand-only generation remains `pptx_structure.mode: flat`. Repeated Slide-local objects never trigger `structured`, Master/Layout promotion, placeholder inference, or deduplication. The minimal Master plus Blank Layout emitted by flat export is package scaffolding, not an inferred reusable design master.+**Hard rule — no automatic structure upgrade**: Free-design, brand-only, and style-only generation remains `pptx_structure.mode: flat`. Repeated Slide-local objects never trigger `structured`, Master/Layout promotion, placeholder inference, or deduplication. The minimal Master plus Blank Layout emitted by flat export is package scaffolding, not an inferred reusable design master.| Input | Route behavior ||---|---|| Raw PPTX called a template + new content | Fill Native PPTX unless the user explicitly asks for a reusable template workspace || Any supported reference bundle or direct-text brief + reusable template request | Create Template || Current template workspace root + content | [`generate-pptx`](./generate-pptx.md) Step 3 |-| Legacy-flat root with current `design_spec.md` and current SVG contract | [`apply-template-workspace`](./stages/apply-template-workspace.md) compatibility reader |+| Legacy-flat Brand/Layout/Deck root satisfying its current kind contract; Layout/Deck also require current structured SVGs | [`apply-template-workspace`](./stages/apply-template-workspace.md) compatibility reader; Style has no flat form || Semantic-legacy or incomplete structured package | Create a new workspace through Create Template; do not migrate in place || Request to add a master directly to an existing PPTX/SVG | Unsupported; explain the Create Template → Generate PPTX lifecycle |@@ -96,14 +96,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 |+| `style` | Dispatch to [`create-style`](./create-template/create-style.md); write reusable communication method and design direction only, with no SVG roster or native structure || `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 descriptive recurring-application context with integrated identity, structure, and an SVG roster |-Create Template remains the fixed route name and owns the shared contract. These three documents are mutually exclusive child workflows, not additional top-level routes.+Create Template remains the fixed route name and owns the shared contract. These four documents are mutually exclusive child workflows, not additional top-level routes.**Hard rule — classify reusable rules, not source completeness**: A completePPTX does not automatically select Deck. Use Brand when only identity is-stable; use Layout when structure is brand-neutral and the communication+stable; use Style when reusable communication method and design direction+should travel without identity truth, page prototypes, or native+structure; use Layout when structure is brand-neutral and the communicationapplication stays downstream-defined; use Deck when structure carries identityor reusable scenario/content semantics.@@ -133,6 +136,7 @@ For that Q&A only, read the matching discovery indexes:| Kind | Discovery index ||---|---|| Brand | [`brands_index.json`](../templates/brands/brands_index.json) |+| Style | [`styles_index.json`](../templates/styles/styles_index.json) || Layout | [`layouts_index.json`](../templates/layouts/layouts_index.json) || Deck | [`decks_index.json`](../templates/decks/decks_index.json) |diff --git a/skills/ppt-master/workflows/stages/apply-template-workspace.md b/skills/ppt-master/workflows/stages/apply-template-workspace.mdindex afed0385..a03782ad 100644--- a/skills/ppt-master/workflows/stages/apply-template-workspace.md+++ b/skills/ppt-master/workflows/stages/apply-template-workspace.md@@ -1,5 +1,5 @@----description: Conditional Generate-PPTX runbook for validating, installing, or fusing explicit Brand, Layout, and Deck workspaces.+description: Conditional Generate-PPTX runbook for validating, installing, or fusing explicit Brand, Style, Layout, and Deck workspaces.---# Apply Template Workspace Stage@@ -13,14 +13,14 @@ description: Conditional Generate-PPTX runbook for validating, installing, or fu| Input shape | Spec and SVG source | Asset source ||---|---|---|| Current workspace root | `<root>/templates/design_spec.md` and `<root>/templates/` | Existing `<root>/images/` and `<root>/icons/` |-| Compatible legacy-flat root | `<root>/design_spec.md` and current-contract SVGs under `<root>/` | Package-local files |+| Compatible legacy-flat Brand/Layout/Deck root | `<root>/design_spec.md`; Layout/Deck also require current-contract SVGs under `<root>/` | Package-local files || Current Create Template handoff | Its exact validated library or project workspace root | Existing portable sibling `images/` and `icons/`; already installed only when the root is the target project |-The spec frontmatter MUST declare `kind: brand`, `kind: layout`, or `kind: deck`. Do not accept only another project's inner `templates/` directory because that omits sibling assets.+The spec frontmatter MUST declare `kind: brand`, `kind: style`, `kind: layout`, or `kind: deck`. Do not accept only another project's inner `templates/` directory because that omits sibling assets.**Hard rule — raw source boundary**: A raw PPTX is not a Step 3 workspace. Raw PPTX plus new content uses [`template-fill-pptx`](../template-fill-pptx.md). When the user wants reusable SVG/template generation, run [`create-template`](../create-template.md) first and return with its validated workspace root. Never add Master/Layout/placeholder structure directly to an existing PPTX or SVG project.-**Compatibility gate**: Reject semantic-legacy or incomplete structured packages, including old baseline/distillation metadata, incomplete Master identity, or legacy direct atomic placeholders. Create a new current workspace through Create Template; use the original PPTX when native topology must be preserved. A legacy-flat directory is readable only when its SVG contract is current.+**Compatibility gate**: Reject semantic-legacy or incomplete structured packages, including old baseline/distillation metadata, incomplete Master identity, or legacy direct atomic placeholders. Create a new current workspace through Create Template; use the original PPTX when native topology must be preserved. A legacy-flat Brand/Layout/Deck directory is readable only when it satisfies its current kind contract; Layout/Deck also require a current structured SVG contract. Style has no legacy-flat form and always requires `<root>/templates/design_spec.md`.## 2. Read the Matching Schema@@ -29,14 +29,27 @@ Read [`templates/README.md`](../../templates/README.md), then only the README fo| Kind | Schema | Owned segment ||---|---|---|| `brand` | [`templates/brands/README.md`](../../templates/brands/README.md) | Identity: color, typography, logo, voice/tone, icon style |+| `style` | [`templates/styles/README.md`](../../templates/styles/README.md) | Direction/method: reusable communication method, visual language, composition, and information-expression defaults || `layout` | [`templates/layouts/README.md`](../../templates/layouts/README.md) | Structure: canvas, page structure, semantic text roles, page types, SVG roster || `deck` | [`templates/decks/README.md`](../../templates/decks/README.md) | Application plus integrated identity and structure |A Layout created with `mirror` remains eligible only when its source contract is brand-neutral and application-neutral. Keep a branded or application-bearing source as a Deck, or re-author it as Layout through `standard` / `fidelity`; do not remove those semantics through mirror.+Before mapping any current workspace, run its shared package validator from the+workspace root. This is the same schema authority used during creation and+library registration; Brand/Style pass without SVG, while Layout/Deck validate+their roster and structure:++```bash+python3 skills/ppt-master/scripts/svg_quality_checker.py "<workspace_root>/templates" --template-mode+```++Any error blocks installation. A compatible legacy-flat root uses its own root+as the checker target.+## 3. Structured Preflight-Before copying a Deck or Layout workspace, inspect every SVG root and slot:+Before copying a Deck or Layout workspace, inspect every SVG root and slot. Brand and Style workspaces are roster-free and skip this structured preflight:- Every page declares root Master/Layout keys and PowerPoint picker names.- Master/Layout visuals are direct atoms, not generic layer `<g>` wrappers.@@ -49,6 +62,7 @@ Before copying a Deck or Layout workspace, inspect every SVG root and slot:| Kind | Install behavior ||---|---|| `brand` | Install `templates/` plus existing `images/` and `icons/`; ignore `exports/`. Identity is constrained; structure remains free. |+| `style` | Install `templates/design_spec.md` only. Ignore sibling project scaffolding and reject a library Style carrying asset/review payloads. Expose reusable direction/method without identity truth, page prototypes, or native structure. Style-only and Style + Brand derive `template_reuse_scope: style` and stay flat; Style + Layout/Deck follows the selected structure plan. A Style workspace never activates visual review. || `layout` | Install the same portable roots. Expose the actual reusable structure; Strategist later inspects the prototypes and derives the application plan automatically. || `deck` | Install the same portable roots. Expose descriptive application context, identity, structure, and the actual prototype roster; Strategist compares them with the current communication contract and content, then derives the application plan automatically. |@@ -72,25 +86,26 @@ Multi-path fusion supports different kinds, or at most two workspaces of the sam### 5.1 Different Kinds-Use segment-level integer replacement; do not mix fields implicitly:+Resolve four whole segments instead of enumerating every kind combination. This table selects the starting workspace owner; explicit current user instructions and the final Strategist confirmation remain authoritative over every result:-| 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 | current Stage-1 communication contract |-| brand + deck | brand | deck | deck |-| layout + deck | deck | compatible layout | deck |-| brand + layout + deck | brand | compatible layout | deck |+| Segment | Starting owner |+|---|---|+| Identity | Brand, otherwise Deck, otherwise the current Stage-2 project decision. Style color/type/icon/image values are direction candidates, never identity truth. |+| Structure | A compatible Layout, otherwise Deck, otherwise free design. Style owns no canvas, prototype, Master/Layout, slot, or page mapping. |+| Application | The current Stage-1 communication contract, informed by Deck's descriptive recurring-application context when present. Style never supplies the current audience, outcome, page count, outline, or content. |+| Direction / method | Style, otherwise the current Stage-2 project decision. Actual Deck prototypes and Signature facts may inform compatibility, but Deck does not own the Style-only method segment. |++Replace each selected segment wholesale; do not mix its fields implicitly. Brand or Deck identity replaces any identity-adjacent defaults carried by Style. A Style direction may adapt to that resolved identity, but cannot relabel its candidates as official brand facts.Before Layout overrides Deck structure, verify that every required application/narrative/content role fits the Layout's page roles, slot types, and capacity. On mismatch, stop and surface exactly three remedies: retain Deck structure, select another Layout, or explicitly revise the application contract.+Before Style overlays Deck-derived prototype/visual guidance, verify that its communication method can serve the Deck application and that its composition requirements fit the selected Layout/Deck structure. On mismatch, stop and surface the conflicting segment facts; require the user to omit the Style, choose a compatible Style/structure, or explicitly revise the application contract. Do not silently weaken Style, Deck, or Layout to make the paths appear compatible.+Field-level micro-adjustments such as a primary-color override are not Step 3 fusion. Carry them into the normal Strategist confirmation fields.### 5.2 Same Kind-Do not use path order as priority. Report every segment-level difference and ask the user to choose workspace A, workspace B, or select per segment. Only the per-segment choice opens a segment-by-segment resolution. Do not resolve field-level conflicts here. Three or more same-kind paths require the user to converge to at most two.+Do not use path order as priority. Report every segment-level difference and ask the user to choose workspace A, workspace B, or select per segment. Only the per-segment choice opens a segment-by-segment resolution. Two Style workspaces conflict over the complete Direction / method segment. Do not resolve field-level conflicts here. Three or more same-kind paths require the user to converge to at most two.### 5.3 Fused Provenance@@ -100,18 +115,19 @@ Write one final `<project>/templates/design_spec.md`. Immediately under its H1,> **Fused from:**> - deck: `templates/decks/example/` (base)> - brand: `templates/brands/example/` (identity override)+> - style: `templates/styles/example/` (direction/method override)> - layout: `templates/layouts/example/` (structure override)> - conflicts resolved: Color Scheme from brand (user selected A)```-Single-path installs do not add provenance. Set fused frontmatter `kind` from the resulting capability: `deck` when identity and structure are both present, `layout` for structure only, or `brand` for identity only. A project-local Brand + Layout fusion uses `kind: deck` for routing but is not automatically a reusable library Deck; its application remains current-project context.+Single-path installs do not add provenance. Set fused frontmatter `kind` from the non-Style capability: `deck` when identity and structure are both present, `layout` for structure only, or `brand` for identity only. Use `kind: style` only for Style-only input. Adding Style to Brand, Layout, Deck, or Brand + Layout does not change that existing capability label; its Direction / method ownership stays explicit in the fused provenance and body. A project-local Brand + Layout fusion uses `kind: deck` for routing but is not automatically a reusable library Deck; its application remains current-project context.-**Completion receipt**: Report `roots=<normalized roots>; kinds=<kind per root>; install=<in-place|copied>; final_spec=<project_path>/templates/design_spec.md`.+**Completion receipt**: Report `roots=<normalized roots>; kinds=<kind per root>; segments=identity:<owner>,structure:<owner>,application:<owner>,direction:<owner>; install=<in-place|copied>; final_spec=<project_path>/templates/design_spec.md`.## ✅ Template Workspace Applied- [x] Every input was an explicit root satisfying a listed workspace contract or the exact current Create Template handoff-- [x] Kind schemas and structured SVG contracts passed preflight+- [x] Every kind schema passed preflight; structured SVG checks ran only for Layout/Deck inputs- [x] All collisions and fusion conflicts were resolved before one atomic install- [x] `<project_path>/templates/` and any portable sibling assets are complete- [ ] **Next**: Return to [`generate-pptx.md`](../generate-pptx.md) Step 4diff --git a/skills/ppt-master/workflows/stages/visual-review.md b/skills/ppt-master/workflows/stages/visual-review.mdindex f6e97575..cbd86d3e 100644--- a/skills/ppt-master/workflows/stages/visual-review.md+++ b/skills/ppt-master/workflows/stages/visual-review.md@@ -6,7 +6,7 @@ description: Optional quality-gate stage for per-page rubric-based visual review> Optional Generate-PPTX quality stage. Goal: reduce human iteration by letting AI subagents visually self-check each rendered slide against a fixed rubric and apply atomic position/spacing fixes.>-> Reads `<project>/svg_output/<page>.svg` and a pre-rendered PNG of each slide, then either applies a fix or flags `needs_human`. **Never touches** brand decisions, layout structure, or other files.+> Reads `<project>/svg_output/<page>.svg` and a pre-rendered PNG of each slide, then either applies a fix or flags `needs_human`. When an installed/fused Style exists, it also reads that workspace's `Review Focus` as supplemental acceptance context. **Never touches** brand decisions, layout structure, or other files.>> This stage is **context-independent** — invokable in a fresh chat session with only `<project_path>` as input. No upstream conversation context required.@@ -14,7 +14,7 @@ description: Optional quality-gate stage for per-page rubric-based visual reviewThis is an **optional auxiliary loop**, opt-in only. The [`generate-pptx`](../generate-pptx.md) Step 1–7 pipeline does not invoke it; trigger only when the user explicitly asks for a visual re-pass on the generated SVGs before export.-**Token cost**: each batch subagent re-reads the rubric + `design_spec.md` + `spec_lock.md` and processes K SVG+PNG pairs. For a 20-page deck with K=5, expect on the order of 100–150K additional input tokens on top of the main generation run.+**Token cost**: each batch subagent re-reads the rubric + `design_spec.md` + `spec_lock.md` + the short Style Review Focus when present, and processes K SVG+PNG pairs. For a 20-page deck with K=5, expect on the order of 100–150K additional input tokens on top of the main generation run.## When to Run@@ -73,7 +73,9 @@ If any page comes back with `"all_background": true` in the JSON summary, that p## Step 2 — Spawn the review team-Create a team and dispatch one orchestrator agent. The orchestrator partitions the N pages into batches of ≤ K pages (default **K = 5**) and spawns one subagent per batch **in parallel** (single message, `ceil(N/K)` parallel `Agent` calls). Each batch subagent reads the fixed inputs (rubric + `design_spec.md` + `spec_lock.md`) **once**, then iterates over its assigned pages sequentially.+Create a team and dispatch one orchestrator agent. The orchestrator partitions the N pages into batches of ≤ K pages (default **K = 5**) and spawns one subagent per batch **in parallel** (single message, `ceil(N/K)` parallel `Agent` calls). Each batch subagent reads the fixed inputs (rubric + `design_spec.md` + `spec_lock.md` + conditional Style Review Focus) **once**, then iterates over its assigned pages sequentially.++Before dispatch, inspect `<project>/templates/design_spec.md`. If it declares `kind: style` or its fused provenance contains an active Style segment, read only `## VII. Review Focus` once and include those checks in every batch prompt. Otherwise pass no Style supplement. This lookup never triggers visual review; it runs only after the user has already activated this stage. The supplement cannot weaken the fixed rubric or widen edit permissions.```textTeamCreate(team_name="visual-review-<project>", agent_type="orchestrator")@@ -92,8 +94,9 @@ The orchestrator prompt must be self-contained and is the **single** place where- Batch size `K` (default 5; raise to 10 for token-sensitive runs on large decks, lower to 3 for high-fidelity short decks — see rubric §6.1)- Iteration budget per page (default 1; 2 only for high-stakes / final-cut runs — see [Appendix: Iteration loop](#appendix-iteration-loop-opt-in))- Path to the rubric: `skills/ppt-master/references/visual-review.md`+- Style Review Focus excerpt, only when the conditional lookup above found one; preserve its wording and source path- Dispatch contract reference: rubric [§6](../../references/visual-review.md#6-dispatch--messaging-contract) (batched parallel spawn, self-contained prompts, mandatory `SendMessage` on idle, anonymous-name tolerance)-- Subagent forbid list: do not edit any other page, `design_spec.md`, `spec_lock.md`, `animations.json`, `image_prompts.json`, or `images/`+- Subagent forbid list: do not edit any other page, `design_spec.md`, `spec_lock.md`, `templates/design_spec.md`, `animations.json`, `image_prompts.json`, or `images/`**Host compatibility**: `TeamCreate` and `SendMessage` are Claude-Code-specific multi-agent primitives. On hosts without those primitives (Cursor, VS Code + Copilot, Codebuddy, etc.) the main agent processes batches sequentially — same partitioning, same per-batch prompts, no parallel dispatch. Token savings from shared fixed inputs still apply; wall-clock time grows roughly N/K-fold.