AI turns documents or topics into real, native PowerPoint decks—with native shapes, transitions and animations, data-backed charts and tables on demand, audio narration from speaker notes, and support for your own .pptx templates. · by Hugo He
docs(create-template): accept multi-channel reference bundles
hugohe340ffd4f4465b
diff --git a/AGENTS.md b/AGENTS.mdindex fa4f1294..c25cd0fd 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -21,7 +21,7 @@ PPT Master is an AI-driven presentation generation system. Multi-role collaborat## Execution Requirements-- For any `brand`, `layout`, or `deck` workspace creation, 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`, `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).- Technical SVG/PPT constraints live in [`skills/ppt-master/references/shared-standards.md`](skills/ppt-master/references/shared-standards.md).- 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/docs/technical-design.md b/docs/technical-design.mdindex 2d3da467..11b48dc0 100644--- a/docs/technical-design.md+++ b/docs/technical-design.md@@ -120,7 +120,7 @@ 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 a PPTX or design reference | Create Template (`create-template`) | the fixed entry dispatches one Create Brand, Create Layout, or Create Deck child workflow; the resulting workspace root later triggers Generate Step 3 and structured children may export a review PPTX |+| 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 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 |diff --git a/docs/templates-guide.md b/docs/templates-guide.mdindex 187d2a37..1f0a56b9 100644--- a/docs/templates-guide.md+++ b/docs/templates-guide.md@@ -109,7 +109,7 @@ When you describe a style, the AI doesn't pick a template — it interprets the## 2. Derive a new template (the focus)-Turn a PPT you like, a brand guideline, or an existing PPTX file into a PPT Master template. This is the core of this guide.+Turn one or more PPTX/SVG files, images/PDFs, documents/websites, brand assets, or direct written requirements into a PPT Master template. References may be combined, and a template may also be designed from a confirmed brief with no external source. This is the core of this guide.### Entry point: the `/create-template` workflow@@ -123,13 +123,15 @@ The workflow will then **mandatorily** confirm a template brief with you beforeThe entry name always remains **Create Template**. It dispatches exactly one child workflow: Create Brand for identity only, Create Layout for brand-neutral structure only, or Create Deck for identity and structure together (the default when both are needed). The selected child is not reconsidered inside the brief.-### Step 1 — Prepare reference material+### Step 1 — Prepare a reference bundle or brief-**Strongly recommended: hand over the original `.pptx` file.** The importer reads OOXML directly and extracts the Master, Layout, placeholder, theme, native-shape, and reusable-asset facts that are actually present and supported into layered analysis references. In `standard` / `fidelity`, Template_Designer uses them as visual reference and authors a new SVG roster plus a new Master/Layout/slot system. In mirror, it materializes those validated source facts into a new workspace without inventing missing topology or design intent. The original PPTX remains immutable analysis evidence and is not packaged into the new template.+You may provide direct conversation text, pasted requirements, Markdown/TXT, DOCX/PDF/HTML/URL, websites, images/screenshots, logo/icon/font assets, PPTX/SVG files, or any useful combination. The workflow analyzes every applicable channel, keeps source provenance, and surfaces conflicts in the mandatory brief instead of silently choosing one source. Exact values stated by you are decisions; traceable statements from identified manuals or official sites are facts; visual estimates and vague-text interpretations remain suggestions until confirmed.++**When an existing deck's native structure matters, hand over the original `.pptx` file.** The importer reads OOXML directly and extracts the Master, Layout, placeholder, theme, native-shape, and reusable-asset facts that are actually present and supported into layered analysis references. In `standard` / `fidelity`, Template_Designer uses them as visual reference and authors a new SVG roster plus a new Master/Layout/slot system. In mirror, it materializes those validated source facts into a new workspace without inventing missing topology or design intent. The original PPTX remains immutable analysis evidence and is not packaged into the new template.You can also design from scratch from a brand guideline: provide a logo, primary color HEX, fonts, tone description, and a few mood references — the AI will design the page skeletons on the spot. This suits brands that don't yet have a finished PPT, only a VI manual.-> **Fallback when no source PPTX exists**: a screenshot set (`cover.png` / `chapter.png` / `content.png` / `closing.png`, ...) still works, but fidelity drops noticeably — decoration, fonts, and layout details all rely on the AI's visual inference. Use `.pptx` whenever you can. Screenshots are better used as annotation alongside a PPTX ("this is the look I want") than as the sole reference.+> **Evidence boundary:** images, screenshots, text, documents, websites, and loose assets can independently drive `standard`. `fidelity` requires PPTX/SVG page evidence, while `mirror` requires an original PPTX or a complete current structured-SVG contract. Supplemental sources may clarify mirror evidence but cannot invent or change its native topology.### Step 2 — The template brief (mandatory confirmation)diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.mdindex 40591d90..0b9be61a 100644--- a/docs/zh/technical-design.md+++ b/docs/zh/technical-design.md@@ -121,7 +121,7 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使| 原生 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 或设计参考构建可复用模板工作区 | Create Template(`create-template`) | 固定入口只分派一个 Create Brand、Create Layout 或 Create Deck 子工作流;所得工作区根目录后续触发 Generate Step 3,结构型子工作流可导出审阅 PPTX |+| 用户想从一个或多个 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 替换 || 用户要求调整对象级动画顺序 / 效果 / 计时 | Generate PPTX + `customize-animations` 阶段 | 通过 `animations.json` 控制可选导出策略 || 用户要求预览、选择、注解或重导出浏览器编辑 | Generate PPTX + `live-preview` 阶段 | 注解只在规定交接点应用 |diff --git a/docs/zh/templates-guide.md b/docs/zh/templates-guide.mdindex 21bcb871..54996adb 100644--- a/docs/zh/templates-guide.md+++ b/docs/zh/templates-guide.md@@ -109,7 +109,7 @@ PPT Master 的“模板”是一份**结构 + 风格**的预设包:每张 SVG## 二、派生新模板(重点)-把你自己喜欢的 PPT、品牌指南、或一份现成的 PPTX,做成 PPT Master 可调用的模板。这是本文的核心。+把一个或多个 PPTX/SVG、图片/PDF、文档/网站、品牌资产或直接文字要求,做成 PPT Master 可调用的模板。参考材料可以混合使用,也可以不提供外部来源,仅根据确认后的简报从零设计。这是本文的核心。### 入口:`/create-template` 工作流@@ -123,13 +123,15 @@ PPT Master 的“模板”是一份**结构 + 风格**的预设包:每张 SVG入口名称始终保持 **Create Template**。它只分派一个子工作流:仅复用身份走 Create Brand,仅复用品牌中立的结构走 Create Layout,身份与结构一起复用走 Create Deck(两者都需要时默认选它)。子工作流一旦选定,不会在简报里再次选 kind。-### 第一步:准备参考材料+### 第一步:准备参考材料包或简报-**强烈推荐:直接给原始 `.pptx` 文件。** 导入器会读取 OOXML,把包内实际存在且受支持的 Master、Layout、placeholder、主题、原生形状与可复用素材事实提取成分层分析参考。`standard` / `fidelity` 把它们当视觉参考,创作新的 SVG roster 与 Master/Layout/slot 系统;mirror 则把这些已验证的来源事实物化到新工作区,不补造缺失拓扑或设计意图。原 PPTX 始终是不可变的分析证据,不进入新模板包。+你可以直接在对话中输入文字或粘贴要求,也可以提供 Markdown/TXT、DOCX/PDF/HTML/URL、网站、图片/截图、logo/icon/字体资产、PPTX/SVG,或这些材料的任意组合。工作流会分析每个适用通道,保留来源,并在强制简报中暴露冲突,而不是静默选择某一个来源。你明确写出的值属于决策;来自已识别手册或官网的可追溯陈述属于事实;视觉估算与模糊文字的解释在确认前都只是建议。++**当现有演示文稿的原生结构很重要时,请直接提供原始 `.pptx` 文件。** 导入器会读取 OOXML,把包内实际存在且受支持的 Master、Layout、placeholder、主题、原生形状与可复用素材事实提取成分层分析参考。`standard` / `fidelity` 把它们当视觉参考,创作新的 SVG roster 与 Master/Layout/slot 系统;mirror 则把这些已验证的来源事实物化到新工作区,不补造缺失拓扑或设计意图。原 PPTX 始终是不可变的分析证据,不进入新模板包。也可以基于品牌指南从零设计:提供 logo、主色 HEX、字体、调性描述、几张氛围参考图,AI 会现场设计页面骨架。适合品牌方还没有成型 PPT、只有 VI 手册的场景。-> **没有源 PPTX 时的兜底**:截图集(`cover.png` / `chapter.png` / `content.png` / `closing.png` 等)也能跑,但保真度会明显下降——装饰、字体、版式细节都靠 AI 视觉推断。能拿到 `.pptx` 就尽量用 `.pptx`。截图更适合作为标注辅助("这页是我想要的样子")混进 PPTX 一起给。+> **证据边界:** 图片、截图、文字、文档、网站和零散资产都可以独立驱动 `standard`。`fidelity` 需要 PPTX/SVG 页面证据;`mirror` 需要原始 PPTX 或完整的当前结构化 SVG 合同。补充来源可以解释 mirror 证据,但不能补造或改变其原生拓扑。### 第二步:模板简报(强制确认环节)diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.mdindex b040428e..7236d163 100644--- a/skills/ppt-master/SKILL.md+++ b/skills/ppt-master/SKILL.md@@ -125,7 +125,7 @@ For complete tool documentation, see `${SKILL_DIR}/scripts/README.md`.| Raw PPTX template plus new material/topic, generate a PPTX | [`template-fill-pptx`](workflows/template-fill-pptx.md) || Existing PPTX, preserve page count/order and slide wording 1:1, improve layout | Main pipeline with the [`beautify-pptx`](workflows/profiles/beautify-pptx.md) profile || Existing PPTX as source material, rethink outline or change page count/order | Main pipeline via `source_to_md.py` plus PPTX intake |-| Build a reusable Brand, Layout, or Deck workspace from a PPTX/design reference | [`create-template`](workflows/create-template.md), which dispatches one matching child workflow, then return with the generated template workspace path |+| Build a reusable Brand, Layout, or Deck workspace from one or more PPTX/SVG files, images/PDFs, documents/websites, brand assets, direct-text requirements, or a mixed reference bundle | [`create-template`](workflows/create-template.md), which dispatches one matching child workflow, then return with the generated template workspace path || Finished PPTX, keep content/layout stable and add notes/audio/timing/transitions | [`native-enhance-pptx`](workflows/native-enhance-pptx.md) |**MUST**: Raw `.pptx` template plus "generate PPTX" routes to `template-fill-pptx` by default. The SVG generation route consumes only an explicit template workspace path with a valid `templates/design_spec.md`, or a compatible flat-directory current-contract root with `design_spec.md`. Semantic-legacy packages are rejected and must be replaced through Create Template.diff --git a/skills/ppt-master/workflows/create-template.md b/skills/ppt-master/workflows/create-template.mdindex 89f77d12..d111f1b0 100644--- a/skills/ppt-master/workflows/create-template.md+++ b/skills/ppt-master/workflows/create-template.md@@ -8,7 +8,7 @@ description: Create Template entry workflow and shared contract for the Create B>> **Role invoked for Create Layout/Create Deck**: [Template_Designer](../references/template-designer.md)-Create one reusable template workspace under either the **global template library** or `projects/` by dispatching to exactly one child workflow.+Create one reusable template workspace under either the **global template library** or `projects/` from one or more reference channels or a direct user brief, then dispatch to exactly one child workflow.**Default — library scope**: Write `skills/ppt-master/templates/<kind_dir>/<template_id>/` and register it in the matching discovery index.@@ -65,7 +65,7 @@ Any failed check aborts before writing `design_spec.md`, SVGs, images, icons, or## Process Overview```-Reference Intake & Analysis -> Fact-Based Brief Proposal -> User Confirmation Gate -> Preflight + Invoke Selected Child -> Validate Child Output -> [Structured Review PPTX: optional for one Master, required for multi-Master] -> [Register Library Index] -> Output+Reference Bundle Intake & Analysis -> Fact-Based Brief Proposal -> User Confirmation Gate -> Preflight + Invoke Selected Child -> Validate Child Output -> [Structured Review PPTX: optional for one Master, required for multi-Master] -> [Register Library Index] -> Output```The first three steps derive the brief from facts, not guesses. **No final template directory may be created and no template SVG / `design_spec.md` may be written until `[TEMPLATE_BRIEF_CONFIRMED]` is emitted in Step 3.** Reference-analysis intermediates produced by `pptx_template_import.py` (typically under `/tmp/pptx_template_import/`) are explicitly **not** subject to this gate — they are temporary workspaces feeding Step 2.@@ -74,22 +74,30 @@ After dispatch, the selected child workflow executes these shared steps with its----## Step 1: Reference Intake & Analysis+## Step 1: Reference Bundle Intake & Analysis-Branch by the type of reference source the user supplied. 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 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 replication-mode column applies to Create Layout/Create Deck. Create Brand uses the same reference formats for identity evidence but has no replication mode, SVG roster, or native-structure path.+The rows are evidence channels, not mutually exclusive routes. Run every matching row and retain source-level provenance. The replication-mode column applies to Create Layout/Create Deck. Create Brand uses the same reference formats for identity evidence but has no replication mode, SVG roster, or native-structure path.| Type | What the user supplied | Tool / read path | Replication modes available ||------|-------------------------|------------------|------------------------------|| **A** `.pptx` reference | A `.pptx` file path | `pptx_template_import.py` → `manifest.json` + `native_structure.json` + `source_template.pptx` + layered SVGs + `assets/`; flat verification SVGs are opt-in | `standard` / `fidelity` / `mirror` || **B** Existing SVG assets | `projects/<x>/svg_output/`, a current template workspace root, a legacy flat template root, or a loose `.svg` folder | Normalize the source directory, create an editable authoring IR bundle with `svg_authoring_view.py`, then use its page SVGs; also read companion `design_spec.md` / `spec_lock.md` when present | `standard` / `fidelity`; `mirror` only when the source already carries a complete explicit Master/Layout/placeholder/native-object contract |-| **C** Image / visual references | Screenshot folder, single image, PDF pages | `ls` + `Read` each file (multimodal visual recognition) | `standard` only |-| **D** No reference source | Verbal description only ("McKinsey style", "tech blue", "dark minimal") | — | `standard` only |+| **C** Image / visual references | PNG/JPG/WebP images, screenshots, moodboards, PDF page visuals, or a visual-reference folder | `ls` + `Read` each supplied visual or PDF (multimodal recognition) | `standard` only by itself |+| **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 |-`fidelity` and `mirror` are not available for type C / D — visual references and verbal-only briefs cannot drive page-by-page replication. Type A is the canonical mirror path: `manifest.json`, `native_structure.json`, layered lossless `svg/`, and inheritance facts describe the native structure that still exists in the PPTX package. Optional `svg-flat/` files are complete-page verification views, never structure authority. In `standard` / `fidelity`, imported facts and visuals do not define output topology.+| Bundle rule | Behavior |+|---|---|+| Combine channels | `standard` may use every confirmed visual, textual, documentary, web, and asset source together. Do not force the user to choose one source type. |+| Determine mode eligibility | `fidelity` requires Type A or B page evidence. `mirror` requires Type A or a complete current Type B structure contract. Type C/D/E evidence may supplement an eligible bundle but never creates native topology. |+| Preserve provenance | Keep facts, explicit user decisions, and AI suggestions distinct. Surface contradictions in Step 2 instead of resolving them silently. |+| Protect mirror | Supplemental text, images, websites, or assets may explain the source but cannot alter a confirmed `mirror` graph or visuals. Use `standard` / `fidelity` when the user wants those inputs to change the resulting system. |++Type A is the canonical mirror path: `manifest.json`, `native_structure.json`, layered lossless `svg/`, and inheritance facts describe the native structure that still exists in the PPTX package. Optional `svg-flat/` files are complete-page verification views, never structure authority. In `standard` / `fidelity`, imported facts and visuals do not define output topology.**Type B source normalization**: when the supplied root contains `templates/design_spec.md`, use `<input>/templates/` as the SVG/spec source and resolve its workspace assets from sibling `<input>/images/` and `<input>/icons/`. Otherwise, use the supplied directory itself as the legacy-flat/loose SVG source. Directory flatness is not a semantic-structure signal.@@ -310,9 +318,27 @@ If a `design_spec.md` or `spec_lock.md` accompanies the SVGs, read it too. In miBe explicit in Step 2 that exact HEX values, font names, and placeholder structure are **estimates from visual inspection** (`[suggested]`), never `[fact]`.-### 1D. No reference source+### 1D. Text, document, website, and asset references++Direct text in the conversation is already a valid input; do not require the user to save it as a file. Read Markdown/TXT directly. Convert supported document or website inputs into a temporary analysis workspace so the reference file or final template workspace is not modified:++```bash+python3 skills/ppt-master/scripts/source_to_md.py "<file_or_URL_or_dir>" -o "<text_analysis_workspace>"+```++Inventory explicitly supplied logo, icon, font, and other brand/design assets. Raster assets also enter the Type C visual pass; readable SVG assets may additionally enter Type B when they are page/template SVGs. Do not infer asset licensing, official status, or native PowerPoint structure from filenames alone.++Extract only what the source actually states:++- Identity rules: colors, typography, logo usage, voice, icon style, and explicit exclusions.+- Structure rules: canvas, page types, grids, zones, placeholders, density, image behavior, and requested variants.+- Deck context: use cases, design intent, presentation rhythm, examples, and negative requirements.++Treat an explicit value written by the user as `[decision]`. Treat a statement as `[fact]` only when it comes from an identified source such as an official manual or website. Any interpretation of vague prose remains `[suggested]` and must pass the Step 3 confirmation gate. Text and asset evidence never supplies Master/Layout topology by itself.++### 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.+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.---@@ -320,13 +346,13 @@ Skip the analysis. Step 2 will list every Required item as `[decision]`; nothingCompose a single message that surfaces every Required brief item to the user, **labelling each value's provenance**:-- **`[fact]`** — extracted from Step 1 analysis (e.g. theme color from `manifest.json`)+- **`[fact]`** — extracted from a traceable Step 1 source (e.g. theme color from `manifest.json` or an identified official manual)- **`[suggested]`** — AI-inferred from analysis or context (e.g. tone summary, applicable scenarios; visually estimated values from type C)-- **`[decision]`** — pure user choice, no analysis substitute (e.g. `template_id`, `replication mode`, `category`)+- **`[decision]`** — an explicit user instruction or choice, including exact values supplied directly in conversation (e.g. `template_id`, replication mode, category, palette, or layout rule)**Language adaptation rule**: write the Step 2 brief in the user's language. For technical enum values, show the localized label first and keep the English ID in parentheses only when needed for precision, for example `<localized deck label> (deck)`, `<localized layout label> (layout)`, or `<localized mirror label> (mirror)`. Do not assume users know what each English word means.-**Option visibility rule**: for every field with a finite option set, show both the recommended value and the other valid options. Do not present a single recommended value as if no alternatives exist. If an option is unavailable for the current input type, list it under `Unavailable` with the reason.+**Option visibility rule**: for every field with a finite option set, show both the recommended value and the other valid options. Do not present a single recommended value as if no alternatives exist. If an option is unavailable for the current bundle evidence, list it under `Unavailable` with the reason.| Field | Must show ||---|---|@@ -343,7 +369,7 @@ Compose a single message that surfaces every Required brief item to the user, **Items to surface:-| Item | Required | Provenance by input type |+| Item | Required | Provenance by evidence channel ||------|----------|--------------------------|| Output scope | Yes | `[decision]` — `library` (default, globally reusable and indexed) or `project` (same portable workspace routing under one initialized project) || Target project | Yes for `project`; N/A for `library` | `[decision]` — explicit path to the initialized target workspace; validate it during the Step 4 preflight |@@ -352,21 +378,21 @@ Items to surface:| Category | Create Layout/Create Deck only | `[decision]` — Create Deck: `brand` / `general` / `scenario` / `government` / `special`; Create Layout: `general` / `scenario` / `government` / `special` || Applicable scenarios | Yes | `[suggested]` from analysis; user confirms || Identity tone or structural summary | Yes | Create Brand/Create Deck: identity tone. Create Layout: structural use case and density/rhythm summary only. |-| Theme mode | Create Layout/Create Deck only | A: `[fact]` from `manifest.json` background colors. B: `[fact]` from SVG `fill`. C: `[suggested]` from visual estimate. D: `[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: `[decision]`, default `ppt169` (`1280x720`, `0 0 1280 720`) |-| Replication mode | Create Layout/Create Deck only | `[decision]` — `standard` always available; `fidelity` is available for A/B; `mirror` is available for A and for B sources with a complete explicit structure contract. `standard` / `fidelity` author new SVG semantics. Mirror retains one materialized prototype per source slide in source order and adds definition-only prototypes for source Layouts unused by those slides. Reject `fidelity` / `mirror` for C/D. |+| 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 identified source or `[decision]` from direct user text; 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 identified source or `[decision]` from direct user text when specified. E: `[decision]`, default `ppt169` (`1280x720`, `0 0 1280 720`). |+| Replication mode | Create Layout/Create Deck only | `[decision]` — `standard` is always available. `fidelity` requires A/B page evidence; `mirror` requires A or B with a complete explicit structure contract. C/D/E channels may supplement an eligible mixed bundle but do not establish mode eligibility. `standard` / `fidelity` author new SVG semantics. Mirror retains one materialized prototype per source slide in source order and adds definition-only prototypes for source Layouts unused by those slides. || Native structure facts | Create Layout/Create Deck with Type A or structured Type B | `[fact]` from `native_structure.json` / source SVG contract: master/layout counts, parentage, page assignments, placeholder identities, and multi-master status. Mirror preserves these validated facts in the new workspace; authored modes do not use them as output topology. || Mode-specific ownership | Create Layout/Create Deck only | `standard` / `fidelity`: `[decision]` newly authored Master/Layout ownership, including the reusable-family reason for every additional Master. `mirror`: `[fact]` source ownership mapped without synthesis. Every Master must own at least one emitted Layout and every Layout must have at least one emitted prototype; export never infers either contract. || Visual fidelity for fixed pages | Create Layout/Create Deck `standard` / `fidelity` when reference exists; **N/A for `mirror` and Create Brand** | `[decision]` — `literal` (closely reproduce reference geometry / decoration / sprite crops within a newly authored structure) or `adapted` (use reference tone/composition but allow design evolution). Different page types may take different settings. || Basic template norms | Yes when reference exists | Create Brand uses the identity fields and provenance rules from its child workflow. Create Layout/Create Deck use `[fact]` / `[suggested]` layout grammar, image system, density rhythm, page roster semantics, and asset policy from Step 1. || Reference source | Optional | already known if Step 1 ran |-| Theme color | Create Brand/Create Deck only | A: `[fact]` from theme XML. B: `[fact]` from dominant SVG `fill`. C: `[suggested]` from visual estimate (HEX is approximate). D: `[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 / D: not derivable — `[decision]` if the child owns a custom stack. Create Layout stores no typography system. |+| 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 identified source or `[decision]` from direct user text; 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 identified source or `[decision]` from direct user text. E: `[decision]` when a custom stack is wanted. Create Layout stores no typography system. || Design style | Optional | `[suggested]` from analysis |-| Assets list | Optional | A: `[fact]` from `assets/` listing; user picks which to bundle. B / C: `[decision]` per file. D: none |+| 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 |-For type A Create Layout/Create Deck execution, also include in this message:+When the bundle includes Type A for Create Layout/Create Deck, also include in this message:- the exact authoring-manifest documents required by the selected mode and verified during Step 1- a one-line summary of the source Master/Layout structure@@ -385,7 +411,7 @@ The user replies with corrections, additions, or "all good".1. Echo back the finalized brief (post-corrections) in a single message2. Emit the marker `[TEMPLATE_BRIEF_CONFIRMED]` on its own line-Skipping this gate — including silently inferring values from the reference source, opened IDE file, or prior conversation — is a route violation. Even if the user said "use this .pptx as a template" upfront, you MUST still surface Step 2 with provenance labels and obtain explicit confirmation here. The reference source informs the brief; it does not substitute for it.+Skipping this gate — including silently inferring values from reference files, direct text, an opened IDE file, or prior conversation — is a route violation. Even if the user already supplied a PPTX, image, website, document, asset bundle, or complete written brief, you MUST still surface Step 2 with provenance labels and obtain explicit confirmation here. The reference bundle informs the brief; it does not substitute for it.**Required outcome of Step 3** (all must be true before emitting `[TEMPLATE_BRIEF_CONFIRMED]`):@@ -395,7 +421,8 @@ Skipping this gate — including silently inferring values from the reference so- [ ] User has replied with values or explicit acceptance of suggested defaults- [ ] Output scope is confirmed; both scopes use the same workspace shape, while `project` includes an explicit initialized target-project path- [ ] For Create Layout/Create Deck, the canvas format is fixed before SVG generation-- [ ] For Create Layout/Create Deck, replication mode is consistent with the input type (`fidelity` allowed for A/B; `mirror` allowed for A and structured B only; both forbidden for C/D)+- [ ] For Create Layout/Create Deck, replication mode is consistent with the bundle evidence (`fidelity` requires A/B page evidence; `mirror` requires A or structured B; C/D/E channels alone permit only `standard`)+- [ ] 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- [ ] Child-specific norms from prior content have been surfaced and accepted, or explicitly marked N/A when no reference exists: identity/provenance for Create Brand; layout/image/density/asset behavior for Create Layout/Create Deck- [ ] For Create Layout/Create Deck, mode-specific ownership is explicit: `standard` / `fidelity` author a new structure without source-topology distillation; `mirror` maps validated source ownership one-to-one into a new workspace@@ -435,7 +462,7 @@ The preflight is atomic at the Create Template parent level: discover and settle**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.-If the input source is type A, pass the following internal package to the role:+When the bundle includes Type A, pass the following internal package to the role:- finalized brief from Step 3- `manifest.json`@@ -447,16 +474,18 @@ If the input source is type A, pass the following internal package to the role:- for `mirror` only, matching immutable `svg/` payload backing plus `svg/inheritance.json`; immutable `svg-flat/` remains an optional visual cross-check- optional screenshots, if available-For type B, pass the cleaned SVG file list from the analysis workspace, `*_vector_asset_inventory.json` if extraction ran, any companion `design_spec.md` / `spec_lock.md`, and the analysis notes. Do not bulk-read extracted vectors; open individual `icons/imported/*.svg` files only when needed.-For type C, pass the image file list and the visual analysis notes.-For type D, pass only the finalized brief.+When the bundle includes Type B, pass the cleaned SVG file list from the analysis workspace, `*_vector_asset_inventory.json` if extraction ran, any companion `design_spec.md` / `spec_lock.md`, and the analysis notes. Do not bulk-read extracted vectors; open individual `icons/imported/*.svg` files only when needed.+When the bundle includes Type C, pass the image file list and the visual analysis notes.+When the bundle includes Type D, pass the direct text, converted document/website outputs, traceable source list, explicit asset inventory, and analysis notes.+For Type E, pass only the finalized brief.+For a mixed reference bundle, pass the union of the applicable packages while keeping each fact's source and every unresolved conflict explicit.The role interprets the package according to replication mode:| Mode | Final SVG authority | Structure behavior ||---|---|---|| `standard` / `fidelity` | Newly authored SVGs based on the confirmed brief and visual references | Design an intentional new Master/Layout/slot system. Source topology is neither preserved nor distilled into the output. |-| `mirror` | Editable `authoring-svg/` IR plus native-structure facts and lossless payload backing | Restore source pages, Master/Layout identities and parentage, placeholder identity/bounds, ownership, and supported native-object metadata one-to-one. Materialization resolves unchanged source refs; it does not copy the lossless tree as the editable source. |+| `mirror` | Editable `authoring-svg/` IR plus native-structure facts and lossless payload backing | Materialize source pages, Master/Layout identities and parentage, placeholder identity/bounds, ownership, and supported native-object metadata one-to-one in the new workspace. Materialization resolves unchanged source refs; it does not copy the lossless tree as the editable source. |For Type A `mirror`, materialize the reviewed layered IR into an empty templateworkspace with the deterministic compiler:diff --git a/skills/ppt-master/workflows/create-template/create-brand.md b/skills/ppt-master/workflows/create-template/create-brand.mdindex 5122dfb7..14d1fe5b 100644--- a/skills/ppt-master/workflows/create-template/create-brand.md+++ b/skills/ppt-master/workflows/create-template/create-brand.md@@ -31,7 +31,9 @@ Enter this child workflow only after [`Create Template`](../create-template.md)| PNG/JPG logo | Inspect visually | Logo asset and approximate colors || Official brand site or manual | Convert/read the source | Published colors, fonts, voice, usage restrictions || Branded PPTX/PDF | Use the existing source converters and theme/package facts | Observed colors, typography, logo assets, and tone |+| Pasted text, Markdown, or text document | Use direct text or the parent workflow's converted text output | Explicit identity values, usage rules, voice, and restrictions || Verbal brief | Use the user's words directly | Any identity field the user explicitly supplies |+| Mixed reference bundle | Run every applicable row and retain per-source provenance | Combined identity evidence; unresolved conflicts go to the shared confirmation gate || No reference | No analysis | Empty skeleton only when the user explicitly requests it |Use these provenance labels in the proposal and final Color Scheme table:diff --git a/skills/ppt-master/workflows/create-template/create-deck.md b/skills/ppt-master/workflows/create-template/create-deck.mdindex 004ec43e..8cbe1b57 100644--- a/skills/ppt-master/workflows/create-template/create-deck.md+++ b/skills/ppt-master/workflows/create-template/create-deck.md@@ -32,6 +32,8 @@ Use Create Template Step 1 for source ingestion and replication-mode eligibility- Middle: use cases, design intent, presentation rhythm, and other deck-specific overview context.- `standard` and `fidelity` author a new complete system; source topology is not output topology. `mirror` preserves only validated package/contract facts in a new workspace and never modifies the source.+Direct conversation text, pasted requirements, converted documents/websites, images, and supplied assets are first-class evidence under Create Template Step 1. In a mixed bundle, combine the applicable identity, structure, and middle evidence without erasing provenance. Exact user instructions remain decisions; vague prose remains suggested interpretation until the shared confirmation gate.+Create Deck is the default child when identity and structure are both requested or when the source is a specific organization's branded presentation system. If the user explicitly wants identity-only or brand-neutral structure, return to Create Template dispatch before the shared confirmation marker is emitted.## 2. Deck Brief and Schemadiff --git a/skills/ppt-master/workflows/create-template/create-layout.md b/skills/ppt-master/workflows/create-template/create-layout.mdindex 6751c25e..76473993 100644--- a/skills/ppt-master/workflows/create-template/create-layout.md+++ b/skills/ppt-master/workflows/create-template/create-layout.md@@ -34,6 +34,8 @@ Use Create Template Step 1 for source ingestion and replication-mode eligibility- When the source is branded, explicitly confirm that Create Layout will strip that identity. If the user wants the identity retained with the structure, return to Create Template dispatch and select Create Deck before the shared confirmation marker is emitted.- `standard` and `fidelity` author a new Master/Layout/slot system. `mirror` is available only when the source contains a complete current structure contract and preserves validated structure facts in a new workspace without modifying the source.+Direct conversation text, pasted requirements, converted documents/websites, images, and supplied assets may define or illustrate reusable structure. In a mixed bundle, combine those channels without treating identity-only evidence as layout ownership. Exact user instructions remain decisions; vague prose remains suggested interpretation until the shared confirmation gate.+## 2. Layout Brief and SchemaAdd these child-owned requirements to Create Template Step 2:diff --git a/skills/ppt-master/workflows/index.md b/skills/ppt-master/workflows/index.mdindex e3dcf45f..728a1e1b 100644--- a/skills/ppt-master/workflows/index.md+++ b/skills/ppt-master/workflows/index.md@@ -15,7 +15,7 @@ Registry for the route authorities and supporting runbooks referenced by [`SKILL| Route | Authority | Trigger | Mutation model | Output ||---|---|---|---|---|| Generate PPTX | [`SKILL.md`](../SKILL.md) | Create or visually regenerate a presentation from source material, a topic, or an existing deck | Author new SVG pages, then export a new PPTX | Project workspace with `design_spec.md`, `spec_lock.md`, `svg_output/`, and `exports/` |-| Create Template | [`create-template.md`](./create-template.md) | Create a reusable `brand`, `layout`, or `deck` workspace | Read reference facts and author a new template workspace; never add Master/Layout structure to the reference file in place | Portable template workspace with required `templates/` and optional assets/review export |+| Create Template | [`create-template.md`](./create-template.md) | Create a reusable `brand`, `layout`, or `deck` workspace from one or more reference channels or a direct-text brief | Read the complete reference bundle and author a new template workspace; never add Master/Layout structure to a reference file in place | Portable template workspace with required `templates/` and optional assets/review export || Fill Native PPTX | [`template-fill-pptx.md`](./template-fill-pptx.md) | Reuse native slides from a raw PPTX and replace/fill their content | Clone and patch PPTX through OOXML; no SVG generation | New filled PPTX under the project `exports/` || Enhance Native PPTX | [`native-enhance-pptx.md`](./native-enhance-pptx.md) | Add notes, narration audio, timings, or transitions while preserving finished slides | Append/update scoped OOXML parts; no slide regeneration | New enhanced PPTX under the project `exports/` |diff --git a/skills/ppt-master/workflows/routing.md b/skills/ppt-master/workflows/routing.mdindex d74d3b45..b13e36a7 100644--- a/skills/ppt-master/workflows/routing.md+++ b/skills/ppt-master/workflows/routing.md@@ -29,7 +29,7 @@ Route selection authority for PPT Master. Select exactly one top-level route, th| 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 | Main [`SKILL.md`](../SKILL.md) | Source facts exist or the topic-research stage can gather them | Author new SVG pages and export a new PPTX | New project with `design_spec.md`, `spec_lock.md`, `svg_output/`, and `exports/` |-| Create Template | Create a reusable brand/layout/deck template from a PPTX, SVG, image/PDF reference, website/brand assets, or a verbal brief | [`create-template`](./create-template.md) | Reference material or an explicit template brief exists; project scope additionally requires an initialized target project | Author a new portable workspace; never modify the reference file in place | Workspace with required `templates/`, optional `images/` / `icons/`, and optional review `exports/` |+| 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/` || 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/` |@@ -71,7 +71,7 @@ When a PPTX already contains native Master/Layout parts, `create-template` mirro| Input | Route behavior ||---|---|| Raw PPTX called a template + new content | Fill Native PPTX unless the user explicitly asks for a reusable template workspace |-| PPTX/SVG/reference + reusable template request | Create Template |+| Any supported reference bundle or direct-text brief + reusable template request | Create Template || Current template workspace root + content | Generate PPTX Step 3 || Legacy-flat root with current `design_spec.md` and current SVG contract | Generate PPTX Step 3 compatibility reader || Semantic-legacy or incomplete structured package | Create a new workspace through Create Template; do not migrate in place |