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
fix(workflow): enforce mandatory read gates for design_spec and chart templates
hugohe3c3e4587aefe2
diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.mdindex 195d9bb6..3a8ae8e0 100644--- a/skills/ppt-master/SKILL.md+++ b/skills/ppt-master/SKILL.md@@ -166,7 +166,9 @@ First, read the role definition:Read references/strategist.md```-**Must complete the Eight Confirmations** (refer to `templates/design_spec_reference.md` for the template structure):+> ⚠️ **Mandatory gate in `strategist.md`**: Before writing `design_spec.md`, Strategist MUST `read_file templates/design_spec_reference.md` and produce the spec following its full I–XI section structure. See `strategist.md` Section 1 for the explicit gate rule.++**Must complete the Eight Confirmations** (full template structure in `templates/design_spec_reference.md`):⛔ **BLOCKING**: The Eight Confirmations MUST be presented to the user as a bundled set of recommendations, and you MUST **wait for the user to confirm or modify** before outputting the Design Specification & Content Outline. This is one of only two core confirmation points in the workflow (the other is template selection). Once confirmed, all subsequent script execution and slide generation should proceed fully automatically.diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.mdindex 7549159b..27dd7e19 100644--- a/skills/ppt-master/references/executor-base.md+++ b/skills/ppt-master/references/executor-base.md@@ -133,15 +133,19 @@ ls skills/ppt-master/templates/icons/tabler-outline/ | grep chart## 5. Visualization Reference-When the Design Spec includes a **VII. Visualization Reference List**, read the referenced SVG templates from `templates/charts/` to understand the intended visualization patterns. The path remains `templates/charts/` for backward compatibility.+When the Design Spec includes a **VII. Visualization Reference List**, read the referenced SVG templates from `templates/charts/` before drawing pages that use those visualization types. The path remains `templates/charts/` for backward compatibility.-> **Rule**: When Executor first uses a visualization type, Executor should look up the relevant SVG template in `templates/charts/` as a reference, then reuse that pattern for subsequent pages of the same type. Only look up another template when the visualization type changes or the structure is still unclear.+🚧 **GATE — Mandatory read before first use**: When Executor encounters a visualization type listed in Section VII of the Design Spec for the first time, Executor **MUST** `read_file templates/charts/<chart_name>.svg` **before** generating that page. Extract the layout coordinates, card structure, spacing rhythm, and visual logic from the template as **creative reference and inspiration** — not as a strict copy. Then design the page independently using the project's own color scheme, typography, and content.++> **Workflow**: read template SVG → understand structure & spacing → design original SVG informed by the reference → do NOT replicate the template verbatim.+> **Reuse**: Once a visualization type has been read and understood, there is no need to re-read for subsequent pages of the same type.+> **Change**: Read the new template when the visualization type changes or the structure needs re-reference.**Adaptation rules**:- **Must preserve**: Visualization type (bar/line/pie/timeline/process/framework etc.) as specified in the Design Spec- **Must adapt**: Data values, labels, colors (match the project's color scheme), and dimensions to fit the page layout-- **May adjust**: Axis ranges, grid lines, legend position, spacing — as long as the chart remains accurate and readable-- **Must NOT**: Change visualization type without Design Spec justification, or remove data points / structural elements specified in the outline+- **May adjust freely**: Visual composition, axis ranges, grid lines, legend position, spacing, decorative elements — creative freedom is encouraged as long as the chart remains accurate and readable+- **Must NOT**: Change visualization type without Design Spec justification, or omit data points / structural elements specified in the outline> Visualization templates: `templates/charts/` (52 types). Index: `templates/charts/charts_index.json`diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.mdindex 34dc7635..358c15ef 100644--- a/skills/ppt-master/references/strategist.md+++ b/skills/ppt-master/references/strategist.md@@ -42,7 +42,13 @@ As a top-tier AI presentation strategist, receive source documents, perform cont## 1. Eight Confirmations Process-⛔ **BLOCKING**: Before starting analysis, reference `templates/design_spec_reference.md` and provide professional recommendations for the following eight items, then **present them as a bundled package to the user and wait for explicit confirmation or modifications**.+🚧 **GATE — Mandatory read before proceeding**: Before starting analysis or writing any part of the Design Specification, you **MUST** `read_file` the reference template:+```+read_file templates/design_spec_reference.md+```+The design_spec.md output **MUST** follow this template's structure exactly (Sections I through XI). After writing, perform a section-by-section self-check: I Project Information ✓ → II Canvas Spec ✓ → III Visual Theme ✓ → IV Typography ✓ → V Layout Principles ✓ → VI Icon Usage ✓ → VII Visualization Reference List ✓ → VIII Image Resource List ✓ → IX Content Outline ✓ → X Speaker Notes Requirements ✓ → XI Technical Constraints Reminder ✓. Any missing section must be completed before outputting the file.++⛔ **BLOCKING**: After completing the read above, provide professional recommendations for the following eight items, then **present them as a bundled package to the user and wait for explicit confirmation or modifications**.> **Execution discipline**: This is the last BLOCKING checkpoint in the pipeline (besides template selection). Once the user confirms, the AI must automatically complete the Design Specification & Content Outline and seamlessly proceed to subsequent image generation (if applicable), SVG generation, and post-processing — no additional questions or pauses in between.