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
feat(strategist): add spec_lock.md as machine-readable execution contract
hugohe3c775e1096149
diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.mdindex dd598ddf..8aa758b7 100644--- a/skills/ppt-master/references/strategist.md+++ b/skills/ppt-master/references/strategist.md@@ -383,6 +383,7 @@ The Strategist should make professional judgments on the template basis generate1. Read reference template: `templates/design_spec_reference.md`2. Generate complete spec from scratch based on analysis3. Save to: `projects/<project_name>.../design_spec.md`+4. **Generate execution lock**: read `templates/spec_lock_reference.md` and produce `projects/<project_name>.../spec_lock.md` — a distilled, machine-readable short form of the color / typography / icon / image decisions above. This file is what the Executor re-reads before every page (see [executor-base.md](executor-base.md) §3). The values in `spec_lock.md` MUST exactly match the decisions recorded in `design_spec.md`; if they ever diverge, `spec_lock.md` wins and `design_spec.md` should be treated as historical narrative---@@ -400,7 +401,7 @@ The Strategist saves the Design Specification & Content Outline to `projects/<pr## 8. Complete Design Spec and Prompt Next Steps-After writing `design_spec.md`, provide the next-step prompt based on the confirmed template option and image usage selection. This prompt is a workflow handoff instruction, not a section inside `design_spec.md`.+After writing `design_spec.md` **and** `spec_lock.md`, provide the next-step prompt based on the confirmed template option and image usage selection. This prompt is a workflow handoff instruction, not a section inside `design_spec.md`.### Template Option A (Using existing template)diff --git a/skills/ppt-master/templates/design_spec_reference.md b/skills/ppt-master/templates/design_spec_reference.mdindex 930d0d38..93e9a3ae 100644--- a/skills/ppt-master/templates/design_spec_reference.md+++ b/skills/ppt-master/templates/design_spec_reference.md@@ -1,6 +1,8 @@# {project_name} - Design Spec-> This document is the unified handoff artifact for design definition and execution constraints. It combines visual specifications, content outline, speaker-notes requirements, and implementation boundaries needed by downstream roles.+> This document is the human-readable design narrative — rationale, audience, style, color choices, content outline. It is read once by downstream roles for context.+>+> The machine-readable execution contract lives in `spec_lock.md` (short form of color / typography / icon / image decisions). Executor re-reads `spec_lock.md` before every SVG page to resist context-compression drift. Keep the two files in sync; if they diverge, `spec_lock.md` wins.## I. Project Informationdiff --git a/skills/ppt-master/templates/spec_lock_reference.md b/skills/ppt-master/templates/spec_lock_reference.mdnew file mode 100644index 00000000..d9d3bd2f--- /dev/null+++ b/skills/ppt-master/templates/spec_lock_reference.md@@ -0,0 +1,46 @@+# Execution Lock++> Machine-readable execution contract. Executor MUST `read_file` this before every SVG page. Values NOT listed here must NOT appear in SVGs. For design narrative (rationale, audience, style), see `design_spec.md`.+>+> After SVG generation begins, this file is the canonical source for color / font / icon / image values. Modifications should go through `scripts/update_spec.py` so both this file and the generated SVGs stay in sync.++## canvas+- viewBox: {canvas_info['viewbox']}+- format: {canvas_info['name']}++## colors+- bg: #FFFFFF+- primary: #......+- accent: #......+- secondary_accent: #......+- text: #......+- text_secondary: #......+- border: #......++> Strategist: fill only the colors actually used in this deck. Extra rows may be added; unused rows should be deleted rather than left as `#......`.++## typography+- font_family: "Microsoft YaHei", Arial, sans-serif+- title: 32+- subtitle: 24+- body: 22+- annotation: 14++> Sizes are in px, matching SVG native units. `font_family` is a CSS font-stack string.++## icons+- library: chunk+- inventory: target, bolt, shield, users, chart-bar, lightbulb++> `library` MUST be one of `chunk` / `tabler-filled` / `tabler-outline` (exactly one — mixing is forbidden). `inventory` lists the approved icon names (without library prefix); Executor may only use icons from this list.++## images+- cover_bg: images/cover_bg.jpg++> One entry per image file actually used. Remove the section entirely if the deck uses no images.++## forbidden+- Mixing icon libraries+- rgba()+- `<style>`, `class`, `<foreignObject>`, `textPath`, `@font-face`, `<animate*>`, `<script>`, `<iframe>`, `<symbol>`+`<use>`+- `<g opacity>` (set opacity on each child element individually)