Skip to content

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

refactor(ppt): widen Strategist chart-match framing and consolidate §VII audit format

hugohe3f59be2ec3cd5
diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.md
index aba283a8..cd48ab88 100644
--- a/skills/ppt-master/references/strategist.md
+++ b/skills/ppt-master/references/strategist.md
@@ -330,37 +330,43 @@ Side-by-side only: container ratio must match image ratio. Hero / atmosphere / a
> **Pipeline handoff**: When C) AI generation is selected, Image_Generator consumes `Pending` rows and updates them to `Generated` or `Needs-Manual` before Executor proceeds. Status names are defined in [`svg-image-embedding.md`](svg-image-embedding.md).
-### Visualization Reference (Non-blocking — Strategist recommends, no user confirmation needed)
+### Template Match — Visualization + Structural Patterns (Non-blocking — Strategist recommends, no user confirmation needed)
-When content outline pages involve **data visualization or infographic-style structured information design** (comparisons, trends, proportions, KPIs, flows, timelines, org structures, strategic frameworks, etc.), Strategist should select appropriate visualization types from the built-in template library.
+The catalog covers **both data charts and structural information designs**. A "match" is not limited to numeric pages — any page whose content shape matches a `Pick for ...` clause is a candidate:
+
+- **Data-type pages**: comparisons, trends, proportions, KPIs, financials, rankings, distributions, conversion funnels
+- **Structural-type pages**: team rosters, agendas, principles & values, methodology phases, customer journey, capability maps, OKR cascades, roadmaps, strategic frameworks (SWOT / BCG / PEST / Porter's Five Forces / Value Chain — matched via `quadrant_text_bullets`, `quadrant_bubble_scatter`, `vertical_pillars`, `hub_inward_arrows`, `chevron_chain_with_tail` respectively)
+
+The most common Strategist failure mode is missing the structural half — treating "chart" as "numeric chart only" and leaving team / agenda / principles / journey pages as text-only when a template would fit. Read the catalog with both lenses.
> **Reading is mandatory; the catalog is a starting point, not a copy target.**
-> - Fully read `templates/charts/charts_index.json` **before drafting the Eight Confirmations** — the read happens up front, not when you sit down to write Section VII. The file contains `meta` + `charts.<key>.summary` only; each `summary` is a selection rule (`"Pick for … Skip if …"`), not a description. There is **no category, quickLookup, or keyword index** — selection is done by semantically matching each page's content shape against all 72 summaries in one pass.
+> - Fully read `templates/charts/charts_index.json` **before drafting the Eight Confirmations** — the read happens up front, not when you sit down to write Section VII. The file contains `meta` + `charts.<key>.summary` only; each `summary` is a selection rule (`"Pick for … Skip if …"`), not a description. There is **no category, quickLookup, or keyword index** — selection is done by semantically matching each page's content shape against all 71 summaries in one pass.
> - Not every page needs a chart. When a page's information structure matches a catalog entry, **use that template as a structural starting point** — keep the visualization type and core layout logic, then adapt composition, density, color, decoration, and accompanying elements to fit this deck's content and visual tone. Free adjustment is encouraged; what is forbidden is (a) generating without reading the catalog, and (b) blind verbatim mimicry that ignores the page's actual content weight.
>
> **Workflow**:
-> 1. Read all 72 summaries; for each page, identify the Pick clause that matches the page's content shape AND does not match any Skip clause.
+> 1. Read all 71 summaries; for each page, identify the Pick clause that matches the page's content shape AND does not match any Skip clause.
> 2. Prefer specificity (`vertical_list` over generic `numbered_steps`).
> 3. One primary visualization per page; a supporting layout may accompany it.
> 4. List selections in Design Spec section VII; section IX only notes the visualization type name per page.
>
> **Source vocabulary mismatch** — the catalog is in English. When source content uses Chinese / industry jargon ("中台", "架构图", "述职", "管道", "前后端"), translate the intent first, then match against summaries. The catalog deliberately keeps no keyword index — full-read forces semantic matching rather than lexical grep.
>
-> **Read-audit (mandatory, written at the top of section VII)** — designed to make fabrication impossible:
+> **Read-audit (mandatory, section VII format)** — single combined table; `summary-quote` column is the anti-fabrication audit, `path` + `usage` serve Executor lookup. Format defined in [`templates/design_spec_reference.md`](../templates/design_spec_reference.md) §VII:
> ```
-> Catalog read: 72 templates
+> Catalog read: 71 templates
>
-> Per-page selection (one row per viz page):
-> P03 bar_chart | summary-quote: "<paste the first sentence of the entry's `summary` field, verbatim>"
-> P07 line_chart | summary-quote: "<verbatim first sentence>"
-> P11 pie_chart | summary-quote: "<verbatim first sentence>"
+> | Page | Template | Path | Summary-quote (verbatim) | Usage |
+> | ---- | ------------- | --------------------------------- | ------------------------ | ----- |
+> | P03 | bar_chart | templates/charts/bar_chart.svg | "<verbatim first sentence>" | <intent> |
+> | P07 | line_chart | templates/charts/line_chart.svg | "<verbatim first sentence>" | <intent> |
+> | P11 | pie_chart | templates/charts/pie_chart.svg | "<verbatim first sentence>" | <intent> |
>
-> Runners-up considered (3 entries minimum, drawn from real second-best matches in this deck):
-> <key_A> | rejected for P03: <reason citing this deck's specifics>
-> <key_B> | rejected for P07: <reason>
-> <key_C> | rejected for P11: <reason>
+> Runners-up considered (3 entries minimum, drawn from real second-best matches):
+> - <key_A> | rejected for P03: <reason citing this deck's specifics>
+> - <key_B> | rejected for P07: <reason>
+> - <key_C> | rejected for P11: <reason>
> ```
-> The `summary-quote` must be copy-pasted from `charts_index.json` — paraphrasing or summarizing breaks the audit. Every `<key_*>` and selected key must `grep` cleanly inside `charts_index.json` (so misspelled or invented keys fail). If fewer than 3 visualization pages exist, list what exists and note "fewer than 3 viz pages"; runners-up still required for each page that does exist.
+> The `summary-quote` must be copy-pasted from `charts_index.json` — paraphrasing or summarizing breaks the audit. Every template name listed (selected or rejected) must `grep` cleanly inside `charts_index.json` (so misspelled or invented keys fail). If fewer than 3 visualization pages exist, list what exists and note "fewer than 3 viz pages"; runners-up still required for each page that does exist.
>
> **Fallback when no template fits**:
> 1. Re-read the full summary list with the page's intent re-stated in plain language — "non-obvious" matches often surface on the second pass (e.g. "causal chain" → `process_flow` or `sankey_chart`).
diff --git a/skills/ppt-master/templates/design_spec_reference.md b/skills/ppt-master/templates/design_spec_reference.md
index c5844865..b3627835 100644
--- a/skills/ppt-master/templates/design_spec_reference.md
+++ b/skills/ppt-master/templates/design_spec_reference.md
@@ -213,20 +213,21 @@ Two views on the same font decisions — fill both, keep them consistent:
## VII. Visualization Reference List (if needed)
-> When the deck includes data visualization or infographic-style structured information, Strategist selects types from `templates/charts/charts_index.json` and lists them here for Executor reference. Path stays under `templates/charts/` for backward compatibility.
+> When pages map to a chart-library template (data charts OR structural patterns — team rosters, agendas, frameworks, etc.), Strategist lists them here for Executor reference. Single combined table — `summary-quote` column is the anti-fabrication audit, `path` + `usage` columns serve Executor lookup.
-**Read-audit** (mandatory):
+Catalog read: 71 templates
-```
-Catalog read: 72 templates
-Runners-up considered: <key_A> (rejected: <reason>), <key_B> (rejected: <reason>), <key_C> (rejected: <reason>)
-```
+| Page | Template | Path | Summary-quote (verbatim from `charts_index.json`) | Usage |
+| ---- | -------- | ---- | ------------------------------------------------- | ----- |
+| P05 | grouped_bar_chart | `templates/charts/grouped_bar_chart.svg` | "Pick for 2-4 series side-by-side across the same categories (e.g. YoY/QoQ). Skip if showing composition within each category (use stacked_bar_chart)." | YoY revenue comparison by product line |
+
+**Runners-up considered** (3 entries minimum, drawn from real second-best matches in this deck):
-Runners-up must be genuine second-best matches for a page in this deck. If fewer than 3 viz pages exist, list what exists and note "fewer than 3 viz pages".
+- `<key_A>` | rejected for P05: `<reason citing this deck's specifics>`
+- `<key_B>` | rejected for P##: `<reason>`
+- `<key_C>` | rejected for P##: `<reason>`
-| Visualization Type | Reference Template | Used In |
-| ------------------ | ------------------ | ------- |
-| [e.g. grouped_bar_chart] | `templates/charts/grouped_bar_chart.svg` | Slide 05 |
+> **Audit rule**: `Summary-quote` must be copy-pasted verbatim — paraphrasing breaks the audit. Every template name listed must `grep` cleanly inside `charts_index.json` (so misspellings/inventions fail). If fewer than 3 viz pages exist, list what exists and note "fewer than 3 viz pages"; runners-up still required for each page that does exist.
---