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): drop directional taste rules from the Executor core
hugohe323bb28571b27
diff --git a/docs/rules/prompt-style.md b/docs/rules/prompt-style.mdindex 640c44d7..3d607987 100644--- a/docs/rules/prompt-style.md+++ b/docs/rules/prompt-style.md@@ -160,7 +160,7 @@ not permit Executor to acquire visual resources.Before adding a `Hard rule`, `Forbidden`, `Mandatory`, `never`, `do not`, or any quota/threshold to a process prompt, name the mechanism that makes it hard: a checker rule id, an exporter behaviour, a DrawingML limit, a structured Master/Layout contract, artifact ownership or gate order, or reading-cost control. A rule with no such mechanism does not affect whether the SVG renders as authored or exports to editable PPTX; it may enter only as a capability entry (what exists and its syntax), a `Reference — not a constraint`, or an example — never as a prohibition, quota, usage default, or "omit when …" clause. Whether and how the model uses a capability is its own judgment. A prohibition that a script already enforces is not restated in prose; write only the fix.-**Owner exceptions — kept as `Mandatory`**: primary-per-page, composition geometry vocabulary, the ±2px font-size band, and the Layout-pattern diversity self-check are deliberate anti-sameness devices retained by the maintainer. If sameness returns after other restrictions are relaxed, add examples first; do not re-escalate demoted rules.+**Owner exceptions — kept as `Mandatory`**: primary-per-page, composition geometry vocabulary (including its slide-versus-web-grid motivation), the ±2px font-size band, the Layout-pattern diversity self-check, and "do not start from a universal palette" are deliberate anti-sameness devices retained by the maintainer. If sameness returns after other restrictions are relaxed, add examples first; do not re-escalate demoted rules.---diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.mdindex 7ed10569..97ef5d0e 100644--- a/skills/ppt-master/references/executor-base.md+++ b/skills/ppt-master/references/executor-base.md@@ -33,11 +33,10 @@ Evaluate branches from each object's actual information model, not only from a C## 1. Effect Capability Discovery-**Mandatory — select by visual job**: establish each page's semantic skeleton,-then run the already-loaded [`svg-effects.md`](./svg-effects.md) §6.1 procedure-before finalizing, with its Visual Job Router as recall; use §6.13 for a-coordinated page recipe when useful. The catalog expands construction-vocabulary; it creates no effect quota. Active cross-page continuous action+**Reference — effects vocabulary**: [`svg-effects.md`](./svg-effects.md) §6.1+lists the visual jobs an effect can serve, with its Visual Job Router as recall,+and §6.13 offers coordinated page recipes. The catalog expands construction+vocabulary. Active cross-page continuous actionadditionally loads [`animations.md`](./animations.md) §3.1 before authoringboth endpoints.@@ -92,7 +91,7 @@ Use named lock roles literally when that role applies, and use optional `Templat|---|---|| `text` | Make the visible page independently understandable. Preserve complete prose, explicit labels / captions / sources, tables, and necessary detail; use bullets only for genuinely parallel or ordered items. || `balanced` | Keep the primary claim and its evidence on the page; when notes are enabled, let them add interpretation and transitions. Mix prose, structured evidence, and necessary lists according to their semantic relationship. |-| `presentation` | Make one claim and one dominant visual expression legible at projection distance. Keep visible copy concise; when notes are enabled, put explanation and transitions there instead of creating paragraph dumps or compressed bullet prose. When notes are disabled, rely only on the confirmed presenter/page channels and never omit required content on the assumption that notes will carry it. |+| `presentation` | Make one claim and one dominant visual expression legible at projection distance. Keep visible copy concise; when notes are enabled, explanation and transitions can live there. When notes are disabled, rely only on the confirmed presenter/page channels and never omit required content on the assumption that notes will carry it. |Apply the content-vs-expression contract above within the selected reading mode. Never drop or invent facts to force a mode. When the authored texture materially conflicts with the lock, render the least-destructive faithful composition and surface `warning: P<NN> content texture conflicts with consumption_mode <value>` as an upstream outline issue; do not encode this subjective judgment in the checker.@@ -110,12 +109,12 @@ Apply the content-vs-expression contract above within the selected reading mode.**Execution anchors and contextual values**:-- 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` brand marks appear there only when the content actually needs that real brand; they are not a separately confirmed library.+- 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.- 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.-- **Core message ≥ `body`**: map the page's primary claim to declared `lead` / `subtitle`, never below the current body treatment. Footnotes, page numbers, and credits use declared `footnote` / `annotation`; do not invent a smaller 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.- **Write unitless px, with at most two decimals.** Structural and mapped-role text uses only its anchor or a value within its `±2`px band; the sparse display-size exception is defined separately below. Do not substitute familiar pt-style numbers or emit long precision tails.- **Sparse display-size exception**: a short non-structural Hero/Display element may use one undeclared size outside all anchor bands at most twice across the deck without a lock row. The third occurrence makes that size recurring: stop and return to Strategist to name the role in the Design Spec and `spec_lock.md`, then read back and validate the affected fragments before reuse. This exception never applies to titles, body copy, subtitles, annotations, footnotes, captions, data labels, or card copy, and nearby sizes must not be introduced to imitate one recurring treatment.- **Prepared decorative lettering**: When the approved plan selects stable artistic lettering as part of the visual, place its prepared AI/slice file as an image asset and keep the ordinary editable title/subtitle in separate native text frames. Do not recreate the asset with layered glyph copies or native WordArt; when the plan keeps that wording as native text and prepares no lettering asset, use ordinary `<text>` without inventing a missing image.@@ -142,9 +141,9 @@ Before drawing each page, look up its entry in `page_rhythm` (key format `P<NN>`| Tag | Layout discipline ||-----|-------------------|-| `anchor` | Structural page (cover / chapter / TOC / ending). `mirror` follows its prototype; `layout` retains its structure system. `style` / free design preserves the §IX cover hook or closing takeaway but may adopt, adapt, or decline the recommended composition. Avoid an information-empty generic cover/sign-off unless content, user direction, or template requires it. |+| `anchor` | Structural page (cover / chapter / TOC / ending). `mirror` follows its prototype; `layout` retains its structure system. `style` / free design preserves the §IX cover hook or closing takeaway but may adopt, adapt, or decline the recommended composition. || `dense` | Information-heavy. Card grids, multi-column layouts, KPI dashboards, tables, and charts are all permitted. This is the baseline behavior. |-| `breathing` | Low-density impact page. Avoid **multi-card grid layouts** — do not organize content as multiple parallel rounded containers (3-card row, 4-card KPI grid, 2×2 matrix rendered as cards). Use naked text blocks, dividers, whitespace, or full-bleed imagery as the content structure. Single rounded visual elements (hero image corners, callouts, tags, one emphasis block) are fine — the rule is about grid structure, not about the `rx` attribute. Proportions follow information weight (not a preset ratio). Typical forms: hero quote, single large number with one-line interpretation, full-bleed image with floating caption, section transition. |+| `breathing` | Low-density impact page. Naked text blocks, dividers, whitespace, or full-bleed imagery can carry the content structure. Proportions follow information weight (not a preset ratio). Typical forms: hero quote, single large number with one-line interpretation, full-bleed image with floating caption, section transition. |> Mechanical repetition comes from reusing the same carrier and topology without a page job—not from semantic cards themselves. Cards remain appropriate when they express real peer grouping, comparison, hierarchy, or capacity; vary rhythm when the content relationship changes. Context recovery follows §2.1.@@ -165,8 +164,8 @@ Before drawing each page, look up its entry in `page_rhythm` (key format `P<NN>`- **Main-agent ownership**: SVG generation must run in the main agent (not sub-agents) — pages share upstream context for cross-page visual continuity- **Generation rhythm**: P01 → first-page gate → remaining pages with one page gate per first-exercised `not-exercised` item → final gate, in one context without batches or other mid-run checker calls.- **Fact provenance**: when a §IX page lists `Fact IDs`, resolve each ID from `sources/*.facts.json` and keep the claim/value unchanged. Render a compact source footnote using the source name and a short URL/domain when space permits; when speaker notes are enabled, state the attribution naturally there too. When §IX says `Data class: scenario`, place a visible localized `Scenario data` / `情景数据` label adjacent to the affected KPI/chart and, when notes are enabled, state naturally there that the number is illustrative. Never attach an external fact ID to scenario data or let an unlabeled invented KPI look factual.-- **Mandatory — resolve the page carrier mix before coordinates**: decide background paint/field, editable text and optional lettering, native geometry/lines, prepared photos/scenes/illustration/icon assets, and applicable visualizations in one page-level composition decision. Use any suitable subset; omitting a carrier remains valid. Do not finish a text/container layout and then treat the other families as optional decoration. Use only prepared external resources, preserve every binding resource job and constraint, and choose the actual combination, visual weight, z-order, and local native construction from the page message and hierarchy. The resolved style controls treatment and emphasis, never carrier eligibility, image source, or the complete native construction vocabulary.-- **Default — stage each page with the style's composition geometry (may override when another page-fit move is stronger)**: an SVG page is a canvas, not a DOM. Resolve the page-scale move from `spec_lock.md`: a preset uses that selected style's §1 `Composition geometry`; `custom` executes `visual_style_behavior` first, then uses §1 geometry only from exact `visual_style_references` that the behavior assigns a shape or composition job. Other bases contribute only their assigned job, and an unreferenced novel custom follows its behavior alone. Treat every listed move as generative vocabulary rather than a finite menu, then apply [`native-shape-authoring.md`](./native-shape-authoring.md) §2.1's shared exact-fit geometry gate.+- **Mandatory — resolve the page carrier mix before coordinates**: decide background paint/field, editable text and optional lettering, native geometry/lines, prepared photos/scenes/illustration/icon assets, and applicable visualizations in one page-level composition decision. Use any suitable subset; omitting a carrier remains valid. Use only prepared external resources, preserve every binding resource job and constraint, and choose the actual combination, visual weight, z-order, and local native construction from the page message and hierarchy. The resolved style controls treatment and emphasis, never carrier eligibility, image source, or the complete native construction vocabulary.+- **Default — stage each page with the style's composition geometry (may override when another page-fit move is stronger)**: an SVG page is a canvas, not a DOM. Resolve the page-scale move from `spec_lock.md`: a preset uses that selected style's §1 `Composition geometry`; `custom` executes `visual_style_behavior` first, then uses §1 geometry only from exact `visual_style_references` that the behavior assigns a shape or composition job. Other bases contribute only their assigned job, and an unreferenced novel custom follows its behavior alone. Its motivation is the slide-versus-web reading: parallel rounded card grids (3-card rows, KPI grids, 2×2 card matrices) read as a web page, while a page-scale geometric move reads as a slide. Treat every listed move as generative vocabulary rather than a finite menu, then apply [`native-shape-authoring.md`](./native-shape-authoring.md) §2.1's shared exact-fit geometry gate.- **Default — consider the planned motif direction (may override when another coherent expression better serves the deck)**: when §III `Theme` recommends a cross-page motif or element family, decide whether it earns a continuity job. If adopted, keep its reuse coherent while varying scale, crop, density, position, and content interaction by page role; otherwise adapt or decline it and establish a more fitting style-consistent expression. An explicit user/template motif remains binding.- **Inherited containers**: preserve meaningful template frames; restyle radius, fill, stroke, and depth from the active Design Spec and `spec_lock.md`. Selected Chart/Table reference adaptation is owned by [`executor-visualization.md`](./executor-visualization.md); preview effects never override project styling or structural roles.- **Reference — prefer semantic geometry over preset stacks**: for relationships such as ascending, converging, breaking through, or stacking, first compose faithful primitives and exact presets as one page geometry system; use a Boolean only when the contour itself must merge, open, or fragment. Only when neither construction works should one page-specific polygon/path replace a stack of generic arrows.@@ -238,8 +237,9 @@ This decision applies only while drawing a new object. A suggestion nevertriggers retrospective scanning, contour classification, or automaticupgrading of ordinary SVG during export.-**Hard rule**: do not hand-write `data-pptx-authoring`, `data-pptx-prst`,-`data-pptx-frame`, adjustment metadata, or registry paths. The preset helper+**Hard rule — helper-written metadata**: `data-pptx-authoring`, `data-pptx-prst`,+`data-pptx-frame`, adjustment metadata, and registry paths are written only by+the preset helper; hand-written values fail the checker. The preset helpergenerates one compact atomic `<g>` from the shared 187-shape registry, withsemantic metadata and base paint written once. Rerun that helper when geometryor paint changes; never edit one of its direct paths.diff --git a/skills/ppt-master/references/executor-structure.md b/skills/ppt-master/references/executor-structure.mdindex d7fd3d68..0bf901d2 100644--- a/skills/ppt-master/references/executor-structure.md+++ b/skills/ppt-master/references/executor-structure.md@@ -103,12 +103,11 @@ Choose the field and map required atoms, then follow:| `labels` | Copy and caveats visibly attach directly or by leader/tether to what they explain; when a node has multiple text roles, cue → claim/value → support → note remains perceptibly descending and absent roles stay absent || `garnish` | Removing accents leaves all meaning intact |-**Hard rule — relationship before styling**: establish atoms, field, spine, nodes, and necessary edges before palette, type, effects, or containers. Prefer containment, alignment, baselines, and proximity; add lines/Connectors only for real edges, never to make a page look process-like.+**Hard rule — relationship before styling**: establish atoms, field, spine, nodes, and necessary edges before palette, type, effects, or containers. Containment, alignment, baselines, and proximity express relationships without edges; lines/Connectors express real edges.-**Default — visible structural composition (may override for naked-text-rhythm/style)**: Make one relationship-bearing field, spine, node carrier, or-directional shape the page-scale move; never add geometry merely because-Structure is `yes`. When drawn roles interact, resolve relationship-bearing+**Structural carriers**: a relationship-bearing field, spine, node carrier, or+directional shape can be the page-scale move; Structure `yes` by itself adds no+geometry. When drawn roles interact, resolve relationship-bearingparent contour/direction → contact → joint or intentional void →z-order/occlusion → canvas-edge behavior before labels/garnish. Skipinapplicable operations; implicit/direct roles remain container-free.diff --git a/skills/ppt-master/references/shared-standards-core.md b/skills/ppt-master/references/shared-standards-core.mdindex d943adbe..71196f7f 100644--- a/skills/ppt-master/references/shared-standards-core.md+++ b/skills/ppt-master/references/shared-standards-core.md@@ -26,7 +26,7 @@ Mandatory reference for every route that authors or regenerates slide visuals th| Containers | Use a card or panel when it expresses grouping, hierarchy, boundary, capacity, or a distinct material plane. Otherwise prefer spacing, rules, or direct text / geometry; peer containers share treatment unless a semantic difference justifies contrast. An unplanned repeated web-card grid is a carrier / topology problem, not a reason to suppress meaningful borders, shapes, or containers. || Titles and page chrome | Treat the semantic page title as part of the current composition rather than an automatic fixed header band; its position, scale, and relationship may change with page role while preserving the active route's content invariants. Add or retain running headers, footers, and page numbers only when they carry navigation, identity, attribution, or another explicit page job. Fidelity profiles preserve required source chrome. |-**Default — active effects vocabulary (may resolve to no added technique when no visual job is diagnosed)**: Default and Quick Generate complete the already-loaded [`svg-effects.md`](./svg-effects.md) §6.1 job diagnostic, which that file makes mandatory, before completing each page; whether any compatible technique is then added is this default's call, with the Visual Job Router as recall.+**Reference — effects vocabulary**: Default and Quick Generate load [`svg-effects.md`](./svg-effects.md); its §6.1 Visual Job Router lists the visual jobs an effect can serve. Whether any compatible technique is added is the author's call.**Fidelity labels**:diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.mdindex ed4ec342..fc580d61 100644--- a/skills/ppt-master/references/strategist.md+++ b/skills/ppt-master/references/strategist.md@@ -165,7 +165,9 @@ 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. Keep body-text contrast at least 4.5:1 and preserve confirmed/brand semantic roles.+**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.++**Reference — not a constraint**: WCAG AA body-text contrast is 4.5:1.**Reference — not a constraint**: Without user/template colors, propose project-specific directions from content and style. `scripts/config.py` industry colors and dominant/support/accent hierarchy are recall aids, never default locks, ratios, or color-count quotas.@@ -365,8 +367,7 @@ composition, resolve each page's complete semantic carrier mix—backgroundfield, editable text and optional lettering, native-geometry/relationship jobs,photos/scenes/illustrations/icons, and applicable visualizations—beforederiving §VIII resource rows. Decide the primary, structural, and supporting-jobs together; do not finish a text/container layout and then treat the other-families as optional decoration. Use existing §VI/§VIII/§IX fields: keep the+jobs together. Use existing §VI/§VIII/§IX fields: keep theordinary icon basis and prepared-pool plan in §VI, and add an image, lettering,or illustrated-icon resource to §VIII only when the page mix assigns it aplausible job. This creates no new field or candidate inventory; omitting any@@ -496,7 +497,7 @@ custom; neither role globs a detail catalog (see## 3. Color Selection Reference-Do not start from a universal palette. Precedence is user / brand → active template → project-specific proposal; `scripts/config.py` industry anchors are optional recall. Keep body-text contrast at least 4.5:1; color count and distribution follow encoding, style, and natural assets, not a quota.+Do not start from a universal palette. Precedence is user / brand → active template → project-specific proposal; `scripts/config.py` industry anchors are optional recall. Color count and distribution follow encoding, style, and natural assets.Lock the stable role set the deck needs, including recurring neutrals such as `surface`, `grid`, `scrim`, `overlay`, or `block-shade`. These are identity anchors, not an exhaustive paint list. Executor may derive tints, shades, alpha, gradients, and effects, preserve necessary natural asset colors, and add sparse page-local accents for differentiation or ornament. Such accents must not form a competing/recurring palette; Strategist owns reusable positive / warning / negative roles.diff --git a/skills/ppt-master/references/svg-effects.md b/skills/ppt-master/references/svg-effects.mdindex 7b3ac4de..6c8fba5b 100644--- a/skills/ppt-master/references/svg-effects.md+++ b/skills/ppt-master/references/svg-effects.md@@ -28,14 +28,13 @@ rhythm, and style; apply those that materially help.| Aesthetic fit | Locked or Quick-resolved `visual_style` / `visual_style_behavior` || Per-page choice | Content purpose, hierarchy, legibility, semantics, and rhythm |-**Mandatory — job-first effect selection**: establish the editable semantic-skeleton first, then diagnose effect jobs before treating the page as complete.-Plain construction remains valid only when that diagnostic finds no unresolved-visual job.+**Reference — job-first effect selection**: establish the editable semantic+skeleton first; the Visual Job Router below lists the visual jobs an effect can+serve. Plain construction remains valid.| Pass | Decision ||---|---|-| Skeleton / diagnose | Establish native information, relationships, and hierarchy. Before completion, check image/text integration, plane separation, focus, state/direction, material/style, and the recurring motif; keep plain construction when none needs treatment. |+| Skeleton / diagnose | Establish native information, relationships, and hierarchy. Image/text integration, plane separation, focus, state/direction, material/style, and the recurring motif are the jobs an effect can serve; plain construction stays valid when none needs treatment. || Surface / select | Name the target, confirm its owning subsection and fidelity, and let the Router recall candidates. Choose a compatible technique that fully performs the job; prefer simpler/native-stable alternatives only when communication is equal. `Approximate` requires review, not automatic rejection. || Integrate / stop | Align paint, contour, light, hierarchy, and z-order; combine only techniques with different jobs. Check legibility, editability, density, fidelity, and style; simplify failures, use legal alternatives, and bake only the smallest pixel-dependent layer. Keep authoritative text/data native. |@@ -341,14 +340,13 @@ uses one deliberate alternative direction)**: every `feOffset` shadow on oneslide shares the same `dx`/`dy` direction (default `dx="0"`,`dy="4"`–`dy="8"`, light from upper front). Contradictory shadow directionsmake one plane read as several incompatible surfaces. A deliberate upward-paper-layer treatment flips every affected layer together; never mix-directions on the same plane.+paper-layer treatment flips every affected layer together, so one plane keeps+one light direction.**Reference — not a constraint**: use no more elevation categories than thehierarchy needs; a page may reuse one category across several related objects.-Do not lift every peer card or stack strong shadow, border, gradient, and tint-on one container. Same-family colored shadow is reserved for a focal accent.-On dark backgrounds, prefer a light hairline or restrained glow; never glow body copy.+Same-family colored shadow is reserved for a focal accent.+On dark backgrounds a light hairline or restrained glow separates surfaces; glow on body copy reduces legibility.For older/strict renderers, replace a filter with two or three offsettranslucent shapes behind the object:alpha `0.03–0.05`, increasing offset/radius, and optional same-family tint near@@ -638,12 +636,9 @@ respective sections; they do not weaken those contracts.| Shadow/glow | §6.4 filter on `<text>` only | Shape shadow / run glow; `Approximate` || Native bullet | Leading `· • ● ▪ ■ ◆ ◇ ◦ ‣` + non-empty content | `·`/`•` → `•`; others unchanged; color/alpha from marker run; font/size follow text |-**Default — lift key information (may override when uniform treatment is-deliberate)**: In prose, lift numerical results, explicit contrasts, and one or-two load-bearing nouns per sentence with bold `<tspan>` runs in the locked or-Quick-resolved accent. Keep connectives, routine verbs, non-load-bearing nouns,-decorative adjectives, and structural copy neutral; reserve green/red for-actual polarity.+**Inline emphasis**: bold or accent-colored `<tspan>` runs lift numerical+results, explicit contrasts, or a load-bearing noun inside prose; green/red+conventionally read as polarity.```xml<!-- Uniform: the two results disappear into the sentence. -->@@ -657,8 +652,7 @@ actual polarity.</text>```-**Default — semantic underline (may override when another cue is clear)**:-Reserve it for links, key terms, or local emphasis—not decoration.+**Underline**: conventionally marks links, key terms, or local emphasis.```xml<!-- Key term -->@@ -683,12 +677,11 @@ text-on-path authoring.baseline-shift="sub" font-size="14">2</tspan></text>```-Use strikethrough for removed/former values; it is ordinary notation, not a+Strikethrough conventionally marks removed/former values; it is ordinary notation, not astyle-exclusive effect. Imported double underline/strike normalizes to single.Bullet detection allows optional leading whitespace, requires non-empty content,and leaves non-leading decorative glyphs as ordinary text.-Keep body tracking normal; CJK tracking defaults near/below 2% of font size and-above 5% triggers review. Text outline is solid only. `textPath`, masks, blend+CJK tracking defaults near/below 2% of font size and above 5% triggers review. Text outline is solid only. `textPath`, masks, blendmodes, generated effects, and text-image knockouts are outside editable text.---@@ -970,9 +963,9 @@ back-to-front and omit every layer without a distinct job.|---|---|---|| Cover | Hero field → optional scrim/wash → purposeful opening/contour → native title, optionally paired with a prepared decorative-lettering image | Stop when copy is safe and title/field read together || Divider | Image band or quiet field → restrained wash → recurring geometry → number/title | Reuse deck language; add no effect family |-| Text-led explanation | Quiet field → recurring material/contour → native hierarchy → optional local emphasis | Emphasis clarifies the argument, never decorates body copy |-| Process / system | Context field → native relation lines → nodes/labels → optional state/direction focus | Every connector stays semantic; atmosphere must not obscure flow |-| Evidence / metric | Context field → local contrast → native leaders/labels/metric → optional focus/elevation | Claims stay native; atmosphere must not weaken evidence |+| Text-led explanation | Quiet field → recurring material/contour → native hierarchy → optional local emphasis | Emphasis sits on the argument's load-bearing runs |+| Process / system | Context field → native relation lines → nodes/labels → optional state/direction focus | Every connector stays semantic |+| Evidence / metric | Context field → local contrast → native leaders/labels/metric → optional focus/elevation | Claims stay native || Comparison | Matched planes → optional shared wash/divider → matched labels → one difference marker | Keep crop, elevation, and paint symmetric unless asymmetry is the claim || Closing / CTA | Receded field → echoed contour/gradient → native action → optional raised accent | Add no effect family or competing image || Cross-page motif | Reuse contour, gradient direction, line language, texture, or light logic; vary scale, crop, or position by page job | Preserve recognition without copying the page or adding novelty effects |diff --git a/skills/ppt-master/scripts/project_management/project_specs.py b/skills/ppt-master/scripts/project_management/project_specs.pyindex 1cc45064..5b89b5ac 100644--- a/skills/ppt-master/scripts/project_management/project_specs.py+++ b/skills/ppt-master/scripts/project_management/project_specs.py@@ -334,8 +334,9 @@ def parse_spec_lock_artifact() -> list[dict[str, object]]:"""Parse one execution lock and normalize supported legacy image rows.- New locks use ``- <key>: <path> | source=... | pattern=... | crop=...``.- Some versioned projects instead placed the image path before the colon.+ Current locks use ``- <key>: <path> | source=... | crop=...`` and may retain+ the legacy ``pattern=...`` projection. Some versioned projects instead+ placed the image path before the colon.Preserve those projects by projecting the key path back into the value soevery consumer sees the same path-first image value."""diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.mdindex 3b49655a..5122667a 100644--- a/skills/ppt-master/workflows/generate-pptx.md+++ b/skills/ppt-master/workflows/generate-pptx.md@@ -618,7 +618,7 @@ Read the exact execution references named by this deck's retainedconstruction block plus the resolved mode/style detail files as one batch:```Read ${SKILL_DIR}/references/shared-standards-core.md # REQUIRED: SVG compatibility + shared aesthetic/leading baseline-Read ${SKILL_DIR}/references/svg-effects.md # REQUIRED: §6.1 job diagnostic + effects/construction vocabulary+Read ${SKILL_DIR}/references/svg-effects.md # REQUIRED: effects/construction vocabulary (§6.1 Visual Job Router as recall)Read ${SKILL_DIR}/references/native-shape-authoring.md # REQUIRED: native-shape selection and Boolean constructionRead ${SKILL_DIR}/references/preset-shape-vocabulary.md # REQUIRED: complete 187-name authoring vocabularyRead ${SKILL_DIR}/references/executor-structure.md # REQUIRED: qualitative relationship and topology grammar@@ -628,7 +628,7 @@ Read ${SKILL_DIR}/references/modes/<resolved-id>.md # one preset id, or eRead ${SKILL_DIR}/references/visual-styles/<resolved-id>.md # one preset id, or each `visual_style_references` id```-Keep the core's shared visual-quality defaults and `svg-effects.md` §6.1 job diagnostic active during page authoring, with its Visual Job Router as recall; they are not passive compatibility reading. Explicit user/template requirements and the locked style override compatible aesthetic defaults, never technical Required / Forbidden boundaries.+Keep the core's shared visual-quality defaults active during page authoring, with `svg-effects.md` §6.1's Visual Job Router as recall; they are not passive compatibility reading. Explicit user/template requirements and the locked style override compatible aesthetic defaults, never technical Required / Forbidden boundaries.> Read only the role core, always-on construction references, exact locked detail files, and conditionally triggered modules below. The selection indexes remain planning-only. A preset reads its one locked file. For `custom`, read only the exact bases named by optional `mode_references` / `visual_style_references`: apply one under the corresponding behavior, or synthesize several by their stated contributions. If absent, read no preset file and follow the behavior directly. Do not infer adjacent bases, glob a catalog, or blend unselected identities.diff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.mdindex 75a24433..103825f2 100644--- a/skills/ppt-master/workflows/profiles/quick-generate.md+++ b/skills/ppt-master/workflows/profiles/quick-generate.md@@ -384,8 +384,7 @@ the same transient-roster resolution and before resource preparation orcoordinates, decide each page's complete mix of background, editable text andoptional lettering, native geometry and lines, photos/scenes,illustrations/icons, and applicable visualizations. Decide their primary,-structural, and supporting jobs together; do not finish a text/container layout-and then treat the other families as optional decoration. Only selected image,+structural, and supporting jobs together. Only selected image,lettering, or illustrated-icon jobs with plausible page roles create imageresources; ordinary SVG/emoji icons retain their curated-pool boundary.Omitting any carrier is valid after this review; Quick speed, resolved style,@@ -644,7 +643,7 @@ Chart/Table reference and final information model are independent loadingsignals; load every applicable authority. Selection never makes an objectnative-ready or replaces the per-page Structure decision.-Keep the core's shared visual-quality / leading defaults and `svg-effects.md` §6.1 job diagnostic active while authoring, with its Visual Job Router as recall. Explicit user/template requirements and the resolved style override compatible aesthetic defaults, never technical Required / Forbidden boundaries, carrier eligibility, or native capability discovery. Treat selected style composition examples as generative vocabulary rather than a finite layout menu.+Keep the core's shared visual-quality / leading defaults active while authoring, with `svg-effects.md` §6.1's Visual Job Router as recall. Explicit user/template requirements and the resolved style override compatible aesthetic defaults, never technical Required / Forbidden boundaries, carrier eligibility, or native capability discovery. Treat selected style composition examples as generative vocabulary rather than a finite layout menu.**Per-page execution anchors**: apply the transient core-message, typography-role, semantic-color, body-frame, density, and composition anchors resolved in §2 while authoring; they guide the current run without creating a persisted planning artifact.