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): tighten template READMEs and the icon library README
hugohe30973cd136366
diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex 12978495..c857dbe5 100644--- a/skills/ppt-master/scripts/prompt_audit_manifest.json+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json@@ -73,7 +73,13 @@"skills/ppt-master/workflows/create-template/create-deck.md": 1500,"skills/ppt-master/workflows/stages/customize-animations.md": 4250,"skills/ppt-master/references/svg-image-embedding.md": 1750,- "skills/ppt-master/references/image-layout-spec.md": 2250+ "skills/ppt-master/references/image-layout-spec.md": 2250,+ "skills/ppt-master/templates/README.md": 1750,+ "skills/ppt-master/templates/brands/README.md": 750,+ "skills/ppt-master/templates/styles/README.md": 1250,+ "skills/ppt-master/templates/layouts/README.md": 1500,+ "skills/ppt-master/templates/decks/README.md": 1250,+ "skills/ppt-master/templates/icons/README.md": 1750},"load_sets": {"bootstrap.routing": {@@ -1199,15 +1205,6 @@"max_exact_results": 100,"max_near_results": 100,"accepted": [- {- "kind": "exact",- "fingerprint": "7c36a9231d14",- "paths": [- "skills/ppt-master/templates/decks/README.md",- "skills/ppt-master/templates/layouts/README.md"- ],- "reason": "Shared boilerplate between sibling template-kind docs; kept in lockstep on purpose."- },{"kind": "exact","fingerprint": "d886e9fcb8dc",@@ -1308,15 +1305,6 @@],"reason": "Corporate brand presets share the same consistent icon convention by design."},- {- "kind": "exact",- "fingerprint": "6a432b0cc1df",- "paths": [- "skills/ppt-master/templates/decks/README.md",- "skills/ppt-master/templates/layouts/README.md"- ],- "reason": "Sibling Deck and Layout docs keep the shared replication-mode explanation in lockstep."- },{"kind": "exact","fingerprint": "286b55cb84d7",diff --git a/skills/ppt-master/templates/README.md b/skills/ppt-master/templates/README.mdindex ada3fd66..e5c54bd3 100644--- a/skills/ppt-master/templates/README.md+++ b/skills/ppt-master/templates/README.md@@ -2,164 +2,55 @@## Reusable template kinds-Brand, Style, Layout, and Deck are independent template kinds, not stages of one-inheritance hierarchy.+Brand, Style, Layout, and Deck are independent kinds, not stages of one inheritance hierarchy — each owns a different segment.| Kind | Owns | Does not own | Discovery index ||---|---|---|---|| [`brands/`](./brands/) | Identity: color, typography, logo, voice, icon style | Page structure or SVG roster | [`brands_index.json`](./brands/brands_index.json) |-| [`styles/`](./styles/) | Direction/method: reusable communication method, visual language, composition rhythm, and information-expression defaults | Official brand identity, current-project application, page structure, or SVG roster | [`styles_index.json`](./styles/styles_index.json) |-| [`layouts/`](./layouts/) | Brand-neutral structure: canvas, Master/Layout graph, page types, slots, SVG roster | Brand identity or a recurring communication application | [`layouts_index.json`](./layouts/layouts_index.json) |-| [`decks/`](./decks/) | A recurring presentation family: application contract + integrated identity + structure | — | [`decks_index.json`](./decks/decks_index.json) |--A brand is not “a layout minus its pages”, and a Style is not a roster-free-Deck: each owns a different segment. Use a brand for identity with free page-composition, a Style for reusable direction/method without identity truth or-page prototypes, a layout for brand-neutral structure whose identity and-communication purpose remain downstream decisions, and a deck for a recurring-presentation family with an explicit application contract.--PowerPoint package objects are compilation targets, not additional template-kinds. Theme values and identity assets are projected from resolved identity-rules supplied by Brand, Deck, or the current project; Layout rules project-into Master/Layout/Placeholder topology, semantic text roles, and-spatial behavior; Deck combines both with descriptive recurring-application-context and actual prototype examples. Style rules guide communication method,-visual language, composition, and information expression; they do not create a-PowerPoint package object or override resolved Brand/Deck identity. Downstream AI planning decides which-prototypes and content to use, then records the required exporter values.-A compiled Slide Master may therefore contain both-structural geometry and brand visuals even though their source rules remain-separately owned.--New workspaces always enter [`Create Template`](../workflows/create-template.md),-which keeps the fixed route name and dispatches exactly one child workflow:-[`Create Brand`](../workflows/create-template/create-brand.md),-[`Create Style`](../workflows/create-template/create-style.md),-[`Create Layout`](../workflows/create-template/create-layout.md), or-[`Create Deck`](../workflows/create-template/create-deck.md).--The four indexes are the complete library-discovery source for Default-[`generate-pptx`](../workflows/generate-pptx.md) Stage-1 template selection.-Step 3 prepares candidate input without interaction or reading template-content. The Stage-1 page confirms the communication contract together with an-explicit free-design/template choice; only template mode expands these indexes.-Exact roots supplied for the run or handed off by Create Template appear as-specified candidates. Ordinary requests default to free design; explicit-template intent or any supplied root defaults to template mode. Exactly one root-may be preselected, while multiple roots remain unselected candidates. The user-can always switch modes. The page accepts one registered choice per kind plus-one supplied-root choice, but the complete selection contains at most one-contribution per kind. All four kinds may combine; Layout owns structure when-both Layout and Deck are present. A supplied multi-kind root is atomic. A registered exact root is `library`; any other exact root is-`explicit`. After that combined confirmation,-[`apply-template-workspace`](../workflows/stages/apply-template-workspace.md)-validates and maps every distinct selected root once, preserving each-contribution as `design_spec.<kind>.<id>.md` before Stage 2 starts. Template-aware reading begins in final Stage 2 from-that project-local copy. Quick skips the page, applies supplied exact roots, and-otherwise uses free design.+| [`styles/`](./styles/) | Direction/method: communication method, visual language, composition rhythm, information-expression defaults | Official identity, current-project application, structure, or roster | [`styles_index.json`](./styles/styles_index.json) |+| [`layouts/`](./layouts/) | Brand-neutral structure: canvas, Master/Layout graph, page types, slots, SVG roster | Identity or a recurring application | [`layouts_index.json`](./layouts/layouts_index.json) |+| [`decks/`](./decks/) | A recurring presentation family: application context + integrated identity + structure | — | [`decks_index.json`](./decks/decks_index.json) |++PowerPoint package objects are compilation targets, not kinds: Theme values and identity assets project from resolved identity rules (Brand, Deck, or the current project); Layout rules project into Master/Layout/Placeholder topology, semantic text roles, and spatial behavior; Deck combines both with descriptive application context and actual prototypes; Style guides method and expression without creating a package object or overriding resolved identity. Downstream planning decides which prototypes and content to use and records the exporter values, so one compiled Master may hold both structural geometry and brand visuals under separately owned rules.++New workspaces enter [`Create Template`](../workflows/create-template.md), which dispatches exactly one child ([`Create Brand`](../workflows/create-template/create-brand.md), [`Create Style`](../workflows/create-template/create-style.md), [`Create Layout`](../workflows/create-template/create-layout.md), [`Create Deck`](../workflows/create-template/create-deck.md)). Selection, mode defaults, preselection, `library` / `explicit` labels, cardinality, and installation are owned by [`routing.md`](../workflows/routing.md) §7 and [`apply-template-workspace`](../workflows/stages/apply-template-workspace.md): the four indexes are the complete library discovery source for Default Stage 1, every selected root is installed as `design_spec.<kind>.<id>.md` before Stage 2, and Quick applies supplied exact roots directly.## Orthogonal contracts| Axis | Values | Meaning ||---|---|---|-| Template kind | `brand` / `style` / `layout` / `deck` | Which reusable contract the package owns: identity, direction/method, brand-neutral structure, or a complete recurring application |-| Selection source | `library` / `explicit` | Step-3 discovery provenance only: exact index-derived root or exact unregistered root; it does not change template semantics |-| Internal creation strategy | `standard` / `fidelity` / `mirror` | AI-derived Create Layout/Create Deck implementation: newly author a compact or broad roster, or materialize validated source-package facts into a new workspace; persisted for tools, never presented as a required user choice |-| Internal application plan | `template_reuse_scope` plus optional `template_adherence` | Strategist derives literal, structural, or style-only use and any strict/adaptive exporter behavior after inspecting the installed template and current content |-| PPTX structure | `flat` / `structured` | Derived application plans that use template structure compile declared Masters and Layouts; Style-only, style-scope, brand-only, and free design remain Slide-local. A Style installed alongside Layout/Deck does not change the non-Style structure plan. |+| Template kind | `brand` / `style` / `layout` / `deck` | Which reusable contract the package owns |+| Selection source | `library` / `explicit` | Discovery provenance only (index-derived root vs exact unregistered root); no semantic effect |+| Internal creation strategy | `standard` / `fidelity` / `mirror` | AI-derived Create Layout/Deck implementation (author a compact or broad roster, or materialize validated source facts); persisted for tools, never a user choice |+| Internal application plan | `template_reuse_scope` plus optional `template_adherence` | Strategist-derived literal, structural, or style-only use and strict/adaptive exporter behavior |+| PPTX structure | `flat` / `structured` | Plans using template structure compile declared Masters and Layouts; Style-only, style-scope, brand-only, and free design stay Slide-local; a Style beside Layout/Deck never changes the structure plan |-These axes must not be used as synonyms or exposed as a user mode matrix. In-particular, a mirror-created deck is still an ordinary reusable `deck` package-after creation; it does not force future presentations to keep the source page-count or order.+Never use these axes as synonyms or expose them as a mode matrix; a mirror-created deck is an ordinary reusable `deck` and forces no future page count or order.## Workspace contract-Every package uses the same portable root under either this library or an-initialized project:-```text<template_workspace>/-├── templates/ # the Design Spec (naming below); optional Layout/Deck SVGs and native_payloads.json.gz store-├── images/ # optional bitmaps-├── icons/-│ └── imported/ # optional imported vectors, one canonical copy-└── exports/ # optional review evidence; never a template input+├── templates/ # the Design Spec (naming below); optional Layout/Deck SVGs and native_payloads.json.gz+├── images/ # optional bitmaps; SVG href ../images/<name>+├── icons/imported/ # optional imported vectors, one canonical copy; data-icon="imported/<name>"+└── exports/ # optional review evidence; never a template input```-**Hard rule — the container disambiguates, the filename carries the rest**: one-schema serves both layers. A library root keeps `templates/design_spec.md`, since-`<kind_dir>/<template_id>/` already names its kind and id. A project root shares-one flat `templates/`, so it keeps one `design_spec.<kind>.<id>.md` per kind;-filename kind/id MUST equal frontmatter `kind`/`<kind>_id`. The shapes never-mix. One `templates/`-holds one active SVG roster: Layout when present, otherwise Deck. Both specs may-coexist because Layout overrides only Deck structure. Either shape is a-workspace root, and selecting it takes every kind it exposes.--Empty optional directories are omitted. Template SVGs reference bitmaps through-`../images/<name>` and imported vectors through `data-icon="imported/<name>"`.-Style contributes only its own Design Spec and no asset or review payload;-sibling scaffolding and other kinds' files are not Style input.-Every kind ignores `exports/`. The conditional-[`apply-template-workspace`](../workflows/stages/apply-template-workspace.md)-stage owns the rest: when installation runs, which roots each kind consumes,-legacy-flat readability, and the boundary that every later consumer reads the-installed project-local files rather than the original root.+**Hard rule — the container disambiguates, the filename carries the rest**: a library root keeps `templates/design_spec.md` (its `<kind_dir>/<template_id>/` names kind and id); a project root shares one flat `templates/` and keeps one `design_spec.<kind>.<id>.md` per kind, with filename kind/id equal to frontmatter `kind` / `<kind>_id`; the shapes never mix. One `templates/` holds one active roster — Layout when present, otherwise Deck — while both specs may coexist because Layout overrides only Deck structure. Either shape is a workspace root, and selecting it takes every kind it exposes. Empty optional directories are omitted; Style contributes only its spec; every kind ignores `exports/`.## Design specification references-[`design_spec_reference.md`](./design_spec_reference.md) and-[`spec_lock_reference.md`](./spec_lock_reference.md) own normal whole-document-authoring; their schemas own machine validation. Files under `scaffolds/` are-optional overwrite-safe CLI conveniences, not Generate-route starting artifacts.-Reusable template `design_spec.md` files are-deliberately smaller: they contain portable metadata and only the identity,-direction/method, structure, or application rules owned by that package. General SVG rules live-in [`shared-standards-core.md`](../references/shared-standards-core.md), with-effects and PowerPoint interfaces loaded only when triggered.+[`design_spec_reference.md`](./design_spec_reference.md) and [`spec_lock_reference.md`](./spec_lock_reference.md) own project-level authoring; their schemas own validation; `scaffolds/` files are optional CLI conveniences. Template specs are deliberately smaller — portable metadata plus only the rules the package owns; general SVG rules live in [`shared-standards-core.md`](../references/shared-standards-core.md).## Visualization Templates-Page-local Shape-first references are catalog families, not reusable template-kinds:--| Family | Owns | Planning map | Machine index |-|---|---|---|---|-| Chart | Value-driven geometry (33) | [`chart-vocabulary.md`](./charts/chart-vocabulary.md) | [`charts_index.json`](./charts/charts_index.json) |-| Table | Row × column fact grid (6) | [`table-vocabulary.md`](./tables/table-vocabulary.md) | [`tables_index.json`](./tables/tables_index.json) |--[`VISUALIZATION_TEMPLATE_AUTHORING.md`](./VISUALIZATION_TEMPLATE_AUTHORING.md)-is the shared authoring contract. Each machine index owns family membership;-the Chart and Table vocabularies are their complete objective planning-projections.--Qualitative Structure is a Slide-local Executor method rather than a catalog:-Default and Quick both derive its relationship model and compose shapes for the-current page. Only Layout and Deck workspaces own reusable Master/Layout, page-types, slots, and placeholders. When both are present, Layout supplies the-active SVG roster and overrides only Deck's structure segment.+Page-local Shape-first catalog families, not kinds: Chart — value-driven geometry (33), planning map [`chart-vocabulary.md`](./charts/chart-vocabulary.md), index [`charts_index.json`](./charts/charts_index.json); Table — row × column fact grid (6), [`table-vocabulary.md`](./tables/table-vocabulary.md), [`tables_index.json`](./tables/tables_index.json). [`VISUALIZATION_TEMPLATE_AUTHORING.md`](./VISUALIZATION_TEMPLATE_AUTHORING.md) is the maintainer authoring contract. Qualitative Structure is a Slide-local Executor method, not a catalog; only Layout and Deck own reusable Master/Layout, page types, slots, and placeholders.## Icon Library-The `icons/` directory contains 12,027 vector icons across five libraries:--| Library | Style | Count |-|---------|-------|-------|-| `chunk-filled` | fill / compact, chunky 16px silhouettes | 641 |-| `tabler-filled` | fill / bezier-curve forms | 1,055 |-| `tabler-outline` | stroke / line | 5,138 |-| `phosphor-duotone` | duotone / single color + 0.2 opacity backplate | 1,518 |-| `simple-icons` | brand logos (company / product marks) | 3,675 |--- **Usage & style rules**: [icons/README.md](./icons/README.md)-- **Versions, licenses & attribution**: [icons/THIRD_PARTY_NOTICES.md](./icons/THIRD_PARTY_NOTICES.md)-- **Search icons**: `rg --files skills/ppt-master/templates/icons/<library>/ | rg <keyword>`+[`icons/`](./icons/) holds 12,027 vectors across five libraries (`chunk-filled` 641, `tabler-filled` 1,055, `tabler-outline` 5,138, `phosphor-duotone` 1,518, `simple-icons` 3,675 brand logos); usage and style rules in [icons/README.md](./icons/README.md), licenses in [icons/THIRD_PARTY_NOTICES.md](./icons/THIRD_PARTY_NOTICES.md).## Sound Library-[`sounds/`](./sounds/) is a post-motion selection resource, not a template or-Strategist resource. Its complete-[cue vocabulary](./sounds/sound-vocabulary.md) is read only after a concrete-auditory job exists; sync selected cues only. See [usage](./sounds/README.md).+[`sounds/`](./sounds/) is a post-motion selection resource, not a template or Strategist resource: read its [cue vocabulary](./sounds/sound-vocabulary.md) only after a concrete auditory job exists and sync selected cues only ([usage](./sounds/README.md)).diff --git a/skills/ppt-master/templates/brands/README.md b/skills/ppt-master/templates/brands/README.mdindex 00029d84..9e76f86f 100644--- a/skills/ppt-master/templates/brands/README.md+++ b/skills/ppt-master/templates/brands/README.md@@ -1,65 +1,25 @@# Brand Identity Presets-This directory holds **brand-only templates**: identity bundles (color / typography / logo / voice / icon style) without an SVG page roster. Strategist locks the brand's identity segment as truth; Executor designs pages freely under those constraints.--Brand is one of four template kinds in the library — alongside-[`styles/`](../styles/) (direction/method defaults), [`layouts/`](../layouts/)-(brand-neutral structure), and [`decks/`](../decks/) (a recurring application-with integrated identity and structure). The shared kind and workspace model-lives in the parent [`README.md`](../README.md).+**Brand-only templates**: identity bundles (color / typography / logo / voice / icon style) without an SVG roster. Strategist locks the identity segment as truth; Executor composes pages freely under it. Brand is one of four kinds alongside [`styles/`](../styles/), [`layouts/`](../layouts/), and [`decks/`](../decks/); the shared kind and workspace model lives in the parent [`README.md`](../README.md).## How brands are consumed-Brand application follows the parent README's Default Stage-1-[`generate-pptx`](../../workflows/generate-pptx.md) template-choice contract.-Its Brand choices come only from `brands_index.json`; no-directory scan or bare-name match is allowed. A supplied exact root appears in-the same selector, defaults Stage 1 to template mode, and preselects that-specific candidate only when it is the sole supplied root.-Registered exact roots are `library`; other exact roots remain `explicit`. The conditional-[`apply-template-workspace`](../../workflows/stages/apply-template-workspace.md)-stage owns path normalization, portable-root installation, per-workspace spec naming,-selection-conflict rejection, and provenance after Stage 1 and before Stage 2. Template-aware-reading begins in final Stage 2 from the installed project-local copy. This file owns-only the Brand schema. Quick applies a supplied exact Brand root directly and-otherwise uses free design.+Selection follows the parent contract: Brand choices come only from `brands_index.json` (no directory scan or bare-name match); a supplied exact root joins the same selector, defaults Stage 1 to template mode, and is preselected only when it is the sole root; [`apply-template-workspace`](../../workflows/stages/apply-template-workspace.md) installs it before Stage 2; Quick applies a supplied exact root directly. This file owns only the Brand schema.## Creating a new brand-Enter the fixed Create Template route, which dispatches the Create Brand child workflow:--```-Read skills/ppt-master/workflows/create-template.md, which dispatches `kind: brand` to skills/ppt-master/workflows/create-template/create-brand.md-```--Three input paths are supported: brand asset (logo / brand site URL / branded PPTX / brand PDF), verbal spec dictated in chat, or empty skeleton for the user to fill in later.+Enter [`create-template.md`](../../workflows/create-template.md), which dispatches `kind: brand` to [`create-brand.md`](../../workflows/create-template/create-brand.md), from a brand asset (logo / site / branded PPTX / PDF), a verbal spec, or an explicitly requested empty skeleton.-## Workspace structure--Every brand uses the same workspace routing as layout and deck templates. Brand identity remains roster-free; omit empty optional directories instead of adding placeholder files.--```+```texttemplates/brands/<brand_id>/-├── templates/-│ └── design_spec.md # required — brand identity spec-├── images/ # optional — logos and visual assets-│ ├── logo.<ext> # optional — primary logo-│ └── <brand>_wordmark.svg # optional — alternate lockups and visual assets+├── templates/design_spec.md # required — identity spec with YAML frontmatter `kind: brand`+├── images/ # optional — logo.<ext>, alternate lockups, visual assets├── icons/ # optional — branded icon overrides-└── exports/ # normally absent; real local derived artifacts only; Git-ignored+└── exports/ # normally absent; Git-ignored derived artifacts only```-Logo filenames are descriptive, not contractual — `templates/design_spec.md` §IV lists exact `../images/...` paths and usage contexts. Single-lockup brands typically ship one logo; dual-lockup brands ship separately named files.--`templates/design_spec.md` carries a YAML frontmatter block with `kind: brand` and is the single source of truth for the brand identity. The six required sections are: I Brand Overview / II Color Scheme / III Typography / IV Logo / V Voice & Tone / VI Icon Style.+Logo filenames are descriptive; `design_spec.md` §IV lists the exact `../images/...` paths and usage. The six required sections are I Brand Overview / II Color Scheme / III Typography / IV Logo / V Voice & Tone / VI Icon Style; omit empty optional directories.## Discovery index-[brands_index.json](./brands_index.json) is a slim machine-readable map (`brand_id → { summary, primary_color }`). Refresh it with `register_template.py --kind brand <brand_id>` after a brand is created or edited. Registration rejects incomplete frontmatter, mismatched IDs, page SVGs, missing required identity sections, invalid or inconsistent colors/provenance, and broken workspace-local asset references.--The Default Stage-1 template controls read this index as their complete-registered-brand catalog; chat discovery reads the same file and returns exact-workspace roots. Choosing an entry and submitting Stage 1 runs installation.-Exact directory-paths and validated Create Template handoffs remain supported, while a bare ID-never resolves implicitly.+[brands_index.json](./brands_index.json) maps `brand_id → { summary, primary_color }`; refresh with `register_template.py <brand_id> --kind brand`, which rejects incomplete frontmatter, mismatched IDs, page SVGs, missing identity sections, invalid colors/provenance, and broken asset references. Stage-1 controls and chat discovery read this index only; a bare ID never resolves implicitly.diff --git a/skills/ppt-master/templates/decks/README.md b/skills/ppt-master/templates/decks/README.mdindex 44069bf3..c16d0af5 100644--- a/skills/ppt-master/templates/decks/README.md+++ b/skills/ppt-master/templates/decks/README.md@@ -1,62 +1,23 @@# Deck Templates-**Deck = a reusable solution for a recurring presentation family.** It owns an-application context together with presentation identity and reusable page-structure. The application context states which communication situations the-template serves, which audience outcomes it supports, and which narrative/page-roles commonly appear. It describes the resource; it does not decide which-pages or visible content a future presentation must retain.-A deck template is not a finished content deck, and `kind: deck` does not mean-“mirror the source PPT”. Its construction mode decides whether the system is-newly authored or materialized from validated source facts.+**Deck = a reusable solution for a recurring presentation family**: descriptive application context (which situations it serves, which outcomes it supports, which narrative/page roles commonly appear) together with presentation identity and reusable structure. It describes the resource without deciding which pages or content a future presentation must keep; a deck template is not a finished content deck, and `kind: deck` does not mean "mirror the source PPT" — the creation strategy decides whether the system is newly authored or materialized from validated facts. The shared kind and workspace model lives in the parent [`README.md`](../README.md).| Axis | Deck behavior ||---|---|-| Template kind | `deck`: descriptive application context + integrated identity + structure |-| Internal creation strategy | AI derives `standard` / `fidelity` for a new system or `mirror` for validated source-package materialization; the field is tool provenance, not a user choice |-| Application planning | Strategist automatically decides which prototypes to select, repeat, skip, or reorganize and derives the exporter behavior |-| PPTX structure | The workspace is `structured`; the derived application plan decides whether generated pages compile its structure or use it only as visual reference |+| Template kind | `deck`: application context + integrated identity + structure |+| Internal creation strategy | AI-derived `standard` / `fidelity` for a new system or `mirror` for validated source materialization; tool provenance, not a user choice |+| Application planning | Strategist decides which prototypes to select, repeat, skip, or reorganize and derives the exporter behavior |+| PPTX structure | The workspace is `structured`; the plan decides whether pages compile its structure or use it as visual reference |-The discovery source of truth is [`decks_index.json`](./decks_index.json)-(`deck_id → { summary, canvas_format, page_count, primary_color }`). This README-defines the kind and intentionally does not enumerate installed decks. The-shared kind and workspace model lives in the parent-[`README.md`](../README.md).--Index `summary` values lead with the recurring presentation family and intended-outcome. Visual tone alone is not enough to select a Deck; open its Template-Overview when application fit must be judged in detail.-----+[`decks_index.json`](./decks_index.json) (`deck_id → { summary, canvas_format, page_count, primary_color }`) is the discovery source of truth; this README enumerates no decks. Index summaries lead with the presentation family and outcome — visual tone alone never selects a Deck; open its Template Overview to judge fit.## Selection and installation-Selection follows the parent README's Default Stage-1-[`generate-pptx`](../../workflows/generate-pptx.md) template-choice contract.-Its Deck choices come only from `decks_index.json`; no-directory scan or bare-ID/style-phrase match is allowed. A supplied exact root-appears in the same selector, defaults Stage 1 to template mode, and preselects-that specific candidate only when it is the sole supplied root. Registered-exact roots are `library`; other exact roots remain-`explicit`. Choosing and confirming an entry runs the conditional-[`apply-template-workspace`](../../workflows/stages/apply-template-workspace.md)-stage, which owns path normalization, compatibility checks, installation, and-installation after Stage 1 and before Stage 2. Template-aware reading begins in final Stage 2 from the-installed project-local copy.-Quick applies a supplied exact Deck root directly and otherwise uses flat free-design. It authors the installed Master/Layout/slot contract as lockless-structured Slides unless the user explicitly requests visual-only flat use.-This file owns the Deck schema and application-context boundary. Chat discovery-reads the same index and returns exact roots; a bare ID never resolves-implicitly.-----+Selection follows the parent contract: Deck choices come only from the index (no directory scan or bare-ID/style-phrase match); a supplied exact root joins the selector and is preselected only when sole; [`apply-template-workspace`](../../workflows/stages/apply-template-workspace.md) installs it before Stage 2; Quick applies a supplied exact root directly and authors the installed Master/Layout/slot contract as lockless structured Slides unless the user explicitly requests visual-only flat use.## `design_spec.md` contract-The spec stores portable metadata plus package-owned application, identity,-and structure rules. It does not repeat generic SVG rules, spacing libraries,-font-ratio bands, or the canonical placeholder table.+Portable metadata plus package-owned application, identity, and structure rules; no generic SVG rules, spacing libraries, font-ratio bands, or the canonical placeholder table.```markdown---@@ -85,66 +46,12 @@ page_count: <N>## VII. Placeholder Overrides # omit when none```-`replication_mode` records how the workspace was produced. Create Template-derives it from the natural-language brief and source evidence; users do not-need to select or understand this field.--`Template Overview` is descriptive application context, not a style-description or future-use policy. It identifies the recurring presentation-family, intended audiences and outcomes, delivery/reading assumptions, and-representative narrative or page roles. These values may be broad when the-source supports a family of related uses, but they must be specific enough to-help Strategist understand the resource.--`Page Roster` must list every SVG and its declared Master/Layout identity, then-describe its observed or intended role, visual character, reusable slots, and-structural capacity. It must not mark pages required/optional/repeatable or-content fixed/replaceable/example-only. Strategist inspects the actual roster-and current material and decides what to use.--Every additional authored Master represents a distinct reusable design family,-not one Layout or an organizational duplicate.-----+`replication_mode` records how the workspace was produced. `Template Overview` is descriptive application context — family, intended audiences/outcomes, delivery/reading assumptions, representative roles — broad when the source supports related uses yet specific enough to help Strategist understand the resource. `Page Roster` lists every SVG with its Master/Layout identity, role, visual character, reusable slots, and capacity, never marking pages required/optional/repeatable or content fixed/replaceable/example-only. Every additional authored Master is a distinct reusable design family.## Structured SVG contract-Every SVG is a complete preview and declares one root Master and Layout.-Master/Layout fixed visuals are direct atoms. Reusable content regions are-top-level slot groups with positive bounds and exactly one compatible carrier;-zero-slot Layouts are valid. `{{...}}` is the authoring vocabulary, while-`data-pptx-placeholder*` is the native reconstruction contract.--`standard` and `fidelity` author new SVGs and a new Master/Layout/slot system.-`mirror` preserves existing source identities, parentage, assignments,-placeholder facts, and supported visuals in a new workspace without semantic-synthesis. Legacy semantic contracts are not upgraded in place; create a new-workspace through [`create-template`](../../workflows/create-template.md). A-flat directory shape alone is not a legacy signal.-----+Every SVG is a complete preview declaring one root Master and Layout; fixed visuals are direct atoms; reusable regions are top-level slot groups with positive bounds and exactly one compatible carrier; zero-slot Layouts are valid; `{{...}}` is the authoring vocabulary and `data-pptx-placeholder*` the native contract. `standard` / `fidelity` author new SVGs and structure; `mirror` preserves source identities, parentage, assignments, placeholder facts, and supported visuals without synthesis; legacy contracts are never upgraded in place, and a flat directory shape alone is not a legacy signal.## Workspace and creation-```text-<template_workspace>/-├── templates/ # design_spec.md + SVG prototypes-├── images/ # optional bitmaps; SVG href is ../images/<name>-├── icons/-│ └── imported/ # optional canonical imported vectors-└── exports/ # review evidence; ignored during template use- └── <deck_id>_template_preview.pptx-```--Library scope writes `skills/ppt-master/templates/decks/<deck_id>/` and updates-the index. Project scope uses an initialized `projects/<name>/` workspace and-does not register globally. Empty optional directories are omitted.--1. Enter [`workflows/create-template.md`](../../workflows/create-template.md), which dispatches recurring-application output with integrated identity and structure to [`create-deck.md`](../../workflows/create-template/create-deck.md).-2. Validate with `svg_quality_checker.py --template-mode`.-3. Run `template_preview_pptx.py` when review is requested and always when the roster declares multiple Masters.-4. In library scope, register with `register_template.py <id> --kind deck`.--See also [`styles/`](../styles/) for direction/method packages,-[`layouts/`](../layouts/) for structure-only packages, and-[`brands/`](../brands/) for identity-only packages.+`templates/` (spec + prototypes), optional `images/` (`../images/<name>`), optional `icons/imported/`, and `exports/<deck_id>_template_preview.pptx` as review evidence. Library scope writes `skills/ppt-master/templates/decks/<deck_id>/` and updates the index; project scope uses an initialized `projects/<name>/` root without registration. Enter [`create-template.md`](../../workflows/create-template.md) (dispatching to [`create-deck.md`](../../workflows/create-template/create-deck.md)), validate with `svg_quality_checker.py --template-mode`, run `template_preview_pptx.py` on request and always for multiple Masters, and in library scope register with `register_template.py <id> --kind deck`. See [`styles/`](../styles/), [`layouts/`](../layouts/), and [`brands/`](../brands/) for the other kinds.diff --git a/skills/ppt-master/templates/icons/README.md b/skills/ppt-master/templates/icons/README.mdindex afc0cd8e..6d74eced 100644--- a/skills/ppt-master/templates/icons/README.md+++ b/skills/ppt-master/templates/icons/README.md@@ -1,125 +1,46 @@# SVG Icon Library-This directory provides **12,027 high-quality SVG icons** across five libraries that can be directly embedded into SVG files generated by PPT Master. Default Strategist or the Quick Generate main agent chooses at most one primary library from the four stylistic libraries; the brand-logo library (`simple-icons`) is prepared as needed for real brands and may be used alone or alongside it. It is not a separate Confirm UI choice.--Upstream versions, compatibility overlays, licenses, attribution, and trademark boundaries are recorded in [THIRD_PARTY_NOTICES.md](./THIRD_PARTY_NOTICES.md).--## Libraries+**12,027 SVG icons** across five libraries, embedded directly into generated SVG. Default Strategist or the Quick main agent chooses at most one primary library from the four stylistic ones; the brand-logo library (`simple-icons`) is prepared as needed for real brands, alone or alongside it, and is never a separate Confirm UI choice. Upstream versions, licenses, attribution, and trademark boundaries: [THIRD_PARTY_NOTICES.md](./THIRD_PARTY_NOTICES.md).| Library | Style | Count | viewBox | Prefix ||---------|-------|-------|---------|--------|-| `chunk-filled` | fill · compact, chunky 16px silhouettes | 641 | primarily `0 0 16 16` | `chunk-filled/` |-| `tabler-filled` | fill · bezier-curve forms (smooth, rounded contours) | 1,055 | `0 0 24 24` | `tabler-filled/` |-| `tabler-outline` | stroke / line | 5,138 | `0 0 24 24` | `tabler-outline/` |-| `phosphor-duotone` | duotone · single color + 0.2 opacity backplate (soft depth) | 1,518 | `0 0 256 256` | `phosphor-duotone/` |-| `simple-icons` | **brand logos** (real company / product marks) — single-color silhouettes, color in via `fill` | 3,675 | `0 0 24 24` | `simple-icons/` |-----+| `chunk-filled` | fill · compact, chunky 16px silhouettes; heavy, solid | 641 | primarily `0 0 16 16` | `chunk-filled/` |+| `tabler-filled` | fill · bezier forms, smooth rounded contours; medium, approachable | 1,055 | `0 0 24 24` | `tabler-filled/` |+| `tabler-outline` | stroke / line art (default stroke-width 2); light, refined; best on screen — thin strokes weaken when printed or projected | 5,138 | `0 0 24 24` | `tabler-outline/` |+| `phosphor-duotone` | duotone · full-opacity shape plus a same-color 20% backplate; medium, layered | 1,518 | `0 0 256 256` | `phosphor-duotone/` |+| `simple-icons` | **brand logos** (real company / product marks), single-color silhouettes colored via `fill` | 3,675 | `0 0 24 24` | `simple-icons/` |## Per-project icons folder-This directory is the **global library**. The active resource owner copies chosen icons into the deck's own `<project>/icons/<lib>/` with `icon_sync.py` before SVG authoring:+This directory is the global library; the resource owner copies chosen icons into `<project>/icons/<lib>/` before SVG authoring:```bashpython3 skills/ppt-master/scripts/icon_sync.py <project_path> tabler-outline/home tabler-outline/bulb simple-icons/github```-Missing names and a single selection batch that mixes the four stylistic libraries exit non-zero; `simple-icons` may coexist for real brand marks. Once files are under `<project>/icons/`, they form the prepared project asset pool and may be combined freely with user-provided, custom, or imported icons. `finalize_svg.py --only embed-icons`, preview, validation, and native export resolve only this project-local pool.--**Custom icons**: drop your own `.svg` into `<project>/icons/<lib>/` (any `<lib>`, e.g. `custom/`) and reference it as `data-icon="<lib>/<name>"` — it embeds like any library icon.--**Imported vectors**: `create-template` reserves the project-local `imported/`-namespace. Each extracted vector lives once at-`<workspace>/icons/imported/<name>.svg` and is referenced as-`data-icon="imported/<name>"`; do not duplicate it under `templates/` or use-`imported/` as a hand-curated style library.+Missing names, or one batch mixing the four stylistic libraries, exit non-zero; `simple-icons` may coexist. Files under `<project>/icons/` form the prepared pool and combine freely with user-provided, custom, or imported icons; `finalize_svg.py --only embed-icons`, preview, validation, and native export resolve only this pool. **Custom icons**: drop `.svg` files into `<project>/icons/<lib>/` (any `<lib>`, e.g. `custom/`) and reference `data-icon="<lib>/<name>"`. **Imported vectors**: `create-template` reserves `imported/` — one copy at `<workspace>/icons/imported/<name>.svg`, referenced as `data-icon="imported/<name>"`, never duplicated under `templates/` or used as a hand-curated library.## Usage-Use placeholder syntax **during SVG generation**:-```xml-<!-- chunk-filled (compact, chunky — strong small-size legibility) --><use data-icon="chunk-filled/home" x="100" y="200" width="48" height="48" fill="#0076A8"/>--<!-- tabler-filled (rounded, organic — lifestyle/health/home tone) -->-<use data-icon="tabler-filled/home" x="100" y="200" width="48" height="48" fill="#0076A8"/>--<!-- tabler-outline (light, line-art — refined screen-only showcases) -->-<use data-icon="tabler-outline/home" x="100" y="200" width="48" height="48" fill="#0076A8"/>--<!-- phosphor-duotone (soft depth — single color renders the backplate at 20% opacity) --><use data-icon="phosphor-duotone/house" x="100" y="200" width="48" height="48" fill="#0076A8"/>--<!-- simple-icons (brand logo — used alone or alongside the deck's primary stylistic library) --><use data-icon="simple-icons/github" x="100" y="200" width="48" height="48" fill="#181717"/>```-**Attributes**:-- `data-icon` — `<library>/<icon-name>` (filename without `.svg`)-- `x`, `y` — Position-- `width`, `height` — Size (recommend 32–48px for legibility)-- `fill` — Color--`data-icon` is case-sensitive because it resolves a real filename. Bundled library directories and basenames are canonical lowercase: use `tabler-outline/award`, not `tabler-outline/Award`. Custom icons retain the exact case of their files; the resolver intentionally does not lowercase identifiers.--Every placeholder resolves only against `<project_path>/icons/`. A complete-`library/name` identifier is mandatory; bare names, abbreviated namespaces,-paths into `templates/icons/`, and unsynced bundled-library files fail instead-of falling back to another root.--`finalize_svg.py` auto-embeds all placeholders during post-processing. To run manually:--```bash-python3 scripts/svg_finalize/embed_icons.py svg_output/*.svg-```-----+`data-icon` is `<library>/<icon-name>` (filename without `.svg`), case-sensitive because it resolves a real file — bundled names are canonical lowercase (`tabler-outline/award`), custom icons keep their file case; `x`, `y` position; `width`, `height` size (32–48px recommended); `fill` color. A complete `library/name` identifier is mandatory: bare names, abbreviated namespaces, paths into `templates/icons/`, and unsynced bundled files fail rather than fall back. `finalize_svg.py` embeds every placeholder during post-processing (`scripts/svg_finalize/embed_icons.py svg_output/*.svg` runs it manually).## Searching for Icons-For a known basename, run `icon_sync.py` directly; it copies and validates without a per-file precheck.--For an uncertain basename, search only the chosen stylistic library; use `simple-icons` only for a real brand mark.--**Hard rule**: search by the drawable object, not the abstract concept. These libraries store things that can be drawn — `bulb`, `target`, `trending-up`, `alert-triangle` — so concept words such as `idea`, `goal`, `growth`, `warning`, or `innovation` return nothing in most of them. Translate the semantic into an object first, then search.--**Reference — not a constraint**: one concept usually has several valid objects. Which one fits is a per-deck judgment of page register and visual style, not a fixed mapping.--**Hard rule**: basenames are not portable across the four stylistic libraries; verify inside the selected one. `alert-*` exists in the tabler libraries but not in `phosphor-duotone`, which uses `warning-*`; `arrow-trend-*` exists in `chunk-filled`, while `tabler-outline` uses `trending-*`.+For a known basename run `icon_sync.py` directly; for an uncertain one search only the chosen stylistic library (`simple-icons` only for a real brand mark):```bashrg --files "skills/ppt-master/templates/icons/tabler-outline" -g '*chart*.svg'rg --files "skills/ppt-master/templates/icons/simple-icons" -g '*github*.svg'```-Do not load a full index or enumerate broad keyword families. Re-pick from the narrow result and rerun the final batch until clean; never switch stylistic libraries for a missing generic icon.--**Empty result** → translate the semantic into a different drawable object and search the same library again. When several translations stay empty, that semantic has no fit in the selected library: let another carrier take it — a chart, typography, or a shape — rather than forcing a loose icon. Widening the keyword family is not the fallback.-----+**Hard rule**: search by the drawable object, not the abstract concept — these libraries store things that can be drawn (`bulb`, `target`, `trending-up`, `alert-triangle`), so `idea`, `goal`, `growth`, `warning`, `innovation` return nothing in most of them; translate the semantic into an object first. **Reference — not a constraint**: one concept usually has several valid objects, chosen per deck from page register and visual style. **Hard rule**: basenames are not portable across the four stylistic libraries — `alert-*` exists in the tabler libraries but `phosphor-duotone` uses `warning-*`; `arrow-trend-*` in `chunk-filled` is `trending-*` in `tabler-outline`. Do not load a full index or enumerate broad keyword families; re-pick from the narrow result and rerun the batch until clean; never switch stylistic libraries for a missing generic icon. An empty result → try another drawable translation in the same library; when several stay empty, let another carrier (chart, typography, shape) take that semantic rather than forcing a loose icon.## Style Rules-**No default library — actively choose based on the deck's visual needs.** Read the source material first, then pick the library whose visual character best serves the presentation. Each library has a distinct visual personality:--- **`chunk-filled`** — **fill** style, designed as compact 16px silhouettes. Bold forms may combine rectilinear and curved geometry while staying highly legible at small sizes. Visual weight: heavy, solid, compact.-- **`tabler-filled`** — **fill** style, built from bezier curves and arcs (C/A). Smooth, rounded, organic contours; warmer and softer than `chunk-filled`. Visual weight: medium, approachable.-- **`tabler-outline`** — **stroke** style (line art, default stroke-width 2). Airy, refined, lightweight; uses negative space. Visual weight: light, elegant. Best for screen-only viewing since thin strokes may become hard to read when printed or projected.-- **`phosphor-duotone`** — **duotone** style; main shape at full opacity plus a backplate of the same color at 20% opacity, producing a soft sense of depth. Visual weight: medium, layered, contemporary.--> **Two axes to consider when choosing**:-> 1. **Geometry**: compact silhouettes (`chunk-filled`) vs. rounded curves (`tabler-filled` / `phosphor-duotone`) vs. open strokes (`tabler-outline`)-> 2. **Visual weight**: heavy solid (`chunk-filled`) → medium solid (`tabler-filled`) → medium layered (`phosphor-duotone`) → light stroke (`tabler-outline`)--**At most one primary bundled stylistic library per deck selection.** When generic icons are useful, pick one of `chunk-filled` / `tabler-filled` / `tabler-outline` / `phosphor-duotone` (home, chart, users, etc.). If it lacks an exact icon, find the closest available alternative within that library instead of selecting from another bundled stylistic library. This is a catalog-selection rule, not a prohibition on combining assets that already exist in the project's `icons/` directory.--**Brand-logo exception (`simple-icons`).** `simple-icons` is **not a stylistic library**, does not participate in the "one library" rule, and is not presented as a user-facing library choice. Its job is brand recognition — Slack's purple, GitHub's cat, AWS's color — which is intentionally heterogeneous. Prepare it **alone or alongside** the chosen stylistic library only when actual content needs a company / product / service brand mark. Do **not** reach for it as a substitute when the chosen stylistic library lacks a generic icon.--| Use `simple-icons` for | Do NOT use `simple-icons` for |-|------------------------|-------------------------------|-| Customer / partner / ecosystem logos on a "trusted by" page | Generic concepts (home, chart, settings, etc.) |-| Tech stack icons on architecture / integration diagrams | Replacing a missing icon in `chunk-filled` / `tabler-*` / `phosphor-duotone` |-| Social media handles in a footer | Decorative / illustrative purposes |--⚠️ During bundled selection, choose generic icons from only one of the four **stylistic** libraries. Prepare `simple-icons` independently when real brand marks are needed. Project-local assets are already prepared material and are not subject to a runtime mixing ban.+**No default library — choose from the deck's visual needs** after reading the source: compact silhouettes (`chunk-filled`) vs rounded curves (`tabler-filled` / `phosphor-duotone`) vs open strokes (`tabler-outline`); visual weight heavy solid → medium solid → medium layered → light stroke. **At most one primary bundled stylistic library per deck selection**: when it lacks an exact icon, use the closest alternative within it rather than another bundled library — a catalog-selection rule, not a ban on combining assets already in the project's `icons/`. **Brand-logo exception**: `simple-icons` is not a stylistic library and does not count toward that rule; its job is brand recognition (Slack's purple, GitHub's cat), intentionally heterogeneous — prepare it only when content needs a company / product / service mark (customer or partner logos, tech-stack icons in architecture diagrams, social handles in a footer), never as a substitute for a missing generic icon or for decoration.diff --git a/skills/ppt-master/templates/layouts/README.md b/skills/ppt-master/templates/layouts/README.mdindex b6fb85b7..25db0233 100644--- a/skills/ppt-master/templates/layouts/README.md+++ b/skills/ppt-master/templates/layouts/README.md@@ -1,78 +1,23 @@# Layout Templates-**Layout = a structure-only reusable template bundle.** It owns canvas,-Master/Layout structure, page types, slot geometry, semantic text roles,-alignment/wrapping/capacity behavior, and the SVG roster. It does not own-brand color, typeface/weight identity, the final resolved type scale, logo,-voice, or icon style. Those identity decisions come from an explicit-brand/deck source or from the Strategist confirmation stage.--A layout may describe the content shapes and delivery conditions its geometry-can support. It must not own a communication objective, audience outcome,-scenario-specific narrative sequence, fixed boilerplate, or example content-that downstream generation is expected to preserve. Those application rules-belong to a Deck. A structurally useful “board update” page can remain a-Layout; a board-update sequence with required decision, risk, and action roles-is a Deck.--Neutral colors, safe fonts, and provisional sizes may appear in SVG prototypes-so the structure is reviewable. They are preview values, not a locked identity-segment or final type scale. The reusable rule is the role hierarchy and its-spatial behavior. When the workspace is used, Strategist inspects the actual-prototypes and current content, decides how much structure to reuse, and writes-the internal exporter plan automatically.+**Layout = a structure-only reusable template bundle**: canvas, Master/Layout structure, page types, slot geometry, semantic text roles, alignment/wrapping/capacity behavior, and the SVG roster — no brand color, typeface/weight identity, final type scale, logo, voice, or icon style (those come from a Brand/Deck or the confirmation stage). A layout may describe the content shapes and delivery conditions its geometry supports but never owns a communication objective, audience outcome, narrative sequence, boilerplate, or example content downstream must preserve — a structurally useful "board update" page stays a Layout; a board-update sequence with required decision, risk, and action roles is a Deck. Neutral colors, safe fonts, and provisional sizes in prototypes are preview values, not identity or a locked scale; Strategist inspects the prototypes and content, decides how much structure to reuse, and writes the exporter plan automatically. The shared kind and workspace model lives in the parent [`README.md`](../README.md).| Axis | Layout behavior ||---|---|| Template kind | `layout`: structure only |-| Internal creation strategy | AI derives `standard` / `fidelity` for a new system or `mirror` for validated source-package materialization; the field is tool provenance, not a user choice |-| Application planning | Strategist automatically decides literal, structural, or style-only use and derives any strict/adaptive exporter value |-| PPTX structure | The workspace is `structured`; the derived application plan decides whether generated pages compile its structure or use it only as visual reference |--The discovery source of truth is [`layouts_index.json`](./layouts_index.json)-(`layout_id → { summary, canvas_format, page_count, page_types }`). This README-defines the kind and intentionally does not enumerate installed layouts. The-shared kind and workspace model lives in the parent-[`README.md`](../README.md).+| Internal creation strategy | AI-derived `standard` / `fidelity` for a new system or `mirror` for validated source materialization; tool provenance, not a user choice — Layout mirror additionally requires a brand-neutral, application-neutral source (otherwise author through `standard` / `fidelity` or create a Deck; removing rules is never mirror) |+| Application planning | Strategist decides literal, structural, or style-only use and any strict/adaptive value |+| PPTX structure | The workspace is `structured`; the plan decides whether pages compile its structure or use it as visual reference |-Layout mirror has one additional eligibility rule: the validated source-contract must already be brand-neutral and application-neutral. A source-outside that boundary can become a Layout only through `standard` or-`fidelity`, which deliberately authors a new neutral system. If its identity or-application rules must remain literal, create a Deck instead. Removing either-kind of rule is never a mirror operation.-----+[`layouts_index.json`](./layouts_index.json) (`layout_id → { summary, canvas_format, page_count, page_types }`) is the discovery source of truth; this README defines the kind and enumerates no layouts.## Selection and identity boundary-Selection follows the parent README's Default Stage-1-[`generate-pptx`](../../workflows/generate-pptx.md) template-choice contract.-Its Layout choices come only from `layouts_index.json`; no-directory scan or bare-ID/style-phrase match is allowed. A supplied exact root-appears in the same selector, defaults Stage 1 to template mode, and preselects-that specific candidate only when it is the sole supplied root. Registered-exact roots are `library`; other exact roots remain `explicit`.-Choosing and confirming an entry runs the conditional-[`apply-template-workspace`](../../workflows/stages/apply-template-workspace.md)-stage, which owns path normalization, compatibility checks, installation, and-installation after Stage 1 and before Stage 2. Template-aware reading begins in final Stage 2 from the-installed project-local copy.-Quick applies a supplied exact Layout root directly and otherwise uses flat free-design. It authors the installed Master/Layout/slot contract as lockless-structured Slides unless the user explicitly requests visual-only flat use.-This file owns the Layout schema and its identity/application boundary. Chat-discovery reads the same index and returns exact roots; a bare ID never resolves-implicitly.-----+Selection follows the parent contract: Layout choices come only from the index (no directory scan or bare-ID/style-phrase match); a supplied exact root joins the selector and is preselected only when sole; [`apply-template-workspace`](../../workflows/stages/apply-template-workspace.md) installs it before Stage 2; Quick applies a supplied exact root directly and authors the installed Master/Layout/slot contract as lockless structured Slides unless the user explicitly requests visual-only flat use.## `design_spec.md` contract-The spec stores portable structural metadata plus rules unique to this layout.-It omits the deck-only Template Overview/application contract and every-identity section. The frontmatter `summary` carries the concise selection-context.+Portable structural metadata plus rules unique to this layout; no Template Overview, application contract, or identity section — the frontmatter `summary` carries selection context.```markdown---@@ -97,66 +42,12 @@ page_types: [cover, toc, chapter, content, ending]## VII. Placeholder Overrides # omit when none```-`replication_mode` records how the workspace was produced. Create Template-derives it from the natural-language brief and source evidence; users do not-need to select or understand this field.--`Signature Design Elements` describes only reusable structure: grids, zones,-image behavior, density rhythm, semantic text roles, alignment/wrapping/-capacity behavior, and slot conventions. It must not introduce a brand-palette, typeface identity, final type scale, communication objective, or-required narrative sequence. `Page Roster` lists every SVG with its Layout-key, PowerPoint picker name, supported content shape, and slot behavior.-----+`replication_mode` records how the workspace was produced. `Signature Design Elements` describes only reusable structure (grids, zones, image behavior, density rhythm, text roles, alignment/wrapping/capacity, slot conventions) and introduces no palette, typeface identity, type scale, objective, or narrative sequence; `Page Roster` lists every SVG with Layout key, picker name, content shape, and slot behavior.## Structured SVG and slot contract-Every SVG is a complete preview and declares one root Master and Layout.-Master/Layout fixed visuals are direct atoms. A reusable slot is a top-level-`<g id>` with positive design-zone bounds and exactly one compatible carrier;-zero-slot Layouts are valid. A typed `picture`, `chart`, or `table` slot does-not by itself promise an inserted picture or native data object: the generated-Slide supplies its content, and Chart/Table native replacement remains an-explicit export choice.--Use canonical `{{PLACEHOLDER}}` names where they fit. A layout with intentional-vocabulary overrides declares a `placeholders:` map in frontmatter. Full rules:-[`template-designer.md`](../../references/template-designer.md#4-placeholder-reference-canonical-convention-overridable-per-template).--`standard` and `fidelity` author new SVGs and a new Master/Layout/slot system.-`mirror` preserves existing source identities, parentage, assignments,-placeholder facts, and supported visuals in a new workspace without semantic-synthesis. Legacy semantic contracts are not upgraded in place; create a new-workspace through [`create-template`](../../workflows/create-template.md). A-flat directory shape alone is not a legacy signal.-----+Every SVG is a complete preview declaring one root Master and Layout; fixed visuals are direct atoms; a slot is a top-level `<g id>` with positive design-zone bounds and exactly one compatible carrier; zero-slot Layouts are valid; a typed `picture` / `chart` / `table` slot promises no inserted picture or native object — the generated Slide supplies content and native replacement stays an explicit export choice. Use canonical `{{PLACEHOLDER}}` names ([`template-designer.md`](../../references/template-designer.md#4-placeholder-reference-canonical-convention-overridable-per-template)) with a `placeholders:` frontmatter map for overrides. `standard` / `fidelity` author new SVGs and structure; `mirror` preserves source identities, parentage, assignments, placeholder facts, and supported visuals without synthesis; legacy contracts are never upgraded in place, and a flat directory shape alone is not a legacy signal.## Workspace and creation-```text-<template_workspace>/-├── templates/ # design_spec.md + SVG prototypes-├── images/ # optional bitmaps; SVG href is ../images/<name>-├── icons/-│ └── imported/ # optional canonical imported vectors-└── exports/ # review evidence; ignored during template use- └── <layout_id>_template_preview.pptx-```--Library scope writes `skills/ppt-master/templates/layouts/<layout_id>/` and-updates the index. Project scope uses an initialized `projects/<name>/`-workspace and does not register globally. Empty optional directories are-omitted.--1. Enter [`workflows/create-template.md`](../../workflows/create-template.md), which dispatches structure-only output to [`create-layout.md`](../../workflows/create-template/create-layout.md).-2. Validate with `svg_quality_checker.py --template-mode`.-3. Run `template_preview_pptx.py` when review is requested and always when the roster declares multiple Masters.-4. In library scope, register with `register_template.py <id> --kind layout`.--General SVG/PPT rules remain authoritative in-[`shared-standards-core.md`](../../references/shared-standards-core.md) and-[`pptx-structure-interface.md`](../../references/pptx-structure-interface.md).-See [`styles/`](../styles/) when reusable method and visual direction should be-combined with this structure without becoming identity truth.+`templates/` (spec + prototypes), optional `images/` (`../images/<name>`), optional `icons/imported/`, and `exports/<layout_id>_template_preview.pptx` as review evidence. Library scope writes `skills/ppt-master/templates/layouts/<layout_id>/` and updates the index; project scope uses an initialized `projects/<name>/` root without registration. Enter [`create-template.md`](../../workflows/create-template.md) (dispatching to [`create-layout.md`](../../workflows/create-template/create-layout.md)), validate with `svg_quality_checker.py --template-mode`, run `template_preview_pptx.py` on request and always for multiple Masters, and in library scope register with `register_template.py <id> --kind layout`. General SVG/PPT rules stay in [`shared-standards-core.md`](../../references/shared-standards-core.md) and [`pptx-structure-interface.md`](../../references/pptx-structure-interface.md); see [`styles/`](../styles/) to combine method and direction with this structure.diff --git a/skills/ppt-master/templates/styles/README.md b/skills/ppt-master/templates/styles/README.mdindex fa6caef0..a298f8fa 100644--- a/skills/ppt-master/templates/styles/README.md+++ b/skills/ppt-master/templates/styles/README.md@@ -1,100 +1,31 @@# Style Workspaces-**Style = a roster-free reusable communication method plus coordinated design defaults.** It can carry argument flow, page-role vocabulary, evidence and data-expression discipline, visual-system defaults, image/icon direction, and additional review focus. It does not own a current project's communication contract, reusable brand identity, page geometry, SVG prototypes, or a recurring application contract.--Style is a fourth independent template kind alongside [`brands/`](../brands/), [`layouts/`](../layouts/), and [`decks/`](../decks/). It is not a replacement for the mode or visual-style catalogs.+**Style = a roster-free reusable communication method plus coordinated design defaults**: argument flow, page-role vocabulary, evidence and data-expression discipline, visual-system defaults, image/icon direction, and review focus. It owns no current-project communication contract, brand identity, page geometry, SVG prototypes, or application contract, and does not replace the mode or visual-style catalogs. The shared kind and workspace model lives in the parent [`README.md`](../README.md).## Axis Separation-| Axis | Meaning |-|---|---|-| Template `kind: style` | A portable workspace that coordinates reusable method and non-binding design defaults |-| Final Stage-2 `mode` | The current deck's confirmed narrative and persuasion skeleton |-| Final Stage-2 `visual_style` | The current deck's confirmed shape, composition, whitespace, typography-character, and texture lock |-| Internal `template_reuse_scope: style` | A flat current-project export plan that reuses no Master/Layout structure |--These names are separate contracts. Style-only and Style + Brand naturally produce a flat application plan, while a Style installed alongside a Layout or Deck may use structured reuse. `kind: style` therefore never forces the internal reuse scope when another workspace supplies structure.+`kind: style` (a portable workspace of method and non-binding defaults), final Stage-2 `mode` (the deck's confirmed narrative skeleton), final Stage-2 `visual_style` (the deck's confirmed composition and texture lock), and internal `template_reuse_scope: style` (a flat export plan reusing no structure) are separate contracts. Style-only and Style + Brand produce a flat plan; a Style beside a Layout or Deck may use structured reuse — `kind: style` never forces the reuse scope when another workspace supplies structure.## Selection, Precedence, and Installation-Selection follows the parent README's Default Stage-1-[`generate-pptx`](../../workflows/generate-pptx.md) template-choice contract.-Its Style choices come only from `styles_index.json`; no-directory scan or bare-name match is allowed. A supplied exact root appears in-the same selector, defaults Stage 1 to template mode, and preselects that-specific candidate only when it is the sole supplied root. A-consulting label or visual description remains a brief and does not activate-this workspace. A non-free confirmation runs the-common installation stage after Stage 1 and before Stage 2; template-aware reading begins-in final Stage 2 from the project-local copy. Quick applies a supplied exact-Style root directly and otherwise uses free design; its current agent reads the-installed copy before authoring flat pages.+Selection follows the parent contract: Style choices come only from `styles_index.json`; a supplied exact root joins the selector and is preselected only when sole; a consulting label or visual description is a brief and never activates a workspace; Quick applies a supplied exact root directly and reads the installed copy before authoring flat pages.| Decision | Precedence ||---|---|-| Current project communication contract, mode, visual style, palette, typography, images, and icons | Latest explicit user instruction and confirmed project values |-| Exact identity values | Brand, then Deck identity; both override overlapping Style fallback values |-| Reusable communication method and evidence discipline | Style, applied only where compatible with the current project contract |-| Reusable structure | Layout when present, otherwise Deck; Style never supplies structure |-| Recurring application context | Deck, subordinate to the current project's Stage-1 communication contract |+| Current contract, mode, visual style, palette, typography, images, icons | Latest explicit user instruction and confirmed project values |+| Exact identity values | Brand, then Deck; both override overlapping Style fallbacks |+| Reusable method and evidence discipline | Style, where compatible with the current contract |+| Reusable structure | Layout, otherwise Deck; Style never supplies structure |+| Recurring application context | Deck, subordinate to the Stage-1 contract |-Style fallback values seed the final Stage-2 solution when the corresponding decision remains open. They are not identity truth and do not bypass confirmation. If a Style method and a Deck application contract materially conflict, surface the mismatch; do not silently weaken either one.+Style fallbacks seed the Stage-2 solution when a decision is open; they are not identity truth and never bypass confirmation. Surface a material Style/Deck conflict rather than weakening either.## `design_spec.md` Contract-The frontmatter is intentionally small:--```markdown-----style_id: <slug>-kind: style-summary: <one-line reusable method and design-default fit>-keywords: [<three-to-five discovery tags>]-----```--The seven required body sections are:--| § | Title | Owned content |-|---|---|---|-| I | Style Overview | Display name, best fit, reusable intent, and provenance |-| II | Communication Method | Argument flow, page-message discipline, claim treatment, and an optional mode seed |-| III | Page Role Vocabulary | Semantic roles with communication jobs, evidence obligations, and non-geometric composition tendencies |-| IV | Evidence & Data Expression | Claim/evidence trace, chart/table/source behavior, and native-editability preference |-| V | Visual System Defaults | Composition, density, decoration, color behavior, typography character, and optional visual-style/fallback seeds |-| VI | Image & Icon Direction | Rendering, usage, framing, and icon treatment without asset selection |-| VII | Review Focus | Extra checks used only after the user explicitly activates visual review |--`Fallback Color Scheme` and `Fallback Typography` are optional subsections under §V. They remain lower-priority defaults, never Brand identity. A preset mode, visual style, or image rendering resolves to a real ID in its matching catalog. A custom seed includes its behavior prose and lists only catalog references actually used as comma-separated IDs; use `Mode References`, `Visual Style References`, or `Image Rendering References` respectively.+Frontmatter: `style_id`, `kind: style`, `summary`, `keywords` (three to five) only. Required body sections: I Style Overview (name, best fit, intent, provenance); II Communication Method (argument flow, page-message discipline, claim treatment, optional mode seed); III Page Role Vocabulary (roles with jobs, evidence obligations, non-geometric tendencies); IV Evidence & Data Expression; V Visual System Defaults (composition, density, decoration, color behavior, typography character, optional visual-style seed and `Fallback Color Scheme` / `Fallback Typography` subsections — lower-priority defaults, never identity); VI Image & Icon Direction (rendering, usage, framing, icon treatment without asset selection); VII Review Focus (checks used only after the user activates visual review, containing exactly one non-localized `<!-- visual-review-trigger: explicit-user-only -->` marker). A preset seed resolves to a real catalog ID; a custom seed carries behavior prose and lists only the catalog references it uses (`Mode References`, `Visual Style References`, `Image Rendering References`).-Section VII contains exactly one non-localized `<!-- visual-review-trigger: explicit-user-only -->` marker. Its surrounding explanation and checks may use the user's language; the marker lets validation enforce that Review Focus is advisory and never activates visual review.--**Forbidden — identity, structure, or application ownership**:--- Do not write `primary_color`, official color provenance, Logo, Voice & Tone, Icon Style, canvas fields, page count/types, `replication_mode`, `native_structure_mode`, or placeholder fields.-- Do not write Template Overview, Signature Design Elements, Page Roster, SVG filenames, Master/Layout identities, slot geometry, fixed page sequences, or reusable application audience/outcome rules.-- Do not write the current project's audience, objective, outcome, core message, delivery context, artifact afterlife, content outline, page assignments, icon inventory, or image-resource list.+**Forbidden — identity, structure, or application ownership**: no `primary_color`, color provenance, Logo, Voice & Tone, Icon Style, canvas fields, page count/types, `replication_mode`, `native_structure_mode`, or placeholder fields; no Template Overview, Signature Design Elements, Page Roster, SVG filenames, Master/Layout identities, slot geometry, fixed sequences, or application audience/outcome rules; no current-project audience, objective, outcome, core message, delivery context, afterlife, outline, page assignments, icon inventory, or image list.## Workspace and Creation-Every Style workspace contains one portable source file and no page or asset payload:--```text-<template_workspace>/-└── templates/- └── design_spec.md-```--Do not create empty `images/`, `icons/`, or `exports/` directories. Existing initialized-project scaffolding may remain untouched but is not Style output.--1. Enter [`workflows/create-template.md`](../../workflows/create-template.md), which dispatches method/default output to [`create-style.md`](../../workflows/create-template/create-style.md).-2. Validate with `svg_quality_checker.py --template-mode`.-3. In library scope, register with `register_template.py <id> --kind style`.--The discovery source of truth is [`styles_index.json`](./styles_index.json).-Each entry is `style_id → { summary, keywords }`; the index never duplicates-the full method or defaults. The Default Stage-1 template controls read this-file as their complete registered-Style catalog, and chat discovery returns-exact roots from the same entries. Choosing an entry and submitting Stage 1-activates installation;-reading a name in ordinary prose does not.+A Style workspace is one file — `<template_workspace>/templates/design_spec.md` — with no page or asset payload; never create empty `images/`, `icons/`, or `exports/`. Enter [`create-template.md`](../../workflows/create-template.md), which dispatches to [`create-style.md`](../../workflows/create-template/create-style.md); validate with `svg_quality_checker.py --template-mode`; in library scope register with `register_template.py <id> --kind style`. [`styles_index.json`](./styles_index.json) maps `style_id → { summary, keywords }` and is the only discovery source; reading a name in prose never activates a workspace.