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(prompts): rewrite strategist-template and video-design concise
hugohe30b06829f271f
diff --git a/skills/ppt-master/references/strategist-template.md b/skills/ppt-master/references/strategist-template.mdindex ac83226a..31223750 100644--- a/skills/ppt-master/references/strategist-template.md+++ b/skills/ppt-master/references/strategist-template.md@@ -4,104 +4,76 @@Conditional extension for applying an installed Brand/Style/Layout/Deck workspace to Stage 2 recommendations and the execution lock.-**Trigger**: Load only after Stage 1 confirms a library or explicit workspace selection and the post-confirmation apply stage either installs it into `<project_path>/templates/` or confirms that the target project is consuming it in place. Bare template names, style words, and free-design projects do not trigger this module.+**Trigger**: Load only after Stage 1 confirms a library or explicit workspace selection and the post-confirmation apply stage installs it into `<project_path>/templates/` or confirms in-place consumption. Bare template names, style words, and free-design projects do not trigger this module.---## 1. AI-Authored Template Application Plan-**Template vs preset**: A style mention and a Style workspace are different inputs. Bare names and style words remain interpretive input and never resolve to a local path; only a selected and installed workspace activates the rules below. Every installed `<project_path>/templates/design_spec.<kind>.<id>.md` is a template-design source; read all of them. The presence of a `design_spec.style.*.md` file is what marks an active Direction / method segment. Whether a source root was labelled `library` or `explicit` is installation provenance only and never affects Stage-2 precedence.+**Inputs**: every installed `<project_path>/templates/design_spec.<kind>.<id>.md` is a template-design source; read all of them. A `design_spec.style.*.md` file marks an active Direction / method segment. Bare names and style words stay interpretive input and never resolve to a local path. Library/explicit provenance never affects precedence. A legacy or incomplete Layout/Deck is not a Step 3 input — rebuild it through [`create-template`](../workflows/create-template.md), preferably from the original PPTX; never mutate the input.-**Source-analysis template boundary**: A legacy or incomplete Layout/Deck is not a Generate Step 3 input. Rebuild it through [`create-template`](../workflows/create-template.md), preferably from the original PPTX when native topology matters. Brand and Style are intentionally roster-free. Never mutate the input.+**Hard rule — no Stage-1 influence**: Do not load this module, the template spec, prototypes, assets, or template canvas while authoring Stage 1, and never revise a confirmed Stage 1 to match the workspace.-**No template-mode confirmation**: Never ask the user to choose internal exporter reuse/adherence values. Natural-language instructions win. Otherwise decide from current content and installed state. Common readings are: reference-led may redesign after full-roster study; augment-only freezes non-slot objects, permits slot edits, and only adds; replacement-only changes information carriers while preserving the rest. They are examples, not fixed modes; use reference-led when no stronger fit exists.+**Outputs**:-**Hard rule — no Stage-1 influence**: Do not load this module, the installed template spec, prototypes, assets, or template canvas while authoring Stage 1. Stage 1 is already confirmed when this module begins; never revise it to match the workspace.--Immediately before authoring the Stage-2 solution, load each relevant template-resource once per path + SHA and inspect:--- every installed `design_spec.<kind>.<id>.md`; inspect the actual Page Roster and every complete Slide prototype from Layout when present, otherwise from Deck; a mirror scope note about omitted source identities is evidence, not a page-candidate list;-- the Identity, Structure, Reusable Application Context, and Direction / method segment owners, resolved here from the installed set under [`apply-template-workspace`](../workflows/stages/apply-template-workspace.md) §5;-- the confirmed current communication contract, source obligations, planned page count, and content shape of every planned page;-- the user's natural-language instructions, including any page names/numbers or elements they explicitly require.--Then author one plan that decides all of the following without presenting an option menu:--- for Layout/Deck, whether the full prototype set, a relevant subset, or only the design language is useful;-- for Layout/Deck, which prototype each generated page starts from, which template pages are skipped, and which prototypes are repeated or reordered;-- whether content is inserted directly, reorganized inside existing structure, or rebuilt under the resolved Direction / method segment;-- for Style, which communication method, visual language, composition rhythm, and information-expression defaults are adopted or adapted without inventing page prototypes;-- which visible elements must remain literal because the user said so, and which may change to serve the current content.--If a prototype detail becomes uncertain, re-read its installed SVG; do not-substitute memory, a semantic label, or the source PPTX.--For Layout/Deck, template size is evidence, not policy. A short template may use every prototype when the content genuinely fits; a 20–30 page source may contribute only a few suitable pages, or several pages may be reorganized into a new sequence. Never infer that all pages must be kept or that visible sample content is protected merely because it exists in the template. Style and Brand have no prototype set.+| Output | Form |+|---|---|+| `recommendations.stage2.json` top-level `template_application.value` | One concise natural-language paragraph; omitted without a template |+| `design_spec.md §I` | `- **Template Application**: <prose>` persisted from the confirmed `result.json` value (or exact chat answer); blank returns the decision to Strategist |+| `spec_lock.md pptx_structure` | Only the derived internal values below (§3); never in `design_spec.md`, stage files, the Confirm UI, or `result.json` |-**Hard rule — Slide prototypes drive authoring**: Every template SVG is a-complete Slide prototype with resolved Master + Layout + Slide context. Use-these files for `page_layouts`; standalone Master/Layout definition SVGs are-invalid. An unselected authored Slide prototype may still supply a-`pptx_layouts` definition, while mirror exposes only actual source Slides.+| Internal value | When the plan requires it |+|---|---|+| `template_reuse_scope: mirror` | Workspace has `replication_mode: mirror`, the plan reuses pages literally, and each page changes only allowed visible text values while preserving visual and text-node topology |+| `template_reuse_scope: layout` | The Master/Layout system and prototypes are reused while current-project content and appearance decisions remain open |+| `template_reuse_scope: style` | A Style-only workspace is active, or only communication/design direction, color, typography, decoration, composition, or rhythm is reused and pages are flat free-design |+| `template_adherence: strict` | Every structured page fits an existing prototype contract without changing Layout identity or slot topology; mandatory for `mirror` |+| `template_adherence: adaptive` | Structured reuse stays useful but at least one page needs a new explicit Layout under the selected Master |-Record the resulting exporter plan internally:+**Procedure** — immediately before authoring the Stage-2 solution, load each relevant resource once per path + SHA: every installed spec with its Page Roster and every complete Slide prototype (Layout first, otherwise Deck; a mirror scope note about omitted source identities is evidence, not a page-candidate list); the Identity, Structure, Reusable Application Context, and Direction / method owners resolved under [`apply-template-workspace`](../workflows/stages/apply-template-workspace.md) §5; the confirmed communication contract, source obligations, planned page count, and content shape of every page; the user's natural-language instructions including required page names/numbers or elements. Then author one plan, without an option menu, that decides: for Layout/Deck, whether the full prototype set, a subset, or only the design language is useful, which prototype each page starts from, which pages are skipped, repeated, or reordered; whether content is inserted directly, reorganized inside existing structure, or rebuilt under the resolved Direction / method; for Style, which communication method, visual language, composition rhythm, and expression defaults are adopted without inventing prototypes; which visible elements stay literal because the user said so. Re-read an installed SVG when a prototype detail is uncertain — never memory, a semantic label, or the source PPTX.-| Internal value | When the authored plan requires it |-|---|---|-| `template_reuse_scope: mirror` | The workspace has `replication_mode: mirror`, the plan calls for literal page reuse, and each page changes only allowed visible text values while preserving visual and text-node topology. |-| `template_reuse_scope: layout` | The plan reuses the template Master/Layout system and prototypes while allowing current-project content and appearance decisions. |-| `template_reuse_scope: style` | A Style-only workspace is active, or the plan uses only communication/design direction, color, typography, decoration language, composition, or rhythm and intentionally creates flat free-design pages. |-| `template_adherence: strict` | Every structured page fits an existing prototype contract without changing its Layout identity or slot topology. Mandatory for `template_reuse_scope: mirror`. |-| `template_adherence: adaptive` | Structured reuse remains useful, but at least one page needs a new explicit Layout under the selected Master. |+**Judgment**: Template size is evidence, not policy — a short template may use every prototype when content fits; a 20–30 page source may contribute a few pages or be reorganized into a new sequence. Never infer that all pages must be kept or that sample content is protected merely because it exists. Natural-language instructions win; otherwise decide from content and installed state. Common readings — reference-led redesigns after full-roster study; augment-only freezes non-slot objects, permits slot edits, and only adds; replacement-only changes information carriers and preserves the rest — are examples, not modes; use reference-led when nothing fits better. Never ask the user to choose internal reuse/adherence values.-Write only the derived values to `spec_lock.md pptx_structure`; omit `template_adherence` for `style`. Do not put these internal values in `design_spec.md`, recommendation stage files, the Confirm UI, or `result.json`.+**Hard rule — Slide prototypes drive authoring**: every template SVG is a complete Slide prototype with resolved Master + Layout + Slide context; use these files for `page_layouts`. Standalone Master/Layout definition SVGs are invalid. An unselected authored prototype may still supply a `pptx_layouts` definition; mirror exposes only actual source Slides.-**Mandatory — natural-language Stage-2 plan**: Write one concise paragraph. For Layout/Deck, state prototype use/order, what stays literal, and what may change; name exact SVG basenames for prototype-specific exceptions, never roles such as “cover”. For Brand/Style, state identity or Direction / method constraints and free composition unless structure comes from another workspace. Write top-level `template_application.value` in `recommendations.stage2.json`; omit it without a template. After Stage 2, re-read the confirmed `result.json` value (or exact chat answer); blank returns the decision to Strategist. Persist `- **Template Application**: <prose>` in `design_spec.md §I`, derive internal mappings, and never copy it to `spec_lock.md` or add fixed options.+**Plan wording**: for Layout/Deck, state prototype use/order, what stays literal, and what may change, naming exact SVG basenames for prototype-specific exceptions rather than roles such as "cover". For Brand/Style, state identity or Direction / method constraints and free composition unless structure comes from another workspace.-**Two-stage boundary**: An installed template changes the content of final Stage 2, never the confirmation sequence. Run Stage 1 → final Stage 2 in order in both Confirm UI and chat fallback; do not skip a stage or treat template inspection as user confirmation. On browser timeout, return to the same stage in chat.+**Two-stage boundary**: an installed template changes the content of final Stage 2, never the confirmation sequence. Run Stage 1 → Stage 2 in order in both Confirm UI and chat fallback; template inspection is not user confirmation. On browser timeout, return to the same stage in chat.---## 2. Scenario Fit and Inherited Design-**Mandatory — decide from the §1 inspection**: For an installed `kind: deck`, compare the retained Template Overview with the confirmed audience, intent, outcome, delivery context, artifact afterlife, and source obligations. Deck application is reusable context for this comparison, never the current project's application contract and never an override. Compare the retained Page Roster and complete SVG roster with required narrative roles, content shapes, slots, and capacity. Reopen a resource only when its path + SHA changed. The template describes what exists; it never overrides the current project or own required/optional/repeatable or fixed/replaceable/example-only policy. For `kind: layout`, compare only structural roles, slots, and capacity. For an active Style segment, compare its communication method with the current contract and its composition requirements with any selected Layout/Deck structure. Surface a material incompatibility; never silently weaken one segment to make it fit.+**Mandatory — decide from the §1 inspection**: for `kind: deck`, compare the retained Template Overview with the confirmed audience, intent, outcome, delivery context, afterlife, and source obligations, and its Page Roster and SVG roster with required narrative roles, content shapes, slots, and capacity; Deck application is reusable context, never the current contract or an override. For `kind: layout`, compare only structural roles, slots, and capacity. For an active Style segment, compare its communication method with the current contract and its composition requirements with any selected Layout/Deck structure. Surface a material incompatibility; never silently weaken one segment to make it fit. Reopen a resource only when its path + SHA changed.| Internal scope | Appropriate when ||---|---|-| `mirror` | The artifact repeats a known form; literal appearance and text topology are requirements; new content fits existing roles and slots. |-| `layout` | The structural system and brand continue, but the communication outcome requires reflow, new emphasis, or an adaptive Layout. |-| `style` | Only communication/design direction is reused, a Style-only workspace is active, or the outcome requires a different sequence, density, or composition system. |+| `mirror` | The artifact repeats a known form; literal appearance and text topology are requirements; new content fits existing roles and slots |+| `layout` | The structural system and brand continue, but the outcome requires reflow, new emphasis, or an adaptive Layout |+| `style` | Only direction is reused, a Style-only workspace is active, or the outcome requires a different sequence, density, or composition system |-When the communication contract conflicts with the workspace, choose and state the best-fit application plan in the complete Stage-2 solution. Surface the mismatch only when it materially limits the result; do not respond with a mode questionnaire. Template capability constrains what is legal; scenario fit decides what is useful.+When the communication contract conflicts with the workspace, state the best-fit plan in the Stage-2 solution and surface the mismatch only when it materially limits the result; no mode questionnaire. Template capability constrains what is legal; scenario fit decides what is useful. (`content_divergence` controls source reorganization; `template_reuse_scope` records the reused layer; `template_adherence` records whether a structured plan keeps or extends Layout identities.)-> Internal note: `content_divergence` controls source reorganization; the AI-derived `template_reuse_scope` records the reused layer; `template_adherence` records whether a structured plan keeps or extends existing Layout identities.+**Precedence**: explicit current user instructions and final confirmation win. The installed set contributes at most one of each kind; all four may coexist. Brand overrides Deck identity. Layout overrides Deck structure; Deck keeps application context and identity not overridden by Brand; without Layout, Deck owns structure. Style owns Direction / method only: its visual values are candidate defaults that yield to resolved Brand/Deck identity, and its preferred Mode / Visual Style seed the single final locks. Style takes this segment ahead of ordinary Stage-2 defaults; active prototypes and Deck Signature facts remain compatibility constraints.-**Template design precedence**: Explicit current user instructions and final confirmation win. The installed set contributes at most one of each kind; all four may coexist. Brand overrides Deck identity. Layout overrides Deck structure; Deck retains application context and identity not overridden by Brand. Without Layout, Deck owns structure. Style owns Direction / method only: its visual values remain candidate defaults and yield to resolved Brand/Deck identity, while its preferred Mode / Visual Style seed the single final locks instead of creating parallel authority. Style takes this segment ahead of ordinary Stage-2 defaults; active prototypes and Deck Signature facts remain compatibility constraints. Library/explicit provenance never changes this order.--**Default — template-led recommendation (may override when explicit user or confirmed-contract requirements demand another result)**: Make all three directions obey the same resolved template context. Repeat fixed Brand/Deck palette roles and complete fonts with `typography.fixed: true`; keep resolved icon/image constraints and vary only open roles or dimensions. Mark the viable direction that most fully expresses the template-owned or template-informed structure, visual language, and application rules as `design_directions.selected`. Never weaken template use or split its segments across cards to manufacture alternatives. Style Review Focus never activates [`visual-review`](../workflows/stages/visual-review.md); only an explicit user request does.+**Default — template-led recommendation (may override for explicit user or confirmed-contract requirements)**: all three directions obey the same resolved template context. Repeat fixed Brand/Deck palette roles and complete fonts with `typography.fixed: true`; keep resolved icon/image constraints and vary only open roles or dimensions. Mark as `design_directions.selected` the viable direction that most fully expresses the template-owned structure, visual language, and application rules. Never weaken template use or split its segments across cards to manufacture alternatives. Style Review Focus never activates [`visual-review`](../workflows/stages/visual-review.md); only an explicit user request does.---## 3. Structured Lock Planning-For Style-only or Style + Brand, write `pptx_structure.mode: flat` plus `template_reuse_scope: style`; omit `template_adherence` and every structured mapping section. When a Style is installed alongside Layout or Deck, it changes only Direction / method and does not force flat/structured routing. Derive reuse scope from the selected Layout/Deck application plan; a literal `mirror` plan is compatible only when the Style segment requires no visual or topology change.--For `mirror` / `layout`, write `pptx_structure.mode: structured` plus `template_adherence: strict|adaptive`; mirror always writes `strict`. Do not write legacy `baseline`, `template`, `preserve`, `layout_strategy`, or Layout-kind rows.--- **Master roster**: Write one `pptx_masters` row per Master as `<master_key>: <picker name>` and copy the workspace's prototype roster. Keys use 1–64 ASCII letters, digits, dots, underscores, or hyphens, start with a letter/digit, and contain no spaces; human-readable spaces belong only in the picker name. Master visuals are root-level atomic elements and may never be `<g>`.-- **Reusable Layout roster**: Write every unique Layout once as `<layout_key>: <master_key> | <PowerPoint layout name> | <prototype source>`. Each installed `template:<basename>` source is a complete Slide prototype, including one not selected for the current generated deck. A new adaptive Layout uses its first generated `P<NN>` as source. Reuse a key only when fixed atoms and slot ids/types/indices/bounds/binding modes are identical. Name authored keys after composition, never page topic. A Layout may intentionally have zero slots; do not manufacture an empty `utility` kind or full-page fake slot.-- **Page assignment**: Write exactly one `page_pptx_layouts` row per page. Each key must exist in `pptx_layouts`. Check that distinct compositions do not collapse into role-only keys and that one skeleton does not split into topic-specific keys.-- **Slot planning**: Each reusable slot is a direct root `<g id>` with `data-pptx-placeholder`, positive design-zone bounds, and exactly one compatible direct carrier. Bounds come from the intended safe area, column, panel inset, or media frame—not sample text ink. A genuinely composite region may use only the explicit `object` + `proxy` downgrade.-- **Adaptive refinement**: Initial definitions are complete. If construction shows that reusable framing or slot topology/bounds must change, return to Strategist to add a definition sourced from that page and update its assignment before execution resumes. Executor never mutates or extends the contract; export only compiles declared structure and never discovers or clusters Layouts.-- **Input prototypes**: Add one `page_layouts` row per page using a complete Slide prototype. Strict preserves that SVG's contract; adaptive keeps its Master and may declare a new output Layout. Mirror preserves ordinary authored visuals and text-node topology; a direct JSON-first Chart/Table may regenerate only its derived preview children while retaining marker, metadata, bounds, and structure.--**Visualization compatibility**: Use `page_layouts` with optional Chart/Table-`page_visualizations` only when the prototype shell can carry the actual §IX-information model. The reference changes neither Layout identity, slot-topology, nor final visualization type. Qualitative relationships stay in §IX-and are composed Slide-locally; they never supply Master/Layout/placeholder-ownership. Without an exact prototype match, adaptive mode starts from the-closest neutral prototype and declares an output Layout; strict mode selects an-existing compatible Layout or revises the outline. Never omit `page_layouts`-on a structured route or write legacy `page_charts` in a new lock.+| Plan | Lock rows |+|---|---|+| Style-only or Style + Brand | `pptx_structure.mode: flat`, `template_reuse_scope: style`; omit `template_adherence` and every structured mapping section |+| `mirror` / `layout` | `pptx_structure.mode: structured`, `template_adherence: strict\|adaptive` (mirror always `strict`); no legacy `baseline`, `template`, `preserve`, `layout_strategy`, or Layout-kind rows |++A Style installed alongside Layout/Deck changes only Direction / method and never forces flat/structured routing; a literal `mirror` plan is compatible only when the Style segment requires no visual or topology change.++- **Master roster**: one `pptx_masters` row per Master as `<master_key>: <picker name>`, copied from the workspace roster. Keys are 1–64 ASCII letters/digits/dots/underscores/hyphens starting with a letter or digit; spaces belong only in the picker name. Master visuals are root-level atoms, never `<g>`.+- **Reusable Layout roster**: every unique Layout once as `<layout_key>: <master_key> | <PowerPoint layout name> | <prototype source>`. Each installed `template:<basename>` is a complete Slide prototype, including ones not selected for this deck; a new adaptive Layout uses its first generated `P<NN>`. Reuse a key only when fixed atoms and slot ids/types/indices/bounds/binding modes are identical. Name authored keys after composition, never page topic. Zero-slot Layouts are valid; do not manufacture an empty `utility` kind or a full-page fake slot.+- **Page assignment**: exactly one `page_pptx_layouts` row per page; each key must exist in `pptx_layouts`. Check that distinct compositions do not collapse into role-only keys and that one skeleton does not split into topic-specific keys.+- **Slot planning**: each reusable slot is a direct root `<g id>` with `data-pptx-placeholder`, positive design-zone bounds from the safe area, column, panel inset, or media frame — not sample text ink — and exactly one compatible direct carrier. A genuinely composite region uses only the explicit `object` + `proxy` downgrade.+- **Adaptive refinement**: initial definitions are complete. If construction shows that reusable framing or slot topology/bounds must change, return to Strategist to add a definition sourced from that page and update its assignment before execution resumes. Executor never mutates the contract; export only compiles declared structure.+- **Input prototypes**: one `page_layouts` row per page using a complete Slide prototype. Strict preserves that SVG's contract; adaptive keeps its Master and may declare a new output Layout. Mirror preserves authored visuals and text-node topology; a JSON-first Chart/Table may regenerate only its derived preview children.++**Visualization compatibility**: use `page_layouts` with optional Chart/Table `page_visualizations` only when the prototype shell can carry the actual §IX information model; the reference changes neither Layout identity, slot topology, nor visualization type. Qualitative relationships stay in §IX and are composed Slide-locally. Without an exact match, adaptive starts from the closest neutral prototype and declares an output Layout; strict selects an existing compatible Layout or revises the outline. Never omit `page_layouts` on a structured route or write legacy `page_charts`.diff --git a/skills/ppt-master/references/video-design.md b/skills/ppt-master/references/video-design.mdindex 1edd89df..4fa01e3a 100644--- a/skills/ppt-master/references/video-design.md+++ b/skills/ppt-master/references/video-design.md@@ -1,246 +1,105 @@# Video-delivery Design Reference Manual-Conditional design guidance for presentations whose intended use is a recorded,-self-running, or video delivery.--**Trigger**: load this reference when the effective delivery purpose is video,-recorded narration, or unattended playback. Also load its script rules for an-explicit final/literal narration input. Speaker notes, animation, or audio-requested for an otherwise ordinary deck do not activate it alone. Explicit-video/MP4 delivery does; Quick additionally activates §3's direct-delivery-contract.--**Ownership**: this is a conditional Generate reference, not a profile or a new-artifact route. Default keeps its Strategist and confirmation flow; Quick keeps-its one-pass active-context flow. Existing notes, animation, audio, and native-PowerPoint export stages retain their schemas and commands.-When Beautify is active, its wording/page/order invariants still bind; apply-this reference only inside the design and motion freedom that profile permits.+Conditional design guidance for presentations whose intended use is recorded, self-running, or video delivery.++**Trigger**: load when the effective delivery purpose is video, recorded narration, or unattended playback, and load its script rules for an explicit final/literal narration input. Speaker notes, animation, or audio requested for an ordinary deck do not activate it alone; explicit video/MP4 delivery does, and Quick additionally activates §3's direct-delivery contract.++**Ownership**: a conditional Generate reference, not a profile or artifact route. Default keeps Strategist and confirmation; Quick keeps its one-pass flow; notes, animation, audio, and native export stages keep their schemas and commands. Under Beautify, its wording/page/order invariants still bind — apply this reference only inside the freedom that profile permits.---## 1. Intake and Script State-Classify supplied spoken material before planning:-| Material | Treatment ||---|---|-| Ordinary source or rough transcript | Use as source material; edit, condense, and reorganize under the selected route's normal content-divergence contract |+| Ordinary source or rough transcript | Source material: edit, condense, reorganize under the route's normal content-divergence contract || Explicit final/literal narration script | Preserve every spoken word and its order; segment only at semantic scene boundaries |-| SRT used to generate new TTS | Preserve cue text when it is explicitly final; use source timecodes only as pacing evidence because the new synthesis timing becomes authoritative |-| SRT bound to an existing recording | Preserve its text/audio timing authority; do not regenerate TTS or pretend that one long recording was split automatically |-| Already page-separated final script | Preserve the supplied page boundaries unless the user explicitly permits restructuring |-| Target platform, canvas, or duration | Use the existing canvas registry; resolve scene granularity, page count, and notes length together |--**Hard rule — final means explicit**: freeze wording only when the user identifies-the script as final, literal, or verbatim. Never promote ASR output, subtitles,-or a draft transcript into a literal contract by inference.--**Default — semantic segmentation (may override for a user-authored page-plan)**: one scene represents one coherent visual state or mental-map step, not-one sentence, subtitle cue, or effect. Several cues may share a scene; one scene-may contain several ordered reveals.--**Final-script production input**: after the page roster is final but before SVG-authoring, write the resolved per-slide script once to `notes/total.md`. Use-`# Slide <number>` headings and `---` separators so the file can exist before SVG-filenames do; preserve each body segment verbatim. It is a production input, not-a storyboard or substitute Design Spec. Run `total_md_split.py` only after the-SVG roster exists.+| SRT used to generate new TTS | Preserve cue text when explicitly final; source timecodes are pacing evidence only, the new synthesis timing is authoritative |+| SRT bound to an existing recording | Preserve its text/audio timing authority; do not regenerate TTS or pretend one long recording was split automatically |+| Already page-separated final script | Preserve supplied page boundaries unless the user permits restructuring |+| Target platform, canvas, or duration | Use the canvas registry; resolve scene granularity, page count, and notes length together |++**Hard rule — final means explicit**: freeze wording only when the user identifies the script as final, literal, or verbatim; never promote ASR output, subtitles, or a draft transcript into a literal contract by inference.++**Final-script production input**: after the page roster is final and before SVG authoring, write the resolved per-slide script once to `notes/total.md` with `# Slide <number>` headings and `---` separators, each body segment verbatim. It is a production input, not a storyboard or substitute Design Spec; run `total_md_split.py` only after the SVG roster exists.++**Default — semantic segmentation (may override for a user-authored page plan)**: one scene is one coherent visual state or mental-map step, not one sentence, cue, or effect; several cues may share a scene and one scene may hold several ordered reveals.---## 2. Scene and Page Planning-**Default — quality follows purpose (may override)**: explanation prioritizes-understanding; promotion or brand work may prioritize emotion, recall, or-impact. Give every change a communication job.+**Default — quality follows purpose (may override)**: explanation prioritizes understanding; promotion or brand work may prioritize emotion, recall, or impact. Give every change a communication job.| Narrative relationship | Page treatment ||---|---|-| Several lines explain one idea | Keep one page/scene and reveal only the semantic units needed for that explanation |-| One system persists | Before roster/notes freeze, derive states from the prior composition; keep orienting cues and change the semantic delta |-| New evidence expands a known map | Retain orienting cues; adapt the active region and context as needed |+| Several lines explain one idea | One page/scene; reveal only the semantic units the explanation needs |+| One system persists | Derive states from the prior composition before roster/notes freeze; keep orienting cues, change the semantic delta |+| New evidence expands a known map | Retain orienting cues; adapt the active region and context || The same object changes position, scale, containment, or state | Consider compatible Morph endpoints when movement improves orientation |-| The audience must adopt a genuinely new mental map | Start a new composition and make the transition explicit |--**Default — stable visual anchors (may override when the mental map resets)**:-within one explanation, preserve recognizable roles, relationships, or spatial-cues. Position, scale, and style may change while identity and orientation-remain legible; reset for a new map.--**Default — one semantic focus change per beat (may override for one inseparable-idea)**: change several elements together only for one communication unit. Do-not alter unrelated regions merely for busyness.--**Default — scene chrome earns its place (may override for navigation, identity,-attribution, or fidelity)**: for newly authored recorded, self-running, or video-scenes, do not carry a report-style fixed header, footer, or page number merely-by deck convention. Let the semantic title participate in the scene composition,-and omit nonessential running chrome especially on cover, ending, and breathing-scenes. Retain source or template chrome when the active profile's fidelity-boundary requires it, and retain new chrome when it genuinely orients the-audience or carries required identity or attribution.--**Default — screen for orientation, notes for speech (may override for literal-on-screen copy)**: place keywords, structure, evidence, and relationships on the-slide; keep full explanation in notes. Do not duplicate the narration script as-body copy.--**Page-count rule**: derive page/notes boundaries from scenes, mental-map arcs,-endpoints, and duration—not cues or sentences. Profile-fixed count/order/content,-including 1:1/fidelity, permits only existing-neighbor evaluation; never alter-those invariants for motion.+| The audience must adopt a new mental map | Start a new composition and make the transition explicit |++**Defaults (each may override for the stated reason)**:++- *Stable anchors* — within one explanation preserve recognizable roles, relationships, or spatial cues; position, scale, and style may change while identity and orientation stay legible; reset for a new map.+- *One semantic focus change per beat* — change several elements together only for one inseparable communication unit; never alter unrelated regions for busyness.+- *Scene chrome earns its place* — newly authored scenes do not carry a report-style header, footer, or page number by convention; let the semantic title join the composition and drop running chrome on cover, ending, and breathing scenes. Keep chrome the active profile's fidelity boundary requires, or that genuinely orients, identifies, or attributes.+- *Screen for orientation, notes for speech* — keywords, structure, evidence, and relationships on the slide; full explanation in notes; never duplicate the narration as body copy, except literal on-screen copy.++**Page count**: derive page/notes boundaries from scenes, mental-map arcs, endpoints, and duration — not cues or sentences. Profile-fixed count/order/content (1:1/fidelity) permits only existing-neighbor evaluation; never alter those invariants for motion.---## 3. Default and Quick Planning Handoff-**Default**: Stage 1 confirms the existing open-text `delivery_context`; it does-not ask a separate video question. When the confirmed value identifies-recorded/self-running/video delivery, load this reference before authoring the-three Stage-2 whole solutions. Apply its scene grammar to every direction; it-does not add a style catalog or confirmation field. Record delivery context and-afterlife in §I, visible states and optional motion jobs in §IX, and script/notes-policy plus target duration in §X. When the final-script branch is active,-create the frozen `notes/total.md` after the approved roster/lock is final and-before Step 5 or split-mode handoff.--**Default — reading mode (may override for durable close reading)**: recorded-explanation leans `presentation`; choose `balanced` when close-reading afterlife-materially outweighs video delivery.--**Quick**: there is no Stage 1 or separate video-purpose confirmation. Explicit-video/recorded/self-running intent activates this reference after source-sufficiency is known and before the one-pass roster, resource, and motion-decisions; absent that intent, keep ordinary Quick behavior. Load the script-rules alone when an explicit final/literal narration will become notes/audio.-Keep the applicable scene grammar and final-script handling in active context.-A pre-SVG `notes/total.md` is an enabled production artifact, not a forbidden-planning checkpoint; Quick still creates no root Design Spec, lock,-confirmation payload, or storyboard.--**Hard rule — Quick video Custom Animations**: when Quick generates a PPTX for-recorded, self-running, or video delivery, enable Custom Animations before SVG-authoring and complete the custom-animation stage before base export. Use-semantic groups and page-specific choreography; deck-wide `-a auto` and page-transitions do not satisfy this requirement. Individual pages or groups may-remain static, so this is not an animation-coverage quota. A validated-`animations.json` is required unless the user explicitly requests static or-page-transition-only playback.--**Mandatory — Quick direct video input**: when Quick must deliver a narrated-video or MP4 rather than only a deck for later recording, enable Speaker Notes,-Narration Audio, and video export; write the complete per-scene narration to-`notes/total.md` before P01 and use it as page-design input. After the SVG-roster, only agent-authored wording may be finalized; final/literal input remains-verbatim. Before audio, complete the required Custom Animations configuration-and decide whether narration governs any group timing.+**Default**: Stage 1 confirms the existing open-text `delivery_context`, no separate video question. When the confirmed value identifies recorded/self-running/video delivery, load this reference before authoring the three Stage-2 solutions and apply its scene grammar to every direction; it adds no catalog or confirmation field. Record delivery context and afterlife in §I, visible states and optional motion jobs in §IX, script/notes policy plus target duration in §X. On the final-script branch, create the frozen `notes/total.md` after the approved roster/lock and before Step 5 or split-mode handoff. Reading mode leans `presentation`; choose `balanced` when close-reading afterlife materially outweighs video delivery.++**Quick**: no Stage 1 or video-purpose confirmation. Explicit video/recorded/self-running intent activates this reference after source sufficiency is known and before the one-pass roster, resource, and motion decisions; absent that intent, ordinary Quick behavior. Load the script rules alone when an explicit final/literal narration becomes notes/audio. A pre-SVG `notes/total.md` is an enabled production artifact; Quick still creates no Design Spec, lock, confirmation payload, or storyboard.**Production outcomes**:| Need | Decision ||---|---|| Spoken delivery or a supplied final script | Enable Speaker Notes |-| User asks the workflow to synthesize narration | Enable Narration Audio; Speaker Notes is its dependency |+| User asks the workflow to synthesize narration | Enable Narration Audio (Speaker Notes is its dependency) || Progressive reveal, continuing geometry, or timed emphasis materially aids explanation | Enable/load the appropriate animation capability |-| Quick generates a PPTX for recorded, self-running, or video delivery | Enable Custom Animations before SVG authoring and validate `animations.json` before base export |-| Quick directly delivers a narrated video or MP4 | Also enable Speaker Notes, Narration Audio, and video export; resolve narration-governed timing before audio, requiring timestamped page-local SRT for cue sync or subtitle delivery |-| The user explicitly requests static playback or disables object motion | Keep object animation off; retain the remaining notes/audio/video outcomes as requested |+| Quick generates a PPTX for recorded, self-running, or video delivery | **Hard rule**: enable Custom Animations before SVG authoring, use semantic groups and page-specific choreography, and complete the stage with a validated `animations.json` before base export; deck-wide `-a auto` and page transitions do not satisfy it; pages or groups may stay static — no coverage quota |+| Quick directly delivers a narrated video or MP4 | **Mandatory**: also enable Speaker Notes, Narration Audio, and video export; write the complete per-scene narration to `notes/total.md` before P01 as page-design input (agent-authored wording may be finalized after the roster, final/literal input stays verbatim); resolve narration-governed timing before audio, requiring timestamped page-local SRT for cue sync or subtitle delivery |+| The user explicitly requests static or page-transition-only playback | Keep object animation off; retain the remaining notes/audio/video outcomes |-**Capability boundary**: Default generation does not force object animation or-generated audio merely because a deck may later be recorded. Quick with an-effective recorded/self-running/video delivery purpose does require Custom-Animations, while explicit user instructions for static or-page-transition-only playback remain authoritative. This requirement selects-the capability, not motion coverage or one effect for every page.+Default never forces object animation or audio merely because a deck may later be recorded; the Quick requirement selects the capability, not motion coverage.---## 4. SVG, Notes, and Motion Realization-When §3 created `notes/total.md` before SVG, read it once before the first SVG-and design each page around its corresponding spoken segment. Give every-independently narrated or timed semantic unit a descriptive direct-root `<g-id>`; keep inseparable units grouped. Preserve a final/literal script exactly;-agent-authored direct-video narration may change only during its final-SVG-validation before audio.--**Hard rule — script/design consistency**: a final script is literal content.-If the finished visual page introduces an independent claim or relationship the-script does not explain, repair the page or return to planning; never rewrite or-pad the final script during the late notes pass. Conversely, every spoken idea-that requires visual orientation must have a visible state or deliberate-speech-only treatment.--**Motion readiness**: load `animations.md` before SVG authoring whenever the-plan needs compatible Morph endpoints or page/object-specific motion. Author-every required start/end state and real semantic group before the final checker;-post-processing cannot invent missing visual endpoints or target IDs.--**Motion restraint**: use transitions, reveals, emphasis, and Morph only for a-named communication job. There is no motion-coverage quota, and `effect: none`-remains valid. Auto-running narration uses `after-previous` / `with-previous`,-never `on-click`.--**Mandatory when narration governs object motion**: before SVG authoring, load-`animations.md` and preserve real semantic groups; before audio, create and-validate canonical `animations.json`. After the base PPTX/report and timestamped-page audio/SRT, map timed groups in `narration_timing.json`, derive-`narration_animations.json`, and export the narrated PPTX/MP4. Only derived-triggers/delays wait for SRT; object identity, effect, and order do not. `-a-auto` or inherited fixed stagger is not semantic synchronization. For an-explicit user-selected static/page-transition-only Quick exception, or for-ordinary Default narration-independent deck-wide motion, omit these sidecars-and the object-sync claim.--**Sound effects**: exclude them from this pass and planning artifacts. After-final SVG/motion, animation post-processing owns on-demand selection and native-PPTX configuration; otherwise remain silent. For direct narrated MP4 delivery,-`generate-audio` owns the selected sound-delivery branch: native PowerPoint-encoding plus triggered post-export mix, or an explicitly requested real-time-PowerPoint slideshow capture. Video gain and limiting never enter-`animations.json`; capture uses the balance actually heard during Slide Show.--**Production sequence**: after the final SVG check, validate any pre-SVG-narration against the visible pages; ordinary draft-source runs instead use the-final-SVG-grounded notes generation. Split notes, execute the resolved motion-path, and export the editable PPTX. Direct Quick video continues-through audio and, when required, timestamped SRT. Custom Animations use the-narrated-sidecar flow when narration governs group timing;-narration-independent custom motion exports its canonical timing without an-object-sync claim before the narrated PPTX and MP4.+When §3 created `notes/total.md` before SVG, read it once before the first SVG and design each page around its spoken segment. Give every independently narrated or timed semantic unit a descriptive direct-root `<g id>`; keep inseparable units grouped. Preserve a final/literal script exactly; agent-authored direct-video narration changes only during final-SVG validation before audio.++**Hard rule — script/design consistency**: a final script is literal content. If a finished page introduces a claim or relationship the script does not explain, repair the page or return to planning — never rewrite or pad the script in the late notes pass. Every spoken idea needing visual orientation has a visible state or a deliberate speech-only treatment.++**Motion**: load `animations.md` before SVG authoring whenever the plan needs Morph endpoints or page/object-specific motion, and author every required start/end state and semantic group before the final checker — post-processing cannot invent endpoints or target IDs. Use transitions, reveals, emphasis, and Morph only for a named communication job; `effect: none` remains valid. Auto-running narration uses `after-previous` / `with-previous`, never `on-click`.++**Mandatory when narration governs object motion**: before SVG, load `animations.md` and preserve semantic groups; before audio, create and validate canonical `animations.json`. After the base PPTX/report and timestamped page audio/SRT, map timed groups in `narration_timing.json`, derive `narration_animations.json`, and export the narrated PPTX/MP4. Only derived triggers/delays wait for SRT; identity, effect, and order do not. `-a auto` or inherited fixed stagger is not semantic synchronization. For a user-selected static/page-transition-only Quick exception, or ordinary Default narration-independent deck-wide motion, omit these sidecars and the object-sync claim.++**Sound effects**: excluded from this pass and planning artifacts. After final SVG/motion, animation post-processing owns on-demand selection and native configuration. For direct narrated MP4, `generate-audio` owns the sound-delivery branch (§5); gain and limiting never enter `animations.json`.++**Production sequence**: after the final SVG check, validate pre-SVG narration against the visible pages (draft-source runs use final-SVG-grounded notes generation instead); split notes, execute the resolved motion path, export the editable PPTX; direct Quick video continues through audio and, when required, timestamped SRT. Narration-governed Custom Animations use the narrated-sidecar flow; narration-independent custom motion exports its canonical timing without an object-sync claim before the narrated PPTX and MP4.---## 5. Delivery Boundary-**Canonical artifact**: the editable PPTX remains canonical. `generate-audio`-owns provider/voice/rate selection, page audio/SRT generation, semantic-narration timing, narrated PPTX export, optional native PowerPoint video export,-the explicit slideshow-capture handoff, and the triggered sound-effects mix for-direct MP4 delivery.+**Canonical artifact**: the editable PPTX. `generate-audio` owns provider/voice/rate selection, page audio/SRT, semantic narration timing, narrated PPTX export, optional native PowerPoint video export, the slideshow-capture handoff, and the triggered sound-effects mix.-**Conditional MP4**: run `powerpoint_video.py --check` only for the native-export-branch. If native Windows PowerPoint export is unavailable, keep the narrated-PPTX as the successful upstream artifact. An explicit slideshow-capture choice-may hand that artifact to a user-operated Windows PowerPoint recorder; it is not-complete until the capture is returned and accepted. Do not substitute-screenshots, HTML, or a third-party renderer and call it equivalent.+**Conditional MP4**: run `powerpoint_video.py --check` only for the native-export branch. Without native Windows PowerPoint export, the narrated PPTX is the successful upstream artifact; an explicit slideshow-capture choice hands it to a user-operated PowerPoint recorder and is complete only when the capture is returned and accepted. Never substitute screenshots, HTML, or a third-party renderer.**Hard rule — choose one PowerPoint video sound boundary**:| Delivery branch | Sound contract ||---|---|-| Native encoder | PowerPoint supplies visual animation and narration but may omit transition/object sounds. With resolved cues, treat its MP4 as raw and require the verified `video_sound_mix.py` output. |-| Real-time slideshow capture | PowerPoint remains the renderer and audio player; a recorder captures the full-screen Slide Show and exactly one application/system-audio source. The accepted capture must contain narration and every configured cue once, and must not enter `video_sound_mix.py`. |--The branches are mutually exclusive because mixing a capture would duplicate-its cues. Keep the native cue configuration in the canonical PPTX. Slideshow-capture is explicit and human-audited; it does not inherit the native mix-receipt or become an automatic fallback.--**Current boundary**: importing and automatically splitting one long finished-recording is unsupported. Require page-level audio or an explicit page/time map;-otherwise deliver the designed deck and frozen notes without claiming audio-integration.+| Native encoder | PowerPoint supplies visual animation and narration but may omit transition/object sounds; with resolved cues its MP4 is raw and requires the verified `video_sound_mix.py` output |+| Real-time slideshow capture | PowerPoint renders and plays audio; a recorder captures the full-screen Slide Show and exactly one application/system-audio source; the accepted capture contains narration and every cue once and never enters `video_sound_mix.py` |++The branches are mutually exclusive because mixing a capture would duplicate its cues. Keep the native cue configuration in the canonical PPTX; capture is explicit and human-audited, never an automatic fallback.++**Current boundary**: importing and automatically splitting one long finished recording is unsupported. Require page-level audio or an explicit page/time map; otherwise deliver the deck and frozen notes without claiming audio integration.diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex 0361c6ed..e9b8b1df 100644--- a/skills/ppt-master/scripts/prompt_audit_manifest.json+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json@@ -36,7 +36,7 @@"skills/ppt-master/references/preset-shape-vocabulary.md": 2750,"skills/ppt-master/references/strategist.md": 12000,"skills/ppt-master/references/strategist-image.md": 3250,- "skills/ppt-master/references/strategist-template.md": 3000,+ "skills/ppt-master/references/strategist-template.md": 2500,"skills/ppt-master/templates/design_spec_reference.md": 4000,"skills/ppt-master/templates/spec_lock_reference.md": 2750,"skills/ppt-master/templates/charts/chart-vocabulary.md": 1250,@@ -44,7 +44,8 @@"skills/ppt-master/templates/sounds/sound-vocabulary.md": 6250,"skills/ppt-master/workflows/generate-pptx.md": 10000,"skills/ppt-master/workflows/stages/apply-template-workspace.md": 3500,- "skills/ppt-master/references/confirm-surface.md": 3000+ "skills/ppt-master/references/confirm-surface.md": 3000,+ "skills/ppt-master/references/video-design.md": 2500},"load_sets": {"bootstrap.routing": {@@ -1952,7 +1953,7 @@{"path": "skills/ppt-master/references/strategist-template.md","role": "compatibility",- "fingerprint": "b0f9494f710a",+ "fingerprint": "8f83a50b3f54","reason": "This site documents a legacy or omission compatibility boundary."},{@@ -2002,6 +2003,12 @@"role": "consumer","fingerprint": "2a2c42538a76","reason": "This stage documents how each Generate runtime consumes the prototype mapping."+ },+ {+ "path": "skills/ppt-master/references/strategist-template.md",+ "role": "consumer",+ "fingerprint": "bffb5ebb6180",+ "reason": "Strategist plans page_layouts rows from complete Slide prototypes."}]},@@ -2027,12 +2034,6 @@"fingerprint": "9cef05268f4f","reason": "This reference mirrors the owner field grammar or ownership boundary."},- {- "path": "skills/ppt-master/references/strategist-template.md",- "role": "producer",- "fingerprint": "fb6d05bac6e4",- "reason": "This producer projects the owner field into the planning contract."- },{"path": "skills/ppt-master/templates/spec_lock_reference.md","role": "reference",@@ -2126,7 +2127,7 @@{"path": "skills/ppt-master/references/strategist-template.md","role": "producer",- "fingerprint": "f97c538adf92",+ "fingerprint": "3d83dfd41293","reason": "This producer projects the owner field into the planning contract."},{@@ -2162,7 +2163,7 @@{"path": "skills/ppt-master/references/strategist-template.md","role": "producer",- "fingerprint": "29a9e58295a9",+ "fingerprint": "5eff475d59c9","reason": "This producer projects the owner field into the planning contract."},{