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
docs(brand): unify brand and layout landing path; fuse on combined input
hugohe353742e6e0a55
diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.mdindex 0183d667..0d891189 100644--- a/skills/ppt-master/SKILL.md+++ b/skills/ppt-master/SKILL.md@@ -184,26 +184,53 @@ cp ${TEMPLATE_DIR}/*.jpg <project_path>/images/ 2>/dev/null || true| User input contains | Step 3 brand action ||---|---|-| An explicit path to a brand directory (e.g. `skills/ppt-master/templates/brands/acme/`, or any path that resolves to a directory whose `design_spec.md` declares `kind: brand`) | Copy `design_spec.md` + `logo.<ext>` + any present asset subdirectories into `<project_path>/brand/` |+| An explicit path to a brand directory (e.g. `skills/ppt-master/templates/brands/acme/`, or any path that resolves to a directory whose `design_spec.md` declares `kind: brand`) | Copy `design_spec.md` + logo files + any present asset subdirectories into `<project_path>/templates/` || Bare brand names ("use acme brand", "用 acme 品牌"), brand mentions without a path, or silence | Skip — same mechanical rule as layout templates: bare names never trigger |-A brand path and a layout template path may both be supplied in the same message. When both are present, **brand identity tokens (color / typography / logo / voice) override the layout template's defaults**, while the layout template's page roster and structural design stay intact.-```bashBRAND_DIR=<user-supplied brand path>-mkdir -p <project_path>/brand-cp ${BRAND_DIR}/design_spec.md <project_path>/brand/-cp ${BRAND_DIR}/logo.* <project_path>/brand/ 2>/dev/null || true-[ -d ${BRAND_DIR}/images ] && cp -r ${BRAND_DIR}/images <project_path>/brand/-[ -d ${BRAND_DIR}/illustrations ] && cp -r ${BRAND_DIR}/illustrations <project_path>/brand/-[ -d ${BRAND_DIR}/icons ] && cp -r ${BRAND_DIR}/icons <project_path>/brand/+cp ${BRAND_DIR}/design_spec.md <project_path>/templates/+cp ${BRAND_DIR}/*.svg <project_path>/templates/ 2>/dev/null || true # brand logo SVG files+cp ${BRAND_DIR}/*.png <project_path>/templates/ 2>/dev/null || true # brand logo raster files+[ -d ${BRAND_DIR}/images ] && cp -r ${BRAND_DIR}/images <project_path>/templates/+[ -d ${BRAND_DIR}/illustrations ] && cp -r ${BRAND_DIR}/illustrations <project_path>/templates/+[ -d ${BRAND_DIR}/icons ] && cp -r ${BRAND_DIR}/icons <project_path>/templates/```+> Brand and layout outputs share `<project_path>/templates/` because they are the same kind of artifact — a reference bundle that Strategist treats as truth. Downstream code never needs to distinguish them.+> "What brands exist?" is out-of-band Q&A — answer by listing entries from `brands_index.json` together with their paths. Listing alone does not advance the pipeline; the user still has to send a path to trigger the Step 3 copy.> To create a new brand, read `workflows/create-brand.md`.-**✅ Checkpoint — Default path proceeds to Step 4 without user interaction. If the user's input contains an explicit template directory path and/or an explicit brand directory path, those directories are copied before advancing.**+#### Brand + layout combined input++A brand path and a layout template path may both be supplied in the same message. When both are present, Step 3 **fuses them into a single `design_spec.md`** inside `<project_path>/templates/` instead of leaving two specs side by side. Field-level precedence is fixed (no per-deck prompting):++| Field group | Source |+|---|---|+| Color (primary / secondary / accents / text / bg) | **brand** |+| Typography (font family) | **brand** |+| Logo | **brand** (if absent, fall back to layout's logo) |+| Voice & tone | **brand** |+| Icon style preference | **brand** |+| Canvas (size / viewBox / margins) | **layout** |+| Page roster + signature visual elements (top bar / underline / decorative motifs) | **layout** |+| Font-size hierarchy (H1 / H2 / body / data / label) | **layout** |+| Spacing, grid, layout patterns | **layout** |+| SVG technical constraints | **layout** |+| Placeholder set | **layout** |++Action: AI reads `${LAYOUT_DIR}/design_spec.md` and `${BRAND_DIR}/design_spec.md`, composes one fused `design_spec.md` using the table above, writes it to `<project_path>/templates/design_spec.md`. SVG page files come from `${LAYOUT_DIR}`; brand logos and asset subdirectories from `${BRAND_DIR}`. The fused spec carries a one-line `> Fused from: layout=<layout_id>, brand=<brand_id>` provenance note under its H1.++**Conflict gates** — clarify with the user only in these two cases:++1. **Brand has no logo, layout has one.** Ask: "your brand has no bundled logo; use the layout's logo, or leave the deck logo-less?"+2. **Layout is itself a branded template (e.g. `招商银行`, `重庆大学`, `中汽研_*`, `中国电建_*`) and the supplied brand is different.** Ask: "this layout carries `<layout's own brand>` identity, which conflicts with the `<supplied brand>` you provided — confirm you want brand identity from `<supplied brand>` and only the page structure from `<layout>`?"++If neither gate trips, fusion proceeds silently and Step 3 advances.++**✅ Checkpoint — Default path proceeds to Step 4 without user interaction. If the user's input contains an explicit template directory path and/or an explicit brand directory path, those directories are copied (or fused) into `<project_path>/templates/` before advancing.**---diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.mdindex 360e0e50..026aa164 100644--- a/skills/ppt-master/references/strategist.md+++ b/skills/ppt-master/references/strategist.md@@ -88,9 +88,9 @@ Accept user combinations and one-off coinages ("Scandinavian + slight industrial### e. Color Scheme Recommendation-**Hard rule**: User / brand / template colors are truth. If the user has specified colors (HEX, brand colors, or natural-language directives like "use blue as primary"), a brand was loaded at Step 3 via an explicit path (`<project_path>/brand/design_spec.md`), or a layout template was loaded with its own theme colors, lock those directly and skip the recommendation table. Do not adjust them to fit any palette or industry default. Only when no color signal exists from user, brand, or template do you proactively propose a scheme below.+**Hard rule**: User / template colors are truth. If the user has specified colors (HEX, brand colors, or natural-language directives like "use blue as primary"), or a template was loaded at Step 3 via an explicit path (`<project_path>/templates/design_spec.md`), lock those directly and skip the recommendation table. Do not adjust them to fit any palette or industry default. Only when no color signal exists from user or template do you proactively propose a scheme below.-> **Precedence when multiple sources are present**: explicit user override > brand > layout template defaults. Brand identity tokens (primary / secondary / accent / text / bg) override layout template defaults; the layout template's page structure stays intact.+> Step 3 already collapses brand and layout inputs into one fused `design_spec.md`; this layer reads from that single source and does not need to re-resolve brand vs layout precedence.Proactively provide a color scheme (HEX values) based on content characteristics and industry.@@ -165,7 +165,7 @@ See [`../templates/icons/README.md`](../templates/icons/README.md) for the curre**Mandatory**: propose **two** combinations to the user — one concord (safe), one contrast (with tension). Do not default to "title = body, same font" without explicit user request.-> **Brand precedence**: when a brand was loaded at Step 3 via an explicit path and declares `title` / `body` font stacks in `<project_path>/brand/design_spec.md §III Typography`, lock those directly and skip the two-combination presentation. Same precedence as e. — user override > brand > layout template defaults.+> **Template precedence**: when a template was loaded at Step 3 via an explicit path and declares `title` / `body` font stacks in `<project_path>/templates/design_spec.md §III Typography` / §IV (or whichever heading the fused spec uses), lock those directly and skip the two-combination presentation. Same precedence as e. — user override > template values.**Cross-platform pre-installed reference**:diff --git a/skills/ppt-master/templates/README.md b/skills/ppt-master/templates/README.mdindex c10a8c06..e68d32cb 100644--- a/skills/ppt-master/templates/README.md+++ b/skills/ppt-master/templates/README.md@@ -23,7 +23,7 @@ The `layouts/` directory contains pre-built page layout templates organized by d## Brand Identity Presets-The `brands/` directory holds brand-only templates: identity bundles (color / typography / logo / voice / icon style) without an SVG page roster. Brands follow the **same explicit-path trigger rule as layout templates** — at SKILL.md Step 3 the user supplies the brand directory path to apply it; bare brand names never trigger. Brands and layout templates may be applied together; brand identity overrides layout-template defaults while the template's page roster stays intact.+The `brands/` directory holds brand-only templates: identity bundles (color / typography / logo / voice / icon style) without an SVG page roster. Brands follow the **same explicit-path trigger rule as layout templates** — at SKILL.md Step 3 the user supplies the brand directory path to apply it; bare brand names never trigger. Both layout and brand inputs land in the same project directory (`<project_path>/templates/`). When supplied together, Step 3 fuses them into a single `design_spec.md` (brand wins on identity tokens, layout wins on page structure) — see `SKILL.md` Step 3 for the precedence table.A brand is structurally a layout template minus its page roster. Use a brand when the user wants identity locking with free page layout; use a layout template when fixed page structures are also required.diff --git a/skills/ppt-master/templates/brands/README.md b/skills/ppt-master/templates/brands/README.mdindex d42f15c0..d75c5629 100644--- a/skills/ppt-master/templates/brands/README.md+++ b/skills/ppt-master/templates/brands/README.md@@ -4,13 +4,13 @@ This directory holds **brand-only templates**: identity bundles (colors / typogr## How brands are consumed-Brand application follows the **same explicit-path rule as layout templates** at SKILL.md Step 3:+Brand application follows the **same explicit-path rule as layout templates** at SKILL.md Step 3, and lands in the **same project directory** (`<project_path>/templates/`) — brands and layouts are the same kind of artifact from the downstream's point of view:| User input at SKILL.md Step 3 | Behavior ||---|---|-| An explicit brand directory path (e.g. `templates/brands/acme/`) | Copy `design_spec.md` + `logo.<ext>` + any present asset subdirectories into `<project_path>/brand/`; Strategist locks color / typography / logo / voice as truth |+| An explicit brand directory path (e.g. `templates/brands/acme/`) | Copy `design_spec.md` + logo files + any present asset subdirectories into `<project_path>/templates/`; Strategist reads it as a normal `design_spec.md` || Bare brand name only ("use acme brand"), brand mention without path, or silence | Skip — same mechanical rule as layout templates: bare names never trigger |-| Both a brand path and a layout template path supplied | Both apply; brand identity overrides layout-template defaults, layout template's page roster stays intact |+| Both a brand path and a layout template path supplied | Step 3 fuses the two into one `design_spec.md` (brand wins on color / typography / logo / voice; layout wins on canvas / page roster / spacing / font-size hierarchy) and writes it to `<project_path>/templates/`. See `SKILL.md` Step 3 for the field-precedence table and the two conflict gates that may surface a clarifying question |`brands_index.json` is discovery-only; listing brands never advances the pipeline.diff --git a/skills/ppt-master/workflows/create-brand.md b/skills/ppt-master/workflows/create-brand.mdindex b7f4197c..99a673fb 100644--- a/skills/ppt-master/workflows/create-brand.md+++ b/skills/ppt-master/workflows/create-brand.md@@ -196,7 +196,7 @@ Emit the confirmation card:How to use in a project:- Include the brand directory path in your initial Step 3 input — e.g. "做一个 Q4 总结 PPT, 用 skills/ppt-master/templates/brands/<brand_id>/ 这个品牌"- Same explicit-path rule as layout templates: bare brand names never trigger-- May be supplied together with a layout template path; brand identity overrides layout-template defaults+- May be supplied together with a layout template path; Step 3 fuses both into a single `design_spec.md` (brand wins on identity tokens, layout wins on page structure) — see `SKILL.md` Step 3- To list available brands: open `templates/brands/brands_index.json`- To edit: modify `templates/brands/<brand_id>/design_spec.md` directly, then re-run `python3 skills/ppt-master/scripts/register_template.py --kind brand <brand_id>````@@ -209,9 +209,9 @@ Brand application happens in [`SKILL.md` Step 3](../SKILL.md) under the **same e| User input at SKILL.md Step 3 | Behavior ||---|---|-| Explicit brand directory path supplied | Step 3 copies the brand into `<project_path>/brand/`; Strategist locks color / typography / logo / voice as truth at Step 4 |+| Explicit brand directory path supplied | Step 3 copies the brand into `<project_path>/templates/` (same target as a layout template); Strategist locks color / typography / logo / voice as truth at Step 4 || Bare brand name, brand mention without path, or silence | Skip — no auto-application based on directory count or any other implicit signal |-| Both a brand path and a layout template path supplied in the same message | Both apply; brand identity overrides layout-template defaults, layout template's page roster and structural design stay intact |+| Both a brand path and a layout template path supplied in the same message | Step 3 fuses both into a single `design_spec.md` inside `<project_path>/templates/` (brand wins on identity tokens, layout wins on page structure). See `SKILL.md` Step 3 for the field-precedence table and the two conflict gates that may surface a clarifying question |`brands_index.json` is discovery-only (mirrors `layouts_index.json` semantics); listing brands never advances the pipeline.@@ -223,4 +223,4 @@ Brand application happens in [`SKILL.md` Step 3](../SKILL.md) under the **same e2. **Self-contained package** — all brand assets (logo, images, illustrations, icons) live inside `templates/brands/<brand_id>/`. Nothing leaks to workspace root or `projects/`.3. **No script dependency** — Step 2A reuses existing converters plus AI inline reading. A dedicated `brand_extract.py` is not introduced unless future user feedback demands batch processing or precise color picking from raster logos.4. **Multi-brand support** — `templates/brands/` accepts any number of brands; agency / freelancer / multi-client workflows are natural.-5. **Precedence rule** — when a brand and a layout template both apply, brand identity tokens (color / typography / logo / voice) override the layout template's defaults while the layout's page structure is preserved.+5. **Precedence rule** — when a brand and a layout template both apply, Step 3 fuses them into one `design_spec.md`: brand wins on color / typography / logo / voice / icon style; layout wins on canvas / page roster / spacing / font-size hierarchy / signature visual elements. See `SKILL.md` Step 3 for the full precedence table.