bit-ppt-generator 0.3.0 → 0.3.1

package/README.md

@@ -6,6 +6,25 @@
 项目目标不是把幻灯片截图塞进 PPT，而是尽量生成原生 Office 对象：
 文本框、形状、表格、图表、图片和 Office Math 公式都应保持可编辑。
 
+在线测试地址：[http://47.109.207.16:8080/](http://47.109.207.16:8080/)
+
+欢迎试用并在 [GitHub Issues](https://github.com/yang-kun-long/bit-ppt-template/issues)
+反馈问题、语法建议、版式需求或生成失败案例。
+
+## 项目来源与相关路线
+
+本项目的视觉风格和最初需求来自 TeXPage 上的北京理工大学 LaTeX 幻灯片模板：
+[BIThesis Beamer Slide Template](https://www.texpage.com/zh/template/18f4a5d2-2167-47b8-b193-85e2475e7a06)。
+原模板适合熟悉 LaTeX / Beamer 的用户，但 LaTeX 工具链较重，输出也通常是 PDF。
+PDF 用 WPS 播放比较方便；如果没有 WPS，常见的 PDF 转 PPT 流程又容易造成格式错乱。
+
+因此这里提供另一条路线：用 YAML 描述内容，直接生成可编辑 PPTX，尽量保留文本、
+表格、图表、形状和 Office Math 公式的可编辑性。
+
+如果你的需求是“已有 PDF 幻灯片，只想在线展示或播放”，可以使用另一个项目
+[pptView](https://github.com/yang-kun-long/pptView)。在线演示：
+[https://ppt.yangkunlong.top](https://ppt.yangkunlong.top)。
+
 代码使用 MIT License。北京理工大学名称、标识和视觉参考归其各自权利人所有。
 
 ## 特性
@@ -19,9 +38,14 @@
 - 支持 `--json` 和 `--strict`，便于脚本、CI 和 AI agent 自动调用
 - 支持图片尺寸读取和 `imageText` 自动排版
 
-## 安装
+## 三种使用方式
+
+同一个 npm 包同时提供 Web UI、CLI 和 MCP 三个入口。普通用户优先使用 Web UI；
+脚本和 CI 使用 CLI；Codex、Claude Code 等本地 agent 使用 MCP。
+
+### 1. 普通用户：打开本地网页
 
-发布到 npm 后，普通用户可直接启动本地网页：
+无需安装，直接启动：
 
 ```powershell
 npx bit-ppt-generator
@@ -35,88 +59,110 @@ http://127.0.0.1:3000/
 
 本地网页默认不需要登录；只有部署者配置了鉴权环境变量时才会显示登录区。
 
-全局安装：
+也可以全局安装后启动：
 
 ```powershell
 npm install -g bit-ppt-generator
 bit-ppt-generator
 ```
 
-仓库开发：
+### 2. 命令行用户：检查和生成 PPTX
 
 ```powershell
-npm install
+npm install -g bit-ppt-generator
+bit-ppt check content/example.yaml --json
+bit-ppt generate content/example.yaml output/example.pptx
 ```
 
-本地开发可以直接使用 Node 入口：
+常用 CLI：
 
-```powershell
-node bin/bit-ppt.mjs --help
+```text
+bit-ppt generate <input.yaml> <output.pptx> [--json] [--strict] [font options]
+bit-ppt check <input.yaml> [--json] [--strict]
+bit-ppt list-layouts [--json]
+bit-ppt guide [topic] [name] [--json]
+bit-ppt doctor [--json]
 ```
 
-也可以链接为全局命令：
+### 3. Agent 用户：配置 MCP
+
+全局安装后，MCP 客户端可以直接启动 npm 包提供的 `bit-ppt-mcp` 命令：
 
 ```powershell
-npm link
-bit-ppt --help
+npm install -g bit-ppt-generator
+bit-ppt-mcp --help
 ```
 
-## 快速开始
-
-启动本地网页：
+MCP 客户端配置示例：
 
-```powershell
-npm run serve
+```json
+{
+  "mcpServers": {
+    "bit-ppt": {
+      "command": "bit-ppt-mcp",
+      "args": []
+    }
+  }
+}
 ```
 
-生成示例 PPT：
+如果 MCP 客户端不继承系统 PATH，改用 `npx` 启动：
 
-```powershell
-npm run build:ppt
-npm run build:body-layouts
-npm run build:charts
+```json
+{
+  "mcpServers": {
+    "bit-ppt": {
+      "command": "npx",
+      "args": ["-y", "--package", "bit-ppt-generator", "bit-ppt-mcp"]
+    }
+  }
+}
 ```
 
-输出文件位于：
+不再需要写类似 `D:/atuodl/presentation-slide/bit-ppt-template/bin/bit-ppt-mcp.mjs`
+这样的本机源码路径。那种写法只适合仓库开发阶段；发布到 npm 后应使用包里的
+`bit-ppt-mcp` 命令。
 
-```text
-output/example.pptx
-output/body-layout-test.pptx
-output/chart-flow-test.pptx
-```
+## 仓库开发
 
-手动指定输入和输出：
+克隆仓库后安装依赖：
 
 ```powershell
-node bin/bit-ppt.mjs generate content/example.yaml output/example.pptx
+npm install
 ```
 
-先检查再生成：
+启动本地网页：
 
 ```powershell
-node bin/bit-ppt.mjs check content/example.yaml --json
-node bin/bit-ppt.mjs generate content/example.yaml output/example.pptx --json
+npm run serve
 ```
 
-严格模式会把 warning 也视为失败：
+生成示例 PPT：
 
 ```powershell
-node bin/bit-ppt.mjs check content/formula-test.yaml --json --strict
-node bin/bit-ppt.mjs generate content/example.yaml output/example.pptx --json --strict
+npm run build:ppt
+npm run build:body-layouts
+npm run build:charts
 ```
 
-## Release Targets
+源码入口：
 
-本仓库采用单主干、多入口策略。CLI、MCP 和 Node HTTP 服务都复用同一套核心生成逻辑。
+```powershell
+node bin/bit-ppt.mjs --help
+node bin/bit-ppt-http.mjs --help
+node bin/bit-ppt-mcp.mjs --help
+```
 
-当前状态：
+本仓库采用单主干、多入口策略。Web UI、CLI、MCP 和 Node HTTP API 都复用同一套核心生成逻辑。
+
+## npm 包入口
 
 - Web UI：默认入口为 `bit-ppt-generator`，适合 npm 用户本地打开网页
 - CLI：已支持，入口为 `bit-ppt` 或 `node bin/bit-ppt.mjs`
 - MCP：已支持，入口为 `bit-ppt-mcp` 或 `node bin/bit-ppt-mcp.mjs`
 - Node HTTP API：已支持，入口为 `bit-ppt-http` 或 `node bin/bit-ppt-http.mjs`
 
-当前 npm 包名预定为 `bit-ppt-generator`。一个 npm release 同时包含 Web UI、CLI 和 MCP 三个入口，不拆成三个包。
+一个 npm release 同时包含 Web UI、CLI 和 MCP 三个入口，不拆成三个包。
 
 ## CLI 命令
 
@@ -134,10 +180,10 @@ bit-ppt-http
 常用命令：
 
 ```powershell
-node bin/bit-ppt.mjs list-layouts
-node bin/bit-ppt.mjs list-layouts --json
-node bin/bit-ppt.mjs doctor
-node bin/bit-ppt.mjs doctor --json
+bit-ppt list-layouts
+bit-ppt list-layouts --json
+bit-ppt doctor
+bit-ppt doctor --json
 ```
 
 `doctor` 会检查 Node 版本、依赖、关键素材、示例 deck、输出目录可写性。
@@ -150,24 +196,23 @@ MCP 只是 adapter，仍复用 CLI 背后的同一套生成和校验函数。
 本地运行：
 
 ```powershell
-node bin/bit-ppt-mcp.mjs
+bit-ppt-mcp
 ```
 
-全局链接后：
+从源码运行：
 
 ```powershell
-bit-ppt-mcp
+node bin/bit-ppt-mcp.mjs
 ```
 
-MCP 客户端配置示例：
+MCP 客户端配置示例，优先使用 npm 包命令：
 
 ```json
 {
   "mcpServers": {
     "bit-ppt": {
-      "command": "node",
-      "args": ["D:/atuodl/presentation-slide/bit-ppt-template/bin/bit-ppt-mcp.mjs"],
-      "cwd": "D:/atuodl/presentation-slide/bit-ppt-template"
+      "command": "bit-ppt-mcp",
+      "args": []
     }
   }
 }
@@ -593,6 +638,32 @@ npm run check:charts
 npm pack --dry-run
 ```
 
+## 发布
+
+npm 包名为 `bit-ppt-generator`。后续版本通过 GitHub Release 触发
+`.github/workflows/publish.yml`，并使用 npm Trusted Publisher 发布，不需要在
+GitHub Secrets 保存 npm token。
+
+Trusted Publisher 配置：
+
+```text
+Publisher: GitHub Actions
+Organization or user: yang-kun-long
+Repository: bit-ppt-template
+Workflow filename: publish.yml
+Environment name: 留空
+```
+
+发布新版本：
+
+```powershell
+npm version patch
+git push
+git push --tags
+```
+
+随后在 GitHub 创建并发布对应 tag 的 Release。
+
 ## 项目结构
 
 ```text

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bit-ppt-generator",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "LaTeX-free Beijing Institute of Technology style PPTX generator with Web UI, CLI, and MCP entrypoints.",
   "license": "MIT",
   "type": "module",
@@ -38,5 +38,13 @@
     "pptxgenjs": "^4.0.1",
     "yaml": "^2.8.4",
     "zod": "^4.4.3"
-  }
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/yang-kun-long/bit-ppt-template.git"
+  },
+  "bugs": {
+    "url": "https://github.com/yang-kun-long/bit-ppt-template/issues"
+  },
+  "homepage": "https://github.com/yang-kun-long/bit-ppt-template#readme"
 }

package/src/layout-guides.mjs

@@ -1,3 +1,5 @@
+import { listLayouts as listSupportedLayouts } from "./core/layouts.mjs";
+
 const writingRules = [
   "Keep slide text short and concrete; use validation warnings as rewrite hints.",
   "Prefer editable PPTX objects: text boxes, shapes, tables, charts, OMML formulas, and native images.",
@@ -226,8 +228,414 @@ const layoutGuides = {
   },
 };
 
+const additionalLayoutGuides = {
+  title: {
+    layout: "title",
+    purpose: "Create the deck cover slide from top-level metadata.",
+    whenToUse: "Use as the first slide; title content usually comes from the deck-level `meta` object.",
+    fields: {
+      layout: { type: "literal", required: true, value: "title" },
+      "meta.title": { type: "string", required: false },
+      "meta.subtitle": { type: "string", required: false },
+      "meta.author": { type: "string", required: false },
+      "meta.advisor": { type: "string", required: false },
+      "meta.date": { type: "string", required: false },
+    },
+    limits: {
+      "meta.title": { recommendedChars: 28 },
+      "meta.subtitle": { recommendedChars: 42 },
+    },
+    notes: [
+      "The slide object normally only needs `layout: title`.",
+      "Cover text is read from deck metadata.",
+    ],
+    example: { layout: "title" },
+  },
+  agenda: {
+    layout: "agenda",
+    purpose: "Show the main agenda or chapter list.",
+    whenToUse: "Use near the beginning of a deck to preview sections.",
+    fields: {
+      layout: { type: "literal", required: true, value: "agenda" },
+      title: { type: "string", required: true },
+      items: { type: "string[]", required: true },
+    },
+    limits: { items: { maxItems: 7, recommendedChars: 24 } },
+    notes: ["Keep agenda labels short and parallel.", "Use `section` slides for major chapter breaks."],
+    example: { layout: "agenda", title: "目录", items: ["研究背景", "方法设计", "实验结果", "总结展望"] },
+  },
+  section: {
+    layout: "section",
+    purpose: "Create a visual chapter divider.",
+    whenToUse: "Use before a major topic shift or report section.",
+    fields: {
+      layout: { type: "literal", required: true, value: "section" },
+      sectionNo: { type: "string", required: false },
+      title: { type: "string", required: true },
+      subtitle: { type: "string", required: false },
+    },
+    limits: { title: { recommendedChars: 24 }, subtitle: { recommendedChars: 42 } },
+    notes: ["`sectionNo` can be supplied explicitly, for example `01`.", "Keep the subtitle as context, not body content."],
+    example: { layout: "section", sectionNo: "01", title: "研究背景", subtitle: "从问题定义与现有瓶颈切入" },
+  },
+  bullets: {
+    layout: "bullets",
+    purpose: "Show a lead sentence and a concise bullet list.",
+    whenToUse: "Use for findings, observations, requirements, and short argument chains.",
+    fields: {
+      layout: { type: "literal", required: true, value: "bullets" },
+      title: { type: "string", required: true },
+      lead: { type: "string", required: false },
+      bullets: { type: "string[]", required: true },
+      fontSize: { type: "number", required: false },
+    },
+    limits: { lead: { recommendedChars: 58 }, bullets: { maxItems: 8, recommendedChars: 38 } },
+    notes: ["Inline `$...$` and `\\(...\\)` formulas are supported.", "Long bullet lists may be split during preflight."],
+    example: { layout: "bullets", title: "核心发现", lead: "结构化输入能降低排版漂移。", bullets: ["模型只填写短字段。", "模板负责视觉规范。", "预检负责溢出修复。"] },
+  },
+  claim: {
+    layout: "claim",
+    purpose: "Emphasize one central claim with supporting evidence.",
+    whenToUse: "Use when a slide needs one clear takeaway rather than several equal points.",
+    fields: {
+      layout: { type: "literal", required: true, value: "claim" },
+      title: { type: "string", required: true },
+      claim: { type: "string", required: true },
+      evidence: { type: "string[]", required: false },
+    },
+    limits: { claim: { recommendedChars: 54 }, evidence: { maxItems: 5, recommendedChars: 38 } },
+    notes: ["Make `claim` a complete sentence.", "Use evidence bullets for proof, not extra claims."],
+    example: { layout: "claim", title: "核心结论", claim: "AI 生成 PPT 的关键是稳定内容结构。", evidence: ["YAML 限定字段。", "PPTX 对象保持可编辑。"] },
+  },
+  twoColumn: {
+    layout: "twoColumn",
+    purpose: "Compare or separate two parallel content blocks.",
+    whenToUse: "Use for before/after, baseline/ours, or two-topic explanation.",
+    fields: {
+      layout: { type: "literal", required: true, value: "twoColumn" },
+      title: { type: "string", required: true },
+      left: { type: "{ title, text? | bullets? }", required: true },
+      right: { type: "{ title, text? | bullets? }", required: true },
+    },
+    limits: { columnTitle: { recommendedChars: 16 }, columnText: { recommendedChars: 105 }, columnBullets: { maxItems: 5, recommendedChars: 34 } },
+    notes: ["Each column can use either `text` or `bullets`.", "Use `comparison` when the point is explicitly adversarial or directional."],
+    example: { layout: "twoColumn", title: "两种路线", left: { title: "传统做法", bullets: ["手工排版", "一致性依赖人工"] }, right: { title: "模板化做法", bullets: ["结构化输入", "生成器固定样式"] } },
+  },
+  cards: {
+    layout: "cards",
+    purpose: "Show several peer points as compact cards.",
+    whenToUse: "Use for features, modules, contributions, or categories with equal weight.",
+    fields: {
+      layout: { type: "literal", required: true, value: "cards" },
+      title: { type: "string", required: true },
+      cards: { type: "{ title, text }[]", required: true },
+    },
+    limits: { cards: { maxItems: 6 }, cardTitle: { recommendedChars: 14 }, cardText: { recommendedChars: 52 } },
+    notes: ["Cards work best when each item has similar importance.", "Use no more than six cards on one slide."],
+    example: { layout: "cards", title: "能力模块", cards: [{ title: "校验", text: "检查字段与长度风险。" }, { title: "生成", text: "写入可编辑 PPTX 对象。" }] },
+  },
+  comparison: {
+    layout: "comparison",
+    purpose: "Show a direct comparison between two options.",
+    whenToUse: "Use when one side is preferred, rejected, or contrasted against another.",
+    fields: {
+      layout: { type: "literal", required: true, value: "comparison" },
+      title: { type: "string", required: true },
+      left: { type: "{ label?, title, bullets }", required: true },
+      right: { type: "{ label?, title, bullets }", required: true },
+    },
+    limits: { comparisonTitle: { recommendedChars: 18 }, bullets: { maxItems: 5, recommendedChars: 32 } },
+    notes: ["`left.label` and `right.label` are short tags.", "Keep the two sides structurally parallel."],
+    example: { layout: "comparison", title: "技术路线取舍", left: { label: "不优先", title: "端到端 Agent", bullets: ["流程封闭", "复核成本高"] }, right: { label: "优先", title: "MCP 工具链", bullets: ["跨客户端", "人类可介入"] } },
+  },
+  timeline: {
+    layout: "timeline",
+    purpose: "Show milestones along a horizontal timeline.",
+    whenToUse: "Use for roadmaps, phases, history, or scheduled work.",
+    fields: {
+      layout: { type: "literal", required: true, value: "timeline" },
+      title: { type: "string", required: true },
+      items: { type: "{ date? | phase?, title, text }[]", required: true },
+    },
+    limits: { items: { maxItems: 6 }, itemTitle: { recommendedChars: 10 }, itemText: { recommendedChars: 24 } },
+    notes: ["Use `date` for calendar time and `phase` for abstract stages.", "Avoid paragraph text in timeline nodes."],
+    example: { layout: "timeline", title: "路线图", items: [{ date: "阶段 1", title: "模板", text: "固化视觉规范。" }, { date: "阶段 2", title: "校验", text: "加入预检修复。" }] },
+  },
+  process: {
+    layout: "process",
+    purpose: "Show a linear process as connected steps.",
+    whenToUse: "Use for workflows, generation pipelines, or execution procedures.",
+    fields: {
+      layout: { type: "literal", required: true, value: "process" },
+      title: { type: "string", required: true },
+      steps: { type: "{ title, text }[]", required: true },
+    },
+    limits: { steps: { maxItems: 5 }, stepTitle: { recommendedChars: 8 }, stepText: { recommendedChars: 24 } },
+    notes: ["Steps are rendered left-to-right.", "Use `flowchart` for branching or non-linear processes."],
+    example: { layout: "process", title: "生成流程", steps: [{ title: "解析", text: "读取 YAML。" }, { title: "校验", text: "检查字段。" }, { title: "导出", text: "生成 PPTX。" }] },
+  },
+  problemSolution: {
+    layout: "problemSolution",
+    purpose: "Present problem, solution, and impact in three panels.",
+    whenToUse: "Use for proposal framing or product/research motivation.",
+    fields: {
+      layout: { type: "literal", required: true, value: "problemSolution" },
+      title: { type: "string", required: true },
+      problem: { type: "{ label?, title, bullets }", required: true },
+      solution: { type: "{ label?, title, bullets }", required: true },
+      impact: { type: "{ label?, title, bullets }", required: true },
+    },
+    limits: { panelTitle: { recommendedChars: 12 }, bullets: { maxItems: 4, recommendedChars: 26 } },
+    notes: ["Use this when the three blocks form one argument.", "Each panel supports a custom short `label`."],
+    example: { layout: "problemSolution", title: "问题与方案", problem: { title: "排版不稳", bullets: ["模型自由发挥导致溢出。"] }, solution: { title: "结构约束", bullets: ["YAML 固定字段。"] }, impact: { title: "可复核", bullets: ["输出可编辑 PPTX。"] } },
+  },
+  painOpportunity: {
+    layout: "painOpportunity",
+    purpose: "Frame current status, pain points, and opportunity.",
+    whenToUse: "Use for background analysis before introducing a solution.",
+    fields: {
+      layout: { type: "literal", required: true, value: "painOpportunity" },
+      title: { type: "string", required: true },
+      status: { type: "{ title, text? | bullets? }", required: true },
+      pain: { type: "{ title, text? | bullets? }", required: true },
+      opportunity: { type: "{ title, text? | bullets? }", required: true },
+    },
+    limits: { panelTitle: { recommendedChars: 12 }, bullets: { maxItems: 4, recommendedChars: 30 } },
+    notes: ["Panels use the same structure as `twoColumn` column blocks.", "Best for moving from observation to opportunity."],
+    example: { layout: "painOpportunity", title: "现状痛点与机会", status: { title: "现状", bullets: ["PPT 生成需求高。"] }, pain: { title: "痛点", bullets: ["直接生成不稳定。"] }, opportunity: { title: "机会", bullets: ["模板化生成可控。"] } },
+  },
+  experimentDesign: {
+    layout: "experimentDesign",
+    purpose: "Summarize an experiment setup.",
+    whenToUse: "Use before result slides to define data, variables, metrics, and baselines.",
+    fields: {
+      layout: { type: "literal", required: true, value: "experimentDesign" },
+      title: { type: "string", required: true },
+      dataset: { type: "string | string[]", required: false },
+      variables: { type: "string | string[]", required: false },
+      metrics: { type: "string | string[]", required: false },
+      baselines: { type: "string | string[]", required: false },
+      procedure: { type: "string[]", required: false },
+    },
+    limits: { eachBlock: { maxItems: 4, recommendedChars: 26 }, procedure: { maxItems: 5 } },
+    notes: ["Scalar strings are accepted and rendered as one bullet.", "Keep procedure items short because they render on one line."],
+    example: { layout: "experimentDesign", title: "实验设计", dataset: ["公开数据集 A"], variables: ["是否启用预检"], metrics: ["溢出页数"], baselines: ["直接生成 PPT"], procedure: ["准备输入", "生成", "人工复核"] },
+  },
+  resultAnalysis: {
+    layout: "resultAnalysis",
+    purpose: "State one finding, key metrics, and analysis bullets.",
+    whenToUse: "Use after experiments to connect numbers to interpretation.",
+    fields: {
+      layout: { type: "literal", required: true, value: "resultAnalysis" },
+      title: { type: "string", required: true },
+      finding: { type: "string", required: true },
+      metrics: { type: "{ value, label, note? }[]", required: false },
+      analysis: { type: "string[]", required: false },
+    },
+    limits: { finding: { recommendedChars: 52 }, metrics: { maxItems: 3 }, analysis: { maxItems: 4, recommendedChars: 38 } },
+    notes: ["Put the strongest result in `finding`.", "Metrics are compact; use `chart` for richer data."],
+    example: { layout: "resultAnalysis", title: "结果分析", finding: "预检显著减少长列表造成的页面溢出。", metrics: [{ value: "-80%", label: "溢出页", note: "相对基线" }], analysis: ["主要收益来自 bullets 和 references 拆页。"] },
+  },
+  riskMitigation: {
+    layout: "riskMitigation",
+    purpose: "Show risks, impacts, and mitigations in a table.",
+    whenToUse: "Use for project planning, deployment risk, or limitation handling.",
+    fields: {
+      layout: { type: "literal", required: true, value: "riskMitigation" },
+      title: { type: "string", required: true },
+      items: { type: "{ risk, impact, mitigation }[]", required: true },
+    },
+    limits: { items: { maxItems: 5 }, cell: { recommendedChars: 28 } },
+    notes: ["Keep mitigation actionable.", "Use this for risks; use `table` for arbitrary structured data."],
+    example: { layout: "riskMitigation", title: "风险与对策", items: [{ risk: "图片缺失", impact: "生成失败", mitigation: "使用 placeholder 并补 prompt" }] },
+  },
+  contribution: {
+    layout: "contribution",
+    purpose: "List the main contributions with numbered emphasis.",
+    whenToUse: "Use near the end of a research or project deck.",
+    fields: {
+      layout: { type: "literal", required: true, value: "contribution" },
+      title: { type: "string", required: true },
+      items: { type: "{ title, text }[]", required: true },
+    },
+    limits: { items: { maxItems: 4 }, itemTitle: { recommendedChars: 14 }, itemText: { recommendedChars: 44 } },
+    notes: ["Use one contribution per item.", "Avoid turning this into a general summary slide."],
+    example: { layout: "contribution", title: "主要贡献", items: [{ title: "可编辑输出", text: "文本、表格、图表均保留为 PPTX 对象。" }, { title: "公式支持", text: "LaTeX 公式转换为原生 OMML。" }] },
+  },
+  summary: {
+    layout: "summary",
+    purpose: "Close a section with one takeaway and supporting points.",
+    whenToUse: "Use at section endings or before the closing slide.",
+    fields: {
+      layout: { type: "literal", required: true, value: "summary" },
+      title: { type: "string", required: true },
+      takeaway: { type: "string", required: true },
+      points: { type: "string[]", required: false },
+    },
+    limits: { takeaway: { recommendedChars: 52 }, points: { maxItems: 5, recommendedChars: 36 } },
+    notes: ["`takeaway` should be a sentence, not a heading.", "Use `closing` only for the final thank-you page."],
+    example: { layout: "summary", title: "章节小结", takeaway: "结构化内容让 PPT 生成更稳定也更容易修复。", points: ["页面类型明确。", "校验信息可回传模型。"] },
+  },
+  architecture: {
+    layout: "architecture",
+    purpose: "Show a layered architecture with components and notes.",
+    whenToUse: "Use for systems, model stacks, or pipeline architecture.",
+    fields: {
+      layout: { type: "literal", required: true, value: "architecture" },
+      title: { type: "string", required: true },
+      layers: { type: "{ title, components, note? }[]", required: true },
+    },
+    limits: { layers: { maxItems: 4 }, layerTitle: { recommendedChars: 8 }, components: { maxItems: 5, recommendedChars: 10 }, note: { recommendedChars: 44 } },
+    notes: ["Layer order is top-to-bottom.", "Use short component labels so chips stay readable."],
+    example: { layout: "architecture", title: "系统架构", layers: [{ title: "输入层", components: ["YAML", "图片"], note: "收集结构化材料。" }, { title: "生成层", components: ["校验", "PPTX", "OMML"], note: "写入可编辑对象。" }] },
+  },
+  ablation: {
+    layout: "ablation",
+    purpose: "Summarize ablation factors, settings, deltas, and conclusions.",
+    whenToUse: "Use for research experiments that remove or vary components.",
+    fields: {
+      layout: { type: "literal", required: true, value: "ablation" },
+      title: { type: "string", required: true },
+      baseline: { type: "string", required: false },
+      items: { type: "{ factor, setting, delta, conclusion }[]", required: true },
+    },
+    limits: { baseline: { recommendedChars: 58 }, items: { maxItems: 6 }, factor: { recommendedChars: 18 }, setting: { recommendedChars: 18 }, delta: { recommendedChars: 18 }, conclusion: { recommendedChars: 28 } },
+    notes: ["Use `delta` for numeric or qualitative change.", "Keep conclusions short enough for table-like rendering."],
+    example: { layout: "ablation", title: "消融实验", baseline: "基线启用所有模块。", items: [{ factor: "预检", setting: "关闭", delta: "+3 overflow", conclusion: "长列表风险上升" }] },
+  },
+  caseStudy: {
+    layout: "caseStudy",
+    purpose: "Show one visual case with context, method, and result.",
+    whenToUse: "Use for qualitative examples, screenshots, or representative samples.",
+    fields: {
+      layout: { type: "literal", required: true, value: "caseStudy" },
+      title: { type: "string", required: true },
+      image: { type: "string | { path, fit? } | { mode: placeholder, prompt, aspectRatio? }", required: true },
+      caption: { type: "string", required: false },
+      context: { type: "string[]", required: false },
+      method: { type: "string[]", required: false },
+      result: { type: "string[]", required: false },
+    },
+    limits: { caption: { recommendedChars: 40 }, context: { maxItems: 2, recommendedChars: 34 }, method: { maxItems: 2, recommendedChars: 34 }, result: { maxItems: 2, recommendedChars: 34 } },
+    notes: ["Image placeholders are supported.", "Use `imageGrid` when comparing multiple images."],
+    example: { layout: "caseStudy", title: "案例分析", image: "assets/bit-campus-photo.png", caption: "示例图片，可替换为实验结果图。", context: ["输入是一段论文草稿。"], method: ["生成器按 layout 写入 PPTX。"], result: ["输出可继续编辑。"] },
+  },
+  imageGrid: {
+    layout: "imageGrid",
+    purpose: "Show multiple images in a regular grid.",
+    whenToUse: "Use for visual result sets, comparisons, or qualitative examples.",
+    fields: {
+      layout: { type: "literal", required: true, value: "imageGrid" },
+      title: { type: "string", required: true },
+      images: { type: "(string | { path, caption? } | { mode: placeholder, prompt, caption?, aspectRatio? })[]", required: true },
+    },
+    limits: { images: { maxItems: 6 }, caption: { recommendedChars: 16 } },
+    notes: ["Each image can be a local path or an image object.", "Use short captions to avoid crowding the grid."],
+    example: { layout: "imageGrid", title: "多图结果", images: [{ path: "assets/bit-campus-photo.png", caption: "输入" }, { path: "assets/bit-campus-photo.png", caption: "输出" }] },
+  },
+  code: {
+    layout: "code",
+    purpose: "Show pseudocode or a compact code block with notes.",
+    whenToUse: "Use for algorithms, command snippets, or implementation sketches.",
+    fields: {
+      layout: { type: "literal", required: true, value: "code" },
+      title: { type: "string", required: true },
+      language: { type: "string", required: false },
+      code: { type: "string", required: false },
+      algorithm: { type: "string", required: false },
+      noteTitle: { type: "string", required: false },
+      notes: { type: "string[]", required: false },
+    },
+    limits: { code: { recommendedLines: 12, recommendedCharsPerLine: 72 }, notes: { maxItems: 5, recommendedChars: 32 } },
+    notes: ["Use either `code` or `algorithm`; `code` takes precedence.", "A YAML block scalar is recommended for multi-line code."],
+    example: { layout: "code", title: "算法伪代码", language: "Algorithm", code: "Input: deck D\n1. validate D\n2. generate PPTX", noteTitle: "关键约束", notes: ["代码块保持短行。"] },
+  },
+  appendix: {
+    layout: "appendix",
+    purpose: "Create an appendix index or supplemental topic list.",
+    whenToUse: "Use for backup slides, extra details, or appendix navigation.",
+    fields: {
+      layout: { type: "literal", required: true, value: "appendix" },
+      title: { type: "string", required: true },
+      items: { type: "{ key?, title, text }[]", required: true },
+    },
+    limits: { items: { maxItems: 8 }, itemTitle: { recommendedChars: 14 }, itemText: { recommendedChars: 42 } },
+    notes: ["`key` is optional and defaults to a numbered label.", "Use this as an index, not as dense body text."],
+    example: { layout: "appendix", title: "附录索引", items: [{ key: "A1", title: "数据细节", text: "样本来源与筛选规则。" }] },
+  },
+  metrics: {
+    layout: "metrics",
+    purpose: "Highlight up to four key metrics.",
+    whenToUse: "Use when numeric or compact KPI-style facts should dominate the slide.",
+    fields: {
+      layout: { type: "literal", required: true, value: "metrics" },
+      title: { type: "string", required: true },
+      metrics: { type: "{ value, label, note? }[]", required: true },
+    },
+    limits: { metrics: { maxItems: 4 }, value: { recommendedChars: 8 }, label: { recommendedChars: 12 }, note: { recommendedChars: 30 } },
+    notes: ["Use compact values such as `12+`, `-8%`, or `0`.", "Use `chart` when the reader needs to inspect a trend or distribution."],
+    example: { layout: "metrics", title: "关键指标", metrics: [{ value: "12+", label: "正文页型", note: "覆盖常见汇报页面" }, { value: "100%", label: "可编辑", note: "原生 PPTX 对象" }] },
+  },
+  matrix: {
+    layout: "matrix",
+    purpose: "Show four quadrants or a compact 2x2 decision matrix.",
+    whenToUse: "Use for strategy tradeoffs, option classification, or two-axis judgment.",
+    fields: {
+      layout: { type: "literal", required: true, value: "matrix" },
+      title: { type: "string", required: true },
+      cells: { type: "{ title, text }[]", required: true },
+    },
+    limits: { cells: { maxItems: 4 }, cellTitle: { recommendedChars: 18 }, cellText: { recommendedChars: 52 } },
+    notes: ["Cells render row-major in a 2x2 grid.", "Provide exactly four cells for a complete matrix."],
+    example: { layout: "matrix", title: "方案判断矩阵", cells: [{ title: "低成本 / 高控制", text: "YAML 内容加模板生成。" }, { title: "高成本 / 高控制", text: "完整设计系统与截图校验。" }] },
+  },
+  quote: {
+    layout: "quote",
+    purpose: "Show a short quote or memorable statement.",
+    whenToUse: "Use for thesis statements, external quotes, or section openers.",
+    fields: {
+      layout: { type: "literal", required: true, value: "quote" },
+      title: { type: "string", required: false },
+      quote: { type: "string", required: true },
+      source: { type: "string", required: false },
+    },
+    limits: { quote: { recommendedChars: 70 } },
+    notes: ["Keep the quote short enough to remain visually dominant.", "`source` is optional and rendered below the quote."],
+    example: { layout: "quote", title: "引用页", quote: "让模型生成结构化内容，让模板承担视觉和排版责任。", source: "BIT PPT Template Generator" },
+  },
+  references: {
+    layout: "references",
+    purpose: "List references or citations.",
+    whenToUse: "Use near the end of academic or research decks.",
+    fields: {
+      layout: { type: "literal", required: true, value: "references" },
+      title: { type: "string", required: false },
+      items: { type: "string[]", required: true },
+      fontSize: { type: "number", required: false },
+    },
+    limits: { items: { recommendedChars: 140 } },
+    notes: ["Long reference lists may be split during preflight.", "Keep each reference as one string item."],
+    example: { layout: "references", title: "参考文献", items: ["PptxGenJS project documentation. Generate editable PowerPoint presentations with JavaScript."] },
+  },
+  closing: {
+    layout: "closing",
+    purpose: "Create the final thank-you slide.",
+    whenToUse: "Use as the final slide of a deck.",
+    fields: {
+      layout: { type: "literal", required: true, value: "closing" },
+      title: { type: "string", required: false },
+      subtitle: { type: "string", required: false },
+    },
+    limits: { title: { recommendedChars: 12 }, subtitle: { recommendedChars: 28 } },
+    notes: ["Defaults to a BIT green closing slide.", "Use `subtitle` for defense/Q&A wording."],
+    example: { layout: "closing", title: "谢谢", subtitle: "敬请各位老师批评指正" },
+  },
+};
+
+Object.assign(layoutGuides, additionalLayoutGuides);
+
 function listGuideLayouts() {
-  return Object.keys(layoutGuides);
+  return listSupportedLayouts();
 }
 
 function getLayoutGuide(layout) {