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(effects): make the Visual Job Router recall, not a gate
hugohe39d3da19d73a9
diff --git a/docs/technical-design.md b/docs/technical-design.mdindex e7cd8ef3..383c2a93 100644--- a/docs/technical-design.md+++ b/docs/technical-design.md@@ -154,7 +154,7 @@ optional native-object and narration flags.For every workflow that authors or redesigns visual slides through SVG, `svg_output/` is the complete page-design authority, but SVG here means project-canonical SVG accepted by the project contract—not any SVG a browser can render. Every visible text, image, shape, diagram, chart/table fallback, background, and template-derived layout element that should appear on a slide must already exist in that page SVG or be explicitly referenced by it. In the default pipeline, templates, `design_spec.md`, and `spec_lock.md` guide SVG authoring; `quick-generate` instead uses active-context decisions and explicit SVG values. The exporter never uses planning inputs as a second visual layer that fills in missing page content.-The always-loaded core also owns the fallback visual-quality and numeric leading defaults. Explicit user, template / brand, and locked-style requirements override compatible aesthetic defaults; when those authorities are silent, hierarchy, typography, alignment, negative space, purposeful assets, and the core's density-based leading ranges still apply. Default and Quick Generate always load `svg-effects.md` and run its Visual Job Router before completing a page. None of these aesthetic choices can override a technical Required / Forbidden boundary.+The always-loaded core also owns the fallback visual-quality and numeric leading defaults. Explicit user, template / brand, and locked-style requirements override compatible aesthetic defaults; when those authorities are silent, hierarchy, typography, alignment, negative space, purposeful assets, and the core's density-based leading ranges still apply. Default and Quick Generate always load `svg-effects.md` and run its §6.1 job diagnostic before completing a page, with the Visual Job Router as recall for what that diagnostic finds. None of these aesthetic choices can override a technical Required / Forbidden boundary.Minimal semantic markers do not weaken that closure. Free-design, brand-only, `quick-generate`, and `template_reuse_scope: style` pages use flat Slide-local ownership: every represented object stays on the Slide and no Master/Layout identity, layer, or placeholder metadata is authored. Default export materializes one clean project-owned Master plus one Blank Layout from the current color/typography lock; lockless `quick-generate` uses converter-default theme scaffolding. Neither promotes Slide content. Only `template_reuse_scope: mirror|layout` uses the structured route, where every new page declares its Master/Layout identity from the first SVG draft. Fixed Master/Layout visuals are direct atomic root children, while reusable content slots are top-level groups with explicit design-zone bounds and one compatible carrier; composite `object` regions use an explicit proxy fallback, and zero-slot Layouts are valid. `data-pptx-role` is reserved for the few structural page-frame objects whose package or animation behavior is not already expressed by specialized metadata. A semantic-legacy template package is not upgraded in place or accepted as a structured Step 3 input: create a new workspace through `create-template`, using a native PPTX's still-present package facts or an old SVG's visuals only as reference, then author new pages through the AI-derived application route. A flat project is intentionally unmapped, not legacy. Export never infers, repairs, or migrates Master/Layout structure or placeholders.diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.mdindex 786d0794..693ce2ab 100644--- a/docs/zh/technical-design.md+++ b/docs/zh/technical-design.md@@ -124,7 +124,7 @@ narration 标记。凡是通过 SVG 创作或重新设计页面的工作流,`svg_output/` 都是完整的页面设计权威,但这里的 SVG 专指项目合同接受的项目规范化 SVG,而不是任意浏览器可渲染的 SVG。最终幻灯片中应出现的文字、图片、形状、图示、图表 / 表格 fallback、背景和模板派生布局元素,都必须已经存在于对应页面 SVG 中,或被它明确引用。默认流程由模板、`design_spec.md` 和 `spec_lock.md` 指导 SVG 创作;`quick-generate` 则使用当前上下文决策和 SVG 中的显式值。导出器不能把规划输入当成第二层画面来源,在导出阶段补入 SVG 缺失的页面内容。-始终必读的 core 还负责兜底视觉质量与数值行距默认值。显式用户要求、模板 / 品牌和已锁定风格可以覆盖相容的美学默认;这些上层权威未规定时,层级、字体、对齐、留白、有目的的素材使用以及按密度设置的行距范围仍然生效。Default 与 Quick Generate 始终加载 `svg-effects.md`,并在完成每页前运行 Visual Job Router。任何美学选择都不能覆盖技术上的 Required / Forbidden 边界。+始终必读的 core 还负责兜底视觉质量与数值行距默认值。显式用户要求、模板 / 品牌和已锁定风格可以覆盖相容的美学默认;这些上层权威未规定时,层级、字体、对齐、留白、有目的的素材使用以及按密度设置的行距范围仍然生效。Default 与 Quick Generate 始终加载 `svg-effects.md`,并在完成每页前运行 §6.1 职能诊断;Visual Job Router 是诊断结果的召回入口。任何美学选择都不能覆盖技术上的 Required / Forbidden 边界。最小语义标记不会削弱这条闭包。自由设计、brand-only、`quick-generate` 和 `template_reuse_scope: style` 页面都采用 flat 的 Slide 本地所有权:所有已表达对象保持在 Slide,不创作 Master/Layout 身份、分层或 placeholder metadata。默认导出器根据当前配色/字体 lock 生成一个属于本项目的干净 Master 和一个 Blank Layout;无 lock 的 `quick-generate` 使用转换器默认 theme 壳。两者都不会提升任何 Slide 内容。只有 `template_reuse_scope: mirror|layout` 使用 structured 路线,每张新页面从第一版 SVG 起就声明 Master/Layout 身份。固定 Master/Layout 视觉是根节点直接原子元素;可复用内容槽位是顶层 group,带显式设计区域 bounds 和一个兼容 carrier;复合 `object` 区域走显式 proxy 降级,Layout 也允许零槽。`data-pptx-role` 只补充专用 metadata 尚未表达的少量页面框架、package 或动画行为。带旧结构语义的模板包不能原地升级,也不能作为 Step 3 的 structured 输入:先通过 `create-template` 创建新工作区;原生 PPTX 只提供包内仍然存在的事实,旧 SVG 只作为视觉参考;随后由 Generate PPTX 路线按照 AI 推导的应用计划创作新页面。flat 项目是有意不带 mapping,不算 legacy。导出器不推断、修补或迁移 Master/Layout 结构与 placeholder。diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.mdindex ba1466ad..bbf6d9fb 100644--- a/skills/ppt-master/references/executor-base.md+++ b/skills/ppt-master/references/executor-base.md@@ -35,10 +35,11 @@ Evaluate branches from each object's actual information model, not only from a C**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-and Visual Job Router before finalizing; 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 additionally loads-[`animations.md`](./animations.md) §3.1 before authoring both endpoints.+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+additionally loads [`animations.md`](./animations.md) §3.1 before authoring+both endpoints.**Hard rule — discovery does not expand compatibility**: Follow`svg-effects.md` syntax and fallbacks; unsupported source/backdrop blur, blenddiff --git a/skills/ppt-master/references/shared-standards-core.md b/skills/ppt-master/references/shared-standards-core.mdindex e228a32d..4def8381 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 run the already-loaded [`svg-effects.md`](./svg-effects.md) §6.1 Visual Job Router before completing each page; apply a compatible technique only for a diagnosed visual job.+**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.**Fidelity labels**:diff --git a/skills/ppt-master/references/svg-effects.md b/skills/ppt-master/references/svg-effects.mdindex a47afa75..1bcb678e 100644--- a/skills/ppt-master/references/svg-effects.md+++ b/skills/ppt-master/references/svg-effects.md@@ -10,8 +10,9 @@ Authority for advanced paint, effects, transforms, freeform/radial geometry, and**Mandatory**: Default and Quick Generate read this file completely before SVGauthoring and keep its compatible techniques in active construction vocabulary.-Before finalizing each page, run the §6.1 selection procedure and Visual Job-Router. Use §6.13 when diagnosed jobs benefit from one coordinated page recipe.+Before finalizing each page, run the §6.1 selection procedure, with the Visual+Job Router as recall for the jobs it diagnoses. Use §6.13 when diagnosed+jobs benefit from one coordinated page recipe.**Default — situational use (may override when plain construction is stronger)**:“Advanced” means capability depth, not an effect quota. During page authoring,@@ -22,7 +23,7 @@ rhythm, and style; apply those that materially help.| Decision layer | Authority ||---|---|-| Technical validity | Required / Forbidden / Conditional contracts in this file |+| Technical validity | Required / Forbidden / Conditional contracts in this file, over the shared core's closed authoring surface, the route's other required construction references, and any triggered module || Project values | Default: `<project_path>/spec_lock.md` anchors plus retained Design Spec/page context; Quick: anchors resolved in the current context || Aesthetic fit | Locked or Quick-resolved `visual_style` / `visual_style_behavior` || Per-page choice | Content purpose, hierarchy, legibility, semantics, and rhythm |@@ -35,7 +36,7 @@ visual job.| 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. |-| Surface / select | Name the target, confirm its owning subsection and fidelity, then use the Router. 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. |+| 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. |**Default — one dominant composition scaffold (may override when a second@@ -47,9 +48,14 @@ simplify any competing scaffold without a separate communication job.#### Visual Job Router-**Reference — not a quota**: route diagnosed problems through this table. A+**Reference — not a quota**: recall candidates for a diagnosed problem from+this table. Apage may use no listed technique, one technique, or several techniques with-different jobs.+different jobs. The table recalls constructions rather than bounding them: one+it never names is equally valid when it satisfies every applicable technical+contract — the shared core's closed authoring surface, this file, the route's+other required construction references, and any triggered module. Those+contracts are the boundary; membership in this table is not.| Diagnosed visual problem | Candidate technique | Authority / stop ||---|---|---|diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.mdindex 80936854..a2187b3c 100644--- a/skills/ppt-master/workflows/generate-pptx.md+++ b/skills/ppt-master/workflows/generate-pptx.md@@ -613,7 +613,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: Visual Job Router + effects/construction vocabulary+Read ${SKILL_DIR}/references/svg-effects.md # REQUIRED: §6.1 job diagnostic + effects/construction vocabularyRead ${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@@ -622,7 +622,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 Visual Job Router active during page authoring; 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 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.> 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 0e57ae3a..5afcb896 100644--- a/skills/ppt-master/workflows/profiles/quick-generate.md+++ b/skills/ppt-master/workflows/profiles/quick-generate.md@@ -604,7 +604,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 Visual Job Router active while authoring. 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 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.**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.