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(planning): author directions before opening any catalog, defer references to the step that uses them, and add a page chrome system
hugohe37b0a626da2f2
diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.mdindex 03e93a14..b7967788 100644--- a/skills/ppt-master/references/executor-base.md+++ b/skills/ppt-master/references/executor-base.md@@ -112,7 +112,7 @@ Apply the content-vs-expression contract above within the selected reading mode.- Base icons may use any SVG already prepared under `<project_path>/icons/`. `icons.library` records the Strategist's primary bundled style choice and `icons.inventory` indexes its curated synced pool; neither assigns icons to pages or limits other project-local assets. `simple-icons` entries are real brand marks; they are not a separately confirmed library.- Illustrated icons are prepared transparent slice files under `images/` and follow [`executor-image.md`](./executor-image.md), even when they perform the same compact semantic job as an SVG icon. Never move them into `icons/`, add them to `icons.inventory`, or render them through `<use data-icon>`.- Core color roles retain their meaning. Derive tints, shades, alpha, gradients, and effects; preserve natural asset colors; and use sparse page-local accents for differentiation/ornament. They must not become a competing or recurring palette.-- §V `Spacing anchors` (page margin, block gap, column gutter, corner radius, body leading) are deck-wide identity anchors: reuse them on every page and depart only for a page job, never to make content fit.+- §V `Spacing anchors` (page margin, block gap, column gutter, corner radius, body leading) are deck-wide identity anchors: reuse them on every page and depart only for a page job, never to make content fit. §V `Page chrome system` is the deck's one decision on running header/eyebrow, page number, source line, and title placement/orientation: realize it consistently and add no chrome it declined.- Resolve structural families by role: exact `<role>_family` first, then `title_family` for title roles or `body_family` for other unoverridden roles, then legacy `font_family`. Never flatten declared role overrides. A sparse export-safe accent family may style short non-structural display/ornament only—never title/body/data/annotation. Recurrence requires upstream selection.- Font sizes use the named `typography` role values as deck-wide anchors. Map every structural text item to a declared role before drawing; never inherit a template placeholder size. Start from the anchor, then use composition and content fit to adjust that occurrence by at most `±2`px. Keep same-page peers consistent and preserve the role hierarchy; bounded adjustment does not create a new role.- **Text roles**: declared `lead` / `subtitle` carry the page's primary claim; `footnote` / `annotation` carry footnotes, page numbers, and credits. Sizes come from declared roles.diff --git a/skills/ppt-master/references/image-renderings/_index.md b/skills/ppt-master/references/image-renderings/_index.mdindex 25cdaf89..056fdc25 100644--- a/skills/ppt-master/references/image-renderings/_index.md+++ b/skills/ppt-master/references/image-renderings/_index.md@@ -10,7 +10,7 @@ A **rendering** is a visual style family: line quality, texture, depth, material## 1. Catalog (20 renderings)-Each rendering keeps its own authoritative file with: style paragraph, line / texture / depth notes, deck HEX usage, and a fewshot prompt snippet. Read this index alone while choosing a direction. Only after a preset or custom bases are fixed may the active role read the selected sibling files: one file for a preset, every exact `image_rendering_references` file for a catalog-based custom, and none for a novel custom. Never glob the directory or read an unselected sibling. Whether AI imagery is recommended remains a separate source decision; Image_Generator follows the same selected-only rule.+Each rendering keeps its own authoritative file with: style paragraph, line / texture / depth notes, deck HEX usage, and a fewshot prompt snippet. Open this index only after the direction has been written in its own words, to name a basis that genuinely matches it; a direction that matches no row names none. Read a sibling file only after that direction is confirmed or, in Quick, decided: one file for a preset, every exact `image_rendering_references` file for a catalog-based custom, and none for a novel custom. Never glob the directory or read an unselected sibling. Whether AI imagery is recommended remains a separate source decision; Image_Generator follows the same selected-only rule.### 1.1 Modern / commercial (the corporate-PPT main field)@@ -62,7 +62,7 @@ Every coordinated Stage-2 direction carries one complete `rendering: custom` can|---|---|| Length | One paragraph, 2-5 sentences || Axes covered | line / texture / depth / material / mood (same as preset files) |-| Catalog basis | Freeze every exact id from this index, then read only those files before applying one basis or synthesizing several |+| Catalog basis | Write the treatment first; record only genuinely matching ids from this index, and read those files only after the direction is confirmed or decided |```yaml- image_rendering: customdiff --git a/skills/ppt-master/references/modes/_index.md b/skills/ppt-master/references/modes/_index.mdindex 79b40f69..fa2a9cca 100644--- a/skills/ppt-master/references/modes/_index.md+++ b/skills/ppt-master/references/modes/_index.md@@ -8,7 +8,7 @@ A **mode** is the deck's **narrative + persuasion skeleton** — how the argumen## 1. Catalog (5 modes)-Each mode keeps its own authoritative file with: narrative skeleton, page-structure tendencies, speaker-notes register, and a page skeleton example. Read this index alone while choosing a direction. Only after a preset or custom bases are fixed may the active role read the selected sibling files: one file for a preset, every exact `mode_references` file for a catalog-based custom, and none for a novel custom. Never glob the directory or read an unselected sibling.+Each mode keeps its own authoritative file with: narrative skeleton, page-structure tendencies, speaker-notes register, and a page skeleton example. Open this index only after the direction has been written in its own words, to name a basis that genuinely matches it; a direction that matches no row names none. Read a sibling file only after that direction is confirmed or, in Quick, decided: one file for a preset, every exact `mode_references` file for a catalog-based custom, and none for a novel custom. Never glob the directory or read an unselected sibling.| Mode | Narrative skeleton | Typical communication context ||---|---|---|@@ -51,8 +51,8 @@ selecting one for the current deck:| Active profile | Use ||---|---|-| Default Generate | Strategist reads only this index while mapping three whole solution intents, freezes each custom direction's exact bases, then reads only their deduplicated detail files. Executor reads the confirmed preset file or exact custom references. |-| Quick Generate | The current main agent reads only this index while deciding, then reads the resolved preset or exact custom bases and keeps that one direction in active context without Design Spec/lock. |+| Default Generate | Strategist authors three whole directions with this index closed, then opens it once to record genuinely matching bases; the confirmed direction's referenced files are read at Design Spec time. Executor reads the confirmed preset file or exact custom references. |+| Quick Generate | The current main agent decides its one direction with this index closed, then opens it once to map, then reads the resolved preset or exact custom bases and keeps that one direction in active context without Design Spec/lock. |**Resolution scope**: deck-wide (one mode per deck). The five are the catalog you select from; if the structure is genuinely mixed, pick the mode of the body pages and let pages vary within it, or use a warranted `custom` blend (§4). Default recommends and confirms; Quick decides directly.@@ -66,7 +66,7 @@ selecting one for the current deck:**Quick custom**: do not display a candidate set. Use `custom` only when a project-specific specialization or fusion serves the deck better than one preset; retain the behavior and exact bases in active context and persist nothing.-**Mandatory — select before detail reading**: Use this index to freeze every catalog source actually used, then read only those exact files before writing the behavior. One source may supply the complete cadence unchanged; when several are named, each owns a distinct executable act, posture, title voice, rhythm, or register. Reference count has no fixed cap; count is an outcome, not a target. A three-basis direction may use `pyramid` for a conclusion-first opening, `narrative` for the risk-tension act, and `instructional` for the closing action sequence; it reads those three files and writes all three ids beside `mode_behavior`. Quick retains its bases only in active context. Omit every source whose contribution cannot be stated, never add a second merely to imply synthesis, and do not open candidates for comparison after this gate. A custom using no catalog source names and reads none.+**Mandatory — write before mapping, map before reading**: write the behavior first; then use this index only to record every catalog source it genuinely uses, and read those exact files only once the direction is confirmed or decided. One source may supply the complete cadence unchanged; when several are named, each owns a distinct executable act, posture, title voice, rhythm, or register. Reference count has no fixed cap; count is an outcome, not a target. A three-basis direction may use `pyramid` for a conclusion-first opening, `narrative` for the risk-tension act, and `instructional` for the closing action sequence; it reads those three files and writes all three ids beside `mode_behavior`. Quick retains its bases only in active context. Omit every source whose contribution cannot be stated, never add a second merely to imply synthesis, and do not open candidates for comparison after this gate. A custom using no catalog source names and reads none.> **One value per deck — fusion is *one* `custom`, not several modes.** A deck always resolves a single `mode`. A multi-mode blend is expressed as **one** custom behavior whose paragraph describes the acts — never as several simultaneous modes.>diff --git a/skills/ppt-master/references/strategist-image.md b/skills/ppt-master/references/strategist-image.mdindex bcc523db..80341080 100644--- a/skills/ppt-master/references/strategist-image.md+++ b/skills/ppt-master/references/strategist-image.md@@ -4,7 +4,7 @@Always-on Stage-2 rendering-candidate extension plus confirmed image elaboration and `design_spec.md §VIII` resource planning.-**Trigger**: Load before every fresh Stage-2 direction set. Apply §2 first from the rendering index, freeze each direction's exact bases, and only then read the deduplicated selected detail files before completing its behavior. [`strategist.md`](./strategist.md) independently owns source recommendation. A confirmed non-`none` source activates the applicable resource-planning sections; confirmed `none` stops before resources. Rendering candidates are authored once before confirmation and never backfilled from a later source toggle.+**Trigger**: Load after final confirmation, when the confirmed image source is not `none`, before authoring §VIII. Stage 2 rendering candidates are authored earlier without this module under [`strategist.md`](./strategist.md) §h; §2 here owns only what happens to them after confirmation. [`strategist.md`](./strategist.md) independently owns source recommendation. A confirmed non-`none` source activates the applicable resource-planning sections; confirmed `none` stops before resources. Rendering candidates are authored once before confirmation and never backfilled from a later source toggle.---@@ -55,9 +55,9 @@ When a subject crosses a native title, panel, frame, or shape, the prepared path## 2. AI Image Strategy — always propose three; lock only for confirmed `ai`-Before any rendering detail, use the already-loaded [`image-renderings/_index.md`](./image-renderings/_index.md) as the sole rendering-basis catalog authority. First author exactly three complete, project-fit solution intents; use the index to freeze each intent's exact rendering bases, then read once only the deduplicated referenced sibling files. Project one complete `image_strategy` into each direction regardless of `recommend.image_usage`. Every candidate carries `name`, `rendering: custom`, `visual`, `mood`, and non-empty `behavior`, each written once in the confirmed UI language. Mood includes a recognizable real-world analogy. All three must credibly serve their owning whole solution; rendering treatments and bases may coincide when other components express the direction difference. Do not force artificial safe / shifted / bold extremes. Image colors always inherit that direction's deck HEX roles; never add an image palette or alter deck colors to rescue a rendering.+The three `image_strategy` candidates were authored inside the Stage-2 directions with the rendering catalog closed ([`strategist.md`](./strategist.md) §h); the index was opened afterwards only to record a genuinely matching basis, and no detail file was read before confirmation. Each candidate carries `name`, `rendering: custom`, `visual`, `mood`, and non-empty `behavior`; image colors always inherit that direction's deck HEX roles.-Every direction is a `custom` rendering, unconstrained by how it relates to the catalog. It may use catalog material in any way or none, including carrying one complete preset treatment unchanged. Name every actual id in the visible behavior and read only those files after selection; when several are named, each owns a distinct line, texture, depth, material, or mood contribution. Reference count has no fixed cap, and a second basis is never required. With no catalog basis, name none and read none. Under a template it obeys inherited identity and application. Only a confirmed custom locks its edited behavior as `image_rendering_behavior`; when catalog material is actually used, also project the exact ids as `image_rendering_references`, otherwise omit that field. Unselected candidates remain recommendation-only. Do not write a separate fourth `custom_candidates.image_strategy`; ignore legacy `image_palette`.+Every direction is a `custom` rendering, unconstrained by how it relates to the catalog. It may use catalog material in any way or none, including carrying one complete preset treatment unchanged. Name every actual id in the visible behavior and read only the confirmed direction's files at Design Spec time; when several are named, each owns a distinct line, texture, depth, material, or mood contribution. Reference count has no fixed cap, and a second basis is never required. With no catalog basis, name none and read none. Under a template it obeys inherited identity and application. Only a confirmed custom locks its edited behavior as `image_rendering_behavior`; when catalog material is actually used, also project the exact ids as `image_rendering_references`, otherwise omit that field. Unselected candidates remain recommendation-only. Do not write a separate fourth `custom_candidates.image_strategy`; ignore legacy `image_palette`.The UI hides these candidates while AI is not selected. If the user adds AI, it reveals the already-authored three without another backend recommendation; source selection never creates or rewrites rendering candidates. After confirmation, Image_Generator reads only the selected preset or exact custom references and must not blend unselected candidate identities.@@ -73,10 +73,10 @@ References describe visual intent: AI uses subject + intent + composition withou**Prepared-user fast path**: For initial imported or user-supplied assets confirmed as `provided`, copy the exact `Filename` basename and derive `Dimensions` / `Ratio` from that row's EXIF-corrected `Width` / `Height` / native `AspectRatio` in the latest `analysis/image_analysis.csv`; `SourceDisplayRatio` is source-context metadata, not the bitmap crop ratio. Drop source-side directories, set `Acquire Via: user` and `Status: Existing`, and decide the remaining §VIII fields normally. Existing §VIII / lock / provenance-manifest records override this inference. Assets declared as `ai`, `web`, `slice`, or manual fulfillment retain that provenance and advance through their own status lifecycle after entering `images/`; location never reclassifies them as `user / Existing`.-**Layout pattern** (the checker requires one non-empty value per placed row): it is preferred expression, not locked geometry; optional hierarchical ids from the already-read [`image-layout-patterns.md`](./image-layout-patterns.md) must be exact. They are prompt lookup handles for Executor, not exporter effect codes. Executor may adopt, adapt, or decline the suggestion while preserving resource identity/source, must-use status, crop/content, and explicit user/template constraints; layout-only changes need no upstream rewrite.+**Layout pattern** (the checker requires one non-empty value per placed row): it is preferred expression, not locked geometry; Strategist does not open [`image-layout-patterns.md`](./image-layout-patterns.md); an id may appear only when already known exactly, never looked up. They are prompt lookup handles for Executor, not exporter effect codes. Executor may adopt, adapt, or decline the suggestion while preserving resource identity/source, must-use status, crop/content, and explicit user/template constraints; layout-only changes need no upstream rewrite.-**Reference — job-bearing pattern text**: a useful entry names the job the image does for the content or the page's shapes, not only a skeleton id, position, size, crop, or scrim. The already-read [`image-layout-patterns.md`](./image-layout-patterns.md) is recall for that composition, never a menu — an unlisted combination or a technique it never names answers a job just as well, and the job is never restated to reach a listed entry. Plain split and full bleed stay valid when the named job is best served plainly. A `no-crop` or supporting row keeps one concise suggestion instead.+**Reference — job-bearing pattern text**: a useful entry names the job the image does for the content or the page's shapes, not only a skeleton id, position, size, crop, or scrim. Executor later reads [`image-layout-patterns.md`](./image-layout-patterns.md) as recall for that composition, never a menu — an unlisted combination answers a job just as well, and the job is never restated to reach a listed entry. Plain split and full bleed stay valid when the named job is best served plainly. A `no-crop` or supporting row keeps one concise suggestion instead.-Choose narrative intent before dimensions, then apply the already-read [`image-layout-spec.md`](./image-layout-spec.md) to the actual page region. Techniques needing a cutout, blurred crop, or desaturated copy require that prepared asset. Write `Crop Policy: no-crop` whenever cropping could remove required pixels, labels, evidence, identity, or edge content; screenshots, charts, certificates/contracts, dense diagrams, logos, and product markings are common triggers rather than an exhaustive list. Otherwise write `Crop Policy: adaptive`: Executor may use complete display or a focal-safe crop, and the value never commands cropping.+Choose narrative intent before dimensions; Executor applies [`image-layout-spec.md`](./image-layout-spec.md) to the actual page region. Techniques needing a cutout, blurred crop, or desaturated copy require that prepared asset. Write `Crop Policy: no-crop` whenever cropping could remove required pixels, labels, evidence, identity, or edge content; screenshots, charts, certificates/contracts, dense diagrams, logos, and product markings are common triggers rather than an exhaustive list. Otherwise write `Crop Policy: adaptive`: Executor may use complete display or a focal-safe crop, and the value never commands cropping.Judge `text_policy` per AI row using [`image-generator.md`](./image-generator.md) §5.3; paper figures, academic schematics, panel comparisons, data-axis graphics, and stable decorative lettering are positive triggers for reconsidering an all-`none` plan. Step 5 dispatches pending `ai` / `slice` rows to Image_Generator and pending `web` rows to Image_Searcher.diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.mdindex 8f655813..8cd192d1 100644--- a/skills/ppt-master/references/strategist.md+++ b/skills/ppt-master/references/strategist.md@@ -36,7 +36,7 @@ solution + production gate:| **1 — communication contract + template choice** | `primary_language` · `c` audience · open-ended communication intent · audience outcome · core message / delivery context (primary + optional secondary) / artifact afterlife · `content_divergence` (all prose fields may be blank) · `a` canvas · explicit `free_design` or `templates` choice and selected roots | confirmed together; candidate workspaces do not influence the communication recommendation || **2 — final solution + production** (authored once from the user's *actual* Stage 1) | reading mode (`delivery_purpose`, PPT only) · `d` mode + visual style · `b` page count · `e` color · `f` icon · `g` typography · `h` image source + generated-image rendering · conditional natural-language template application · conditional AI-image acquisition path · generation mode · refine-spec toggle · `design_spec_depth` · proactive speaker notes / custom animations / narration audio | derived as one coherent plan from the confirmed contract; internal template exporter modes remain hidden |-Do not force communication intent into one catalog label; Stage 1 records composite intent in prose. Editable prose fields are recommendation drafts, not required inputs: confirmation preserves current text and blanks; never repopulate a cleared field. Stage 2 confirms narrative spine, reading density, page budget, visual system, image direction, production mechanics, and how any installed template should be used. It never chooses or installs a template. Inspect only project-local template spec/prototypes, present one editable application plan, and keep exporter reuse/adherence internal. First author exactly three complete, project-fit solution directions from the confirmed contract and source; only then project each direction into mode, visual style, color, type, icons, and generated-image rendering for lower-level adjustment. Every direction projects a project-specific `custom` mode, `custom` visual style, and `custom` generated-image rendering; the fixed catalogs remain conservative lower-level single-select alternatives. Each direction is one complete design authored top-down within the confirmed contract, never assembled bottom-up from catalog picks; three exist so a single recommendation cannot lock the user in, and the fixed catalogs stay the manual lower layer. Its custom projections are unrestricted by catalog relationship and may carry one preset unchanged. The three directions are plainly different designs at the whole-deck level before any field is written; that difference lives in the solutions, not in one designated field. Whichever components a direction's own design requires carry it — mode, visual style, rendering, color, type, or icons — any of them may, and none is required to differ. A different name, note, or reference count alone is not a difference, and projections identical on every component are not three solutions. Do not force safe / shifted / bold archetypes or artificial extremes. After all three bundles are complete, choose the strongest overall fit when no template is installed; with installed template state, choose the viable direction that most strongly expresses its resolved context under [`strategist-template.md`](./strategist-template.md). Write its actual zero-based index as `design_directions.selected` (`0`, `1`, or `2`); array order never determines preference. Every direction carries a complete generated-image rendering candidate even when AI imagery is not recommended; `recommend.image_usage` independently decides whether AI is proposed. Generated images inherit deck colors—there is no second image palette. Proactive defaults are speaker notes `true`, custom animations `false`, and narration audio `false`; a prior explicit user instruction overrides the matching recommendation, and effective narration audio requires effective speaker notes. `design_spec_depth` defaults to `brief`; `split` mode, `refine_spec: true`, or a preservation profile forces `complete`. Author each stage once; same-stage edits update only visible browser state through documented deterministic dependencies, without another AI/backend recommendation. Launch/derive/wait mechanics live in [`generate-pptx.md`](../workflows/generate-pptx.md) Step 4; item specs keep `a`–`h`.+Do not force communication intent into one catalog label; Stage 1 records composite intent in prose. Editable prose fields are recommendation drafts, not required inputs: confirmation preserves current text and blanks; never repopulate a cleared field. Stage 2 confirms narrative spine, reading density, page budget, visual system, image direction, production mechanics, and how any installed template should be used. It never chooses or installs a template. Inspect only project-local template spec/prototypes, present one editable application plan, and keep exporter reuse/adherence internal. First author exactly three complete, project-fit solution directions from the confirmed contract and source with every mode / visual-style / rendering catalog closed; only then project each direction into mode, visual style, color, type, icons, and generated-image rendering for lower-level adjustment. Every direction projects a project-specific `custom` mode, `custom` visual style, and `custom` generated-image rendering; the fixed catalogs remain conservative lower-level single-select alternatives. Each direction is one complete design authored top-down within the confirmed contract, never assembled bottom-up from catalog picks; three exist so a single recommendation cannot lock the user in, and the fixed catalogs stay the manual lower layer. Its custom projections are unrestricted by catalog relationship and may carry one preset unchanged. The three directions are plainly different designs at the whole-deck level before any field is written; that difference lives in the solutions, not in one designated field. Whichever components a direction's own design requires carry it — mode, visual style, rendering, color, type, or icons — any of them may, and none is required to differ. A different name, note, or reference count alone is not a difference, and projections identical on every component are not three solutions. Do not force safe / shifted / bold archetypes or artificial extremes. After all three bundles are complete, choose the strongest overall fit when no template is installed; with installed template state, choose the viable direction that most strongly expresses its resolved context under [`strategist-template.md`](./strategist-template.md). Write its actual zero-based index as `design_directions.selected` (`0`, `1`, or `2`); array order never determines preference. Every direction carries a complete generated-image rendering candidate even when AI imagery is not recommended; `recommend.image_usage` independently decides whether AI is proposed. Generated images inherit deck colors—there is no second image palette. Proactive defaults are speaker notes `true`, custom animations `false`, and narration audio `false`; a prior explicit user instruction overrides the matching recommendation, and effective narration audio requires effective speaker notes. `design_spec_depth` defaults to `brief`; `split` mode, `refine_spec: true`, or a preservation profile forces `complete`. Author each stage once; same-stage edits update only visible browser state through documented deterministic dependencies, without another AI/backend recommendation. Launch/derive/wait mechanics live in [`generate-pptx.md`](../workflows/generate-pptx.md) Step 4; item specs keep `a`–`h`.**Default — continuity-aware whole solution (may override when a scene reset communicates better)**: Within active-profile invariants and before recommending page count or production mechanics, judge whether adjacent explanation beats can remain within one recognizable mental map while a visible state changes. Where that choice lowers cognitive switching and motion has a named communication job, let it shape the solution's narrative spine, page rhythm, visual approach, and enabled notes/narration segmentation, and recommend the existing `proactive_custom_animations: true`. This is one positive signal, not the only reason to enable animation; absent it, retain the existing default or other valid evidence. Topic or wording repetition alone is insufficient. A `Motion suggestion` remains optional advice and never changes the effective outcome.@@ -127,11 +127,11 @@ When authoring §IX, translate every purpose named in `communication_intent` intTwo independent layers, each locks one preset or `custom`. Output: `d. Mode: <mode> + Visual style: <visual_style>`.-> **Top-down custom direction construction.** Author three complete solution intents from the confirmed project contract and source before selecting any catalog basis; do not assemble three apparent solutions from independent mode/style/rendering picks. The fixed planning-capability batch may already be in context, but only the three mode/style/rendering indexes act as basis selectors. Use their summaries to freeze the exact reference ids for each direction, then read once only the deduplicated union of those referenced detail files and author the final behaviors. Every direction MUST serialize `mode: custom`, `visual_style: custom`, and `image_strategy.rendering: custom`, each with visible, non-empty behavior prose. `custom` is not constrained by a catalog relationship: it may use catalog material in any way or none, including carrying one exact preset unchanged. References record only actual sources; one may carry the complete preset behavior, while several must each own a distinct executable contribution. Omit every basis whose contribution the behavior cannot state, and never add a decorative second basis. The three whole-deck directions MUST be plainly different designs before any field is written; complete each one's detail, then project that detail onto the fields. No component is the designated proof: whichever ones a direction's design requires carry the difference, any of them may, and mode, style, rendering, catalog bases, color, type, and icons are each free to coincide. A different name, note, or reference count alone is not a difference, and projections identical on every component are not three solutions. Where authoritative truth fixes some components, the remaining open ones carry it; when nothing is open, keep the projections identical and state that boundary instead of inventing a false difference. These three projections are the project-specific choices above the conservative fixed catalogs, not a fourth Custom proposal. Never glob a catalog, read an unselected sibling, or write bespoke prose as an enum value.+> **Direction before catalog.** Author three complete solutions from the confirmed contract and source while no mode/style/rendering index or detail file is in context: each states its own narrative cadence, shape language, composition geometry, decoration density, typographic character, texture, and generated-image treatment in executable prose drawn from the material. Only then open the three indexes once to map: record a reference where a row genuinely matches what is written, none where nothing does; never rewrite a direction toward a row. Detail files are read only after confirmation, for the selected direction, at Design Spec time. Every direction MUST serialize `mode: custom`, `visual_style: custom`, and `image_strategy.rendering: custom`, each with visible, non-empty behavior prose. `custom` is not constrained by a catalog relationship: it may use catalog material in any way or none, including carrying one exact preset unchanged. References record only actual sources; one may carry the complete preset behavior, while several must each own a distinct executable contribution. Omit every basis whose contribution the behavior cannot state, and never add a decorative second basis. The three whole-deck directions MUST be plainly different designs before any field is written; complete each one's detail, then project that detail onto the fields. No component is the designated proof: whichever ones a direction's design requires carry the difference, any of them may, and mode, style, rendering, catalog bases, color, type, and icons are each free to coincide. A different name, note, or reference count alone is not a difference, and projections identical on every component are not three solutions. Where authoritative truth fixes some components, the remaining open ones carry it; when nothing is open, keep the projections identical and state that boundary instead of inventing a false difference. These three projections are the project-specific choices above the conservative fixed catalogs, not a fourth Custom proposal. Never glob a catalog, read an unselected sibling, or write bespoke prose as an enum value.#### Layer 1 — Communication mode-🚧 **GATE**: use the already-loaded [`modes/_index.md`](./modes/_index.md) as the sole mode-basis catalog authority. After the three direction intents exist and their mode reference ids are frozen, read only those exact sibling files once; a novel mode reads none.+🚧 **GATE**: open [`modes/_index.md`](./modes/_index.md) only after the three direction proses exist, and only to name a genuinely matching basis as `mode_references`; read the selected direction's referenced mode file once after final confirmation, while authoring the Design Spec. A novel mode reads none.The deck's **narrative + persuasion skeleton** — how the argument is organized and advanced. Lock one preset from `pyramid` / `narrative` / `instructional` / `showcase` / `briefing`, or `custom` with behavior.@@ -145,7 +145,7 @@ Record the confirmed mode and rationale in `design_spec.md` first, including eve#### Layer 2 — Visual style-🚧 **GATE**: use the already-loaded [`visual-styles/_index.md`](./visual-styles/_index.md) as the sole style-basis catalog authority. After the three direction intents exist and their style reference ids are frozen, read only those exact sibling files once; a novel style reads none.+🚧 **GATE**: open [`visual-styles/_index.md`](./visual-styles/_index.md) only after the three direction proses exist, and only to name a genuinely matching basis as `visual_style_references`; read the selected direction's referenced style file once after final confirmation, while authoring the Design Spec. A novel style reads none.The deck's **visual aesthetic** — shape language, decoration density, whitespace rhythm, typographic character, texture. Anchors downstream fields e (Color), f (Icon), g (Typography), h (Image). Lock one preset from the catalog, or `custom`.@@ -165,7 +165,7 @@ Record the confirmed visual style and rationale in `design_spec.md` first, inclu### e. Color Scheme Recommendation-**Hard rule**: User-specified colors are truth. Lock supplied HEX, brand colors, or natural-language directives; templates follow inherited-design precedence. Even direct locks fill all six roles (`background`, `secondary_bg`, `primary`, `accent`, `secondary_accent`, `body_text`) in each of the three directions: repeat fixed roles and vary only open ones. Never emit an empty palette. Preserve confirmed/brand semantic roles. When writing §III, derive the standard `secondary_text` and `divider` neutrals and project them to `spec_lock.md colors`; §V fixes the five deck-wide spacing anchors.+**Hard rule**: User-specified colors are truth. Lock supplied HEX, brand colors, or natural-language directives; templates follow inherited-design precedence. Even direct locks fill all six roles (`background`, `secondary_bg`, `primary`, `accent`, `secondary_accent`, `body_text`) in each of the three directions: repeat fixed roles and vary only open ones. Never emit an empty palette. Preserve confirmed/brand semantic roles. When writing §III, derive the standard `secondary_text` and `divider` neutrals and project them to `spec_lock.md colors`; §V fixes the five deck-wide spacing anchors and the page chrome system.**Reference — not a constraint**: WCAG AA body-text contrast is 4.5:1.@@ -225,7 +225,7 @@ supplied or `simple-icons` mark. This requires no extra user-facing option.> **After the Strategist confirmation stage is approved — when writing `design_spec.md` §VI / `spec_lock.md`**, materialize a curated project icon pool:>> 3. A confirmed bundled library is materialized as a synced project pool before Executor starts; Executor cannot sync. Which prepared icons a page uses is realization, never a preassignment.-> 4. Put known basenames in the final batch. For an uncertain one, search the chosen style library — or `simple-icons` for a real brand mark — with `rg --files "skills/ppt-master/templates/icons/<library>" -g '*<drawable-object>*.svg'`. Abstract concept words return nothing; translate the semantic into a drawable object first, per [`../templates/icons/README.md`](../templates/icons/README.md). Do not enumerate broad keyword families.+> 4. Read [`../templates/icons/README.md`](../templates/icons/README.md) at this step, then put known basenames in the final batch. For an uncertain one, search the chosen style library — or `simple-icons` for a real brand mark — with `rg --files "skills/ppt-master/templates/icons/<library>" -g '*<drawable-object>*.svg'`. Abstract concept words return nothing; translate the semantic into a drawable object first, per [`../templates/icons/README.md`](../templates/icons/README.md). Do not enumerate broad keyword families.> 5. **Copy and validate in one batch** — run `python3 skills/ppt-master/scripts/icon_sync.py <project_path> <lib/name> [<lib/name> …]`. This both validates and materializes `<project>/icons/<lib>/`; skip per-file prechecks.> 6. Keep each successful, case-sensitive `lib/name`: bundled basenames are lowercase (`tabler-outline/award`, never `tabler-outline/Award`); custom icons retain exact case.> 7. Record each synced bundled path with broad suitable scenarios in `design_spec.md` §VI; record the same curated pool, its primary stylistic library, and any stroke-library `stroke_width` in `spec_lock.md icons`. Keep actually needed `simple-icons/*` ids in the same inventory without treating them as a second stylistic library or user-facing selection. `inventory` indexes the synced pool; other prepared project-local icons remain usable.@@ -236,7 +236,7 @@ supplied or `simple-icons` mark. This requires no extra user-facing option.### g. Typography Plan Confirmation (Font + Size)-🚧 **GATE**: Apply the chosen custom behavior and only the detail files already loaded from its exact `visual_style_references`. The title carries the character; the body may remain neutral.+🚧 **GATE**: Apply the confirmed direction's own typographic character; the referenced style detail files, read at Design Spec time, refine it but never replace it. The title carries the character; the body may remain neutral.**Family selection**:@@ -318,7 +318,7 @@ system.| Capability | Opportunity signal | Design Spec handoff ||---|---|---|-| Image composition | Image-as-canvas, editorial crop, collage, cutout, or meaningful focus / comparison / evidence units carry the page better than an adjacent rectangle | Propose a permitted source; when selected, apply the already-loaded [`strategist-image.md`](./strategist-image.md) resource contract and image-layout references, record a concise §VIII `Layout pattern` suggestion, and describe page-level image/overlay relationships in §IX `Layout` / `Images` |+| Image composition | Image-as-canvas, editorial crop, collage, cutout, or meaningful focus / comparison / evidence units carry the page better than an adjacent rectangle | Propose a permitted source; when selected, load [`strategist-image.md`](./strategist-image.md) now and apply its resource contract, record a concise plain-language §VIII `Layout pattern` job, and describe page-level image/overlay relationships in §IX `Layout` / `Images` || Composable illustration family | One or more pages benefit from coherent reusable title/corner ornaments, dominant anchors, supporting figures, compact illustrated-icon cues, or accents that can mix with text, shapes, photos, or lettering | Apply [`strategist-image.md`](./strategist-image.md): plan transparent elements by compatible family, record fixed reuse or adaptive variation in §VIII `Reference`, and describe each used page's carrier relationships in §IX `Layout` / `Images` || Native paint / overlay | Gradient, translucency, scrim, vignette, or wash supports focus, hierarchy, depth, legibility, or image integration | Record purpose/layering in §IX `Layout`, plus `Images` when imagery participates; no new field or type/stops/opacity/coordinates—Executor chooses realization || AI decorative lettering asset | Any stable display string in the deck — including a complete long or multi-line title, cover hook, chapter word, place or product name, dish or exhibit name, year, hero number, pull quote, or motif word — reads better with a material, dimensional, hand-rendered, or otherwise illustrative treatment than as ordinary text | Apply [`strategist-image.md`](./strategist-image.md): preserve every complete exact string, group compatible marks when useful, and keep chrome/body as native text. The lettering asset may carry the complete long or multi-line title as its display layer; keep an ordinary native title/subtitle in a separate text frame wherever the page needs a searchable, selectable, or outline-visible heading. Never shorten copy to make it look more like a wordmark |@@ -352,8 +352,9 @@ Classify by information model, never source PowerPoint object type:**Mandatory — relationship handoff**: keep every qualitative relationship in §IX free prose; never serialize grammar atoms, coordinates, or named models. Executor makes the per-page Structure decision at runtime.-**Reference — Chart/Table vocabularies**: the already-loaded Chart and Table-expression vocabularies list what can be selected for a page's information+**Reference — Chart/Table vocabularies**: read `chart-vocabulary.md` and+`table-vocabulary.md` at this point, only when the roster has value-driven or+cell-grid pages; they list what can be selected for a page's informationmodel; their descriptions do not rank candidates or replace judgment from theactual information. Custom objects and qualitative composition stay outsidethem. Retain `no-template-match` when no registered reference fits.@@ -432,20 +433,20 @@ editable-only requirements win. Execution follows**Always-on decision module; conditional resource extension**:-1. Before authoring Stage-2 directions, load the workflow's complete fixed- planning-capability batch. It includes this module, the image-layout- authorities, all compact decision maps, the icon-library contract, the- complete Chart and Table expression vocabularies. After the- three whole-direction intents exist and their mode/style/rendering reference- ids are frozen, read only- those exact detail siblings once and author one complete custom rendering- inside each direction before deciding whether `recommend.image_usage`- includes AI.-2. Independently derive `recommend.image_usage` from source needs. Confirmed- non-`none` sources activate the module's resource-planning sections.- Confirmed `none` writes no image rows, but does not erase the three- recommendation-only rendering candidates or the already-loaded composition- vocabulary.+1. Author one complete custom rendering inside each Stage-2 direction from+ the material, with no rendering index, detail file, or image module in+ context: `name`, `rendering: custom`, `visual`, `mood` (with a recognizable+ real-world analogy), and a 2–5 sentence `behavior` covering line, texture,+ depth, material, and mood; colors inherit the direction's deck HEX roles.+ After all three exist, open+ [`image-renderings/_index.md`](./image-renderings/_index.md) once only to+ record a genuinely matching `image_rendering_references`, then decide+ whether `recommend.image_usage` includes AI.+2. Independently derive `recommend.image_usage` from source needs. After+ confirmation, a non-`none` source loads+ [`strategist-image.md`](./strategist-image.md) and activates its+ resource-planning sections; confirmed `none` writes no image rows but keeps+ the three recommendation-only rendering candidates.The module owns AI rendering alternatives, acquisition paths, resource rows, prompt depth, page roles, and placement intent.@@ -482,12 +483,11 @@ Confirmation `d` locks two independent catalog items:- **Mode** — narrative skeleton: [`modes/_index.md`](./modes/_index.md) → `pyramid` / `narrative` / `instructional` / `showcase` / `briefing`.- **Visual style** — aesthetic: [`visual-styles/_index.md`](./visual-styles/_index.md) → presets + `custom`.-Strategist first loads the fixed planning-capability batch. For-mode/style/rendering basis selection it uses only the three corresponding-indexes, freezes the bases for the three whole directions, then reads only the-deduplicated referenced detail files before authoring their custom behaviors.-Executor reads one locked preset file or the exact references of a selected-custom; neither role globs a detail catalog (see+Strategist authors the three whole directions with the catalogs closed, then+opens the three indexes once to record genuinely matching bases, and reads only+the confirmed direction's referenced detail files while authoring the Design+Spec. Executor reads one locked preset file or the exact references of a+selected custom; neither role globs a detail catalog (see[`generate-pptx`](../workflows/generate-pptx.md) Step 6).---@@ -513,6 +513,12 @@ Lock the stable role set the deck needs, including recurring neutrals such as `s| Core + surrounding forces | center-radiating or hub-spoke || Wide visual + explanation | top-bottom split |+**Default — page chrome is a deck decision (may override when a template or+explicit instruction fixes it)**: decide once in §V whether the deck carries a+running header/eyebrow, page number, source line, and where titles live and in+which orientation; `none` is valid for any part. The kicker → rule → title →+body → footer skeleton is one choice, never the default.+**Reference — not a constraint**: after the complete §IX roster and plannedvisual resources are known, recommend a cross-page motif or coherent elementfamily when it can carry identity or meaning—such as title/corner ornaments, adiff --git a/skills/ppt-master/references/visual-styles/_index.md b/skills/ppt-master/references/visual-styles/_index.mdindex 5d2a00c2..bcccd122 100644--- a/skills/ppt-master/references/visual-styles/_index.md+++ b/skills/ppt-master/references/visual-styles/_index.md@@ -17,7 +17,7 @@ forms belong to one visual system.## 1. Catalog-Each style keeps its own authoritative file with: shape & decoration, typography character, color-usage discipline (no HEX), texture / elevation, and the paired image-rendering. Read this index alone while choosing a direction. Only after a preset or custom bases are fixed may the active role read the selected sibling files: one file for a preset, every exact `visual_style_references` file for a catalog-based custom, and none for a novel custom. Never glob the directory or read an unselected sibling. The catalog mirrors [`image-renderings`](../image-renderings/_index.md): each style's "Paired rendering" names the illustration family that shares its aesthetic.+Each style keeps its own authoritative file with: shape & decoration, typography character, color-usage discipline (no HEX), texture / elevation, and the paired image-rendering. Open this index only after the direction has been written in its own words, to name a basis that genuinely matches it; a direction that matches no row names none. Read a sibling file only after that direction is confirmed or, in Quick, decided: one file for a preset, every exact `visual_style_references` file for a catalog-based custom, and none for a novel custom. Never glob the directory or read an unselected sibling. The catalog mirrors [`image-renderings`](../image-renderings/_index.md): each style's "Paired rendering" names the illustration family that shares its aesthetic.> The **`visual_style` value is only ever a first-column `id`** (`swiss-minimal`, `editorial`, …). The "Paired rendering" column lists **image-rendering** names (`flat`, `minimalist-swiss`, `digital-dashboard`, …) — never treat one of those as the `visual_style`. Default records rendering under confirmation h; Quick keeps the selected rendering only in active context and any required image manifest.>@@ -107,11 +107,11 @@ an exact authoring preset here.## 3. Editable `custom` projection-Each coordinated Default Stage-2 direction authors one visible, non-empty `custom` aesthetic whose paragraph names its executable shape language, composition geometry, decoration density, whitespace, typographic character, and texture — **no HEX, no color names as values**. `custom` is not constrained by its relationship to the catalog: it may use catalog material in any way or none, including carrying one fitting preset unchanged. The three complete directions are plainly different designs; this axis expresses that difference whenever their aesthetics genuinely differ, and catalog bases may coincide. A different name, note, reference count, or palette alone is not another aesthetic. Style behaviors may also coincide when other components carry the direction difference or authoritative user/template truth forbids visual variation; state that boundary in the direction note instead of fabricating difference. Use this index to freeze any catalog bases before reading their detail files. A template-backed direction stays inside the inherited identity and confirmed application plan. Record the confirmed current aesthetic in the Design Spec first, then project `- visual_style: custom` plus `- visual_style_behavior:`. The 18 fixed styles remain lower-level single-select alternatives; do not create a fourth AI-custom proposal.+Each coordinated Default Stage-2 direction authors one visible, non-empty `custom` aesthetic whose paragraph names its executable shape language, composition geometry, decoration density, whitespace, typographic character, and texture — **no HEX, no color names as values**. `custom` is not constrained by its relationship to the catalog: it may use catalog material in any way or none, including carrying one fitting preset unchanged. The three complete directions are plainly different designs; this axis expresses that difference whenever their aesthetics genuinely differ, and catalog bases may coincide. A different name, note, reference count, or palette alone is not another aesthetic. Style behaviors may also coincide when other components carry the direction difference or authoritative user/template truth forbids visual variation; state that boundary in the direction note instead of fabricating difference. Write the aesthetic first; open this index afterwards only to record genuinely matching bases. A template-backed direction stays inside the inherited identity and confirmed application plan. Record the confirmed current aesthetic in the Design Spec first, then project `- visual_style: custom` plus `- visual_style_behavior:`. The 18 fixed styles remain lower-level single-select alternatives; do not create a fourth AI-custom proposal.-Quick does not display a candidate spectrum. It reads this index, resolves one preset or custom behavior, then reads only the selected detail files and persists nothing.+Quick does not display a candidate spectrum. It resolves one custom behavior or preset with this index closed, opens it once to map, then reads only the selected detail files and persists nothing.-**Mandatory — select before detail reading**: Freeze every catalog source actually used from this index, then read only those exact files before writing the behavior. One source may supply the complete aesthetic unchanged; when several are named, each contributes a distinct executable job across shape language, composition, decoration, whitespace, typography, or texture. Reference count has no fixed cap; count is an outcome, not a target. A coherent three-basis direction may assign `swiss-minimal` to grid and whitespace, `soft-rounded` to selective surface contours and elevation, and `editorial` to evidence hierarchy and rules. Default persists every actual id as `visual_style_references`; Quick retains them only in active context. Omit every source whose contribution cannot be stated, never add a second merely to imply synthesis, and do not open candidates for comparison after this gate. A custom using no catalog source names and reads none.+**Mandatory — write before mapping, map before reading**: write the behavior first; then use this index only to record every catalog source it genuinely uses, and read those exact files only once the direction is confirmed or decided. One source may supply the complete aesthetic unchanged; when several are named, each contributes a distinct executable job across shape language, composition, decoration, whitespace, typography, or texture. Reference count has no fixed cap; count is an outcome, not a target. A coherent three-basis direction may assign `swiss-minimal` to grid and whitespace, `soft-rounded` to selective surface contours and elevation, and `editorial` to evidence hierarchy and rules. Default persists every actual id as `visual_style_references`; Quick retains them only in active context. Omit every source whose contribution cannot be stated, never add a second merely to imply synthesis, and do not open candidates for comparison after this gate. A custom using no catalog source names and reads none.---@@ -119,8 +119,8 @@ Quick does not display a candidate spectrum. It reads this index, resolves one p| Active profile | Use ||---|---|-| Default Generate | Strategist reads only this index while mapping three whole solution intents, freezes each custom direction's exact bases, then reads only their deduplicated detail files. Executor reads the confirmed preset file or exact custom references. |-| Quick Generate | The current main agent reads only this index while deciding, then reads the resolved preset or exact custom bases and retains that one direction without Design Spec/lock. |+| Default Generate | Strategist authors three whole directions with this index closed, then opens it once to record genuinely matching bases; the confirmed direction's referenced files are read at Design Spec time. Executor reads the confirmed preset file or exact custom references. |+| Quick Generate | The current main agent decides its one direction with this index closed, then opens it once to map, then reads the resolved preset or exact custom bases and retains that one direction without Design Spec/lock. |**Resolution scope**: deck-wide (one style per deck). It anchors taste as a**reference**, not a whitelist. Each §1 `Composition geometry` list isdiff --git a/skills/ppt-master/scripts/docs/confirm_ui.md b/skills/ppt-master/scripts/docs/confirm_ui.mdindex c1c2425a..8abcda33 100644--- a/skills/ppt-master/scripts/docs/confirm_ui.md+++ b/skills/ppt-master/scripts/docs/confirm_ui.md@@ -325,7 +325,7 @@ template-selection receipt.Direction-local custom projections apply to mode, visual style, and generated-image rendering; all three are editable after selection and a selected custom value cannot be blank. The original recommendation remains immutable so the active whole-direction card can explicitly restore every edited component without making an ordinary card click destructive. Legacy standalone `custom_candidates` remain readable but are optional and are not authored in new files. Color / typography keep their existing manual Custom cards. Image usage uses source ids plus `image_notes`; closed sets have no Custom path.-**Stage-2 catalog read gate.** Before choosing component bases, Strategist reads only `modes/_index.md`, `visual-styles/_index.md`, and `image-renderings/_index.md`. It authors the three whole solution intents first, freezes every basis id from those indexes, and only then reads the deduplicated selected detail files before completing the custom behaviors. `custom` has no required catalog relationship: one exact preset may supply an entire editable projection unchanged, several may contribute distinct jobs, or no preset may be used. These are examples, not a closed classification. The behavior remains non-empty; omit every source whose contribution it cannot state and never add a decorative second basis. Unselected sibling files never enter context.+**Stage-2 catalog read gate.** Strategist authors the three whole solutions with no mode/style/rendering index or detail file in context, then opens `modes/_index.md`, `visual-styles/_index.md`, and `image-renderings/_index.md` once only to record genuinely matching bases. No detail file is read before final confirmation; the selected direction's referenced files are read while authoring the Design Spec. `custom` has no required catalog relationship: one exact preset may supply an entire editable projection unchanged, several may contribute distinct jobs, or no preset may be used. These are examples, not a closed classification. The behavior remains non-empty; omit every source whose contribution it cannot state and never add a decorative second basis. Unselected sibling files never enter context.**Stage-1 current-value contract.** Each editable prose box starts with the Strategist's recommendation, if one exists. The user may retain, revise, or clear it; no Stage-1 prose field has a non-empty validation gate. On confirmation, the browser submits the current strings and the server preserves them through every later stage and the final `result.json`, including `""`. Blank means no explicit user constraint and may cause downstream default judgment, but it never causes the initial recommendation to be restored. A profile-declared `locked: true` field is read-only and remains the sole exception.diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex 54acc6f5..00d7c0d4 100644--- a/skills/ppt-master/scripts/prompt_audit_manifest.json+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json@@ -280,7 +280,7 @@"skills/ppt-master/references/image-base.md","skills/ppt-master/references/image-generator.md"],- "max_tokens": 145000+ "max_tokens": 150000},"route.generate.quick-generate.video-design": {"description": "Quick Generate with conditional video-delivery design, frozen-script notes, custom animation, and narration/audio delivery. Ceiling raised after BUDGET_LOAD_SET reported 154620 tokens.",@@ -1047,7 +1047,7 @@"route.generate.planning-ai"],"files": [],- "max_tokens": 120000+ "max_tokens": 125000},"stage.generate.executor.chart": {"description": "Conditional value-driven chart execution rules.",diff --git a/skills/ppt-master/templates/design_spec_reference.md b/skills/ppt-master/templates/design_spec_reference.mdindex a78aac52..3559e435 100644--- a/skills/ppt-master/templates/design_spec_reference.md+++ b/skills/ppt-master/templates/design_spec_reference.md@@ -122,6 +122,7 @@ Use these exact subsections and field shapes:- **Hierarchy direction**: <how attention should move across a typical page>- **Composition tendency**: <non-binding macro direction; no coordinates or authoring method>- **Cross-page continuity**: <what may recur or vary across the roster>+- **Page chrome system**: <one deck-level decision: running header or eyebrow, page number, source line, title placement and orientation; `none` is valid for any part>- **Spacing posture**: <dense, open, or variable by page rhythm>- **Spacing anchors**: <five deck-wide px values — page margin, block gap, column gutter, corner radius, body leading — kept stable across pages like the color and type anchors>@@ -177,7 +178,7 @@ in `kebab-case` and add one `Native-ready` map: `<key>=yes|no; ...`. Decideobject. Qualitative relationships/read order remain unkeyed prose, as doincidental microvisuals.-In §VIII, author every planned or explicitly required resource from the confirmed source boundary. Write one concise, non-empty `Layout pattern` suggestion in ordinary language; optionally cite hierarchical ids from the layout library when they help recall a technique. An image-led `adaptive` row names the page job the image resolves next to the composition serving it; a `no-crop` or supporting row keeps the concise suggestion alone. Set `Crop Policy` to `adaptive` or `no-crop`; set `Acquire Via` to `ai`, `web`, `user`, `placeholder`, or `slice`. Preserve unresolved required assets as `Pending` or `Needs-Manual` instead of dropping or reclassifying them. Native formulas never enter this table or `spec_lock.md images`.+In §VIII, author every planned or explicitly required resource from the confirmed source boundary. Write one concise, non-empty `Layout pattern` suggestion in ordinary language naming the job the image does; do not open the layout library to find an id. An image-led `adaptive` row names the page job the image resolves next to the composition serving it; a `no-crop` or supporting row keeps the concise suggestion alone. Set `Crop Policy` to `adaptive` or `no-crop`; set `Acquire Via` to `ai`, `web`, `user`, `placeholder`, or `slice`. Preserve unresolved required assets as `Pending` or `Needs-Manual` instead of dropping or reclassifying them. Native formulas never enter this table or `spec_lock.md images`.§VIII `Layout pattern` is a per-resource preference. When a page uses several images, repeats one image in multiple views, or combines an image with native overlays, describe the page-level relationship and participating resources in §IX `Layout` / `Images`; do not duplicate an unchanged resource row merely to encode animation sequencing.diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.mdindex 7298a20b..8413bc43 100644--- a/skills/ppt-master/workflows/generate-pptx.md+++ b/skills/ppt-master/workflows/generate-pptx.md@@ -260,7 +260,7 @@ workspace has been installed.At Step-4 entry, load the always-required planning context directly in onebatch: the role core, every canonical content-type source file defined below,and the compact structured analysis facts already present. Do not load any-mode, visual-style, or image-rendering detail file before Stage 1. For a multi-deck+mode, visual-style, or image-rendering index or detail file before Stage 1. For a multi-deck`source_profile.json`, read its compact `decks[]` digests in that batch and opena deck's larger identity/slide-library files only when the specific need belowarises.@@ -277,29 +277,24 @@ Then load only the extra role modules triggered by the current plan:| Stage 1 is confirmed and its template choice installed a selected Brand/Style/Layout/Deck workspace into this project | `references/strategist-template.md` before Stage 2 || The confirmed Stage-1 `delivery_context` identifies recorded/self-running/video delivery, or input is an explicit final/literal narration script | `references/video-design.md` before the three Stage-2 whole solutions and page roster |-After Stage 1 and template handoff, load the fixed planning-capability block-below in one batch before authoring any Stage-2 whole-solution intent, image-source recommendation, or page roster:--```-Read ${SKILL_DIR}/references/strategist-image.md-Read ${SKILL_DIR}/references/image-layout-spec.md-Read ${SKILL_DIR}/references/image-layout-patterns.md-Read ${SKILL_DIR}/references/modes/_index.md-Read ${SKILL_DIR}/references/visual-styles/_index.md-Read ${SKILL_DIR}/references/image-renderings/_index.md-Read ${SKILL_DIR}/templates/icons/README.md-Read ${SKILL_DIR}/templates/charts/chart-vocabulary.md-Read ${SKILL_DIR}/templates/tables/table-vocabulary.md-```--This is a capability map; retain the Strategist/Executor ownership boundary. Author the three whole solution-intents before mapping any component basis. Freeze every referenced-mode/style/rendering id from the indexes, then read once only the deduplicated-union of those exact detail files and finish the three custom behaviors. A novel-custom reads no detail file. Confirmed non-`none` uses the already-loaded image-layout references and continues into resource planning; confirmed `none` writes-no image rows while retaining recommendation-only rendering candidates. Only an installed+**Hard rule — judgment reads only what it needs**: Stage 2 directions come+from the material, the confirmed contract, the role core, and+`canvas-formats.md` alone. After final confirmation, read each reference at+the Design Spec step that uses it: `strategist-image.md` for §VIII when the+confirmed image source is not `none`; `templates/icons/README.md` when+materializing a confirmed icon pool; the chart/table vocabularies only when the+roster has value-driven or cell-grid pages. `image-layout-spec.md` and+`image-layout-patterns.md` are Executor material; Strategist never opens them.++**Hard rule — direction before catalog**: author the three whole solutions+from the material and the confirmed contract with no mode / visual-style /+rendering index or detail file in context. Only then read the three+`_index.md` files once, solely to record a `*_references` basis where a row+genuinely matches what was written; no match records none, and no direction+is revised toward a row. Detail files are read only after final confirmation,+only for the selected direction, while authoring the Design Spec. Confirmed non-`none` loads `strategist-image.md`+and continues into resource planning; confirmed `none` writes no image rows+while retaining recommendation-only rendering candidates. Only an installedproject-local template state loads the template module, and only after Stage 1is confirmed; a bare template/style name does not.@@ -387,10 +382,9 @@ or `templates` with at least one server-resolved root.it. The server requires this handoff before Stage 2.2. Only now inspect installed template state and apply- `strategist-template.md` when active. Load the fixed Stage-2 planning-capability- block above, author three whole solution intents, freeze their exact component- references from its indexes, then read only the referenced detail files and- complete the custom projections. Derive the+ `strategist-template.md` when active. Under the two hard rules above, author+ the three whole solutions with the catalogs closed, then open the three+ indexes only to record genuinely matching references. Derive theremaining production defaults and create`confirm_ui/recommendations.stage2.json` without changing Stage 1; declare`stage: "stage2"`, then wait for the final confirmation:@@ -503,7 +497,7 @@ python3 ${SKILL_DIR}/scripts/analyze_images.py <project_path>/imagesFor a new project, use the reference-first whole-document sequence:-1. Read `${SKILL_DIR}/templates/design_spec_reference.md`; create complete I–X `<project_path>/design_spec.md` once from retained confirmation, analysis, and context, without placeholders/examples.+1. Read `${SKILL_DIR}/templates/design_spec_reference.md` plus only the detail files named by the confirmed direction's `*_references` (none for a novel custom); create complete I–X `<project_path>/design_spec.md` once from retained confirmation, analysis, and context, without placeholders/examples.2. Audit it field by field against retained confirmation; Gate 1 must pass.3. If enabled, run [`refine-spec`](stages/refine-spec.md) on that file until explicit approval; touch no lock.4. Read `${SKILL_DIR}/templates/spec_lock_reference.md`; create or resynchronize the lock once from approved Design Spec and context. Never reopen `result.json` or make a new design choice.diff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.mdindex ed025dd1..beefbb13 100644--- a/skills/ppt-master/workflows/profiles/quick-generate.md+++ b/skills/ppt-master/workflows/profiles/quick-generate.md@@ -274,31 +274,25 @@ artifact. If a detail becomes uncertain later, re-read the exact installed SVGinstead of relying on memory or reopening the source PPTX. If no template wasinstalled, make the same design choices freely.-Before resolving the one-pass design, read this fixed planning-capability batch-in one pass:--```-Read ${SKILL_DIR}/references/canvas-formats.md-Read ${SKILL_DIR}/references/image-layout-spec.md-Read ${SKILL_DIR}/references/image-layout-patterns.md-Read ${SKILL_DIR}/references/modes/_index.md-Read ${SKILL_DIR}/references/visual-styles/_index.md-Read ${SKILL_DIR}/references/image-renderings/_index.md-Read ${SKILL_DIR}/templates/icons/README.md-Read ${SKILL_DIR}/templates/charts/chart-vocabulary.md-Read ${SKILL_DIR}/templates/tables/table-vocabulary.md-```--This batch is the complete capability map for planning, not a usage checklist:-zero use of any capability remains valid. Resolve one recommended whole+Before resolving the one-pass design, read only+`${SKILL_DIR}/references/canvas-formats.md`. Judgment reads nothing else;+reference material is read at the step that uses it: `templates/icons/README.md`+when preparing an icon pool, `templates/charts/chart-vocabulary.md` and+`templates/tables/table-vocabulary.md` only when the roster has value-driven or+cell-grid pages, and the image-layout authorities in §3 before the first image+page. Zero use of any capability remains valid. Resolve one recommended wholesolution directly; do not materialize Default's three candidates. Without aninstalled template, choose the strongest overall fit from the project brief andloaded decision authorities. With one, choose the viable solution that mostfully expresses the resolved template context and frozen Template Application,-varying only dimensions they leave open. Freeze its exact mode/style/rendering-ids, then read only those selected detail files or custom bases. A novel custom-reads none. Never open unselected detail siblings to compare candidates, glob a-catalog, or let them influence the decision. Decide+varying only dimensions they leave open. Write that solution in its own words+first — cadence, shape language, composition geometry, decoration density,+typographic character, texture, generated-image treatment — with no+mode/style/rendering index or detail file in context. Only then read the three+`_index.md` files once to record genuinely matching bases (no match records+none and reads nothing), then read only the recorded detail files. Never revise+the solution toward a row, open unselected siblings, glob a catalog, or let+them influence the decision. Decidewhether AI images are useful as a separate source judgment; even when theanswer is no, retain the chosen rendering direction for visual coherence. Keepthe chosen mode, style, rendering, and exact bases in active context only.@@ -321,6 +315,10 @@ the roster after the whole-roster check:- the resolved visual direction's deck-level shape language under[`visual-styles/_index.md`](../../references/visual-styles/_index.md) §2,retained for page-fit native geometry without selecting an exact preset here;+- one deck-wide page chrome system — running header/eyebrow, page number,+ source line, title placement and orientation — each decided, `none` valid;+ the kicker → rule → title → body → footer skeleton is one option, never the+ default;- when useful, an additional transient deck-level visual motif system with an identity orcommunication job, a recognizable invariant, and a reuse mode: fixed chrome,adaptive variation, or both; treat restraint as control of visual weight,@@ -466,8 +464,9 @@ This carrier menu does not satisfy or replace the per-page Structure decision inResolving one visual style, `Illus.` propensity, or generated-image rendering resolves how imagery **looks**; it resolves the source for no page. A named place, building, product, artwork, person, or other externally verifiable subject stays a web/supplied candidate no matter how illustrative the deck looks. When such a subject is deliberately not shown as itself, state that choice and its reason in the final report rather than leaving it implicit.-**Reference — Chart/Table vocabularies**: the already-loaded Chart and Table-expression vocabularies list what exists for a page's information model; their descriptions do not rank+**Reference — Chart/Table vocabularies**: read the Chart and Table+expression vocabularies now, only when the roster has value-driven or cell-grid+pages; they list what exists for a page's information model; their descriptions do not rankcandidates or replace judgment from the actual information, and they areneither usage quotas nor whitelists. Do not select a catalog reference forqualitative shape composition. Choose at most one primary Chart/Table@@ -555,9 +554,11 @@ by their stated contributions, or follow the behavior directly when none exist.Do not load `executor-base.md`: it owns Default's persisted-plan handoff,first-page gate, and completion routing. Excluding that file is not a capabilityexclusion; Quick loads the shared and conditional execution authorities here-directly. Reuse the already-loaded image-layout authorities. When any image+directly. When any imageexists, read once before the first affected page and reuse throughout the valid-execution context: [`executor-image.md`](../../references/executor-image.md)+execution context: [`executor-image.md`](../../references/executor-image.md),+[`image-layout-spec.md`](../../references/image-layout-spec.md),+[`image-layout-patterns.md`](../../references/image-layout-patterns.md),and [`svg-image-embedding.md`](../../references/svg-image-embedding.md); add[`executor-web-image.md`](../../references/executor-web-image.md) for a placed`Status: Sourced` image or filename recorded in `image_sources.json`.@@ -819,7 +820,7 @@ or lock.## ✅ Quick Generate Complete- [x] All required source/resource preparation is complete-- [x] The fixed planning-capability batch was read before the roster, and every selected detail source was read+- [x] The direction was written before any catalog was opened; reference material was read only at the step that used it, and every selected detail source was read- [x] The complete 187-name native preset vocabulary was read before P01; each page chose from that full capability surface, with objective candidate details inspected only when needed- [x] Every page considered suitable carrier combinations without a coverage quota or single-carrier assumption- [x] The proactive decorative-lettering capability scan ran before carrier selection; every selected lettering job entered an AI item or lettering sheet/slice job, and zero selected jobs remained valid