Skip to content

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

refactor(template): trigger templates by explicit path only; drop slug matching

hugohe3b47e7ab64ef0
diff --git a/docs/templates-guide.md b/docs/templates-guide.md
index dbec8ca4..7836bd7b 100644
--- a/docs/templates-guide.md
+++ b/docs/templates-guide.md
@@ -14,40 +14,27 @@ This guide answers three questions:
### How to trigger
-The workflow **defaults to free design** — it will not ask whether you want a template and will not proactively suggest one. Templates are opt-in by **exact slug** only.
-
-### What is a slug?
-
-A slug is the unique identifier of a template — the directory name under [`templates/layouts/`](../skills/ppt-master/templates/layouts/) and equivalently the top-level key in [`layouts_index.json`](../skills/ppt-master/templates/layouts/layouts_index.json). All three are the same string. Examples:
-
-| Slug | Directory | Index key |
-|---|---|---|
-| `mckinsey` | `templates/layouts/mckinsey/` | `"mckinsey"` |
-| `academic_defense` | `templates/layouts/academic_defense/` | `"academic_defense"` |
-| `招商银行` | `templates/layouts/招商银行/` | `"招商银行"` |
-| `中国电建_常规` | `templates/layouts/中国电建_常规/` | `"中国电建_常规"` |
-
-Slugs are case-sensitive and must appear **verbatim** in your message to trigger the template flow.
+The workflow **defaults to free design** — it will not ask whether you want a template and will not proactively suggest one. Templates are opt-in by **explicit directory path** only: name the path in your initial message.
### How to enter the template flow
-Type a message that contains an exact slug, anywhere in the sentence:
+Send a path to a template directory in your initial message. Anywhere in the sentence is fine; the path just has to be unambiguous:
-> "use the **mckinsey** template for this report" ✅
-> "用 **academic_defense** 模板做这份汇报" ✅
-> "做一份 **招商银行** 风格的产品介绍" ✅
+> "use this template: `skills/ppt-master/templates/layouts/mckinsey/`" ✅
+> "用这个模板做汇报:`projects/last_deck/template/`" ✅
+> "做一份产品介绍,模板用 `/Users/me/Desktop/our_brand_v3/`" ✅
-The AI reads [`layouts_index.json`](../skills/ppt-master/templates/layouts/layouts_index.json), copies the template's SVGs, `design_spec.md`, and assets into your project, then proceeds to the Strategist phase. You can also point at the directory (`templates/layouts/mckinsey/`) and the AI will extract the slug from the path.
+The AI copies that directory's SVGs, `design_spec.md`, and assets into your project, then proceeds to the Strategist phase. The path can point to anywhere — the built-in library under `skills/ppt-master/templates/layouts/`, a previous project's `template/` folder, or any other location on disk.
### What does NOT trigger the template flow
-- **Style descriptions** that aren't slugs: "McKinsey style" / "Google style" / "麦肯锡那种" / "极简风" / "Keynote 风" → free design. The descriptive words flow into Strategist as a style brief, but no template is copied.
-- **Partial / ambiguous matches**: "中国电建" when the library has both `中国电建_常规` and `中国电建_现代` → free design. The AI does not guess; you can clarify which one if you wanted a template.
-- **Vague intent**: "想用个模板" / "I want a template" with no slug → free design.
+- **A bare template name without a path**: "use the mckinsey template" / "用 mckinsey 模板" / "做一份 academic_defense 模板的答辩" → free design. The AI does not look the name up. You must give a path.
+- **Style descriptions**: "McKinsey style" / "Google style" / "麦肯锡那种" / "极简风" / "Keynote 风" → free design. The descriptive words flow into Strategist as a style brief, but no template is copied.
+- **Vague intent**: "想用个模板" / "I want a template" with no path → free design.
-This is intentional — the AI never makes a fuzzy / interpretive judgment about whether your wording maps to a template. If you want a template, name it by its exact slug.
+This is intentional — the AI never makes a fuzzy / interpretive judgment about whether your wording maps to a template, and never resolves a name to a path on your behalf. If you want a template, give the path.
-To browse what's available, ask "what templates are available?" — the AI will list slugs from the index. Listing alone does not enter the template flow; you still need to repeat the chosen slug to trigger Step 3.
+To browse what's available in the built-in library, ask "what templates are available?" — the AI lists names and paths from the discovery index. Listing alone does not enter the template flow; you still need to send back a path to trigger Step 3.
### Template catalog
@@ -61,16 +48,16 @@ Free design is **not** "no style" — the AI designs a fresh visual system **for
### Styles are not templates
-A **style** is a description ("minimalist" / "Keynote-style" / "magazine 风") — a few words you type in chat. A **template** is a copy-and-paste asset bundle (SVGs + design_spec + assets) the workflow installs into your project when you type a slug exactly.
+A **style** is a description ("minimalist" / "Keynote-style" / "magazine 风") — a few words you type in chat. A **template** is a copy-and-paste asset bundle (SVGs + design_spec + assets) the workflow installs into your project when you give it an explicit directory path.
| | Template | Style |
|---|---|---|
-| How invoked | Exact slug in your message | Free-form description in your message |
+| How invoked | Explicit directory path in your message | Free-form description in your message |
| What happens | Files copied into project; layouts inherit from template SVGs | Words flow to Strategist; color / typography / tone proposed in Eight Confirmations |
| Locked values | Yes — values come from the template's `design_spec.md` | No — Strategist invents values that fit the deck |
| Best for | Brand-locked decks; scenarios with strong visual conventions | When you have a feel in mind but no specific brand commitment |
-A style mention may resemble a template name (e.g., "McKinsey style" looks like the `mckinsey` slug), but they go through different machinery — the slug match is a literal string check, the style mention is interpretive language. Same words, different paths.
+A style mention may resemble a template name (e.g., "McKinsey style" sounds like the `mckinsey/` template directory), but they go through different machinery — a template requires a real path the AI can copy from, a style mention is interpretive language. Similar words, different paths in the most literal sense.
### Common styles you can describe
@@ -108,7 +95,7 @@ Three axes, freely combinable ("dark tech + minimalist" or "magazine + neo-Chine
| **Memphis / pop** | High-saturation blocks, geometric, 80s |
| **Cyberpunk / vaporwave** | Neon purple-pink, grids, dreamlike |
-When you describe a style, the AI doesn't pick a template — it interprets the words and lands them in Layer 2 of confirmation `d` (Style Objective) inside Strategist's Eight Confirmations, which then drives e (color), f (icon), g (typography), and h (image). You confirm or refine. If the style you want happens to match one of our templates exactly (e.g., `academic_defense` / `mckinsey` / `pixel_retro`), you have a choice: name the slug for locked values, or describe the style for AI-interpreted values that adapt to your deck content.
+When you describe a style, the AI doesn't pick a template — it interprets the words and lands them in Layer 2 of confirmation `d` (Style Objective) inside Strategist's Eight Confirmations, which then drives e (color), f (icon), g (typography), and h (image). You confirm or refine. If the style you want happens to match one of our built-in templates (e.g., `academic_defense` / `mckinsey` / `pixel_retro`), you have a choice: send the template's directory path for locked values, or describe the style for AI-interpreted values that adapt to your deck content.
---
@@ -178,7 +165,7 @@ After generation, the workflow:
2. Registers the template ID in [`layouts_index.json`](../skills/ppt-master/templates/layouts/layouts_index.json)
3. Syncs the table in [`templates/layouts/README.md`](../skills/ppt-master/templates/layouts/README.md)
-Once registered, any future project can invoke it by saying "use the `<your_template_id>` template".
+Registration makes the template **discoverable** — when someone asks "what templates are available?", the AI lists it from the index. To use it in a new project, follow the SKILL.md Step 3 rule: name its directory path in your first message, e.g. `use this template: skills/ppt-master/templates/layouts/<your_template_id>/`.
### What a derived template looks like
diff --git a/docs/zh/templates-guide.md b/docs/zh/templates-guide.md
index b1e00c7c..1d5b7efa 100644
--- a/docs/zh/templates-guide.md
+++ b/docs/zh/templates-guide.md
@@ -14,40 +14,27 @@ PPT Master 的"模板"是一份**结构 + 风格**的预设包:包含若干页
### 触发方式
-工作流**默认走自由设计**——不会主动问你要不要用模板,也不会基于内容主动推荐模板。模板是 opt-in 的,**只接受精确 slug**。
-
-### 什么是 slug?
-
-slug 是模板的唯一标识——[`templates/layouts/`](../../skills/ppt-master/templates/layouts/) 下的目录名,同时也是 [`layouts_index.json`](../../skills/ppt-master/templates/layouts/layouts_index.json) 里的顶层 key,三者完全一致。例如:
-
-| slug | 目录 | 索引 key |
-|---|---|---|
-| `mckinsey` | `templates/layouts/mckinsey/` | `"mckinsey"` |
-| `academic_defense` | `templates/layouts/academic_defense/` | `"academic_defense"` |
-| `招商银行` | `templates/layouts/招商银行/` | `"招商银行"` |
-| `中国电建_常规` | `templates/layouts/中国电建_常规/` | `"中国电建_常规"` |
-
-slug 区分大小写,必须**一字不差**地出现在你的输入里才会触发模板流程。
+工作流**默认走自由设计**——不会主动问你要不要用模板,也不会基于内容主动推荐模板。模板是 opt-in 的,**只接受显式目录路径**:你在第一条消息里把模板目录的路径写出来。
### 怎么触发模板流程
-在对话里把 slug 写进去(位置不重要,只要出现即可):
+在对话里把模板目录的路径写进去(位置不重要,只要明确即可):
-> "用 **mckinsey** 模板做这份报告" ✅
-> "做一份 **academic_defense** 模板的答辩 PPT" ✅
-> "做一份 **招商银行** 风格的产品介绍" ✅
+> "用这个模板做:`skills/ppt-master/templates/layouts/mckinsey/`" ✅
+> "用上次那个模板:`projects/last_deck/template/`" ✅
+> "做一份产品介绍,模板用 `/Users/me/Desktop/our_brand_v3/`" ✅
-AI 会读取 [`layouts_index.json`](../../skills/ppt-master/templates/layouts/layouts_index.json),把对应模板的 SVG、`design_spec.md` 和素材复制到项目目录,然后进入 Strategist 阶段。你也可以直接给出目录路径(`templates/layouts/mckinsey/`),AI 从路径里抽 slug。
+AI 会把这个目录里的 SVG、`design_spec.md` 和素材复制到项目目录,然后进入 Strategist 阶段。路径可以是任意位置——内置库的 `skills/ppt-master/templates/layouts/` 下、上一个项目的 `template/` 文件夹、或者磁盘上其他任何地方都行。
### 什么**不会**触发模板流程
-- **不是 slug 的风格描述**:"麦肯锡风格" / "Google style" / "麦肯锡那种" / "极简风" / "Keynote 风" → 走自由设计。这些描述会顺着对话流到 Strategist 那边作为风格说明使用,但**不会复制任何模板文件**。
-- **不完整 / 有歧义的匹配**:"中国电建"——库里有 `中国电建_常规` 和 `中国电建_现代` 两个,没有唯一对应 → 走自由设计。AI 不替你猜(你可以再说一次精确的那个 slug 重新触发)。
-- **模糊意图**:"想用个模板" / "选一个吧"——没出现具体 slug → 走自由设计。
+- **只写模板名、不给路径**:"用 mckinsey 模板" / "做一份 academic_defense 模板的答辩 PPT" → 走自由设计。AI 不会替你把名字解析成路径。要用模板,请直接给路径。
+- **风格描述**:"麦肯锡风格" / "Google style" / "麦肯锡那种" / "极简风" / "Keynote 风" → 走自由设计。这些描述会顺着对话流到 Strategist 那边作为风格说明使用,但**不会复制任何模板文件**。
+- **模糊意图**:"想用个模板" / "选一个吧"——没给路径 → 走自由设计。
-这是有意的——AI 永远**不做模糊 / 解释性判断**,不替你决定模糊的描述对应哪个模板。要用模板,请用精确 slug 点名。
+这是有意的——AI 永远**不做模糊 / 解释性判断**,不替你把名字解析成路径。要用模板,直接给路径。
-想知道库里有哪些模板,问一句"有哪些模板可以用?"——AI 会从索引里列出 slug 清单。单纯列出并不进入模板流程,需要你再用其中一个 slug 重新说一次才会触发 Step 3。
+想知道内置库里有哪些模板,问一句"有哪些模板可以用?"——AI 会从发现索引里列出名字和对应路径。单纯列出并不进入模板流程,需要你**把其中一条路径**再发回来才会触发 Step 3。
### 现有模板一览
@@ -61,16 +48,16 @@ AI 会读取 [`layouts_index.json`](../../skills/ppt-master/templates/layouts/la
### 风格不是模板
-**风格**是一种描述("极简风" / "Keynote 风" / "杂志风")——你在对话里打几个字。**模板**是一份要复制粘贴的资产包(SVG + design_spec + 素材),只在你精确点出 slug 时由工作流安装到项目里。
+**风格**是一种描述("极简风" / "Keynote 风" / "杂志风")——你在对话里打几个字。**模板**是一份要复制粘贴的资产包(SVG + design_spec + 素材),只在你给出**显式目录路径**时由工作流安装到项目里。
| | 模板 | 风格 |
|---|---|---|
-| 怎么触发 | 消息里出现精确 slug | 消息里写自由描述 |
+| 怎么触发 | 消息里给出明确的目录路径 | 消息里写自由描述 |
| 发生什么 | 文件复制到项目;layouts 继承自模板 SVG | 描述流到 Strategist;色彩 / 字体 / 调性在八项确认里推荐 |
| 数值锁定 | 是 — 来源于模板的 `design_spec.md` | 否 — Strategist 现场推适合 deck 的具体值 |
| 适用场景 | 品牌锁定的 deck;强视觉约定的场景 | 心里有感觉但没有具体品牌承诺 |
-风格描述可能看起来像模板名(比如 "麦肯锡风格" 看上去像 `mckinsey` slug),但走的是**两套机制**——slug 匹配是字面字符串检查,风格描述是解释性语言。同样的字,路径不同。
+风格描述可能看起来像模板名(比如 "麦肯锡风格" 听上去像 `mckinsey/` 模板目录),但走的是**两套机制**——模板需要你给一个真实可复制的路径,风格描述是解释性语言。字面接近,落地完全是两条路。
### 常见风格描述
@@ -108,7 +95,7 @@ AI 会读取 [`layouts_index.json`](../../skills/ppt-master/templates/layouts/la
| **孟菲斯/波普风** | 高饱和大色块、几何图形、80 年代 |
| **赛博朋克/蒸汽波** | 霓虹紫粉、网格、迷幻 |
-你描述风格时,AI **不会基于这些词去挑模板**——它把这些词解释为对应的色彩 / 字体 / 版式建议,放到 Strategist 八项确认里 `d` 项的第二层(视觉风格),然后驱动 e/f/g/h(色彩 / 图标 / 字体 / 图片)。你可以确认或调整。如果你想要的风格刚好对上库里某个模板(如 `academic_defense` / `mckinsey` / `pixel_retro`),有两条路可选:用 slug 触发模板得到锁定值,或描述风格让 AI 现场推适配你内容的值。
+你描述风格时,AI **不会基于这些词去挑模板**——它把这些词解释为对应的色彩 / 字体 / 版式建议,放到 Strategist 八项确认里 `d` 项的第二层(视觉风格),然后驱动 e/f/g/h(色彩 / 图标 / 字体 / 图片)。你可以确认或调整。如果你想要的风格刚好对上库里某个模板(如 `academic_defense` / `mckinsey` / `pixel_retro`),有两条路可选:把模板的目录路径发出来锁定值,或描述风格让 AI 现场推适配你内容的值。
---
@@ -178,7 +165,7 @@ AI 会读取 [`layouts_index.json`](../../skills/ppt-master/templates/layouts/la
2. 把模板 ID 注册到 [`layouts_index.json`](../../skills/ppt-master/templates/layouts/layouts_index.json)
3. 同步 [`templates/layouts/README.md`](../../skills/ppt-master/templates/layouts/README.md) 表格
-注册完毕,下次任何项目里你说"用 `<你的模板 ID>` 模板",工作流就能找到它。
+注册让模板**可被发现**——下次有人问"有哪些模板可用?"时,AI 会从索引里把它列出来。要在新项目里用它,仍然按 SKILL.md Step 3 的规则:在第一条消息里把目录路径写出来,例如 `用这个模板:skills/ppt-master/templates/layouts/<your_template_id>/`。
### 派生后的目录长什么样
diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.md
index 265deb4a..0d0a897c 100644
--- a/skills/ppt-master/SKILL.md
+++ b/skills/ppt-master/SKILL.md
@@ -134,34 +134,36 @@ Import source content (choose based on the situation):
🚧 **GATE**: Step 2 complete; project directory structure is ready.
-**Default — free design.** Proceed directly to Step 4. Do NOT query `layouts_index.json` unless triggered. Do NOT ask the user. Do NOT proactively suggest, hint at, or fuzzy-match any template based on content or vague style descriptions.
+**Default — free design.** Proceed directly to Step 4. Do NOT query `layouts_index.json` unless triggered. Do NOT ask the user. Do NOT proactively suggest, hint at, or fuzzy-match any template based on content, slug-like words, or vague style descriptions.
-**Template flow triggers ONLY on exact slug.** A "slug" is the directory name under `templates/layouts/` and equivalently a top-level key in `layouts_index.json` (e.g. `mckinsey`, `academic_defense`, `中国电建_常规`). The trigger rule is mechanical, not interpretive:
+**Template flow triggers ONLY on an explicit template directory path** supplied by the user in their initial message. The trigger rule is mechanical, not interpretive:
| User input contains | Step 3 action |
|---|---|
-| An exact slug as a substring ("用 mckinsey 模板" / "use the academic_defense template" / "用 招商银行 模板") | Resolve via `layouts_index.json`, copy the template (SVGs + design_spec + assets) into the project, advance |
-| A path under `templates/layouts/<slug>/` | Same as above — extract slug from path, copy, advance |
-| Anything else — including style descriptions ("麦肯锡风格" / "Google style"), partial matches ("中国电建" when the library has `中国电建_常规` and `中国电建_现代`), vague intent ("想用个模板"), or silence | Skip Step 3, free design |
+| An explicit path to a template directory (e.g. `skills/ppt-master/templates/layouts/mckinsey/`, `projects/foo/template/`, or any other absolute / relative path that resolves to a directory containing `design_spec.md` and one or more page SVGs) | Copy that directory's SVGs + `design_spec.md` + assets into the project, advance |
+| Anything else — including bare template names ("用 mckinsey 模板"), style descriptions ("麦肯锡风格" / "Google style"), brand mentions ("招商银行风格"), vague intent ("想用个模板"), or silence | Skip Step 3, free design |
-The matcher is exact-slug substring matching — no semantic mapping, no near-name fuzzy matching, no AI judgment. If the user's text does not contain a slug verbatim, the template path does not trigger.
+There is no slug matching, no name lookup, no fuzzy resolution. A template name without a path does not trigger — the user must give a path the AI can `cd` into.
+
+The path may live anywhere — `skills/ppt-master/templates/layouts/<name>/` (the built-in library), `projects/<other_project>/template/` (reusing a previous project's templates), or any other location. Location is irrelevant; what matters is that the user named the path.
```bash
-cp ${SKILL_DIR}/templates/layouts/<slug>/*.svg <project_path>/templates/
-cp ${SKILL_DIR}/templates/layouts/<slug>/design_spec.md <project_path>/templates/
-cp ${SKILL_DIR}/templates/layouts/<slug>/*.png <project_path>/images/ 2>/dev/null || true
-cp ${SKILL_DIR}/templates/layouts/<slug>/*.jpg <project_path>/images/ 2>/dev/null || true
+TEMPLATE_DIR=<user-supplied path>
+cp ${TEMPLATE_DIR}/*.svg <project_path>/templates/
+cp ${TEMPLATE_DIR}/design_spec.md <project_path>/templates/
+cp ${TEMPLATE_DIR}/*.png <project_path>/images/ 2>/dev/null || true
+cp ${TEMPLATE_DIR}/*.jpg <project_path>/images/ 2>/dev/null || true
```
-> Style descriptions ("麦肯锡风格" / "Keynote 风" / "极简风" / etc.) are NOT slugs and never trigger Step 3. They flow naturally into Strategist's Eight Confirmations as part of the user's input — Strategist uses them as a style brief when proposing color / typography / tone in confirmations e and g.
+> Style descriptions ("麦肯锡风格" / "Keynote 风" / "极简风" / etc.) never trigger Step 3. They flow naturally into Strategist's Eight Confirmations as part of the user's input — Strategist uses them as a style brief when proposing color / typography / tone in confirmations e and g.
-> Partial matches ("中国电建" alone) do not auto-pick among `中国电建_常规` / `中国电建_现代` — that's the user's choice. AI may ask which one as normal dialogue, but does not guess.
+> Bare template names ("mckinsey", "招商银行") do NOT trigger Step 3 even if a folder by that name exists in the library. The user must give a path. AI must not "helpfully" resolve a name to a path.
-> "What templates exist?" is out-of-band Q&A — answer by listing entries from `layouts_index.json`. Listing alone does not advance the pipeline; only an exact slug match triggers the Step 3 copy.
+> "What templates exist?" is out-of-band Q&A — answer by listing entries from `layouts_index.json` together with their paths. Listing alone does not advance the pipeline; the user still has to send a path to trigger the Step 3 copy.
-> To create a new global template, read `workflows/create-template.md`.
+> To create a new template, read `workflows/create-template.md`.
-**✅ Checkpoint — Default path proceeds to Step 4 without user interaction. If the user's input contains an exact slug, that template is copied before advancing.**
+**✅ Checkpoint — Default path proceeds to Step 4 without user interaction. If the user's input contains an explicit template directory path, that directory is copied before advancing.**
---
diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.md
index 0d78634f..6d960e51 100644
--- a/skills/ppt-master/references/strategist.md
+++ b/skills/ppt-master/references/strategist.md
@@ -82,7 +82,7 @@ Anchors the downstream confirmations e (Color), f (Icon), g (Typography), h (Ima
Accept user combinations and one-off coinages ("Scandinavian + slight industrial"). The list is for recall, not constraint.
-> **Slug overlap**: a style mention may resemble a template slug (`mckinsey` slug vs "McKinsey style" descriptor). Step 3 has already resolved any slug match upstream — if a template was triggered, files are in `<project_path>/templates/`. Layer 2 only handles descriptors that did NOT trigger a slug match.
+> **Template vs descriptor**: a style mention may sound like a template name ("McKinsey style" vs the `mckinsey/` template directory). Step 3 only triggers on an explicit template directory path supplied by the user — bare names and style words never copy templates. If a template was triggered upstream, its files are already in `<project_path>/templates/`. Layer 2 only handles descriptors that did NOT come with a template path.
**Downstream effect**: e / f / g / h values realize the Layer 2 descriptor on top of the Layer 1 mode. Example: "A) Versatile + neo-Chinese" → e leans cinnabar / ink / rice-paper; g pairs serif (KaiTi-class) with sans body; f minimal line icons; h restrained traditional imagery with negative space.
diff --git a/skills/ppt-master/templates/README.md b/skills/ppt-master/templates/README.md
index 0ec10b68..0cdf9e03 100644
--- a/skills/ppt-master/templates/README.md
+++ b/skills/ppt-master/templates/README.md
@@ -19,7 +19,7 @@ The `layouts/` directory contains pre-built page layout templates organized by d
- **Academic Defense**: Academic defense style, research-oriented
- **Human browsing**: [layouts/README.md](./layouts/README.md)
-- **Slim lookup (opt-in)**: [layouts/layouts_index.json](./layouts/layouts_index.json) — only consulted when the user explicitly opts into the template flow
+- **Slim lookup (discovery only)**: [layouts/layouts_index.json](./layouts/layouts_index.json) — used to answer "what templates exist?". Step 3 triggers on an explicit directory path supplied by the user, not on names from this index.
## Visualization Templates
diff --git a/skills/ppt-master/templates/layouts/README.md b/skills/ppt-master/templates/layouts/README.md
index 1dafb789..98aa1a34 100644
--- a/skills/ppt-master/templates/layouts/README.md
+++ b/skills/ppt-master/templates/layouts/README.md
@@ -5,7 +5,7 @@ Pre-built PPT page layout templates supporting multiple styles and use cases.
- **Full Index**: [README.md](./README.md) (human browsing — includes categories, primary colors, detailed tone)
- **Slim Index**: [layouts_index.json](./layouts_index.json) (lightweight lookup — `summary` / `keywords` per template id)
-> **Template selection is opt-in.** The main workflow defaults to free design and does NOT read `layouts_index.json` unless the user explicitly requests a template. See `SKILL.md` Step 3.
+> **Template selection is opt-in by explicit path.** The main workflow defaults to free design. A template is only used when the user gives an explicit directory path (e.g. `skills/ppt-master/templates/layouts/mckinsey/` or any other path) in their initial message. Bare names like "mckinsey" do not trigger — `layouts_index.json` and this README are discovery aids for finding the path, not triggers in themselves. See `SKILL.md` Step 3.
---
@@ -196,20 +196,11 @@ Templates use `{{PLACEHOLDER}}` format to mark replaceable content:
## Usage
-### Copy from Template Library to Project
+To use a template, give the AI an explicit directory path in your initial message — e.g. "用 `skills/ppt-master/templates/layouts/mckinsey/` 这个模板做……". The Step 3 logic copies that directory's SVGs + `design_spec.md` + assets into your project before Strategist starts.
-```bash
-# Copy exhibit style template to project
-cp templates/layouts/exhibit/* projects/<project>/templates/
+The directory does not have to live under `templates/layouts/`. A template kept in `projects/<other_project>/template/` or any other location works the same way as long as you give the path.
-# Copy Google style template to project
-cp templates/layouts/google_style/* projects/<project>/templates/
-
-# Copy government style template to project (e.g., government red)
-cp templates/layouts/government_red/* projects/<project>/templates/
-```
-
-### After Copying
+After the copy:
1. Read `design_spec.md` to understand the design specification
2. Adjust colors based on project requirements (if needed)
@@ -230,7 +221,7 @@ cp templates/layouts/government_red/* projects/<project>/templates/
6. Validate the template directory with `python3 scripts/svg_quality_checker.py templates/layouts/<template_name> --format ppt169`
7. Register the new template by running `python3 scripts/register_template.py <template_id>` — it derives the `summary` and `keywords` index entry from `design_spec.md` and refreshes the Quick Index above
-`layouts_index.json` is the lightweight lookup used when a user explicitly opts into the template flow. A template folder without an index entry will not be discoverable by that flow.
+`layouts_index.json` is the lightweight lookup used to **discover** library templates (e.g. answering "what templates exist?"). It is not consulted when triggering Step 3 — Step 3 triggers on an explicit directory path the user supplied, regardless of whether that path is in the index. A template folder without an index entry still works fine if the user names its path; it just won't show up in discovery listings.
### SVG Technical Constraints (All Templates Must Comply)
diff --git a/skills/ppt-master/workflows/create-template.md b/skills/ppt-master/workflows/create-template.md
index 979955ce..bdc930ba 100644
--- a/skills/ppt-master/workflows/create-template.md
+++ b/skills/ppt-master/workflows/create-template.md
@@ -218,7 +218,7 @@ Outputs:
The completion card's file roster is collected by globbing `*.svg` in the template directory, so `fidelity`-mode templates that include variant pages such as `03a_content_two_col` are listed automatically.
-`layouts_index.json` is the lightweight lookup used when a user explicitly names a template. The main workflow defaults to free design and does not read this file unless the user has named a template (see `SKILL.md` Step 3). A template directory that has not been run through `register_template.py` will not be discoverable by that flow.
+`layouts_index.json` is a **discovery index** — it lets the AI answer "what templates are available?" by listing names and paths. It is **not** consulted to trigger Step 3. Step 3 triggers on an explicit directory path supplied by the user, regardless of whether that path is registered. A template directory that has not been run through `register_template.py` still works fine when the user gives its path; it just won't 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 the §I table and lets you set `category`, `keywords`, `summary`, etc. without relying on prose extraction:
>