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(visualizations): split chart structure and table catalogs
hugohe38b990e63a41a
diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex aec0c923..337e0da0 100644--- a/skills/ppt-master/scripts/prompt_audit_manifest.json+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json@@ -9,6 +9,8 @@"AGENTS.md","skills/ppt-master/**/*.md","skills/ppt-master/templates/charts/charts_index.json",+ "skills/ppt-master/templates/structures/structures_index.json",+ "skills/ppt-master/templates/tables/tables_index.json","skills/ppt-master/templates/schemas/*.json"],"exclude": [],@@ -314,7 +316,7 @@"route.generate.quick-generate","stage.generate.executor.chart","stage.generate.executor.native-data",- "stage.generate.chart-authoring",+ "stage.generate.visualization-authoring","stage.generate.verify-charts"],"files": [@@ -561,7 +563,7 @@"route.generate.flat-no-image","stage.generate.executor.chart","stage.generate.executor.native-data",- "stage.generate.chart-authoring",+ "stage.generate.visualization-authoring","stage.generate.verify-charts"],"files": [],@@ -769,12 +771,14 @@],"max_tokens": 7000},- "stage.generate.chart-authoring": {- "description": "Conditional visualization-library authoring guidance.",+ "stage.generate.visualization-authoring": {+ "description": "Conditional shared chart, structure, and table template authoring guidance.","scope": "incremental","files": [+ "skills/ppt-master/templates/VISUALIZATION_TEMPLATE_AUTHORING.md","skills/ppt-master/templates/charts/README.md",- "skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.md"+ "skills/ppt-master/templates/structures/README.md",+ "skills/ppt-master/templates/tables/README.md"],"max_tokens": 10000},@@ -1249,6 +1253,46 @@"type","types"]+ },+ {+ "name": "structure-templates",+ "kind": "json_collection",+ "source": "skills/ppt-master/templates/structures/structures_index.json",+ "key": "structures",+ "reference_terms": [+ "structures_index.json",+ "structure catalog"+ ],+ "claim_nouns": [+ "structure",+ "structures",+ "summary",+ "summaries",+ "template",+ "templates",+ "type",+ "types"+ ]+ },+ {+ "name": "table-templates",+ "kind": "json_collection",+ "source": "skills/ppt-master/templates/tables/tables_index.json",+ "key": "tables",+ "reference_terms": [+ "tables_index.json",+ "table catalog"+ ],+ "claim_nouns": [+ "table",+ "tables",+ "summary",+ "summaries",+ "template",+ "templates",+ "type",+ "types"+ ]}],"schema_grammars": [@@ -1257,6 +1301,7 @@"fields": ["font_family","image_rendering",+ "page_visualizations","page_charts","page_layouts","page_pptx_layouts",@@ -1357,7 +1402,15 @@},{"glob": "skills/ppt-master/templates/charts/charts_index.json",- "reason": "Machine-consumed chart-recall registry; Strategist receives only the ranked candidate summaries."+ "reason": "Machine-consumed chart-family registry; Strategist receives only bounded visualization-recall candidates."+ },+ {+ "glob": "skills/ppt-master/templates/structures/structures_index.json",+ "reason": "Machine-consumed structure-family registry; Strategist receives only bounded visualization-recall candidates."+ },+ {+ "glob": "skills/ppt-master/templates/tables/tables_index.json",+ "reason": "Machine-consumed table-family registry; Strategist receives only bounded visualization-recall candidates."},{"glob": "skills/ppt-master/templates/schemas/*.json",diff --git a/skills/ppt-master/scripts/visualization_catalog.py b/skills/ppt-master/scripts/visualization_catalog.pyindex 038fc6b9..d7ae0433 100644--- a/skills/ppt-master/scripts/visualization_catalog.py+++ b/skills/ppt-master/scripts/visualization_catalog.py@@ -163,18 +163,12 @@ def _load_family(family: str) -> tuple[dict[str, VisualizationEntry], dict[str,def load_visualization_catalog(families: Iterable[str] | None = None,- *,- allow_missing_families: bool = False,) -> VisualizationCatalog:"""Load selected live family registries."""selected = _normalize_families(families)entries: dict[str, VisualizationEntry] = {}aliases: dict[str, str] = {}for family in selected:- directory_name, index_name, _object_key = _FAMILY_SPECS[family]- index_path = _TEMPLATES_DIR / directory_name / index_name- if not index_path.is_file() and allow_missing_families:- continuefamily_entries, family_aliases = _load_family(family)entries.update(family_entries)aliases.update(family_aliases)@@ -188,14 +182,9 @@ def load_visualization_catalog(def load_visualization_entries(families: Iterable[str] | None = None,- *,- allow_missing_families: bool = False,) -> dict[str, VisualizationEntry]:"""Return canonical entries keyed by ``family/key``."""- return load_visualization_catalog(- families,- allow_missing_families=allow_missing_families,- ).entries+ return load_visualization_catalog(families).entriesdef _require_svg(entry: VisualizationEntry) -> VisualizationEntry:@@ -216,7 +205,7 @@ def resolve_visualization_reference(if not normalized:raise VisualizationCatalogError("visualization reference must not be empty")- catalog = load_visualization_catalog(allow_missing_families=True)+ catalog = load_visualization_catalog()if "/" in normalized:family, separator, key = normalized.partition("/")if (diff --git a/skills/ppt-master/scripts/visualization_recall.py b/skills/ppt-master/scripts/visualization_recall.pyindex 3b31d2e1..8e5a5848 100644--- a/skills/ppt-master/scripts/visualization_recall.py+++ b/skills/ppt-master/scripts/visualization_recall.py@@ -101,7 +101,6 @@ def load_catalog(family: str = "all") -> dict[str, VisualizationEntry]:"""Load the selected live family catalogs."""return load_visualization_entries(_selected_families(family),- allow_missing_families=family == "all",)diff --git a/skills/ppt-master/templates/README.md b/skills/ppt-master/templates/README.mdindex 944e6d87..b145af21 100644--- a/skills/ppt-master/templates/README.md+++ b/skills/ppt-master/templates/README.md@@ -116,23 +116,20 @@ effects and PowerPoint interfaces loaded only when triggered.## Visualization Templates-The `charts/` directory contains the registered visualization templates. For backward compatibility, the directory name remains `charts/`, but its scope includes charts, infographics, process diagrams, relationship diagrams, strategic frameworks, and system architecture diagrams:--- KPI Cards-- Bar Chart / Stacked Bar Chart-- Line Chart / Dual-Axis Line Chart-- Donut Chart-- Radar Chart-- Funnel Chart-- Matrix (2x2)-- Timeline-- Gantt Chart-- Process Flow-- Org Chart-- Layered Architecture / Module Composition / Hub with Described Spokes / Pipeline with Stages / Client-Server Flow--- **Library index (single source of truth)**: [charts/charts_index.json](./charts/charts_index.json)-- **Directory overview**: [charts/README.md](./charts/README.md)+Page-local Shape-first references are families, not reusable template kinds:++| Family | Owns | Directory | Index |+|---|---|---|---|+| Chart | Value-driven geometry | [`charts/`](./charts/) | [`charts_index.json`](./charts/charts_index.json) |+| Structure | Qualitative topology | [`structures/`](./structures/) | [`structures_index.json`](./structures/structures_index.json) |+| Table | Cell grid | [`tables/`](./tables/) | [`tables_index.json`](./tables/tables_index.json) |++[`VISUALIZATION_TEMPLATE_AUTHORING.md`](./VISUALIZATION_TEMPLATE_AUTHORING.md)+is the shared authoring contract. Each index owns family membership and+selection rules.++Only [`layouts/`](./layouts/) owns Master/Layout, page types, slots, and+placeholders; structures stay Slide-local.## Icon Librarydiff --git a/skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.md b/skills/ppt-master/templates/VISUALIZATION_TEMPLATE_AUTHORING.mdsimilarity index 77%rename from skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.mdrename to skills/ppt-master/templates/VISUALIZATION_TEMPLATE_AUTHORING.mdindex 24553d21..48ae6c10 100644--- a/skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.md+++ b/skills/ppt-master/templates/VISUALIZATION_TEMPLATE_AUTHORING.md@@ -1,17 +1,31 @@-# Chart Template Authoring Guide+# Visualization Template Authoring Guide-`templates/charts/` 的模板负责可视化结构、数据编码和信息关系,不负责最终项目风格。模板必须保持源码可读、独立可渲染,并允许 Executor 根据项目 Design Spec 与 `spec_lock.md` 重做字体、配色和装饰。+`templates/charts/`、`templates/structures/` 和 `templates/tables/` 共同组成+page-local Visualization 模板库。模板负责信息结构、数据编码或单元格关系,+不负责最终项目风格。模板必须保持源码可读、独立可渲染,并允许 Executor+根据项目 Design Spec 与 `spec_lock.md` 重做字体、配色和装饰。++| Family | 定义 | 判定边界 |+|---|---|---|+| `chart` | Value-driven visualization | 数值、类别、时间、权重或持续时间决定 mark 的位置、长度、面积、角度、字号或连接宽度 |+| `structure` | Page-local qualitative topology | 顺序、层级、角色、分区或关系决定页面内的节点与连接;几何不由数值映射驱动 |+| `table` | Cell grid | 行、列、单元格、表头、合并、对齐和边界构成主要语义;单元格数值不决定外部 mark 几何 |++**Hard rule — Visualization is not Layout**: `structure` 只拥有一页内可适配的+qualitative topology,不拥有 `data-pptx-master`、`data-pptx-layout`、+`data-pptx-layer` 或 `data-pptx-placeholder`。跨页 Master/Layout、page type、+slot geometry 和 placeholder 合同仍只属于 [`layouts/`](./layouts/) workspace。## 0. 上游规范-**Hard rule**: 本指南只定义 Chart 模板库的结构与中性预览合同。通用 SVG 语法、效果、原生数据接口和 PowerPoint 结构分别由以下权威文件定义:+**Hard rule**: 本指南只定义三个 Visualization family 的结构与中性预览合同。通用 SVG 语法、效果、原生数据接口和 PowerPoint 结构分别由以下权威文件定义:| 合同 | 权威文件 ||---|---|-| 通用 SVG | [`shared-standards.md`](../../references/shared-standards.md) |-| 效果与兼容输入 | [`svg-effects.md`](../../references/svg-effects.md) |-| Native Chart/Table | [`native-data-interface.md`](../../references/native-data-interface.md) |-| 画布格式 | [`canvas-formats.md`](../../references/canvas-formats.md) |+| 通用 SVG | [`shared-standards.md`](../references/shared-standards.md) |+| 效果与兼容输入 | [`svg-effects.md`](../references/svg-effects.md) |+| Native Chart/Table | [`native-data-interface.md`](../references/native-data-interface.md) |+| 画布格式 | [`canvas-formats.md`](../references/canvas-formats.md) |**Forbidden — second SVG specification**: 不在本指南复述或放宽上游语法。发生冲突时以上游权威文件为准。@@ -19,19 +33,28 @@## 1. 所有权边界-### 1.1 模板与项目+### 1.1 作者合同与项目消费-| Chart 模板拥有 | 项目拥有 |+以下所有权只约束库内单个模板工件的维护,不把该工件变成项目页面的布局锁:++| 单个 Visualization 模板的作者合同 | 项目页面决策拥有 ||---|---|-| 可视化类型与数据到图形的映射 | 项目字体与字号体系 |-| 节点、连接、轴、系列和标签关系 | 项目调色板与品牌色 |-| 可视化类型、构图骨架和阅读顺序 | 实际分组、框架数量、项目数量与容量适配 |+| 该工件的 family 与相应信息模型 | 最终采用的页面级结构、类型与几何 |+| 该工件内的数据映射、拓扑或单元格关系 | 项目字体、字号、调色板与品牌色 |+| 该工件的示例骨架和阅读顺序 | 实际分组、框架数量、项目数量、组合方式与容量适配 || 必要的状态与语义区分 | 页面背景、页头、页脚和品牌 chrome || 独立预览所需的中性样式 | 最终强调策略与页面级视觉层级 |-**Hard rule**: Executor 适配模板时保留可视化类型、信息关系和数据准确性;最终视觉必须来自当前项目,而不是继承模板的示例审美。+**Hard rule — authoring integrity**: 维护某个库模板时必须保持该模板自身的+family 与信息模型:Chart 的 value mapping、Structure 的 qualitative topology、+Table 的 cell grid。若修改结果已经属于另一 family,应作为另一 family 的工件+登记,不能保留错误标签。最终视觉样式仍来自使用它的项目,而不是模板的示例审美。-**Reference — not a constraint**: 模板的分组、框架数、项目数和示例容量用于展示结构,不是项目上限。Executor 可按实际内容调整,但不能改变已选可视化类型、关系或数据语义。+**Hard rule — flexible project reference**: Executor 选中的 `family/key` 仍只是+flexible page-local reference。Default 的 §IX 或 Quick 的页面决策拥有最终结构;+选中引用不会锁死页面的可视化类型、几何、分组数、项目数或组合方式,Executor+可按已确认的页面意图适配、重组或替换。项目若实际采用某一信息模型,必须保持+其真实数据与关系准确;仅有引用本身不构成页面结构权威。### 1.2 保留判断@@ -174,12 +197,16 @@| 顶层组 | 典型内容 ||---|---|| `header` | 标题与副标题 |-| `chart-area` / replacement carrier | 轴、数据系列、标签、必要 metadata |+| `chart-area` / replacement carrier | Chart 的轴、数据系列、标签、必要 metadata || `legend` | 系列或状态说明 || `card-1` / `feature-card-1` | 一个完整信息单元 || `timeline-track` | 时间轴与阶段标签 || `milestone-cards` | 同一结构的一组里程碑卡片 |+**Forbidden — workspace metadata**: 三个 family 都不得写入 Master/Layout/+placeholder 所有权标记。即使 Structure 预览占满整个 `1280×720` 画布,它仍是+一页内的 flexible reference,不会因此成为 Layout workspace。+### 5.2 `data-pptx-bounds`**Hard rule**: 每个可见直属根 `<g>` 都声明正数、根坐标系的 `data-pptx-bounds="x y width height"`。即使该组已有 native chart/table frame,也保留 bounds。@@ -220,7 +247,7 @@----## 6. 数据图表合同+## 6. Chart 与 Native Data 合同### 6.1 绘图区标记@@ -234,7 +261,7 @@ Pie、Donut、Radar 使用对应中心和半径格式。该注释是工具输入### 6.2 Native Chart/Table-**Hard rule**: 只有 [`native-data-interface.md`](../../references/native-data-interface.md) 支持的真实数据图表或纯文本表格使用 replacement marker。JSON metadata 与可见 fallback 必须表达同一份数据。+**Hard rule**: 只有 [`native-data-interface.md`](../references/native-data-interface.md) 支持的真实 Chart 或纯文本 Table 使用 replacement marker。JSON metadata 与可见 fallback 必须表达同一份数据。Structure 永远不使用 Chart/Table replacement marker。```xml<g id="line-chart"@@ -275,9 +302,17 @@ Pie、Donut、Radar 使用对应中心和半径格式。该注释是工具输入**Forbidden — placeholder storytelling**: 不写长篇营销文案、部门归属、真实品牌或无法复用的项目背景。-### 7.2 `charts_index.json`+### 7.2 Family indexes++新增模板只登记到其 owning family index:-新增模板必须登记 `<key>.summary`:+| Family | Directory | Index object |+|---|---|---|+| `chart` | `charts/` | `charts_index.json` → `charts` |+| `structure` | `structures/` | `structures_index.json` → `structures` |+| `table` | `tables/` | `tables_index.json` → `tables` |++每个 `<key>.summary` 使用相同的选择句合同:```json"line_chart": {@@ -285,13 +320,26 @@ Pie、Donut、Radar 使用对应中心和半径格式。该注释是工具输入}```-**Hard rule**: `summary` 是选型句,使用 `Pick for ... Skip if ...`,不是视觉描述;`key` 与文件名一致,`meta.total` 与 catalog 数量一致。+**Hard rule**: `summary` 是选型句,使用 `Pick for ... Skip if ...`,不是视觉描述;`key` 与同 family 文件名一致,`meta.total` 与该 family catalog 数量一致。不要建立跨 family 的第二份成员清单。---## 8. 迁移边界-本指南是新建和修改模板的目标合同。当前目录中的 76 个 SVG 均已纳入该合同;后续不得以历史文件为由恢复无语义装饰,也不得把中性化误解为删除结构边界。+本指南是新建和修改模板的目标合同。当前三个 family 共 76 个 SVG:+Chart 33 个、Structure 36 个、Table 7 个。各 live index 是成员清单的唯一权威;+后续不得以历史文件为由恢复无语义装饰,也不得把中性化误解为删除结构边界。++**Canonical migration aliases**:++| Legacy bare key | Canonical reference |+|---|---|+| `pros_cons_chart` | `structure/pros_cons_comparison` |+| `pyramid_chart` | `structure/layered_pyramid` |+| `quadrant_bubble_scatter` | `structure/quadrant_text_cards` |++新文档、§VII 和 `page_visualizations` 只写 canonical family/key。Alias 只服务旧+`page_charts` 读取,不是新模板命名候选。**Current reference set**:@@ -334,7 +382,7 @@ Pie、Donut、Radar 使用对应中心和半径格式。该注释是工具输入| `hub_inward_arrows.svg` | 外围输入、向心关系和中心结论 || `treemap_chart.svg` | 层级面积编码、分类色块、标签和解释注记 || `hub_spoke.svg` | 中心枢纽、径向连接、能力节点和参考环 |-| `matrix_2x2.svg` | 双轴象限、点位分布、象限标签和优先级说明 |+| `matrix_2x2.svg` | 数据点的 x/y 坐标分别编码两轴数值,半径编码第三指标,并保留象限标签 || `process_flow.svg` | 顺序节点、连接关系、阶段时长和状态图例 || `donut_chart.svg` | 环形占比、中心总值、系列图例和摘要指标 || `grouped_bar_chart.svg` | 多系列并列柱、共用分类轴和系列图例 |@@ -347,11 +395,11 @@ Pie、Donut、Radar 使用对应中心和半径格式。该注释是工具输入| `comparison_table.svg` | 多方案表头、横向属性行和结果强调 || `client_server_flow.svg` | 客户端与服务端分区、请求响应和交互方向 || `dumbbell_chart.svg` | 双状态端点、变化连线、差值和项目排序 |-| `pyramid_chart.svg` | 递进层级、分层容量和层级说明 |+| `layered_pyramid.svg` | 递进层级、分层容量和层级说明;不以数值映射层高或面积 || `vertical_pillars.svg` | 并列支柱、分类标题、要点列表和底部结论 || `journey_map.svg` | 阶段轨道、用户行动、情绪曲线和痛点卡片 || `consulting_table.svg` | 分层行列、指标数值、数据条和重点结论 |-| `pros_cons_chart.svg` | 正反双栏、判断轴、论据列表和建议结论 |+| `pros_cons_comparison.svg` | 正反双栏、判断轴、论据列表和建议结论 || `project_schedule_table.svg` | 任务表格、负责人、状态和横向排期 || `horizontal_bar_chart.svg` | 长标签排名、横向数值条和洞察侧栏 || `funnel_chart.svg` | 递减阶段、转化率、流失关系和摘要指标 |@@ -369,7 +417,7 @@ Pie、Donut、Radar 使用对应中心和半径格式。该注释是工具输入| `feature_matrix_table.svg` | 功能行、产品列、二元状态和方案对照 || `histogram_chart.svg` | 连续分箱、频数柱、统计标记和分布解释 || `venn_diagram.svg` | 集合边界、交集区域、关系标签和结论说明 |-| `quadrant_bubble_scatter.svg` | 双轴象限、气泡位置、尺寸编码和项目标签 |+| `quadrant_text_cards.svg` | 固定 2×2 命名象限,每个象限承载标题与文本条目;不含 value-mapped bubbles || `bar_of_pie_chart.svg` | 主饼占比、长尾聚合、堆叠条明细和连接关系 || `pie_of_pie_chart.svg` | 主饼占比、长尾聚合、次级饼明细和连接关系 || `word_cloud.svg` | 词项权重、字号编码、主题分布和关键词层级 |@@ -397,18 +445,20 @@ Pie、Donut、Radar 使用对应中心和半径格式。该注释是工具输入- [ ] 颜色差异确实表达 series、state、positive/negative 等语义。- [ ] 标题、副标题和来源只用于展示必要结构或容量。-### 9.3 数据与 PowerPoint+### 9.3 Family 与 PowerPoint-- [ ] 数据图表保留准确 `chart-plot-area` 标记。-- [ ] Eligible Chart/Table 的 metadata 与可见 fallback 数据一致。+- [ ] Family 判定正确:Chart 为 value-driven、Structure 为 qualitative topology、Table 为 cell grid。+- [ ] Structure 不含 Master/Layout/layer/placeholder ownership metadata。+- [ ] Calculator-supported Chart 保留准确 `chart-plot-area` 标记。+- [ ] Eligible Chart/Table 的 metadata 与可见 fallback 数据一致;Structure 无 replacement marker。- [ ] 默认 Shape-first 导出通过。- [ ] 存在 replacement marker 时,显式 native Chart/Table 导出通过。- [ ] `svg_quality_checker.py` 无 error;warning 已人工判断。### 9.4 Catalog-- [ ] 新模板已登记 `charts_index.json`。-- [ ] 修改 key/summary 后通过 `chart_recall.py validate` 和 recall 烟测。+- [ ] 新模板只登记到 owning family index,index object、`meta.total` 与 SVG roster 一致。+- [ ] 修改 key/summary 后通过 `visualization_recall.py validate` 和 recall 烟测。- [ ] 前后可见文本差异已审阅,非重复内容没有意外丢失或改写。- [ ] 前后渲染对比确认结构仍可读。- [ ] 记录 bytes/tokens 变化,但不以牺牲源码可读性换取数字。@@ -420,14 +470,15 @@ Pie、Donut、Radar 使用对应中心和半径格式。该注释是工具输入```bash# 单文件 SVG 合同python3 skills/ppt-master/scripts/svg_quality_checker.py \- skills/ppt-master/templates/charts/<key>.svg+ skills/ppt-master/templates/<family-directory>/<key>.svg-# Catalog key-python3 skills/ppt-master/scripts/chart_recall.py validate <key>+# Canonical family/key+python3 skills/ppt-master/scripts/visualization_recall.py validate \+ <family>/<key># 可安全压缩的页面坐标(默认 dry-run)python3 skills/ppt-master/scripts/compact_svg_coordinates.py \- skills/ppt-master/templates/charts/<key>.svg+ skills/ppt-master/templates/<family-directory>/<key>.svg```**Validation**: 修改后至少完成 XML 解析、独立 SVG 渲染、Checker、默认 Shape-first 导出,以及 marker 模板的 native Chart/Table 导出。diff --git a/skills/ppt-master/templates/charts/README.md b/skills/ppt-master/templates/charts/README.mdindex 41330974..75b26081 100644--- a/skills/ppt-master/templates/charts/README.md+++ b/skills/ppt-master/templates/charts/README.md@@ -1,74 +1,51 @@-# SVG Visualization Template Library+# Chart Visualization Templates-This directory contains the standardized SVG visualization templates used by PPT Master — charts, infographics, process diagrams, relationship diagrams, and strategic frameworks. The directory name `charts/` is kept for backward compatibility; the library scope is broader than charts.+This directory contains the value-driven chart family. A chart belongs here+when source values, categories, time, weights, or durations determine visual+mark position, length, area, angle, font size, or connection width.++Qualitative page topology belongs in [`structures/`](../structures/). Cell-grid+semantics belong in [`tables/`](../tables/). Reusable PowerPoint Master/Layout,+page-type, slot, and placeholder contracts belong in+[`layouts/`](../layouts/).## Source of truth-[`charts_index.json`](./charts_index.json) is the single source of truth for the library: total count + one selection-rule `summary` per template (format: `"Pick for X. Skip if Y (use other_key)."`). [`chart_recall.py`](../../scripts/chart_recall.py) can recall a bounded candidate set from this live registry without maintaining a second category or keyword index.+[`charts_index.json`](./charts_index.json) is the sole chart registry. Its+`charts` object maps each canonical key to one selection-rule `summary` in the+form `Pick for ... Skip if ...`. The key matches `<key>.svg`; `meta.total`+matches the canonical SVG roster.-For one page, provide 3-8 English semantic content-shape tags, then inspect the positive-scoring summaries plus the explicit `no-template-match` option. The requested limit is a cap, not a padding target, and lexical confidence never expands the output automatically. At `high` / `medium`, retain `no-template-match` when no bounded candidate fits. At `low` / `none`, a fitting candidate needs no expansion, but rerun the same query once with `--semantic-fallback` before keeping `no-template-match`. In Default Generate, a selected result creates one `Page | Template | Usage` row in §VII and one matching `page_charts` entry; its path is derived from the key, while Usage is concise page-local intent and detailed adaptation remains in §IX. Quick Generate keeps the selected key/purpose only in active context and writes no mapping artifact. A negative result creates no row in either profile. See [`chart-recall.md`](../../scripts/docs/chart-recall.md). The Generate workflow remains the authority for when the active profile uses this helper; maintainers may still open the registry directly when editing or auditing the catalog.+Use [`visualization_recall.py`](../../scripts/visualization_recall.py) for+bounded all-family or chart-only recall. New Default planning writes+`chart/<key>` to `page_visualizations`; Quick keeps the selected reference in+active context. [`chart_recall.py`](../../scripts/chart_recall.py) and bare keys+remain legacy compatibility only.## Authoring contract-[`CHART_STYLE_GUIDE.md`](./CHART_STYLE_GUIDE.md) owns readable standalone SVG, semantic and structural fidelity, root-group bounds, data encoding, and neutral previews. Default Design Spec §IX or the Quick active-context page decision plus source data own the generated page's semantics; Default `spec_lock.md` owns stable project anchors. A selected SVG is a page-local structural reference, while its type, styling, frames, grouping, item count, capacity, and geometry remain adaptable.--## Visualization output model--This library is **Shape-first**. Infographics, process diagrams, architecture-diagrams, frameworks, and the default rendering of data charts export as-independently editable PowerPoint shapes:--- Use ordinary SVG primitives for basic nodes, containers, and straight- relationships; they export as editable PowerPoint shapes. A straight- directional relationship uses `<line>` with a registered arrow marker.-- When a bent or curved relationship exactly matches a stock Connector contour,- prefer a compact authored `bentConnector*` / `curvedConnector*` preset. It is- an unconnected native Connector shape and does not create node attachment or- automatic routing.-- Use a stock PowerPoint preset for a solid block arrow, chevron, or standard- flowchart node when it exactly expresses the intended object. A template may- retain the complete compact atomic `<g>` generated by `preset_shape_svg.py`,- so direct export preserves the native preset identity. The group owns the- metadata and base paint once; its direct visible paths are registry-derived- layers with only necessary per-layer paint overrides. It has no hidden- carrier, preview wrapper, or stored fingerprint. If preset, frame,- adjustments, or paint changes, regenerate the whole group instead of editing- metadata or paths. PPTX import and `mirror` retain their separate expanded- lossless representation; do not copy that transport form into new templates.-- When no single preset suffices but closed operands can express the object,- materialize the Union / Combine / Fragment / Intersect / Subtract result with- `shape_boolean_svg.py` before considering a hand-authored contour.-- Keep a hand-authored `<path>` / `<polygon>` only for branded, data-defined,- locked organic / hand-drawn, or other contours that primitives, an exact- preset, and Boolean materialization cannot faithfully express. They still- export as editable DrawingML shapes.-- Authored Connector metadata comes only from `preset_shape_svg.py`; never- hand-write endpoint attachment metadata. Existing attached Connector topology- imported from a source PPTX belongs to the preserve/mirror round-trip- contract, not chart-template authoring.--Data-backed charts retain the separate opt-in replacement route described-below. Conceptual diagrams and frameworks are never labeled as native charts.--## Native Chart/Table replacement markers--Supported data chart templates include a `<g data-pptx-replace-with="chart">` marker by default, and pure text-grid table templates include the table form. These are capability examples, not project decisions: Default keeps and rewrites the marker only when its Design Spec §IX page block says `Native-ready: yes` (legacy §VII fallback only); Quick makes the same independent-object decision in active context before drawing. Otherwise omit it. The default SVG export path remains shape-based DrawingML. With `--native-charts-and-tables`, prepared groups become native PowerPoint Chart/Table objects from their JSON metadata. The legacy `--native-objects` spelling remains a compatibility alias.--`--native-charts-and-tables` is an explicit native-object opt-in and may be lossy or visually normalized. Replacement-local value labels, center KPIs, callouts, quadrant notes, fixed axis ranges, and custom binning/splits may not survive native replacement unless represented by the payload. ChartEx palette entries do survive when supplied through valid payload colors, but this does not preserve every ChartEx style detail. Detectable information-loss risks should be reported as warnings, not handled by disabling an otherwise supported replacement marker. Review those warnings and compare the native-object export with the default shape-based export before delivery.--Native replacement authoring remains active for all 23 currently supported data-chart templates:--| Family | Active replacement templates | Native output |-|---|---|---|-| Category comparison | `column_chart`, `horizontal_bar_chart`, `grouped_bar_chart`, `stacked_bar_chart` | Classic category charts |-| Time trend | `line_chart`, `area_chart`, `stacked_area_chart`, `dual_axis_line_chart` | Classic line/area/combo charts |-| Part-to-whole | `pie_chart`, `donut_chart`, `pie_of_pie_chart`, `bar_of_pie_chart`, `treemap_chart`, `sunburst_chart` | Classic pie-family or ChartEx hierarchy charts |-| Distribution and relationship | `scatter_chart`, `bubble_chart`, `histogram_chart`, `pareto_chart`, `box_plot_chart` | Classic XY or ChartEx distribution charts |-| Specialty business charts | `waterfall_chart`, `funnel_chart`, `stock_chart`, `radar_chart` | ChartEx or classic specialty charts |-| Text-grid tables | `basic_table`, `financial_statement_table` | Native DrawingML tables |--Replacement payloads must include explicit `name`, `x`, `y`, `width`, and `height` fields so the native frame aligns with the fallback drawing. Keep legends, explanatory cards, source notes, center KPIs, and custom callouts outside the marked group when they must remain separate shapes; otherwise accept and review the native-object export warning. Canonical rectangular merged text cells may use anchor-only `row_span` / `col_span` metadata with blank covered cells; nonrectangular merges and graphical cells (harvey balls, rating dots, avatars) stay unmarked on the SVG fallback route. Per-side borders, plain multi-paragraph cells, and the closed run-rich paragraph schema use the contracts in [`native-data-interface.md`](../../references/native-data-interface.md#2-powerpoint-native-chart--table-replacement-markers-opt-in). Relationship-bearing text, structural line breaks, fields, tabs, bullets, and arbitrary rich-text OOXML stay on the SVG fallback route.--## Usage--Execution loads only selected keys under [`executor-chart.md`](../../references/executor-chart.md) §1 and reuses an unchanged file within the active context. Files are named after the `key` field in `charts_index.json` (e.g. `column_chart.svg`, `quadrant_bubble_scatter.svg`). Templates are named by visual structure, not by business-model name — terms like SWOT, BCG, PEST, OKR, Porter's Five Forces, and Value Chain are translated into semantic content-shape tags before candidate recall.+[`VISUALIZATION_TEMPLATE_AUTHORING.md`](../VISUALIZATION_TEMPLATE_AUTHORING.md)+owns the shared standalone-SVG, neutral-preview, root-boundary, Shape-first,+family, and catalog rules. Chart-specific requirements are:++- Preserve the exact value-to-mark mapping, labels, units, categories, series,+ ordering, and source notes required by the information.+- Keep calculator-supported `chart-plot-area` markers accurate.+- Default output remains independently editable DrawingML shapes.+- Add native Chart replacement metadata only for a supported independent data+ object. The visible fallback and metadata describe the same data.+- Do not classify a named quadrant, process, hierarchy, or relationship diagram+ as a chart unless values actually determine its marks.++`matrix_2x2` is a chart: each item's x/y coordinates encode two values and its+radius encodes a third metric. A fixed 2×2 set of titled text regions is instead+`structure/quadrant_text_cards` or another structure reference.++## Runtime boundary++One selected SVG is a flexible reference for one mapped page. Design Spec §IX+or the Quick active-context decision plus source data owns final semantics.+Project palette, typography, chrome, grouping, capacity, and geometry remain+adaptable. Selecting a chart reference does not itself select native output;+`Native-ready` and explicit `--native-charts-and-tables` export remain separate+decisions.diff --git a/skills/ppt-master/templates/charts/charts_index.json b/skills/ppt-master/templates/charts/charts_index.jsonindex 5d8d83f0..e3046bbf 100644--- a/skills/ppt-master/templates/charts/charts_index.json+++ b/skills/ppt-master/templates/charts/charts_index.json@@ -1,12 +1,14 @@{"meta": {- "total": 76,+ "total": 33,"defaultViewBox": "0 0 1280 720",- "formats": ["ppt169"],+ "formats": [+ "ppt169"+ ],"filePattern": "{key}.svg",- "libraryPositioning": "Visualization template library covering charts, infographics, diagrams, and strategic frameworks. The `charts/` path is retained for backward compatibility. Templates are named by visual structure, not by business-model name — model-specific frameworks (SWOT, BCG, PEST, OKR, Porter's Five Forces, Value Chain, etc.) are matched via keywords in `summary`.",- "summaryGrammar": "Each chart's `summary` is a selection rule, not a description. Format: 'Pick for <content shape + scale>. Skip if <reason → alternative>'. Strategist supplies 3–8 semantic content-shape tags per candidate page; chart_recall.py returns a bounded lexical shortlist and exposes the full catalog only through an explicitly requested semantic fallback.",- "updated": "2026-07-21"+ "libraryPositioning": "Data-driven visualization templates whose source values determine geometry or visual encoding.",+ "summaryGrammar": "Each chart summary is a selection rule, not a description. Format: 'Pick for <content shape + scale>. Skip if <reason → alternative>'.",+ "updated": "2026-08-08"},"charts": {"area_chart": {@@ -15,9 +17,6 @@"bar_of_pie_chart": {"summary": "Pick for pie composition where small long-tail slices should be expanded into a stacked bar detail. Skip if secondary detail should stay circular (use pie_of_pie_chart) or flat shares suffice (use pie_chart)."},- "column_chart": {- "summary": "Pick for single-series category value comparison, 3-8 categories. Skip for >12 long-label items (use horizontal_bar_chart) or multi-series (use grouped_bar_chart)."- },"box_plot_chart": {"summary": "Pick for distribution shape per group (median, quartiles, outliers). Skip if only the average per group matters (use column_chart)."},@@ -30,11 +29,14 @@"butterfly_chart": {"summary": "Pick for two mirrored datasets sharing a common axis (age pyramid, A/B, income vs expense). Skip for >2 sides (use grouped_bar_chart)."},+ "column_chart": {+ "summary": "Pick for single-series category value comparison, 3-8 categories. Skip for >12 long-label items (use horizontal_bar_chart) or multi-series (use grouped_bar_chart)."+ },"donut_chart": {"summary": "Pick for 3-6 part proportions where a center KPI/total deserves emphasis. Skip if no center value to feature (use pie_chart)."},"dual_axis_line_chart": {- "summary": "Pick when 2 metrics with different units/scales must be compared over time. Skip if both metrics share the same unit (use line_chart)."+ "summary": "Pick for comparing 2 metrics with different units/scales over time. Skip if both metrics share the same unit (use line_chart)."},"dumbbell_chart": {"summary": "Pick for before-vs-after or two-state difference across 5-10 items. Skip for single snapshot (use column_chart) or 3+ states (use grouped_bar_chart)."@@ -60,23 +62,14 @@"horizontal_bar_chart": {"summary": "Pick for ranking 5-12 items, especially with long labels. Skip if <=8 short-label items (use column_chart)."},- "kpi_cards": {- "summary": "Pick for 4-8 standalone numeric metrics shown as overview cards (2x2 or 1x4) — exec summary opener, dashboard headline, quarterly recap, results-at-a-glance. Skip if metrics have target baselines (use bullet_chart) or single hero number (use gauge_chart)."- },"line_chart": {"summary": "Pick for 1-3 time-series on a continuous axis showing direction. Skip if cumulative volume matters (use area_chart) or different units (use dual_axis_line_chart)."},"matrix_2x2": {- "summary": "Pick for items plotted on Impact x Effort or similar generic 2-axis prioritization. Skip for named-quadrant text frameworks (use quadrant_text_bullets) or bubble-sized portfolios (use quadrant_bubble_scatter)."- },- "quadrant_text_bullets": {- "summary": "Pick for any 2×2 framework where each quadrant holds a titled bullet list — SWOT (Strengths/Weaknesses/Opportunities/Threats, internal-external × helpful-harmful), Ansoff (Existing/New Markets × Existing/New Products), or any named two-axis matrix with text content. Skip for items plotted as points (use matrix_2x2) or bubble-sized portfolios (use quadrant_bubble_scatter)."- },- "quadrant_bubble_scatter": {- "summary": "Pick for 2×2 portfolio where items are plotted as bubbles sized by a third metric — BCG Growth × Share with Stars/Cash Cows/Question Marks/Dogs, revenue-weighted portfolio matrix. Skip for textual named quadrants (use quadrant_text_bullets) or generic prioritization without bubble size (use matrix_2x2)."+ "summary": "Pick for 4-10 items whose x and y positions encode two dimensions and whose bubble radius encodes a third magnitude inside a 2×2 quadrant frame. Skip for fixed named quadrant text cards (use quadrant_text_cards) or detailed quadrant bullet frameworks without plotted items (use quadrant_text_bullets)."},"pareto_chart": {- "summary": "Pick to show 80/20 contribution: descending bars + cumulative line. Skip if cumulative line is not the message (use column_chart)."+ "summary": "Pick for showing 80/20 contribution with descending bars and a cumulative line. Skip if the cumulative line is not the message (use column_chart)."},"pie_chart": {"summary": "Pick for simple 3-6 part proportions of one whole. Skip for >=7 parts (use donut_chart or treemap_chart) or hierarchical composition (use treemap_chart)."@@ -84,12 +77,6 @@"pie_of_pie_chart": {"summary": "Pick for pie composition where small slices need a secondary pie detail. Skip if the secondary detail is easier to compare as bars (use bar_of_pie_chart) or hierarchy matters (use sunburst_chart)."},- "hub_inward_arrows": {- "summary": "Pick for 1 center subject + 4-5 surrounding forces with arrows pointing inward — Porter's Five Forces (central rivalry, threat of new entrants/substitutes, bargaining power of buyers/suppliers), threat-model with central asset, pressure-on-core diagrams. Skip for outward radiation from center capability (use hub_spoke) or non-directional cluster (use mind_map)."- },- "process_flow": {- "summary": "Pick for 3-8 sequential steps connected by simple arrows — approval workflows, customer onboarding, request handling, lifecycle stages. Skip if cyclical (use circular_stages) or stages produce named outputs (use pipeline_with_stages)."- },"progress_bar_chart": {"summary": "Pick for 3-8 items each with a completion %. Skip if items have explicit target+actual values (use bullet_chart)."},@@ -106,7 +93,7 @@"summary": "Pick for 2-4 series showing both total and composition over time. Skip if individual series matter more than total (use line_chart)."},"stacked_bar_chart": {- "summary": "Pick when each category splits into 2-4 internal parts and total still matters. Skip if only comparing totals (use column_chart)."+ "summary": "Pick for categories split into 2-4 internal parts when each total still matters. Skip if only comparing totals (use column_chart)."},"stock_chart": {"summary": "Pick for open-high-low-close price movement over dates. Skip if showing only close-price direction (use line_chart) or category volume comparison (use column_chart)."@@ -114,128 +101,14 @@"sunburst_chart": {"summary": "Pick for hierarchical part-to-whole composition across 2-3 levels where each ring should stay visible. Skip if rectangular area comparison is clearer (use treemap_chart) or shares are flat (use donut_chart)."},- "timeline": {- "summary": "Pick for 3-8 milestone events on a horizontal time axis (no duration). Skip for tasks with start/end ranges (use gantt_chart) or vertical layout (use roadmap_vertical)."- },"treemap_chart": {"summary": "Pick for hierarchical/grouped area proportion with many parts of varying size. Skip for flat 3-6 parts (use pie_chart or donut_chart)."},"waterfall_chart": {"summary": "Pick for stepwise additive/subtractive breakdown bridging a starting value to an ending value. Skip if no running total (use column_chart)."},- "pyramid_chart": {- "summary": "Pick for 3-6 stratified hierarchy layers in flat 2D side-view — Maslow's hierarchy, maturity models, value hierarchy, capability tiers, market segments, audience pyramid. Skip for dramatic tone (use pyramid_isometric), flat priority list (use vertical_list), or org reporting (use top_down_tree)."- },- "pyramid_isometric": {- "summary": "Pick for 4-tier maturity/achievement model with presentation drama (review reports, capability tiers). Tier count fixed at 4 (hand-tuned vertices). Skip for documentary tone (use pyramid_chart) or tier count != 4."- },- "venn_diagram": {- "summary": "Pick for 2-3 overlapping sets where the intersection is the message. Skip if no overlap exists (use icon_grid)."- },- "pros_cons_chart": {- "summary": "Pick for bilateral pros/cons list, 2-5 items per side. Skip for full feature comparison (use comparison_table) or numeric A/B mirror data (use butterfly_chart)."- },- "circular_stages": {- "summary": "Pick for 4-6 stage closed loop where stages compose a cycle — PDCA, flywheel compounding loops (Attract → Engage → Delight), lifecycle, continuous improvement. Skip for linear flow (use process_flow), one-shot sequence (use numbered_steps), or wedge-based central topic (use segmented_wheel)."- },- "numbered_steps": {- "summary": "Pick for 3-6 horizontal sequential steps with numeric emphasis — how-it-works section, getting-started guide, methodology overview, implementation phases. Skip if steps need connector arrows (use process_flow) or named output artifacts (use pipeline_with_stages)."- },- "icon_grid": {- "summary": "Pick for 4-9 parallel features/capabilities/services as icon cards — feature grid, service lineup, benefits matrix, brand values, product highlights. Skip for sequential ordering (use numbered_steps) or hierarchical layers (use pyramid_chart)."- },- "isometric_stairs": {- "summary": "Pick for 4-7 ascending stages emphasizing growth/maturity progression visually. Skip for flat sequential steps (use numbered_steps) or formal hierarchy (use pyramid_chart)."- },- "mind_map": {- "summary": "Pick for one core topic radiating into 3-6 brainstorm branches. Skip for capability hub-and-spoke (use hub_spoke) or strict hierarchy (use top_down_tree)."- },- "comparison_table": {- "summary": "Pick for 2-4 plans/products compared across many feature rows (dense matrix). Skip for pricing-tier marketing layout (use comparison_columns)."- },- "snake_flow": {- "summary": "Pick for 6-10 winding sequential steps fitting a long journey/lifecycle on one slide. Skip for <=5 steps (use numbered_steps)."- },- "roadmap_vertical": {- "summary": "Pick for 4-8 milestones on a vertical timeline with status indicators. Skip for horizontal time emphasis (use timeline) or tasks with durations (use gantt_chart)."- },"word_cloud": {"summary": "Pick for 20-30 keywords sized by frequency/weight. Skip if individual keyword position carries meaning (use icon_grid)."- },- "concentric_circles": {- "summary": "Pick for 3-5 priority rings from core to periphery — bullseye/onion model, sphere of influence, stakeholder rings, core-to-ecosystem priority layers, target-vs-extended audience. Skip for non-prioritized layers (use pyramid_chart)."- },- "segmented_wheel": {- "summary": "Pick for one central topic split into 4-8 equally-weighted parallel dimensions (5W1H, 4P, 5S, 6-aspect review), each wedge paired with a description card. Skip for sequential cycles (use circular_stages), proportional shares (use pie_chart), or hub with non-wedge spokes (use hub_spoke)."- },- "arc_anchored_list": {- "summary": "Pick for 3-5 parallel tracks/pillars unified by a left-edge radial fan as visual anchor (each lane = numbered wedge + title + body + right-end color square). Skip for plain numbered enumeration without unifying core (use vertical_list or numbered_steps), or sequential phases (use process_flow)."- },- "chevron_process": {- "summary": "Pick for 3-6 phase methodology with chunky arrow-chain progression and deliverables per phase. Skip for <=2 phases or non-linear flow (use process_flow), or chain ending in an aggregate outcome wedge (use chevron_chain_with_tail)."- },- "chevron_chain_with_tail": {- "summary": "Pick for 4-6 sequential chevron blocks plus a final wedge representing aggregate outcome — Porter's value chain (primary + support activities mapped to margin), process leading to a summary deliverable, contribution chain to a result. Skip for plain chevron flow without summary tail (use chevron_process) or non-chevron pipeline (use pipeline_with_stages)."- },- "comparison_columns": {- "summary": "Pick for 2-4 pricing/service tier cards in side-by-side columns (marketing layout). Skip for dense feature comparison (use comparison_table)."- },- "fishbone_diagram": {- "summary": "Pick for cause-and-effect root cause analysis with 4-6 cause branches (Ishikawa, 6M). Skip for sequential flow (use process_flow)."- },- "hub_spoke": {- "summary": "Pick for 1 core capability + 4-8 surrounding capabilities (platform/ecosystem); each spoke = title or title + 1-2 line description. Skip if center is a system containing parts with their own descriptions (use module_composition), or surroundings exert inward pressure on the center (use hub_inward_arrows)."- },- "vertical_list": {- "summary": "Pick for 3-6 numbered key points each with a short description — design principles, core tenets, action items, key takeaways, recommendations, executive summary points. Skip for icon-style cards (use icon_grid) or sequential steps (use numbered_steps)."- },- "vertical_pillars": {- "summary": "Pick for 1×3 / 1×4 / 1×5 vertical column layout where each pillar = one independent category with title + bullets — PEST (Political/Economic/Social/Technological), four-pillar strategy overview, side-by-side independent categories. Skip for 2×2 quadrant (use quadrant_text_bullets), pricing tiers (use comparison_columns), or 2×2 parallel aspects (use labeled_card)."- },- "layered_architecture": {- "summary": "Pick for 3-4 horizontal architecture layers (presentation/service/data), 2-4 module cards per layer, each card = title + 1-line description (description required, even if source brief). Skip if no per-module descriptions (use icon_grid) or no horizontal layering (use module_composition)."- },- "module_composition": {- "summary": "Pick for one parent container wrapping 3-N child module cards, each = title + 2-3 bullets — fits 'Feature X contains 3 parts, each with its own description'. Skip if source has only labels without descriptions (use numbered_steps or icon_grid)."- },- "pipeline_with_stages": {- "summary": "Pick for 3-5 horizontal pipeline stages, each = title + 1-line description + output artifact, connected by arrows (data pipelines, ETL, build pipelines). Skip if any stage lacks an artifact (use process_flow or numbered_steps)."- },- "client_server_flow": {- "summary": "Pick for left-side clients + right-side servers with labeled bidirectional arrows for key interactions (request/response/push). Each module = name + 1-line description; each arrow must have an action label. Skip for non-distributed flows (use process_flow)."- },- "basic_table": {- "summary": "Pick for plain tabular text/number grid, 3-8 columns. Skip if cells need visual bars (use consulting_table) or qualitative scores (use harvey_balls_table)."- },- "consulting_table": {- "summary": "Pick for high-density tables with embedded micro bar visuals (consulting/financial reports). Skip for plain text data (use basic_table)."- },- "project_schedule_table": {- "summary": "Pick for table-style task tracker (task / owner / status / timeline). Skip for true Gantt with dependencies (use gantt_chart) or schedule without ownership (use roadmap_vertical)."- },- "financial_statement_table": {- "summary": "Pick for income statement / balance sheet style with right-aligned numbers and strong total rows. Skip for non-financial tabular data (use basic_table)."- },- "feature_matrix_table": {- "summary": "Pick for competitive feature checklist with checkmarks across products. Skip for qualitative scores (use harvey_balls_table) or pricing tier marketing (use comparison_columns)."- },- "harvey_balls_table": {- "summary": "Pick for qualitative scoring grid using 0-100% Harvey balls (vendor/skill assessment). Skip for binary checkmarks (use feature_matrix_table) or numeric values (use basic_table)."- },- "team_roster": {- "summary": "Pick for 3-12 leadership/team profile cards (photo + name + title + short bio). Skip for reporting hierarchy (use top_down_tree)."- },- "top_down_tree": {- "summary": "Pick for hierarchical top-down tree 2-4 levels deep with parent→children reporting/decomposition lines — org charts (CEO → VPs → Directors), OKR cascades (Objective → Key Results → Initiatives), WBS decomposition. Skip for non-hierarchical brainstorm (use mind_map) or flat team showcase (use team_roster)."- },- "journey_map": {- "summary": "Pick for multi-phase customer experience matrix with actions, emotion curve, and pain points per phase. Skip for simple linear funnel (use funnel_chart)."- },- "agenda_list": {- "summary": "Pick for table of contents, meeting agendas, or presentation roadmap — numbered items + brief description + duration / owner per row. Skip for substantive content lists (use vertical_list) or single-page section dividers (use a cover layout)."- },- "labeled_card": {- "summary": "Pick for 3-4 parallel aspects of one subject with per-aspect titles + short body (self-introduction, four-pillar overview, capability quadrant). Skip for plain feature lists (use icon_grid), sequential steps (use numbered_steps), or strategic quadrants (use quadrant_text_bullets / matrix_2x2)."}}}diff --git a/skills/ppt-master/templates/charts/matrix_2x2.svg b/skills/ppt-master/templates/charts/matrix_2x2.svgindex ffca6995..2f89eb1f 100644--- a/skills/ppt-master/templates/charts/matrix_2x2.svg+++ b/skills/ppt-master/templates/charts/matrix_2x2.svg@@ -116,7 +116,7 @@</g></g><!-- ==================== Priority Migration (Diagonal Dashed Arrow) ==================== -->- <!-- Demonstrates CHART_STYLE_GUIDE §11.5: diagonal dashed connector to express+ <!-- Demonstrates VISUALIZATION_TEMPLATE_AUTHORING §11.5: diagonal dashed connector to expresscross-quadrant trajectory. Migrates work from Thankless → Quick Wins. --><g id="priority-migration" data-pptx-bounds="326 173 583 459"><line x1="850" y1="605" x2="385" y2="200" stroke="#475569" stroke-width="2"diff --git a/skills/ppt-master/templates/structures/README.md b/skills/ppt-master/templates/structures/README.mdnew file mode 100644index 00000000..bcb20056--- /dev/null+++ b/skills/ppt-master/templates/structures/README.md@@ -0,0 +1,53 @@+# Structure Visualization Templates++This directory contains page-local qualitative topology references. A+structure belongs here when sequence, hierarchy, role, region, comparison, or+relationship determines its nodes and connections, while numeric values do not+drive mark geometry.++Value-driven graphics belong in [`charts/`](../charts/). Cell-grid semantics+belong in [`tables/`](../tables/). Reusable PowerPoint Master/Layout systems+belong in [`layouts/`](../layouts/).++## Source of truth++[`structures_index.json`](./structures_index.json) is the sole structure+registry. Its `structures` object maps each canonical key to one selection-rule+`summary`; keys match `<key>.svg`, and `meta.total` matches the canonical SVG+roster.++Use [`visualization_recall.py`](../../scripts/visualization_recall.py) for+bounded all-family or structure-only recall. New Default planning writes+`structure/<key>` to `page_visualizations`; Quick keeps the selected reference+in active context.++## Authoring contract++[`VISUALIZATION_TEMPLATE_AUTHORING.md`](../VISUALIZATION_TEMPLATE_AUTHORING.md)+owns the shared standalone-SVG, neutral-preview, root-boundary, Shape-first,+family, and catalog rules. Structure-specific requirements are:++- Preserve qualitative order, hierarchy, containment, direction, comparison,+ and reading flow.+- Keep every object Slide-local. Structure SVGs never own+ `data-pptx-master`, `data-pptx-layout`, `data-pptx-layer`, or+ `data-pptx-placeholder`.+- Treat a full-canvas preview as one-page composition guidance, not as a+ reusable PowerPoint Layout.+- Never add native Chart/Table replacement markers to conceptual diagrams,+ frameworks, processes, timelines, or topology.++`quadrant_text_cards` is a structure: it provides four fixed named regions,+each with a title and text items, and has no value-mapped bubbles.+`layered_pyramid` is a qualitative hierarchy; `pyramid_isometric` remains the+separate dramatic four-tier structure. `pros_cons_comparison` is the canonical+bilateral argument structure.++## Layout workspace boundary++A Layout workspace is selected as a reusable package and owns Master/Layout+atoms, page types, slot geometry, placeholder roles, and structured export+mapping. A structure reference applies only to one mapped page and remains+adaptable under §IX. When a Layout workspace is active, use a structure only+inside compatible open or object content regions; never let it overwrite the+Layout's fixed atoms or slot topology.diff --git a/skills/ppt-master/templates/charts/agenda_list.svg b/skills/ppt-master/templates/structures/agenda_list.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/agenda_list.svgrename to skills/ppt-master/templates/structures/agenda_list.svgdiff --git a/skills/ppt-master/templates/charts/arc_anchored_list.svg b/skills/ppt-master/templates/structures/arc_anchored_list.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/arc_anchored_list.svgrename to skills/ppt-master/templates/structures/arc_anchored_list.svgdiff --git a/skills/ppt-master/templates/charts/chevron_chain_with_tail.svg b/skills/ppt-master/templates/structures/chevron_chain_with_tail.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/chevron_chain_with_tail.svgrename to skills/ppt-master/templates/structures/chevron_chain_with_tail.svgdiff --git a/skills/ppt-master/templates/charts/chevron_process.svg b/skills/ppt-master/templates/structures/chevron_process.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/chevron_process.svgrename to skills/ppt-master/templates/structures/chevron_process.svgdiff --git a/skills/ppt-master/templates/charts/circular_stages.svg b/skills/ppt-master/templates/structures/circular_stages.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/circular_stages.svgrename to skills/ppt-master/templates/structures/circular_stages.svgdiff --git a/skills/ppt-master/templates/charts/client_server_flow.svg b/skills/ppt-master/templates/structures/client_server_flow.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/client_server_flow.svgrename to skills/ppt-master/templates/structures/client_server_flow.svgdiff --git a/skills/ppt-master/templates/charts/comparison_columns.svg b/skills/ppt-master/templates/structures/comparison_columns.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/comparison_columns.svgrename to skills/ppt-master/templates/structures/comparison_columns.svgdiff --git a/skills/ppt-master/templates/charts/concentric_circles.svg b/skills/ppt-master/templates/structures/concentric_circles.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/concentric_circles.svgrename to skills/ppt-master/templates/structures/concentric_circles.svgdiff --git a/skills/ppt-master/templates/charts/fishbone_diagram.svg b/skills/ppt-master/templates/structures/fishbone_diagram.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/fishbone_diagram.svgrename to skills/ppt-master/templates/structures/fishbone_diagram.svgdiff --git a/skills/ppt-master/templates/charts/hub_inward_arrows.svg b/skills/ppt-master/templates/structures/hub_inward_arrows.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/hub_inward_arrows.svgrename to skills/ppt-master/templates/structures/hub_inward_arrows.svgdiff --git a/skills/ppt-master/templates/charts/hub_spoke.svg b/skills/ppt-master/templates/structures/hub_spoke.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/hub_spoke.svgrename to skills/ppt-master/templates/structures/hub_spoke.svgdiff --git a/skills/ppt-master/templates/charts/icon_grid.svg b/skills/ppt-master/templates/structures/icon_grid.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/icon_grid.svgrename to skills/ppt-master/templates/structures/icon_grid.svgdiff --git a/skills/ppt-master/templates/charts/isometric_stairs.svg b/skills/ppt-master/templates/structures/isometric_stairs.svgsimilarity index 99%rename from skills/ppt-master/templates/charts/isometric_stairs.svgrename to skills/ppt-master/templates/structures/isometric_stairs.svgindex e068e394..49a59de0 100644--- a/skills/ppt-master/templates/charts/isometric_stairs.svg+++ b/skills/ppt-master/templates/structures/isometric_stairs.svg@@ -7,7 +7,7 @@Scenarios: Digital transformation phases, capability maturity, strategic milestonesSupports: 6 Steps (Recommended 4-7)Design Principles:- - Each step = top parallelogram + front face + side face (3 shades from one Tailwind hue, see CHART_STYLE_GUIDE §1.2)+ - Each step = top parallelogram + front face + side face (3 shades from one Tailwind hue, see VISUALIZATION_TEMPLATE_AUTHORING §1.2)- Step palette walks the spectrum Sky -> Blue -> Indigo -> Violet -> Purple -> Rose- Visual weight: thicker top-edge highlight (2.5px), darker side facets, larger numbers (font 34 weight 900),each description anchored by a tinted background card so it does not floatdiff --git a/skills/ppt-master/templates/charts/journey_map.svg b/skills/ppt-master/templates/structures/journey_map.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/journey_map.svgrename to skills/ppt-master/templates/structures/journey_map.svgdiff --git a/skills/ppt-master/templates/charts/kpi_cards.svg b/skills/ppt-master/templates/structures/kpi_cards.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/kpi_cards.svgrename to skills/ppt-master/templates/structures/kpi_cards.svgdiff --git a/skills/ppt-master/templates/charts/labeled_card.svg b/skills/ppt-master/templates/structures/labeled_card.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/labeled_card.svgrename to skills/ppt-master/templates/structures/labeled_card.svgdiff --git a/skills/ppt-master/templates/charts/layered_architecture.svg b/skills/ppt-master/templates/structures/layered_architecture.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/layered_architecture.svgrename to skills/ppt-master/templates/structures/layered_architecture.svgdiff --git a/skills/ppt-master/templates/charts/pyramid_chart.svg b/skills/ppt-master/templates/structures/layered_pyramid.svgsimilarity index 99%rename from skills/ppt-master/templates/charts/pyramid_chart.svgrename to skills/ppt-master/templates/structures/layered_pyramid.svgindex 30590598..65e67127 100644--- a/skills/ppt-master/templates/charts/pyramid_chart.svg+++ b/skills/ppt-master/templates/structures/layered_pyramid.svg@@ -2,7 +2,7 @@font-family="-apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif"font-size="12"><!--- Pyramid Capability Chart Template+ Layered Pyramid TemplatePurpose: Hierarchical structure, capability maturity, strategic layersUse cases: Maslow's hierarchy, Enterprise strategy layers, Maturity modelsSupports: 5 precise geometric layers@@ -11,7 +11,7 @@<rect width="1280" height="720" fill="#F8FAFC"/><!-- ==================== Header Area ==================== --><g id="header" data-pptx-bounds="40 15 1200 125">- <text x="60" y="70" font-size="32" font-weight="800" fill="#0F172A">Strategic Capability Pyramid</text>+ <text x="60" y="70" font-size="32" font-weight="800" fill="#0F172A">Layered Capability Pyramid</text><text x="60" y="100" font-size="14" font-weight="700" fill="#64748B" letter-spacing="1">FIVE-TIER EVOLUTION MODEL · FROM FOUNDATION TO VISION</text></g><!-- Translate group to perfectly center vertically -->diff --git a/skills/ppt-master/templates/charts/mind_map.svg b/skills/ppt-master/templates/structures/mind_map.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/mind_map.svgrename to skills/ppt-master/templates/structures/mind_map.svgdiff --git a/skills/ppt-master/templates/charts/module_composition.svg b/skills/ppt-master/templates/structures/module_composition.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/module_composition.svgrename to skills/ppt-master/templates/structures/module_composition.svgdiff --git a/skills/ppt-master/templates/charts/numbered_steps.svg b/skills/ppt-master/templates/structures/numbered_steps.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/numbered_steps.svgrename to skills/ppt-master/templates/structures/numbered_steps.svgdiff --git a/skills/ppt-master/templates/charts/pipeline_with_stages.svg b/skills/ppt-master/templates/structures/pipeline_with_stages.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/pipeline_with_stages.svgrename to skills/ppt-master/templates/structures/pipeline_with_stages.svgdiff --git a/skills/ppt-master/templates/charts/process_flow.svg b/skills/ppt-master/templates/structures/process_flow.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/process_flow.svgrename to skills/ppt-master/templates/structures/process_flow.svgdiff --git a/skills/ppt-master/templates/charts/pros_cons_chart.svg b/skills/ppt-master/templates/structures/pros_cons_comparison.svgsimilarity index 98%rename from skills/ppt-master/templates/charts/pros_cons_chart.svgrename to skills/ppt-master/templates/structures/pros_cons_comparison.svgindex 7997cdd7..f10824ee 100644--- a/skills/ppt-master/templates/charts/pros_cons_chart.svg+++ b/skills/ppt-master/templates/structures/pros_cons_comparison.svg@@ -2,7 +2,7 @@font-family="-apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif"font-size="12"><!--- Pros vs Cons Analysis Chart+ Pros vs Cons Comparison TemplatePurpose: Dual-sided comparison, advantage/disadvantage evaluationUse cases: Product comparison, strategy evaluation, decision supportSupports: Symmetrical 3 vs 3 layout with central dividing axis@@ -11,7 +11,7 @@<rect width="1280" height="720" fill="#F8FAFC"/><!-- ==================== Header Area ==================== --><g id="header" data-pptx-bounds="40 15 1200 125">- <text x="640" y="60" text-anchor="middle" font-size="32" font-weight="800" fill="#0F172A">Pros vs Cons Analysis</text>+ <text x="640" y="60" text-anchor="middle" font-size="32" font-weight="800" fill="#0F172A">Pros vs Cons Comparison</text><text x="640" y="90" text-anchor="middle" font-size="14" font-weight="700" fill="#64748B" letter-spacing="1.5">STRATEGIC EVALUATION · OBJECTIVE DECISION FRAMEWORK</text></g><!-- ==================== Column Headers ==================== -->diff --git a/skills/ppt-master/templates/charts/pyramid_isometric.svg b/skills/ppt-master/templates/structures/pyramid_isometric.svgsimilarity index 98%rename from skills/ppt-master/templates/charts/pyramid_isometric.svgrename to skills/ppt-master/templates/structures/pyramid_isometric.svgindex 81501cb2..26d11470 100644--- a/skills/ppt-master/templates/charts/pyramid_isometric.svg+++ b/skills/ppt-master/templates/structures/pyramid_isometric.svg@@ -8,10 +8,10 @@Design Principles:- 4-tier 3D isometric pyramid: each tier = top diamond (shadow facet) + 2 side faces (lit gradients)- Light source from upper-left → right faces slightly darker than left faces- - Tier numbers tilted along the left slope (CHART_STYLE_GUIDE §11 "semantic-polygon" pattern)+ - Tier numbers tilted along the left slope (VISUALIZATION_TEMPLATE_AUTHORING §11 "semantic-polygon" pattern)- Tier labels tilted along the right slope- Twin ground rhombi as 3D shadow base (alternative to ellipse anchor §11.6 for 3D objects)- Versus pyramid_chart.svg: choose this for dramatic / presentation tone; choose pyramid_chart for+ Versus layered_pyramid.svg: choose this for dramatic / presentation tone; choose layered_pyramid forformal documentary / consulting tone (flat side view).Layer count is FIXED at 4 (geometric parameterization for 3/5/6 layers requires recomputed vertices).-->diff --git a/skills/ppt-master/templates/charts/quadrant_text_bullets.svg b/skills/ppt-master/templates/structures/quadrant_text_bullets.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/quadrant_text_bullets.svgrename to skills/ppt-master/templates/structures/quadrant_text_bullets.svgdiff --git a/skills/ppt-master/templates/charts/quadrant_bubble_scatter.svg b/skills/ppt-master/templates/structures/quadrant_text_cards.svgsimilarity index 90%rename from skills/ppt-master/templates/charts/quadrant_bubble_scatter.svgrename to skills/ppt-master/templates/structures/quadrant_text_cards.svgindex 7dbefe91..15ceed77 100644--- a/skills/ppt-master/templates/charts/quadrant_bubble_scatter.svg+++ b/skills/ppt-master/templates/structures/quadrant_text_cards.svg@@ -2,16 +2,16 @@font-family="Roboto, -apple-system, BlinkMacSystemFont, sans-serif"font-size="12"><!--- Quadrant Bubble Scatter Template- Structure: 2×2 quadrant grid with items plotted as bubbles sized by a third metric- Use cases: BCG Growth-Share Matrix (Stars / Cash Cows / Question Marks / Dogs), revenue-weighted portfolio matrix, any named two-axis chart where each item carries a magnitude- Design Principles: 4 named quadrants with strong visual distinctness; bubble radius encodes the third dimension+ Quadrant Text Cards Template+ Structure: Fixed 2×2 named-quadrant grid; each quadrant contains an axis-state label and short item list+ Use cases: Portfolio categories, named strategic quadrants, and qualitative two-axis classification+ Design Principles: Strong quadrant labels and fixed text-card placement; no value-mapped points or bubble-radius encoding--><rect width="1280" height="720" fill="#F8FAFC"/><!-- ==================== Header ==================== --><g id="header" data-pptx-bounds="40 15 1200 125">- <text x="80" y="70" font-family="Roboto, -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif" font-size="32" font-weight="800" fill="#0F172A">Product Portfolio Strategy</text>- <text x="80" y="100" font-family="Roboto, -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif" font-size="14" font-weight="700" fill="#64748B" letter-spacing="1">BCG GROWTH-SHARE MATRIX ANALYSIS</text>+ <text x="80" y="70" font-family="Roboto, -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif" font-size="32" font-weight="800" fill="#0F172A">Product Portfolio Quadrants</text>+ <text x="80" y="100" font-family="Roboto, -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif" font-size="14" font-weight="700" fill="#64748B" letter-spacing="1">FIXED TEXT-CARD MATRIX · QUALITATIVE CLASSIFICATION</text></g><!-- ==================== Axis & Labels ==================== --><g id="quadrant-matrix" data-pptx-bounds="44 104 1122 581" transform="translate(180, 160)">diff --git a/skills/ppt-master/templates/charts/roadmap_vertical.svg b/skills/ppt-master/templates/structures/roadmap_vertical.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/roadmap_vertical.svgrename to skills/ppt-master/templates/structures/roadmap_vertical.svgdiff --git a/skills/ppt-master/templates/charts/segmented_wheel.svg b/skills/ppt-master/templates/structures/segmented_wheel.svgsimilarity index 99%rename from skills/ppt-master/templates/charts/segmented_wheel.svgrename to skills/ppt-master/templates/structures/segmented_wheel.svgindex 7e26e8ec..ac677b53 100644--- a/skills/ppt-master/templates/charts/segmented_wheel.svg+++ b/skills/ppt-master/templates/structures/segmented_wheel.svg@@ -9,7 +9,7 @@- Central hub + 6 equal annular sectors (not data-proportional like pie/donut)- Wedge = category cell (parallel weight), not a sequential step- Dashed connector from wedge outer edge to its description card (3 left + 3 right)- - Single hue progression (top-heavy mirrored), per CHART_STYLE_GUIDE §1.2+ - Single hue progression (top-heavy mirrored), per VISUALIZATION_TEMPLATE_AUTHORING §1.2--><rect width="1280" height="720" fill="#FFFFFF"/>diff --git a/skills/ppt-master/templates/charts/snake_flow.svg b/skills/ppt-master/templates/structures/snake_flow.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/snake_flow.svgrename to skills/ppt-master/templates/structures/snake_flow.svgdiff --git a/skills/ppt-master/templates/structures/structures_index.json b/skills/ppt-master/templates/structures/structures_index.jsonnew file mode 100644index 00000000..60f170ee--- /dev/null+++ b/skills/ppt-master/templates/structures/structures_index.json@@ -0,0 +1,128 @@+{+ "meta": {+ "total": 36,+ "defaultViewBox": "0 0 1280 720",+ "formats": [+ "ppt169"+ ],+ "filePattern": "{key}.svg",+ "libraryPositioning": "Layout-driven visualization structures for sequences, relationships, hierarchies, frameworks, lists, and content composition.",+ "summaryGrammar": "Each structure summary is a selection rule, not a description. Format: 'Pick for <content shape + scale>. Skip if <reason → alternative>'.",+ "updated": "2026-08-08"+ },+ "aliases": {+ "pros_cons_chart": "pros_cons_comparison",+ "pyramid_chart": "layered_pyramid",+ "quadrant_bubble_scatter": "quadrant_text_cards"+ },+ "structures": {+ "agenda_list": {+ "summary": "Pick for table of contents, meeting agendas, or presentation roadmap — numbered items + brief description + duration / owner per row. Skip for substantive content lists (use vertical_list) or single-page section dividers (use a cover layout)."+ },+ "arc_anchored_list": {+ "summary": "Pick for 3-5 parallel tracks/pillars unified by a left-edge radial fan as visual anchor (each lane = numbered wedge + title + body + right-end color square). Skip for plain numbered enumeration without unifying core (use vertical_list or numbered_steps), or sequential phases (use process_flow)."+ },+ "chevron_chain_with_tail": {+ "summary": "Pick for 4-6 sequential chevron blocks plus a final wedge representing aggregate outcome — Porter's value chain (primary + support activities mapped to margin), process leading to a summary deliverable, contribution chain to a result. Skip for plain chevron flow without summary tail (use chevron_process) or non-chevron pipeline (use pipeline_with_stages)."+ },+ "chevron_process": {+ "summary": "Pick for 3-6 phase methodology with chunky arrow-chain progression and deliverables per phase. Skip for <=2 phases or non-linear flow (use process_flow), or chain ending in an aggregate outcome wedge (use chevron_chain_with_tail)."+ },+ "circular_stages": {+ "summary": "Pick for 4-6 stage closed loop where stages compose a cycle — PDCA, flywheel compounding loops (Attract → Engage → Delight), lifecycle, continuous improvement. Skip for linear flow (use process_flow), one-shot sequence (use numbered_steps), or wedge-based central topic (use segmented_wheel)."+ },+ "client_server_flow": {+ "summary": "Pick for left-side clients + right-side servers with labeled bidirectional arrows for key interactions (request/response/push). Each module = name + 1-line description; each arrow must have an action label. Skip for non-distributed flows (use process_flow)."+ },+ "comparison_columns": {+ "summary": "Pick for 2-4 pricing/service tier cards in side-by-side columns (marketing layout). Skip for dense feature comparison (use comparison_table)."+ },+ "concentric_circles": {+ "summary": "Pick for 3-5 priority rings from core to periphery — bullseye/onion model, sphere of influence, stakeholder rings, core-to-ecosystem priority layers, target-vs-extended audience. Skip for non-prioritized layers (use layered_pyramid)."+ },+ "fishbone_diagram": {+ "summary": "Pick for cause-and-effect root cause analysis with 4-6 cause branches (Ishikawa, 6M). Skip for sequential flow (use process_flow)."+ },+ "hub_inward_arrows": {+ "summary": "Pick for 1 center subject + 4-5 surrounding forces with arrows pointing inward — Porter's Five Forces (central rivalry, threat of new entrants/substitutes, bargaining power of buyers/suppliers), threat-model with central asset, pressure-on-core diagrams. Skip for outward radiation from center capability (use hub_spoke) or non-directional cluster (use mind_map)."+ },+ "hub_spoke": {+ "summary": "Pick for 1 core capability + 4-8 surrounding capabilities (platform/ecosystem); each spoke = title or title + 1-2 line description. Skip if center is a system containing parts with their own descriptions (use module_composition), or surroundings exert inward pressure on the center (use hub_inward_arrows)."+ },+ "icon_grid": {+ "summary": "Pick for 4-9 parallel features/capabilities/services as icon cards — feature grid, service lineup, benefits matrix, brand values, product highlights. Skip for sequential ordering (use numbered_steps) or hierarchical layers (use layered_pyramid)."+ },+ "isometric_stairs": {+ "summary": "Pick for 4-7 ascending stages emphasizing growth/maturity progression visually. Skip for flat sequential steps (use numbered_steps) or formal hierarchy (use layered_pyramid)."+ },+ "journey_map": {+ "summary": "Pick for multi-phase customer experience matrix with actions, emotion curve, and pain points per phase. Skip for simple linear funnel (use funnel_chart)."+ },+ "kpi_cards": {+ "summary": "Pick for 4-8 standalone numeric metrics shown as overview cards (2x2 or 1x4) — exec summary opener, dashboard headline, quarterly recap, results-at-a-glance. Skip if metrics have target baselines (use bullet_chart) or single hero number (use gauge_chart)."+ },+ "labeled_card": {+ "summary": "Pick for 3-4 parallel aspects of one subject with per-aspect titles + short body (self-introduction, four-pillar overview, capability quadrant). Skip for plain feature lists (use icon_grid), sequential steps (use numbered_steps), or strategic quadrants (use quadrant_text_bullets / matrix_2x2)."+ },+ "layered_architecture": {+ "summary": "Pick for 3-4 horizontal architecture layers (presentation/service/data), 2-4 module cards per layer, each card = title + 1-line description (description required, even if source brief). Skip if no per-module descriptions (use icon_grid) or no horizontal layering (use module_composition)."+ },+ "layered_pyramid": {+ "summary": "Pick for 3-6 stratified hierarchy layers in flat 2D side-view — Maslow's hierarchy, maturity models, value hierarchy, capability tiers, market segments, audience pyramid. Skip for dramatic tone (use pyramid_isometric), flat priority list (use vertical_list), or org reporting (use top_down_tree)."+ },+ "mind_map": {+ "summary": "Pick for one core topic radiating into 3-6 brainstorm branches. Skip for capability hub-and-spoke (use hub_spoke) or strict hierarchy (use top_down_tree)."+ },+ "module_composition": {+ "summary": "Pick for one parent container wrapping 3-N child module cards, each = title + 2-3 bullets — fits 'Feature X contains 3 parts, each with its own description'. Skip if source has only labels without descriptions (use numbered_steps or icon_grid)."+ },+ "numbered_steps": {+ "summary": "Pick for 3-6 horizontal sequential steps with numeric emphasis — how-it-works section, getting-started guide, methodology overview, implementation phases. Skip if steps need connector arrows (use process_flow) or named output artifacts (use pipeline_with_stages)."+ },+ "pipeline_with_stages": {+ "summary": "Pick for 3-5 horizontal pipeline stages, each = title + 1-line description + output artifact, connected by arrows (data pipelines, ETL, build pipelines). Skip if any stage lacks an artifact (use process_flow or numbered_steps)."+ },+ "process_flow": {+ "summary": "Pick for 3-8 sequential steps connected by simple arrows — approval workflows, customer onboarding, request handling, lifecycle stages. Skip if cyclical (use circular_stages) or stages produce named outputs (use pipeline_with_stages)."+ },+ "pros_cons_comparison": {+ "summary": "Pick for bilateral pros/cons list, 2-5 items per side. Skip for full feature comparison (use comparison_table) or numeric A/B mirror data (use butterfly_chart)."+ },+ "pyramid_isometric": {+ "summary": "Pick for 4-tier maturity/achievement model with presentation drama (review reports, capability tiers). Tier count fixed at 4 (hand-tuned vertices). Skip for documentary tone (use layered_pyramid) or tier count != 4."+ },+ "quadrant_text_bullets": {+ "summary": "Pick for a named 2×2 framework where each quadrant holds a titled bullet list — SWOT, Ansoff, or another two-axis text framework with detailed points. Skip for value-mapped x/y positions or bubble radii (use matrix_2x2), or short fixed item lists inside strongly labeled quadrant cards (use quadrant_text_cards)."+ },+ "quadrant_text_cards": {+ "summary": "Pick for a fixed 2×2 named-quadrant structure where each quadrant is a text card with an axis-state label and a short item list. Skip for value-mapped x/y positions or bubble radii (use matrix_2x2), or detailed quadrant bullet frameworks (use quadrant_text_bullets)."+ },+ "roadmap_vertical": {+ "summary": "Pick for 4-8 milestones on a vertical timeline with status indicators. Skip for horizontal time emphasis (use timeline) or tasks with durations (use gantt_chart)."+ },+ "segmented_wheel": {+ "summary": "Pick for one central topic split into 4-8 equally-weighted parallel dimensions (5W1H, 4P, 5S, 6-aspect review), each wedge paired with a description card. Skip for sequential cycles (use circular_stages), proportional shares (use pie_chart), or hub with non-wedge spokes (use hub_spoke)."+ },+ "snake_flow": {+ "summary": "Pick for 6-10 winding sequential steps fitting a long journey/lifecycle on one slide. Skip for <=5 steps (use numbered_steps)."+ },+ "team_roster": {+ "summary": "Pick for 3-12 leadership/team profile cards (photo + name + title + short bio). Skip for reporting hierarchy (use top_down_tree)."+ },+ "timeline": {+ "summary": "Pick for 3-8 milestone events on a horizontal time axis (no duration). Skip for tasks with start/end ranges (use gantt_chart) or vertical layout (use roadmap_vertical)."+ },+ "top_down_tree": {+ "summary": "Pick for hierarchical top-down tree 2-4 levels deep with parent→children reporting/decomposition lines — org charts (CEO → VPs → Directors), OKR cascades (Objective → Key Results → Initiatives), WBS decomposition. Skip for non-hierarchical brainstorm (use mind_map) or flat team showcase (use team_roster)."+ },+ "venn_diagram": {+ "summary": "Pick for 2-3 overlapping sets where the intersection is the message. Skip if no overlap exists (use icon_grid)."+ },+ "vertical_list": {+ "summary": "Pick for 3-6 numbered key points each with a short description — design principles, core tenets, action items, key takeaways, recommendations, executive summary points. Skip for icon-style cards (use icon_grid) or sequential steps (use numbered_steps)."+ },+ "vertical_pillars": {+ "summary": "Pick for 1×3 / 1×4 / 1×5 vertical column layout where each pillar = one independent category with title + bullets — PEST (Political/Economic/Social/Technological), four-pillar strategy overview, side-by-side independent categories. Skip for 2×2 quadrant (use quadrant_text_bullets), pricing tiers (use comparison_columns), or 2×2 parallel aspects (use labeled_card)."+ }+ }+}diff --git a/skills/ppt-master/templates/charts/team_roster.svg b/skills/ppt-master/templates/structures/team_roster.svgsimilarity index 94%rename from skills/ppt-master/templates/charts/team_roster.svgrename to skills/ppt-master/templates/structures/team_roster.svgindex 6369c230..c66f9394 100644--- a/skills/ppt-master/templates/charts/team_roster.svg+++ b/skills/ppt-master/templates/structures/team_roster.svg@@ -25,7 +25,7 @@<rect width="270" height="420" rx="16" fill="#FFFFFF" stroke="#E2E8F0" stroke-width="1"/><!-- Photo Placeholder --><g transform="translate(55, 40)">- <!-- Ground anchor ellipse (CHART_STYLE_GUIDE §11.6) — visually grounds the+ <!-- Ground anchor ellipse (VISUALIZATION_TEMPLATE_AUTHORING §11.6) — visually grounds thephoto on the card surface without using a filter shadow. --><ellipse cx="80" cy="172" rx="70" ry="5" fill="#0F172A" opacity="0.10"/><circle cx="80" cy="80" r="80" fill="#E2E8F0"/>@@ -46,7 +46,7 @@<g transform="translate(300, 0)"><rect width="270" height="420" rx="16" fill="#FFFFFF" stroke="#E2E8F0" stroke-width="1"/><g transform="translate(55, 40)">- <!-- Ground anchor ellipse (CHART_STYLE_GUIDE §11.6) — visually grounds the+ <!-- Ground anchor ellipse (VISUALIZATION_TEMPLATE_AUTHORING §11.6) — visually grounds thephoto on the card surface without using a filter shadow. --><ellipse cx="80" cy="172" rx="70" ry="5" fill="#0F172A" opacity="0.10"/><circle cx="80" cy="80" r="80" fill="#E2E8F0"/>@@ -65,7 +65,7 @@<g transform="translate(600, 0)"><rect width="270" height="420" rx="16" fill="#FFFFFF" stroke="#E2E8F0" stroke-width="1"/><g transform="translate(55, 40)">- <!-- Ground anchor ellipse (CHART_STYLE_GUIDE §11.6) — visually grounds the+ <!-- Ground anchor ellipse (VISUALIZATION_TEMPLATE_AUTHORING §11.6) — visually grounds thephoto on the card surface without using a filter shadow. --><ellipse cx="80" cy="172" rx="70" ry="5" fill="#0F172A" opacity="0.10"/><circle cx="80" cy="80" r="80" fill="#E2E8F0"/>@@ -84,7 +84,7 @@<g transform="translate(900, 0)"><rect width="270" height="420" rx="16" fill="#FFFFFF" stroke="#E2E8F0" stroke-width="1"/><g transform="translate(55, 40)">- <!-- Ground anchor ellipse (CHART_STYLE_GUIDE §11.6) — visually grounds the+ <!-- Ground anchor ellipse (VISUALIZATION_TEMPLATE_AUTHORING §11.6) — visually grounds thephoto on the card surface without using a filter shadow. --><ellipse cx="80" cy="172" rx="70" ry="5" fill="#0F172A" opacity="0.10"/><circle cx="80" cy="80" r="80" fill="#E2E8F0"/>diff --git a/skills/ppt-master/templates/charts/timeline.svg b/skills/ppt-master/templates/structures/timeline.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/timeline.svgrename to skills/ppt-master/templates/structures/timeline.svgdiff --git a/skills/ppt-master/templates/charts/top_down_tree.svg b/skills/ppt-master/templates/structures/top_down_tree.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/top_down_tree.svgrename to skills/ppt-master/templates/structures/top_down_tree.svgdiff --git a/skills/ppt-master/templates/charts/venn_diagram.svg b/skills/ppt-master/templates/structures/venn_diagram.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/venn_diagram.svgrename to skills/ppt-master/templates/structures/venn_diagram.svgdiff --git a/skills/ppt-master/templates/charts/vertical_list.svg b/skills/ppt-master/templates/structures/vertical_list.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/vertical_list.svgrename to skills/ppt-master/templates/structures/vertical_list.svgdiff --git a/skills/ppt-master/templates/charts/vertical_pillars.svg b/skills/ppt-master/templates/structures/vertical_pillars.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/vertical_pillars.svgrename to skills/ppt-master/templates/structures/vertical_pillars.svgdiff --git a/skills/ppt-master/templates/tables/README.md b/skills/ppt-master/templates/tables/README.mdnew file mode 100644index 00000000..852a5f56--- /dev/null+++ b/skills/ppt-master/templates/tables/README.md@@ -0,0 +1,41 @@+# Table Visualization Templates++This directory contains the cell-grid table family. A table belongs here when+rows, columns, cells, headers, merges, alignment, borders, and cell content form+the primary information model. Numeric values inside cells do not by themselves+turn the grid into a chart.++Value-driven mark geometry belongs in [`charts/`](../charts/). Qualitative+page topology belongs in [`structures/`](../structures/). Reusable PowerPoint+Master/Layout systems belong in [`layouts/`](../layouts/).++## Source of truth++[`tables_index.json`](./tables_index.json) is the sole table registry. Its+`tables` object maps each canonical key to one selection-rule `summary`; keys+match `<key>.svg`, and `meta.total` matches the canonical SVG roster.++Use [`visualization_recall.py`](../../scripts/visualization_recall.py) for+bounded all-family or table-only recall. New Default planning writes+`table/<key>` to `page_visualizations`; Quick keeps the selected reference in+active context.++## Authoring contract++[`VISUALIZATION_TEMPLATE_AUTHORING.md`](../VISUALIZATION_TEMPLATE_AUTHORING.md)+owns the shared standalone-SVG, neutral-preview, root-boundary, Shape-first,+family, and catalog rules. Table-specific requirements are:++- Preserve the complete row/column topology, headers, values, units, ordering,+ merges, alignment, totals, status, and source notes.+- Default output remains independently editable DrawingML shapes.+- Add native Table replacement metadata only for a supported pure text grid+ selected as an independent native-ready object. The fallback and metadata+ contain the same cells.+- Keep graphical cells such as Harvey balls, icons, ratings, avatars, or+ embedded bars on the Shape fallback route unless the active native-data+ contract explicitly supports them.++Selecting a table reference does not itself select native output. Design Spec+§IX `Native-ready` and explicit `--native-charts-and-tables` export remain+separate decisions.diff --git a/skills/ppt-master/templates/charts/basic_table.svg b/skills/ppt-master/templates/tables/basic_table.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/basic_table.svgrename to skills/ppt-master/templates/tables/basic_table.svgdiff --git a/skills/ppt-master/templates/charts/comparison_table.svg b/skills/ppt-master/templates/tables/comparison_table.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/comparison_table.svgrename to skills/ppt-master/templates/tables/comparison_table.svgdiff --git a/skills/ppt-master/templates/charts/consulting_table.svg b/skills/ppt-master/templates/tables/consulting_table.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/consulting_table.svgrename to skills/ppt-master/templates/tables/consulting_table.svgdiff --git a/skills/ppt-master/templates/charts/feature_matrix_table.svg b/skills/ppt-master/templates/tables/feature_matrix_table.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/feature_matrix_table.svgrename to skills/ppt-master/templates/tables/feature_matrix_table.svgdiff --git a/skills/ppt-master/templates/charts/financial_statement_table.svg b/skills/ppt-master/templates/tables/financial_statement_table.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/financial_statement_table.svgrename to skills/ppt-master/templates/tables/financial_statement_table.svgdiff --git a/skills/ppt-master/templates/charts/harvey_balls_table.svg b/skills/ppt-master/templates/tables/harvey_balls_table.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/harvey_balls_table.svgrename to skills/ppt-master/templates/tables/harvey_balls_table.svgdiff --git a/skills/ppt-master/templates/charts/project_schedule_table.svg b/skills/ppt-master/templates/tables/project_schedule_table.svgsimilarity index 100%rename from skills/ppt-master/templates/charts/project_schedule_table.svgrename to skills/ppt-master/templates/tables/project_schedule_table.svgdiff --git a/skills/ppt-master/templates/tables/tables_index.json b/skills/ppt-master/templates/tables/tables_index.jsonnew file mode 100644index 00000000..e27fb18b--- /dev/null+++ b/skills/ppt-master/templates/tables/tables_index.json@@ -0,0 +1,36 @@+{+ "meta": {+ "total": 7,+ "defaultViewBox": "0 0 1280 720",+ "formats": [+ "ppt169"+ ],+ "filePattern": "{key}.svg",+ "libraryPositioning": "Row-and-column visualization templates whose primary information structure is a table or comparison grid.",+ "summaryGrammar": "Each table summary is a selection rule, not a description. Format: 'Pick for <content shape + scale>. Skip if <reason → alternative>'.",+ "updated": "2026-08-08"+ },+ "tables": {+ "basic_table": {+ "summary": "Pick for plain tabular text/number grid, 3-8 columns. Skip if cells need visual bars (use consulting_table) or qualitative scores (use harvey_balls_table)."+ },+ "comparison_table": {+ "summary": "Pick for 2-4 plans/products compared across many feature rows (dense matrix). Skip for pricing-tier marketing layout (use comparison_columns)."+ },+ "consulting_table": {+ "summary": "Pick for high-density tables with embedded micro bar visuals (consulting/financial reports). Skip for plain text data (use basic_table)."+ },+ "feature_matrix_table": {+ "summary": "Pick for competitive feature checklist with checkmarks across products. Skip for qualitative scores (use harvey_balls_table) or pricing tier marketing (use comparison_columns)."+ },+ "financial_statement_table": {+ "summary": "Pick for income statement / balance sheet style with right-aligned numbers and strong total rows. Skip for non-financial tabular data (use basic_table)."+ },+ "harvey_balls_table": {+ "summary": "Pick for qualitative scoring grid using 0-100% Harvey balls (vendor/skill assessment). Skip for binary checkmarks (use feature_matrix_table) or numeric values (use basic_table)."+ },+ "project_schedule_table": {+ "summary": "Pick for table-style task tracker (task / owner / status / timeline). Skip for true Gantt with dependencies (use gantt_chart) or schedule without ownership (use roadmap_vertical)."+ }+ }+}