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): default to free design; trigger templates by exact slug only

hugohe3f4b2ec13465e
diff --git a/AGENTS.md b/AGENTS.md
index 0283ece7..759a6682 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -8,7 +8,7 @@ Before any PPT generation task, **you MUST first read [`skills/ppt-master/SKILL.
PPT Master is an AI-driven presentation generation system. Multi-role collaboration (Strategist → Image_Generator → Executor) converts source documents (PDF/DOCX/URL/Markdown) into natively editable PPTX with real PowerPoint shapes (DrawingML).
-**Core Pipeline**: `Source Document → Create Project → Template Option → Strategist Eight Confirmations → [Image_Generator] → Executor → Quality Check → Post-processing → Export PPTX`
+**Core Pipeline**: `Source Document → Create Project → [Template] → Strategist Eight Confirmations → [Image_Generator] → Executor → Quality Check → Post-processing → Export PPTX`
> Topic-only requests with no source material: run the standalone [`topic-research`](skills/ppt-master/workflows/topic-research.md) workflow before SKILL.md Step 1 to gather web materials.
>
diff --git a/CLAUDE.md b/CLAUDE.md
index 6eb9e6af..9fe0f2e5 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -8,7 +8,7 @@ Before any PPT generation task, **you MUST first read [`skills/ppt-master/SKILL.
PPT Master is an AI-driven presentation generation system. Multi-role collaboration (Strategist → Image_Generator → Executor) converts source documents (PDF/DOCX/URL/Markdown) into natively editable PPTX with real PowerPoint shapes (DrawingML).
-**Core Pipeline**: `Source Document → Create Project → Template Option → Strategist Eight Confirmations → [Image_Generator] → Executor → Quality Check → Post-processing → Export PPTX`
+**Core Pipeline**: `Source Document → Create Project → [Template] → Strategist Eight Confirmations → [Image_Generator] → Executor → Quality Check → Post-processing → Export PPTX`
> Topic-only requests with no source material: run the standalone [`topic-research`](skills/ppt-master/workflows/topic-research.md) workflow before SKILL.md Step 1 to gather web materials.
>
diff --git a/docs/technical-design.md b/docs/technical-design.md
index 8a39c837..ec41f737 100644
--- a/docs/technical-design.md
+++ b/docs/technical-design.md
@@ -124,7 +124,7 @@ 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.
-**Soft-hint, not soft-prompt.** When the content is an obvious match for an existing template AND no trigger fired, Strategist emits a single non-blocking notice and continues with free design. The reason it's a hint rather than a question: blocking on every "you might want a template" prompt would erode the default pace of the flow, and the user can interrupt mid-stream anyway.
+**No proactive matching.** The AI does not suggest, hint at, or auto-map content to a template. Even when a deck looks like an obvious fit for an existing template, the AI stays silent and proceeds with free design unless the user has named the template. The reason is reliability over discoverability: matching content to templates is a judgment call that drifts as the library evolves, and a wrong "you might want X" pushes the user toward a commitment the AI cannot reliably make. Discoverability is handed to docs (`templates/layouts/README.md`) and to the explicit query path ("what templates are available?"), not the runtime prompt.
**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.
diff --git a/docs/templates-guide.md b/docs/templates-guide.md
index 9034c852..1f3b3da4 100644
--- a/docs/templates-guide.md
+++ b/docs/templates-guide.md
@@ -14,15 +14,40 @@ This guide answers three questions:
### How to trigger
-The workflow **defaults to free design** — it will not ask whether you want a template. To enter the template flow, give an explicit trigger in chat:
+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.
-| Trigger type | Example |
-|--------------|---------|
-| Name a specific template | "use the mckinsey template for this report" |
-| Name a style / brand reference | "McKinsey style" / "Google style" / "academic defense look" |
-| Ask for a list | "what templates are available?" |
+### What is a slug?
-On a hit, the AI reads [`templates/layouts/layouts_index.json`](../skills/ppt-master/templates/layouts/layouts_index.json), copies the matching template's SVGs, `design_spec.md`, and assets into the project's `templates/` directory, then proceeds to the Strategist phase.
+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.
+
+### How to enter the template flow
+
+Type a message that contains an exact slug, anywhere in the sentence:
+
+> "use the **mckinsey** template for this report" ✅
+> "用 **academic_defense** 模板做这份汇报" ✅
+> "做一份 **招商银行** 风格的产品介绍" ✅
+
+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.
+
+### 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.
+
+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.
+
+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.
### Template catalog
diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.md
index 492fae31..ba0047bb 100644
--- a/docs/zh/technical-design.md
+++ b/docs/zh/technical-design.md
@@ -124,7 +124,7 @@ PPT Master 不只服务 PPT——同一套 SVG → DrawingML 流水线还能产
**为什么默认自由设计。** 模板是地板,但很容易变成天花板:它会把整个 deck 锁进模板自有的视觉惯用语,无视内容本身想要怎样被呈现。自由设计的布局从源内容的结构推导而来,而不是从一套固定语法套上去——视觉节奏跟着内容走,而不是跟内容打架。约束模式在窄场景里确实更好(品牌锁定的 deck、强类型场景如学术答辩或政府报告),所以它一直在;但 AI 不主动去抓,是用户去抓。
-**软提示,不是软追问。** 当内容明显匹配某个模板而用户又没触发时,Strategist 发一句非阻塞的提示就继续按自由设计走。这里之所以是提示而不是问题:每次"也许你想用模板"都打断流,会侵蚀默认节奏;而用户随时可以中途打断,没有信息损失。
+**不主动匹配。** AI 不会基于内容向用户推荐、暗示或自动映射模板。即便某份 deck 看起来"明显适合"库里某个模板,没有用户点名,AI 也保持沉默,按自由设计走。理由是可靠性优先于发现性:把内容与模板做匹配是会随库演进而漂移的判断,一句错误的"或许你想用 X"会把用户推向 AI 本就无法可靠承诺的选择。发现性交给文档(`templates/layouts/README.md`)和显式查询路径("有哪些模板可以用?")承担,不放进运行时 prompt。
**布局是 opt-in,图表和图标不是。** 这种不对称不是矛盾——*布局*正是锁定视觉惯用语的那一层(地板/天花板问题),而图表和图标是不会施加 deck 级风格约束的复用原语。同一个 `templates/` 目录,但在视觉契约里扮演的角色不同。
diff --git a/docs/zh/templates-guide.md b/docs/zh/templates-guide.md
index 9a93fdd8..387e2338 100644
--- a/docs/zh/templates-guide.md
+++ b/docs/zh/templates-guide.md
@@ -14,15 +14,40 @@ PPT Master 的"模板"是一份**结构 + 风格**的预设包:包含若干页
### 触发方式
-工作流**默认走自由设计**——不会主动问你要不要用模板。要进入模板流程,在对话里给出明确触发即可:
+工作流**默认走自由设计**——不会主动问你要不要用模板,也不会基于内容主动推荐模板。模板是 opt-in 的,**只接受精确 slug**。
-| 触发类型 | 例子 |
-|----------|------|
-| 直接点名 | "用 mckinsey 模板做这份报告" |
-| 风格类比 | "麦肯锡那种风格" / "Google style" / "学术答辩样式" |
-| 列清单 | "有哪些模板可以用?" |
+### 什么是 slug?
-命中后,AI 会读取 [`templates/layouts/layouts_index.json`](../../skills/ppt-master/templates/layouts/layouts_index.json),把对应模板的 SVG、`design_spec.md` 和素材复制到当前项目的 `templates/` 目录,再进入策略师阶段。
+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 区分大小写,必须**一字不差**地出现在你的输入里才会触发模板流程。
+
+### 怎么触发模板流程
+
+在对话里把 slug 写进去(位置不重要,只要出现即可):
+
+> "用 **mckinsey** 模板做这份报告" ✅
+> "做一份 **academic_defense** 模板的答辩 PPT" ✅
+> "做一份 **招商银行** 风格的产品介绍" ✅
+
+AI 会读取 [`layouts_index.json`](../../skills/ppt-master/templates/layouts/layouts_index.json),把对应模板的 SVG、`design_spec.md` 和素材复制到项目目录,然后进入 Strategist 阶段。你也可以直接给出目录路径(`templates/layouts/mckinsey/`),AI 从路径里抽 slug。
+
+### 什么**不会**触发模板流程
+
+- **不是 slug 的风格描述**:"麦肯锡风格" / "Google style" / "麦肯锡那种" / "极简风" / "Keynote 风" → 走自由设计。这些描述会顺着对话流到 Strategist 那边作为风格说明使用,但**不会复制任何模板文件**。
+- **不完整 / 有歧义的匹配**:"中国电建"——库里有 `中国电建_常规` 和 `中国电建_现代` 两个,没有唯一对应 → 走自由设计。AI 不替你猜(你可以再说一次精确的那个 slug 重新触发)。
+- **模糊意图**:"想用个模板" / "选一个吧"——没出现具体 slug → 走自由设计。
+
+这是有意的——AI 永远**不做模糊 / 解释性判断**,不替你决定模糊的描述对应哪个模板。要用模板,请用精确 slug 点名。
+
+想知道库里有哪些模板,问一句"有哪些模板可以用?"——AI 会从索引里列出 slug 清单。单纯列出并不进入模板流程,需要你再用其中一个 slug 重新说一次才会触发 Step 3。
### 现有模板一览
diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.md
index 9b2247b5..265deb4a 100644
--- a/skills/ppt-master/SKILL.md
+++ b/skills/ppt-master/SKILL.md
@@ -11,7 +11,7 @@ description: >
> AI-driven multi-format SVG content generation system. Converts source documents into high-quality SVG pages through multi-role collaboration and exports to PPTX.
-**Core Pipeline**: `Source Document → Create Project → Template Option → Strategist → [Image_Generator] → Executor → Post-processing → Export`
+**Core Pipeline**: `Source Document → Create Project → [Template] → Strategist → [Image_Generator] → Executor → Post-processing → Export`
> [!CAUTION]
> ## 🚨 Global Execution Discipline (MANDATORY)
@@ -134,32 +134,34 @@ 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`. Do NOT ask the user an A/B template-vs-free-design question.
+**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.
-**Template flow is opt-in.** Enter it only when an explicit trigger appears in the user's prior messages:
+**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:
-1. Names a specific template (e.g., "用 mckinsey 模板" / "use the academic_defense template")
-2. Names a style / brand reference that maps to a template (e.g., "McKinsey 那种" / "Google style" / "学术答辩样式")
-3. Asks what templates exist (e.g., "有哪些模板可以用")
+| 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 |
-When triggered: read `${SKILL_DIR}/templates/layouts/layouts_index.json`, resolve the match (or list options for trigger 3), and copy:
+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.
```bash
-cp ${SKILL_DIR}/templates/layouts/<template_name>/*.svg <project_path>/templates/
-cp ${SKILL_DIR}/templates/layouts/<template_name>/design_spec.md <project_path>/templates/
-cp ${SKILL_DIR}/templates/layouts/<template_name>/*.png <project_path>/images/ 2>/dev/null || true
-cp ${SKILL_DIR}/templates/layouts/<template_name>/*.jpg <project_path>/images/ 2>/dev/null || true
+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
```
-**Soft hint (non-blocking).** When content is an obvious strong match for an existing template (e.g., academic defense, government report, McKinsey-style deck) AND no template trigger fired, emit a single-sentence notice and continue without waiting:
+> 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.
-> Note: the library has a template `<name>` that matches this scenario closely. Say the word if you want to use it; otherwise I'll continue with free design.
+> 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.
-Hint, not question — do NOT block. Skip entirely on weak/ambiguous match.
+> "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.
-> To create a new global template, read `workflows/create-template.md`
+> To create a new global template, read `workflows/create-template.md`.
-**✅ Checkpoint — Default path proceeds to Step 4 without user interaction. If a template trigger fired, template files are copied before advancing.**
+**✅ 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.**
---
diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.md
index 7303ea48..a56f16d9 100644
--- a/skills/ppt-master/references/strategist.md
+++ b/skills/ppt-master/references/strategist.md
@@ -24,7 +24,7 @@ As a top-tier AI presentation strategist, receive source documents, perform cont
⛔ **BLOCKING**: After the read, present professional recommendations for the eight items below as a bundled package and wait for explicit user confirmation.
-> **Execution discipline**: This is the last BLOCKING checkpoint (besides template selection). After confirmation, complete the Design Spec and proceed to image generation / SVG / post-processing without further pauses.
+> **Execution discipline**: This is the last BLOCKING checkpoint in the pipeline. After confirmation, complete the Design Spec and proceed to image generation / SVG / post-processing without further pauses.
### a. Canvas Format Confirmation
@@ -494,22 +494,22 @@ Save outputs to `projects/<project_name>_<format>_<YYYYMMDD>/design_spec.md`.
## 8. Complete Design Spec and Prompt Next Steps
-After writing `design_spec.md` and `spec_lock.md`, output the next-step prompt below based on template + image selection. This is a handoff instruction, not part of `design_spec.md`.
+After writing `design_spec.md` and `spec_lock.md`, output the next-step prompt below. This is a handoff instruction, not part of `design_spec.md`. Pick the variant by whether Step 3 copied a template into `<project_path>/templates/`.
-### Template Option A (Using existing template)
+### Template mode (template applied in Step 3)
```
✅ Design spec complete. Template ready.
Next step:
- Images include AI generation → Invoke Image_Generator
-- Images do not include AI generation → Invoke Executor
+- Otherwise → Invoke Executor
```
-### Template Option B (No template)
+### Free design (default, no template)
```
✅ Design spec complete.
Next step:
- Images include AI generation → Invoke Image_Generator
-- Images do not include AI generation → Invoke Executor (free design for every page)
+- Otherwise → Invoke Executor (free design for every page)
```
diff --git a/skills/ppt-master/scripts/register_template.py b/skills/ppt-master/scripts/register_template.py
index 2d6b3ee0..57ddc736 100644
--- a/skills/ppt-master/scripts/register_template.py
+++ b/skills/ppt-master/scripts/register_template.py
@@ -130,11 +130,6 @@ def _clean_field_value(value: str) -> str:
return value.strip()
-def _strip_paren_alias(value: str) -> str:
- """Drop a trailing ``(... alias ...)`` if the slug appears at the start."""
- return re.sub(r"\s*\([^)]*\)\s*$", "", value).strip()
-
-
def _find_first_color(section: str) -> str | None:
match = re.search(r"`(#[0-9A-Fa-f]{3,8})`", section)
return match.group(1).upper() if match else None
@@ -167,7 +162,7 @@ def _summary_from_use_cases(use_cases: str | None) -> str | None:
cleaned = use_cases.strip().rstrip(".")
if not cleaned:
return None
- return f"For {cleaned}."
+ return f"{cleaned}."
# ---------------------------------------------------------------------------
@@ -186,23 +181,6 @@ def _extract_entry(template_id: str, template_dir: Path) -> dict:
frontmatter, body = _read_spec(spec_path)
fm = frontmatter or {}
- label = fm.get("label")
- if not label:
- raw = _extract_section_field(
- body, "I. Template Overview", ["Template Name", "Name"]
- )
- if raw:
- # Prefer the human-facing form when present, else fall back to id.
- if "(" in raw and ")" in raw:
- inner = _clean_field_value(
- raw[raw.find("(") + 1: raw.rfind(")")]
- )
- label = inner or _strip_paren_alias(raw) or template_id
- else:
- label = _strip_paren_alias(raw) or template_id
- else:
- label = template_id
-
summary = fm.get("summary")
if not summary:
summary = _summary_from_use_cases(
@@ -239,13 +217,12 @@ def _extract_entry(template_id: str, template_dir: Path) -> dict:
pages = _list_pages(template_dir)
entry = OrderedDict(
- label=label,
summary=summary,
keywords=keywords,
- pages=pages,
)
extras = OrderedDict(
+ pages=pages,
category=str(category),
primary_color=str(primary_color or ""),
use_cases=str(use_cases),
@@ -365,8 +342,7 @@ def _print_completion_card(template_id: str, entry: dict, extras: dict) -> None:
print()
print("## Template Creation Complete")
print()
- print(f"**Template Name**: {template_id}"
- f" ({entry.get('label', template_id)})")
+ print(f"**Template Name**: {template_id}")
print(f"**Template Path**: `templates/layouts/{template_id}/`")
print(f"**Category**: {extras.get('category', 'general')}")
primary = extras.get("primary_color") or "—"
@@ -377,7 +353,7 @@ def _print_completion_card(template_id: str, entry: dict, extras: dict) -> None:
print()
print("| File | Status |")
print("|------|--------|")
- for page in entry.get("pages", []):
+ for page in extras.get("pages", []):
print(f"| `{page}.svg` | Done |")
print()
diff --git a/skills/ppt-master/templates/layouts/README.md b/skills/ppt-master/templates/layouts/README.md
index f999fd5f..1dafb789 100644
--- a/skills/ppt-master/templates/layouts/README.md
+++ b/skills/ppt-master/templates/layouts/README.md
@@ -3,7 +3,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 — `label` / `summary` / `keywords` / `pages`)
+- **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.
@@ -228,7 +228,7 @@ cp templates/layouts/government_red/* projects/<project>/templates/
4. All SVGs use `viewBox="0 0 1280 720"`
5. Follow SVG technical constraints (see below)
6. Validate the template directory with `python3 scripts/svg_quality_checker.py templates/layouts/<template_name> --format ppt169`
-7. Register the new template in `templates/layouts/layouts_index.json` with four fields: `label`, `summary`, `keywords`, `pages` (the SVG file stems shipped by the template)
+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.
diff --git a/skills/ppt-master/templates/layouts/layouts_index.json b/skills/ppt-master/templates/layouts/layouts_index.json
index bdc9b663..2e92503e 100644
--- a/skills/ppt-master/templates/layouts/layouts_index.json
+++ b/skills/ppt-master/templates/layouts/layouts_index.json
@@ -1,359 +1,190 @@
{
"academic_defense": {
- "label": "academic_defense",
- "summary": "For Thesis defense, academic presentations, research progress reports, grant applications.",
+ "summary": "Thesis defense, academic presentations, research progress reports, grant applications.",
"keywords": [
"Professional",
"rigorous",
"research-oriented",
"clear hierarchy"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"ai_ops": {
- "label": "Enterprise Digital Intelligence",
- "summary": "For Telecom AI operations architecture, IT system overviews, digital transformation proposals, smart infrastructure reports.",
+ "summary": "Telecom AI operations architecture, IT system overviews, digital transformation proposals, smart infrastructure reports.",
"keywords": [
"Information-dense",
"structured",
"modular zoning",
"telecom",
"enterprise style"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending",
- "reference_style"
]
},
"anthropic": {
- "label": "Anthropic Style Template",
- "summary": "For AI tech talks, developer conferences, technical training, product launches.",
+ "summary": "AI tech talks, developer conferences, technical training, product launches.",
"keywords": [
"Tech-forward",
"professional",
"modern",
"conclusion-first"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"china_telecom_template": {
- "label": "中国电信模板",
- "summary": "For China Telecom related briefings, 政企数字化方案, 转型规划, 内部汇报.",
+ "summary": "China Telecom related briefings, 政企数字化方案, 转型规划, 内部汇报.",
"keywords": [
"Authoritative",
"structured",
"restrained",
"enterprise-government hybrid"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"exhibit": {
- "label": "Exhibit Style Template",
- "summary": "For Strategic planning, executive reports, investment analysis, board presentations.",
+ "summary": "Strategic planning, executive reports, investment analysis, board presentations.",
"keywords": [
"Premium",
"refined",
"authoritative",
"data-driven",
"conclusion-first"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"google_style": {
- "label": "Google Style Template",
- "summary": "For Annual work reports, technical sharing, project showcases, data-driven presentations.",
+ "summary": "Annual work reports, technical sharing, project showcases, data-driven presentations.",
"keywords": [
"Professional",
"modern",
"clean and restrained",
"data-driven",
"generous whitespace"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"government_blue": {
- "label": "Government Blue Template",
- "summary": "For Key project briefings, Five-Year Plan presentations, work summaries, investment promotion, policy interpretation.",
+ "summary": "Key project briefings, Five-Year Plan presentations, work summaries, investment promotion, policy interpretation.",
"keywords": [
"Grand",
"tech-forward",
"modern",
"professional government style"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"government_red": {
- "label": "Government Red Template",
- "summary": "For Government briefings, policy interpretation, work summaries, project introductions, investment promotion.",
+ "summary": "Government briefings, policy interpretation, work summaries, project introductions, investment promotion.",
"keywords": [
"Authoritative",
"dignified",
"professional",
"modern government style"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"mckinsey": {
- "label": "McKinsey Style Template",
- "summary": "For Strategic consulting, executive briefings, investment analysis, business proposals.",
+ "summary": "Strategic consulting, executive briefings, investment analysis, business proposals.",
"keywords": [
"Data-driven",
"structured thinking",
"professional whitespace",
"minimalist premium"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"medical_university": {
- "label": "Hospital / Medical University Template",
- "summary": "For Medical academic reports, case discussions, research presentations, hospital work reports, medical education and training.",
+ "summary": "Medical academic reports, case discussions, research presentations, hospital work reports, medical education and training.",
"keywords": [
"Professional",
"rigorous",
"life-affirming",
"tech-forward",
"trustworthy"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"pixel_retro": {
- "label": "Pixel Retro Template",
- "summary": "For Tech talks, programming tutorials, game introductions, geek-style showcases.",
+ "summary": "Tech talks, programming tutorials, game introductions, geek-style showcases.",
"keywords": [
"Retro gaming",
"neon cyberpunk",
"geek tech",
"8-bit style"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"psychology_attachment": {
- "label": "Psychology Healing Template",
- "summary": "For Psychotherapy training, academic lectures, counseling case analysis, professional sharing.",
+ "summary": "Psychotherapy training, academic lectures, counseling case analysis, professional sharing.",
"keywords": [
"Professional",
"warm",
"healing",
"trustworthy"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"smart_red": {
- "label": "Smart Red-Orange Business Style",
- "summary": "For Company introductions, product launches, solution presentations, education industry courseware.",
+ "summary": "Company introductions, product launches, solution presentations, education industry courseware.",
"keywords": [
"Modern",
"energetic",
"professional",
"geometric"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"中国电建_常规": {
- "label": "formerly powerchina",
- "summary": "For Engineering project reports, technical proposal presentations, business negotiations, corporate promotion, annual summaries.",
+ "summary": "Engineering project reports, technical proposal presentations, business negotiations, corporate promotion, annual summaries.",
"keywords": [
"Professional",
"composed",
"international",
"state-owned enterprise style"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"中国电建_现代": {
- "label": "formerly powerchina_v2",
- "summary": "For Major engineering reports, international market promotion, technology achievement showcases, high-end business negotiations.",
+ "summary": "Major engineering reports, international market promotion, technology achievement showcases, high-end business negotiations.",
"keywords": [
"Grand narrative",
"modern precision",
"digital tech",
"international vision"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"中汽研_商务": {
- "label": "formerly zhongqiyan_v2",
- "summary": "For Product certification display, evaluation presentations, technology promotion, high-end business reporting.",
+ "summary": "Product certification display, evaluation presentations, technology promotion, high-end business reporting.",
"keywords": [
"Modern tech",
"authoritative & professional",
"composed & grand"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"中汽研_常规": {
- "label": "formerly zhongqiyan",
- "summary": "For Product certification display, evaluation presentations, technology promotion, business visits.",
+ "summary": "Product certification display, evaluation presentations, technology promotion, business visits.",
"keywords": [
"Professional",
"authoritative",
"trustworthy",
"consulting style"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"中汽研_现代": {
- "label": "CATARC_Modern_Tech",
- "summary": "For Forward-looking technology showcases, strategic releases, high-end business reporting.",
+ "summary": "Forward-looking technology showcases, strategic releases, high-end business reporting.",
"keywords": [
"Futuristic",
"tech-forward",
"deep & refined"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"招商银行": {
- "label": "招商银行",
- "summary": "For 交易银行产品介绍、销售收款方案汇报、客户案例拆解、分行培训材料.",
+ "summary": "交易银行产品介绍、销售收款方案汇报、客户案例拆解、分行培训材料.",
"keywords": [
"Brand-consistent",
"structured",
"product-focused",
"refined finance"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"科技蓝商务": {
- "label": "科技蓝商务 / tech_blue_business",
- "summary": "For Corporate reports, product launches, proposals, process standards, training materials.",
+ "summary": "Corporate reports, product launches, proposals, process standards, training materials.",
"keywords": [
"Tech",
"business",
"professional",
"clean"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
},
"重庆大学": {
- "label": "重庆大学",
- "summary": "For Academic defense, research reports, teaching presentations, scholarly exchange.",
+ "summary": "Academic defense, research reports, teaching presentations, scholarly exchange.",
"keywords": [
"Academically grounded · Mountain City charm · Modern minimalism"
- ],
- "pages": [
- "01_cover",
- "02_chapter",
- "02_toc",
- "03_content",
- "04_ending"
]
}
}
diff --git a/skills/ppt-master/workflows/create-template.md b/skills/ppt-master/workflows/create-template.md
index 42b967b7..979955ce 100644
--- a/skills/ppt-master/workflows/create-template.md
+++ b/skills/ppt-master/workflows/create-template.md
@@ -52,7 +52,7 @@ Items to confirm with the user:
| Assets list | Optional | Logos / background textures / reference images to include in the template package |
| Keywords | Yes | 3–5 short tags for `layouts_index.json` lookup (e.g., `McKinsey`, `Consulting`, `Structured`) |
-> **Persist the brief into `design_spec.md`**. When the Template_Designer writes `design_spec.md` in Step 3, declare a YAML frontmatter block at the top with the confirmed brief (`template_id`, `label`, `category`, `summary`, `keywords`, `primary_color`, `canvas_format`, `replication_mode`, etc.). `register_template.py` reads this in Step 5, so the brief flows directly into the index without the AI re-deriving it from prose. See Step 5 for the recommended frontmatter shape.
+> **Persist the brief into `design_spec.md`**. When the Template_Designer writes `design_spec.md` in Step 3, declare a YAML frontmatter block at the top with the confirmed brief (`template_id`, `category`, `summary`, `keywords`, `primary_color`, `canvas_format`, `replication_mode`, etc.). `register_template.py` reads this in Step 5, so the brief flows directly into the index without the AI re-deriving it from prose. See Step 5 for the recommended frontmatter shape.
**Required outcome of Step 1** (all must be true before emitting `[TEMPLATE_BRIEF_CONFIRMED]`):
@@ -212,22 +212,21 @@ python3 skills/ppt-master/scripts/register_template.py <template_id>
Outputs:
-- updates `skills/ppt-master/templates/layouts/layouts_index.json` — the flat `template_id → { label, summary, keywords, pages }` map
+- updates `skills/ppt-master/templates/layouts/layouts_index.json` — the flat `template_id → { summary, keywords }` map
- refreshes the auto-managed Quick Index inside `skills/ppt-master/templates/layouts/README.md` (the surrounding category sections stay hand-edited)
- prints a "Template Creation Complete" card you can use directly for Step 6
-`pages` 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.
+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 opts into the template flow. The main workflow defaults to free design and does not read this file unless a template trigger fires (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 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.
> **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:
>
> ```yaml
> ---
> template_id: my_template
-> label: My Template
> category: brand # brand | general | scenario | government | special
-> summary: For ...
+> summary: Strategic consulting, executive briefings, ...
> keywords: [tag1, tag2, tag3]
> primary_color: "#005587"
> canvas_format: ppt169