Skip to content

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(svg-policy): centralize exception-driven authoring constraints

hugohe321d6d2f3c071
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 030aca42..a95ee641 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -90,24 +90,16 @@ If you're unsure, open an issue to ask — that's always welcome.
## SVG Guidelines
-If your contribution involves SVG files, follow the technical constraints documented in [CLAUDE.md](./CLAUDE.md):
-
-- Do not use: `mask`, `<style>`, `class`, external CSS, `<foreignObject>`, `<animate*>`, `<script>`
-- Paint colors may use supported CSS forms: named colors, `rgb()` / `rgba()`,
- `hsl()` / `hsla()`, and 3/4/6/8-digit HEX. Embedded alpha multiplies with
- `opacity`, `fill-opacity`, or `stroke-opacity` during native export
-- `marker-start` / `marker-end` are conditionally allowed — see `shared-standards.md` §1.1 (must live in `<defs>`, `orient="auto"`, shape must be triangle / diamond / oval)
-- `clipPath` on `<image>` is conditionally allowed — see `shared-standards.md` §1.2 (must live in `<defs>`, single shape child, only on `<image>` elements)
-- Static local `<use>` / `<symbol>` reuse is conditionally allowed — see
- `shared-standards.md` §1.3. Use only exact same-document `href="#id"` or
- `xlink:href="#id"` references to the listed shape/group/text/image targets.
- Symbol instances require a valid `viewBox` and positive unitless/`px`
- `width`/`height`; `x`/`y` are unitless/`px`. External, missing, conflicting,
- circular, or duplicate-ID references; `slice` / `refX` / `refY`; reusable
- PPTX layer/native/placeholder metadata; and non-exact internal `url(#id)`
- syntax are rejected. Reference depth is capped at 64 and expansion at 10,000
- instances per SVG. PPTX-to-SVG import does not reconstruct `<use>`.
-- All SVGs must use the correct `viewBox` for the target canvas format
+If your contribution involves SVG files, follow the canonical authoring and
+PPTX-compatibility contract in
+[`shared-standards.md`](./skills/ppt-master/references/shared-standards.md).
+This guide does not duplicate its required, forbidden, or conditional entries.
+
+Validate the affected SVG file or directory before submitting:
+
+```bash
+python3 skills/ppt-master/scripts/svg_quality_checker.py <file_or_directory>
+```
## Reporting Bugs
diff --git a/docs/roadmap.md b/docs/roadmap.md
index ac0577fa..7db6191a 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -40,7 +40,7 @@ The past two months' structural capability growth. Single flags / incremental po
- **Kubernetes Blueprint example deck shipped** ([`examples/ppt169_kubernetes_blueprint_2026/`](../examples/ppt169_kubernetes_blueprint_2026/)) — second of the three P0 capability-backing demos: isometric technical-drawing aesthetic + blueprint cyan/amber palette + hand-authored SVG geometry (no raster images) + custom drawing-in animation; 10-page Kubernetes architecture walkthrough stressing geometric shape generalization and chart-structure extensibility
- **AI image `custom` escape hatch** — `rendering` / `palette` / hero composition each accept `custom` + a one-paragraph `*_behavior` prose, replacing the false "default to vector-illustration / cool-corporate" fallback; end-to-end contract spans [`image-renderings/_index.md`](../skills/ppt-master/references/image-renderings/_index.md) §1.5, [`image-palettes/_index.md`](../skills/ppt-master/references/image-palettes/_index.md) §2, Strategist h.5 hard-rule (≤1 custom per dimension; one candidate may carry both), spec_lock fields, and Image_Generator Step 2 consumption branch
- **Template architecture: three-kind consolidation** ([`docs/templates-architecture.md`](./templates-architecture.md)) — brand / layout / deck split into three independent dirs with per-kind schemas + segment-level fusion + git-style conflict resolution; SKILL.md Step 3 dispatches per `kind`, trigger rule remains "explicit path only"
-- **Pattern fill PPTX safety net** — `svg_quality_checker.py` now warns on `<pattern>` without `data-pptx-pattern` (silent fallback to `ltUpDiag`) and errors on values outside OOXML `ST_PresetPatternVal` (schema-failed PPTX that won't open); `shared-standards.md §7` documents the closed preset enum and the required `<rect fill="<bg>"/>` child convention
+- **Pattern fill PPTX safety net** — `svg_quality_checker.py` now warns on `<pattern>` without `data-pptx-pattern` (silent fallback to `ltUpDiag`) and errors on values outside OOXML `ST_PresetPatternVal` (schema-failed PPTX that won't open); `shared-standards.md §7` documents the closed preset enum and color resolution from importer metadata or child paint
- **LaTeX math formula rendering shipped** ([`scripts/latex_render.py`](../skills/ppt-master/scripts/latex_render.py)) — Strategist locks one of three policies (`mixed` / `render-all` / `text-only`) inside the Typography confirmation and writes an explicit `images/formula_manifest.json`; the renderer walks a codecogs → quicklatex → mathpad → wikimedia fallback chain and emits transparent PNGs that land in §VIII as `Acquire Via: formula` / `Status: Rendered` rows; formula-heavy decks (academic / engineering / educational) finally have a native rendering route. Formula selection is a Strategist decision — the renderer never scans source files for `$...$` markers
- **Live preview direct editing — L1 / L2 / L3** ([`workflows/live-preview.md`](../skills/ppt-master/workflows/live-preview.md)) — the browser editor gains deterministic in-place edits with no AI round-trip: text content (L1), presentation attributes like fill / stroke / font-size (L2), and on-canvas geometry (L3) — drag a selected element to move it, arrow-key nudge (`Shift` = 10px), multi-select, plus a right-click overlap picker for stacked shapes. Edits stage with `Ctrl+Z` undo + coalescing and write to `svg_output/` on **Apply changes**; moves persist through finalize / export (moved text frames, promoted multi-line tspans, repositioned icons all reproduce in the PPTX). Re-export stays chat-driven; on-canvas resize handles are not yet implemented (resize via the geometry inputs)
diff --git a/docs/technical-design.md b/docs/technical-design.md
index 8cbd84b4..2e337c63 100644
--- a/docs/technical-design.md
+++ b/docs/technical-design.md
@@ -172,9 +172,13 @@ SVG wins because it shares the same world view as DrawingML: both are absolute-c
| `linearGradient` / `radialGradient` | `<a:gradFill>` |
| `fill-opacity` / `stroke-opacity` | `<a:alpha>` |
+This table shows conceptual counterparts, not an authoring allowlist or a
+promise of lossless semantics. Restricted or approximate mappings are owned by
+[`shared-standards.md`](../skills/ppt-master/references/shared-standards.md).
+
The conversion is a translation between two dialects of the same idea — not a format mismatch.
-SVG is also the only format that simultaneously satisfies every role in the pipeline: **AI can reliably generate it, humans can preview and debug it in any browser, and scripts can precisely convert it** — all before a single line of DrawingML is written.
+SVG is also the only format that simultaneously satisfies every role in the pipeline: **AI can reliably generate it, humans can preview and debug it in any browser, and scripts can translate it under an explicit compatibility contract** — all before a single line of DrawingML is written.
---
@@ -352,32 +356,32 @@ The catalog of *how an image is placed on a slide* (full vocabulary in [`referen
**Why composition flows through Strategist's resource list, not just Executor's improvisation.** The `Layout pattern` column in `§VIII Image Resource List` accepts a `#<id> + #<id> ...` expression — Primary id plus optional Modifier ids — so the composition is declared *before* SVG generation, audited by `svg_quality_checker`, and survives session re-entry. Pushing composition onto Executor alone would lose it on context compression in long decks; encoding it in the spec_lock-adjacent resource list makes it a piece of the design contract.
-**Why true hard constraints stay upstream.** Cross-cutting technical constraints (`<clipPath>` only on `<image>`, no `<mask>`, supported CSS paint grammar, alpha-effect routing) live exclusively in [`shared-standards.md`](../skills/ppt-master/references/shared-standards.md). The layout patterns file points at them with one-line references rather than restating — so when a constraint relaxes (e.g., a new DrawingML feature becomes reliable), only one file changes, and a stale duplicate in patterns can't silently keep enforcing the old rule.
+**Why true hard constraints stay upstream.** Cross-cutting SVG authoring and PPTX-compatibility exceptions live exclusively in [`shared-standards.md`](../skills/ppt-master/references/shared-standards.md). The layout patterns file points there rather than restating the contract — so when a constraint changes, only one file changes, and a stale duplicate in patterns cannot silently keep enforcing the old rule.
---
-## SVG Constraints: Banned Features and Conditional Allowances
+## SVG Compatibility Boundary
-PowerPoint's DrawingML is a strict subset of what SVG can express. The Executor operates inside an empirically-grown blacklist (mask, style/class, `@font-face`, foreignObject, textPath, animate*, script/iframe …) plus narrow conditional allowances for `marker-start`/`marker-end`, image-only `clip-path`, and static same-document `<use>` / `<symbol>` reuse. The authoritative list and exact per-feature constraints — including the substitute-effect routing table for `<mask>` (gradient overlays, clipPath, filter shadow, source-image bake-in) — live in [`references/shared-standards.md`](../skills/ppt-master/references/shared-standards.md).
+PowerPoint's DrawingML is a strict subset of what SVG can express. Within the converter's implemented vocabulary, ordinary SVG is allowed by default. Only rejected constructs and features that require constrained mappings are enumerated in [`references/shared-standards.md`](../skills/ppt-master/references/shared-standards.md), the sole authority for their accepted forms and limits; this architecture document deliberately does not reproduce them.
-**Why local `<use>` is compile-time reuse, not a retained PowerPoint object.** The accepted form is an exact same-document `href="#id"` or `xlink:href="#id"` targeting `symbol`, `g`, `use`, `rect`, `circle`, `ellipse`, `line`, `path`, `polygon`, `polyline`, `text`, or `image`; internal references use exact `url(#id)` fragments. `x` / `y` are finite unitless or `px` values. A symbol requires a valid `viewBox` whose dimensions are positive, positive unitless/`px` instance `width` / `height`, and either aligned `meet` or plain `none`; `slice`, `refX`, and `refY` are rejected. Symbol artwork must stay inside the `viewBox` because expansion does not reproduce overflow clipping. External, missing, conflicting, circular, and duplicate-ID references fail validation, as does reuse of `data-pptx-layer*`, `data-pptx-native*`, or `data-pptx-placeholder*` structure. The pipeline recursively materializes the subtree and rewrites cloned IDs before export. PPTX-to-SVG import returns the expanded primitives rather than reconstructing the authoring-time `<use>` graph.
+**Why local reuse is compile-time reuse, not a retained PowerPoint object.** The canonical contract defines accepted authoring forms, and the shared validator enforces them. After validation, the pipeline recursively materializes each referenced subtree and rewrites clone-local IDs before export. PPTX-to-SVG import therefore returns expanded primitives rather than reconstructing the authoring-time reuse graph.
The architectural reasons worth knowing here:
-- **Why a blacklist, not a whitelist.** SVG is a wide spec; enumerating allowed features would force constant maintenance as the Executor finds new useful constructs. The blacklist captures the narrow set whose semantics have no DrawingML representation, leaving everything else implicitly available.
-- **Why empirical, not derived from spec.** The list grew from real PPT export failures, not from reading the OOXML spec. Several features (e.g., `<mask>`) are theoretically expressible in DrawingML but practically unreliable across PowerPoint versions; the blacklist reflects the actually-shippable subset.
-- **XML well-formedness traps.** Two cross-cutting gotchas independent of DrawingML: typography must use raw Unicode (`—`, `→`, `©`, NBSP) since HTML named entities (`&mdash;`) are XML-illegal in SVG, and reserved XML chars (`& < >`) must be entity-escaped or `R&D` will abort the export. These bite often enough to flag at the architecture level.
-- **The blacklist runs before post-processing.** `svg_quality_checker.py` enforces it on `svg_output/`; post-processing rewrites SVG and would mask source-level violations. Fixes are always re-authoring in the Executor — there is intentionally no auto-fix mode (see Quality Gate).
+- **Why an exception list, not an allowlist.** SVG is a wide specification; enumerating every allowed feature would require constant maintenance as the converter grows. A centralized exception list leaves ordinary implemented constructs available by default.
+- **Why empirical, not derived from spec.** The compatibility boundary grew from real PPT export failures, not from reading the OOXML specification. Some theoretically representable effects remain unreliable across PowerPoint versions, so the contract reflects the actually shippable subset.
+- **XML well-formedness remains a precondition.** Malformed SVG fails before DrawingML compatibility matters. The canonical contract owns the accepted authoring forms so XML guidance cannot drift across architecture and prompt documents.
+- **Compatibility validation runs before post-processing.** `svg_quality_checker.py` evaluates `svg_output/`; post-processing rewrites SVG and could mask source-level violations. Fixes are always re-authoring in the Executor — there is intentionally no auto-fix mode (see Quality Gate).
---
## Quality Gate
-**Why a checker exists at all.** SVG generated by an LLM is not deterministic — banned features creep in over long decks and only surface when `svg_to_pptx` aborts mid-conversion or PowerPoint silently drops elements. The checker turns "PowerPoint export failed at page 14" into "the Executor used `<style>` on page 14, regenerate it" — an order-of-magnitude faster diagnosis loop, which is what makes long decks economically feasible to iterate on.
+**Why a checker exists at all.** SVG generated by an LLM is not deterministic — compatibility violations creep in over long decks and only surface when `svg_to_pptx` aborts mid-conversion or PowerPoint silently drops elements. The checker turns "PowerPoint export failed at page 14" into "page 14 violates the SVG compatibility contract" — an order-of-magnitude faster diagnosis loop, which is what makes long decks economically feasible to iterate on.
**Why placed before post-processing, not after.** Post-processing rewrites SVG (icon embedding, image inlining), which would mask source-level violations. Reading `svg_output/` directly catches the Executor's actual output, before any cleanup that might paper over a bug.
-**Severity model: errors block, warnings don't, and there is intentionally no auto-fix.** Errors require the Executor to re-author the offending page in context — a banned `<style>` element isn't a mechanical patch, because the Executor used it for a reason and the substitute (e.g., inline attributes) needs the same design intent re-applied. Auto-fix would silently lose that intent and ship a worse-looking page.
+**Severity model: errors block, warnings don't, and there is intentionally no auto-fix.** Errors require the Executor to re-author the offending page in context — a compatibility violation is not necessarily a mechanical patch, because the replacement must preserve the same design intent. Auto-fix would silently lose that intent and ship a worse-looking page.
**Why chart coordinate verification hangs off the same gate.** Chart pages have geometric correctness requirements (bar heights / pie sweep angles / axis tick positions) that aren't structural and aren't caught by SVG validity rules. The natural place to catch them is the same gate where the AI is asked to revisit its output — bundling the cognitive context "look at what you generated and fix it" into one phase, rather than splitting structural and geometric review into separate review rounds.
diff --git a/docs/zh/roadmap.md b/docs/zh/roadmap.md
index 4c427142..d78d9967 100644
--- a/docs/zh/roadmap.md
+++ b/docs/zh/roadmap.md
@@ -40,7 +40,7 @@
- **Kubernetes Blueprint 示例 deck 交付**([`examples/ppt169_kubernetes_blueprint_2026/`](../../examples/ppt169_kubernetes_blueprint_2026/)) — P0 三档第二档落地:等距工程图美学 + 蓝图青/琥珀色板 + 全手写 SVG 几何(无 raster 图)+ 自定义"逐笔绘制"动画,10 页 Kubernetes 架构走读实压「几何形状泛化 + chart 结构扩展性」
- **AI 图 `custom` 兜底出口** — `rendering` / `palette` / hero 构图三处允许声明 `custom` + 一段 `*_behavior` prose,替换原"找不到匹配就硬塞 vector-illustration / cool-corporate"的假兜底;端到端契约:[`image-renderings/_index.md`](../../skills/ppt-master/references/image-renderings/_index.md) §1.5 + [`image-palettes/_index.md`](../../skills/ppt-master/references/image-palettes/_index.md) §2 + Strategist h.5 hard-rule(每维 ≤1 custom,单候选可双 custom)+ spec_lock 字段 + Image_Generator Step 2 消费分支
- **Template 架构三分类收口**([`docs/zh/templates-architecture.md`](./templates-architecture.md)) — brand / layout / deck 三独立目录 + 每类独立 schema + 段级合成 + git-style 冲突解决;SKILL.md Step 3 按 kind 分支处理,触发规则仍是「显式路径才触发」
-- **Pattern 填充 PPTX 安全网** — `svg_quality_checker.py` 现在对未标 `data-pptx-pattern` 的 `<pattern>` 元素发 warning(会静默回退 `ltUpDiag` 斜纹)、对超出 OOXML `ST_PresetPatternVal` 枚举的值发 error(schema 校验失败 PPT 无法打开);`shared-standards.md §7` 落地了完整 preset 清单和 `<rect fill="<bg>"/>` 子元素约定
+- **Pattern 填充 PPTX 安全网** — `svg_quality_checker.py` 现在对未标 `data-pptx-pattern` 的 `<pattern>` 元素发 warning(会静默回退 `ltUpDiag` 斜纹)、对超出 OOXML `ST_PresetPatternVal` 枚举的值发 error(schema 校验失败 PPT 无法打开);`shared-standards.md §7` 落地了完整 preset 清单,以及从导入元数据或子元素 paint 解析颜色的合同
- **LaTeX 数学公式渲染上线**([`scripts/latex_render.py`](../../skills/ppt-master/scripts/latex_render.py)) — Strategist 在 Typography 确认中锁定 `mixed` / `render-all` / `text-only` 三档策略,显式写 `images/formula_manifest.json`;脚本走 codecogs → quicklatex → mathpad → wikimedia 四源 fallback chain,输出透明 PNG 进 §VIII 表的 `Acquire Via: formula` / `Status: Rendered` 行;公式密集型 deck(学术 / 工程 / 教学)首次拥有原生渲染路径,规则面禁止扫源文件 `$...$` 自动渲染(公式选取是 Strategist 决策)
- **实时预览直接编辑 — L1 / L2 / L3**([`workflows/live-preview.md`](../../skills/ppt-master/workflows/live-preview.md)) — 浏览器编辑器新增无需 AI 往返的确定性就地编辑:文字内容(L1)、fill / stroke / font-size 等样式属性(L2)、以及画布上的几何操作(L3)——在选中元素上拖拽即移动、方向键微调(`Shift` = 10px)、多选、加右键重叠选择器选取堆叠元素。编辑支持 `Ctrl+Z` 撤销 + 合并,点 **Apply changes** 写回 `svg_output/`;移动经 finalize / 导出保位(移动的 text、提升的多行 tspan、重定位的 icon 都在 PPTX 中如实再现)。重新导出仍由对话触发;画布上的缩放手柄尚未实现(缩放走几何输入框)
diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.md
index 721a42df..0bf6d98f 100644
--- a/docs/zh/technical-design.md
+++ b/docs/zh/technical-design.md
@@ -172,9 +172,11 @@ SVG 胜出,因为它与 DrawingML 拥有相同的世界观:两者都是绝
| `linearGradient` / `radialGradient` | `<a:gradFill>` |
| `fill-opacity` / `stroke-opacity` | `<a:alpha>` |
-转换不是格式错配,而是两种方言之间的精确翻译。
+这张表只展示概念对应关系,不是创作允许清单,也不承诺语义无损。受限或近似的映射统一由 [`shared-standards.md`](../../skills/ppt-master/references/shared-standards.md) 定义。
-SVG 也是唯一同时满足流程中所有角色需要的格式:**AI 能可靠地生成它,人能在任意浏览器里直接预览和调试,脚本能精确地转换它**——在生成任何 DrawingML 之前,设计稿就已经完全透明可见。
+转换不是格式错配,而是在两种结构相近的方言之间做翻译。
+
+SVG 也是唯一同时满足流程中所有角色需要的格式:**AI 能可靠地生成它,人能在任意浏览器里直接预览和调试,脚本能按明确的兼容合同转换它**——在生成任何 DrawingML 之前,设计稿就已经完全透明可见。
---
@@ -352,32 +354,32 @@ Strategist 阶段产出两份看起来冗余但服务不同对象的产物:
**为什么组合走 Strategist 资源列表,不只交给 Executor 临场发挥。** `§VIII 图片资源列表` 的 `Layout pattern` 列接受 `#<id> + #<id> ...` 表达式——Primary id 加可选 Modifier id——所以组合在 SVG 生成**之前**就被声明、被 `svg_quality_checker` 审计、并能在 session 重入后存活。把组合责任只压在 Executor 身上,长 deck 上下文压缩时就会丢;把它编码进 spec_lock 旁的资源列表,组合就成为设计契约的一部分。
-**为什么真正的硬约束留在上游。** 跨切的技术硬约束(`<clipPath>` 只能用在 `<image>` 上、禁 `<mask>`、受支持的 CSS 颜色语法、alpha 效果的路由表)独家住在 [`shared-standards.md`](../../skills/ppt-master/references/shared-standards.md)。版式词表只用一行指针指向它们,不复述——这样某条约束放开时(比如某个 DrawingML 特性变得可靠),只有一个文件要改,词表里也不会留下一份过期副本继续暗中强制旧规则。
+**为什么真正的硬约束留在上游。** 跨切的 SVG 创作与 PPTX 兼容性例外独家住在 [`shared-standards.md`](../../skills/ppt-master/references/shared-standards.md)。版式词表只指向这份合同,不再复述——这样规则变化时只有一个文件要改,词表里也不会留下一份过期副本继续暗中强制旧规则。
---
-## SVG 约束:禁用特性与条件允许
+## SVG 兼容性边界
-PowerPoint 的 DrawingML 是 SVG 表达力的严格子集。Executor 在一份经验生长起来的黑名单(mask、style/class、`@font-face`、foreignObject、textPath、animate*、script/iframe ……)里运行,外加对 `marker-start`/`marker-end`、仅 `<image>` 上的 `clip-path` 和同文档静态 `<use>` / `<symbol>` 复用的窄条件允许。权威清单和每条特性的具体约束——包括 `<mask>` 的替代效果路由表(渐变叠加、clipPath、filter shadow、源图烘焙)——住在 [`references/shared-standards.md`](../../skills/ppt-master/references/shared-standards.md)。
+PowerPoint 的 DrawingML 是 SVG 表达力的严格子集。在转换器已实现的词汇内,普通 SVG 默认允许。只有导出拒绝项与需要受限映射的能力才集中枚举在 [`references/shared-standards.md`](../../skills/ppt-master/references/shared-standards.md);它是接受形式与限制的唯一权威,本架构文档有意不再复述。
-**为什么本地 `<use>` 是编译期复用,不是 PowerPoint 保留对象。** 允许的引用必须是精确的同文档 `href="#id"` 或 `xlink:href="#id"`,目标仅限 `symbol`、`g`、`use`、`rect`、`circle`、`ellipse`、`line`、`path`、`polygon`、`polyline`、`text`、`image`,内部引用使用精确的 `url(#id)` 片段。`x` / `y` 只能是有限 unitless 或 `px` 值。`symbol` 必须有合法且维度为正数的 `viewBox`,实例必须提供正数 unitless/`px` `width` / `height`,并使用对齐的 `meet` 或纯 `none`;`slice`、`refX`、`refY` 会被拒绝。由于展开不会复现 overflow clipping,symbol 图形必须留在 `viewBox` 内。外部、缺失、冲突、循环、重复 ID 引用,以及对 `data-pptx-layer*`、`data-pptx-native*`、`data-pptx-placeholder*` 结构的复用都会校验失败。流水线会递归实体化子树并重写克隆 ID 后再导出;PPTX 回导只返回展开后的原语,不重建创作期 `<use>` 图。
+**为什么本地复用是编译期复用,不是 PowerPoint 保留对象。** 接受的创作形式由权威合同定义、共享校验器执行。校验通过后,流水线会递归实体化引用子树并重写克隆局部 ID 后再导出;PPTX 回导因此只返回展开后的原语,不重建创作期复用图。
值得在架构层标记的理由:
-- **为什么是黑名单,不是白名单。** SVG 是个宽规范;穷举允许特性会随着 Executor 不断发现新的有用构造而要持续维护。黑名单只圈住语义上没有 DrawingML 表达的窄集合,其余隐式可用。
-- **为什么是经验性,不是从规范推导。** 这份清单从真实的 PPT 导出失败长出来,不是读 OOXML 规范读出来的。有几个特性(如 `<mask>`)理论上能在 DrawingML 表达,但跨 PowerPoint 版本不可靠;黑名单反映的是实际能交付的子集。
-- **XML 良构性陷阱。** 两个独立于 DrawingML 的跨切陷阱:排版字符必须用裸 Unicode(`—`、`→`、`©`、NBSP),HTML 命名实体(`&mdash;`)在 SVG 里是非法 XML;XML 保留字符(`& < >`)必须实体转义,否则 `R&D` 直接终止导出。这两个坑出现频率高到值得在架构层 flag 一下。
-- **黑名单在后处理之前执行。** `svg_quality_checker.py` 在 `svg_output/` 上执行;后处理会重写 SVG,会掩盖源级别违规。修复永远是 Executor 重新写——有意没有 auto-fix 模式(见 § 质量门)。
+- **为什么是例外清单,不是允许清单。** SVG 是个宽规范;穷举所有允许能力会随着转换器演进而持续增加维护成本。集中维护例外,才能让已实现的普通构造默认可用。
+- **为什么是经验性,不是从规范推导。** 兼容性边界从真实的 PPT 导出失败长出来,不是读 OOXML 规范推导出来的。有些理论上能表达的效果跨 PowerPoint 版本仍不可靠,因此合同反映的是实际能交付的子集。
+- **XML 良构性仍是前置条件。** SVG 一旦不是合法 XML,尚未进入 DrawingML 兼容性阶段就会失败。接受的创作形式集中在权威合同中,避免架构与提示文档分别维护后发生漂移。
+- **兼容性校验在后处理之前执行。** `svg_quality_checker.py` 在 `svg_output/` 上执行;后处理会重写 SVG,可能掩盖源级别违规。修复永远是 Executor 重新写——有意没有 auto-fix 模式(见 § 质量门)。
---
## 质量门
-**为什么需要这道检查器。** LLM 生成的 SVG 不是确定性的——禁用特性会在长 deck 中悄悄混入,只在 `svg_to_pptx` 中途崩或 PowerPoint 静默丢元素时才暴露。检查器把「PowerPoint 在第 14 页导出失败」转化为「Executor 在第 14 页用了 `<style>`,重新生成它」,诊断速度提升一个数量级——这正是让长 deck 在经济上可迭代的关键。
+**为什么需要这道检查器。** LLM 生成的 SVG 不是确定性的——兼容性违规会在长 deck 中悄悄混入,只在 `svg_to_pptx` 中途崩或 PowerPoint 静默丢元素时才暴露。检查器把「PowerPoint 在第 14 页导出失败」转化为「第 14 页违反 SVG 兼容性合同」,诊断速度提升一个数量级——这正是让长 deck 在经济上可迭代的关键。
**为什么放在后处理之前,而不是之后。** 后处理会重写 SVG(图标嵌入、图片内联),会掩盖源级别违规。直接读 `svg_output/` 抓的是 Executor 的实际输出,先于任何可能掩盖 bug 的清理动作。
-**严重性模型:error 阻塞、warning 不阻塞,且有意没有 auto-fix。** error 要求 Executor 在上下文里重新写出错的页面——一个被禁的 `<style>` 元素不是机械 patch,因为 Executor 用它是有原因的,替代方案(比如改成内联属性)需要带着同样的设计意图重新落地。Auto-fix 会静默丢失这份意图,交付一个更难看的页面。
+**严重性模型:error 阻塞、warning 不阻塞,且有意没有 auto-fix。** error 要求 Executor 在上下文里重新写出错的页面——兼容性违规不一定能机械 patch,因为替代方案必须重新承载同样的设计意图。Auto-fix 会静默丢失这份意图,交付一个更难看的页面。
**为什么图表坐标验证挂在同一道 gate。** 图表页面有几何正确性需求(柱高、饼图扇角、坐标轴刻度位置),这些不是结构问题,SVG 合法性规则也抓不到。最自然的捕捉位置就是已经要求 AI 回看自己输出的那道 gate——把「看一眼你刚生成的东西然后修」的认知上下文打包到一个阶段,比把结构和几何审查分到两轮 review 更高效。
diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.md
index fb31fd83..c0e03128 100644
--- a/skills/ppt-master/SKILL.md
+++ b/skills/ppt-master/SKILL.md
@@ -347,7 +347,7 @@ First, read the role definition:
Read references/strategist.md
```
-> ⚠️ **Mandatory gate**: before writing `design_spec.md`, Strategist MUST `read_file templates/design_spec_reference.md` and follow its full I–XI section structure. See `strategist.md` Section 1.
+> ⚠️ **Mandatory gate**: before writing `design_spec.md`, Strategist MUST `read_file templates/design_spec_reference.md` and follow its full I–X section structure. See `strategist.md` Section 1.
**Artifact ownership**: fact-channel and source/derived artifact boundaries are defined in [`references/artifact-ownership.md`](references/artifact-ownership.md). This Step uses those ownership rules; it does not redefine them.
@@ -645,7 +645,8 @@ python3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path>
> ⚠️ Run the three sub-steps **one at a time** — each must complete successfully before the next.
> ❌ **NEVER** combine them into a single code block or shell invocation.
-Canonical three-command pipeline (mirrors `references/shared-standards.md` §5):
+Canonical three-command pipeline (this step is the workflow authority;
+`references/shared-standards.md` §5 points here):
**Step 7.1** — Split speaker notes:
```bash
diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.md
index 8e3e3378..b6b4d691 100644
--- a/skills/ppt-master/references/executor-base.md
+++ b/skills/ppt-master/references/executor-base.md
@@ -262,7 +262,7 @@ grep "chart-plot-area" <project_path>/svg_output/<current_page>.svg
- **Technical specs**: see [shared-standards.md](shared-standards.md) for SVG/PPT constraints
- **Card containers — use the documented patterns**: when a content page needs section cards (4 quadrants, parallel aspects, capability blocks, info cards), use the patterns codified in [`templates/charts/CHART_STYLE_GUIDE.md`](../templates/charts/CHART_STYLE_GUIDE.md) §11 — half-rounded section tab (§11.1), nested card border without stroke (§11.2), card-grid skeletons (§11.3), diagonal dashed connector for cross-quadrant relationships (§11.5), ground-anchor ellipse as a non-filter depth marker (§11.6), bidirectional interaction arrows for paired protocols (§11.7). Do not reinvent the "tinted full-rounded rect + white cover-rect to hide the bottom corners" hack; it survives in older templates but breaks SVG→PPTX color editing. Reference templates: [`labeled_card.svg`](../templates/charts/labeled_card.svg), [`quadrant_text_bullets.svg`](../templates/charts/quadrant_text_bullets.svg), [`kpi_cards.svg`](../templates/charts/kpi_cards.svg), [`matrix_2x2.svg`](../templates/charts/matrix_2x2.svg), [`team_roster.svg`](../templates/charts/team_roster.svg), [`client_server_flow.svg`](../templates/charts/client_server_flow.svg).
- **Reference — prefer semantic shapes over preset stacks (not a constraint)**: when a slide needs to express "ascending / converging / breaking through / stacking" — i.e., a relationship that goes beyond a generic arrow — prefer a single custom `<polygon>` or `<path>` that encodes the semantics geometrically, rather than stacking multiple preset arrows. A converging-tip path or a podium polygon reads faster than three arrows pointing at a label. Examples of this technique appear in many imported corporate decks; see `projects/01_template_import/svg_output/slide_01.svg` shape-158 for a reference (gradient-filled inward-pointing arrow). Do not codify these as templates — they are page-specific; the rule is just "consider polygon before stacking presets."
-- **Reference — visual depth through restraint (not a constraint)**: layered depth comes from rhythm (flat vs lifted, dense vs spacious), not from shadows everywhere. Shadow typically suits 2-3 genuinely floating elements per page (cards on photos, primary CTA, overlays); keep peer-grid cards, dividers, body containers flat. Reach for typography weight, spacing, accent bars, subtle tints **before** shadow. Full rules in shared-standards.md §6.
+- **Reference — visual depth through restraint (not a constraint)**: layered depth comes from rhythm (flat vs lifted, dense vs spacious), not from shadows everywhere. Shadow typically suits 2-3 genuinely floating elements per page (cards on photos, primary CTA, overlays); keep peer-grid cards, dividers, body containers flat. Reach for typography weight, spacing, accent bars, subtle tints **before** shadow.
### 3.2 Native Object Metadata Marker (MANDATORY on eligible data-chart and text-grid table pages)
@@ -280,7 +280,7 @@ grep "chart-plot-area" <project_path>/svg_output/<current_page>.svg
- Native chrome: write `title`, `subtitle`, axis titles, or `show_legend: true` only when the fallback visibly renders the same chrome inside the native chart's replacement scope. `title` is the PowerPoint chart title, not an object name; use `name` for page-semantic object naming (e.g. `p03-revenue-chart`). Write explicit `x`/`y`/`width`/`height` read from the drawn plot area; omission is the fallback — the exporter then infers the frame from the drawn fallback geometry.
- Value-axis labels: when the fallback keeps category labels but intentionally omits numeric value-axis tick labels, set `show_value_axis_labels: false`.
- Freeform chart text: transcribe center labels, source notes, and other in-chart annotations as companion `caption` / `note` / `notes` entries with explicit slide-coordinate bounds; do not rely on fallback `<text>` children to survive native export.
-- Native chart typography mirrors the SVG fallback. Copy the fallback's shared chart font into `style.font_family` and visible chart text sizes into the matching metadata fields (`title_font_size`, `subtitle_font_size`, `axis_font_size`, `note_font_size`, etc.) when role sizes differ; if omitted, the exporter infers shared font family and base chart text size from visible fallback text inside the native marker. When a visible chart title, subtitle, or axis title needs its own size/color/font, write that field as an object with `text`, `font_size`, `font_family`, and `color`. Use `axis_title_font_size`, `legend_font_size`, or companion per-entry `font_size` only when the fallback visibly uses a separate size. If a fallback role has no explicit size, use the compact three-tier chart defaults from [shared-standards.md](shared-standards.md).
+- Native chart typography mirrors the SVG fallback. Copy the fallback's shared chart font into `style.font_family` and visible chart text sizes into the matching metadata fields (`title_font_size`, `subtitle_font_size`, `axis_font_size`, `note_font_size`, etc.) only when role sizes differ; otherwise let the exporter infer them from visible fallback text. When a visible chart title, subtitle, or axis title needs its own size/color/font, write that field as an object with `text`, `font_size`, `font_family`, and `color`. Use `axis_title_font_size`, `legend_font_size`, or companion per-entry `font_size` only when the fallback visibly uses a separate size.
- Native table typography mirrors the SVG fallback. Write `style.font_family` and `style.font_size` from the visible table text; use `header_font_size` or per-cell `font_size` only when the fallback visibly does so. If the fallback has no explicit table font, fall back to the deck body family and locked body size from `spec_lock.md typography`.
- The marker group's transform stays translate/scale only (no rotate / matrix / skew).
- Visual parity is not a goal: the SVG drawing remains the designed visual; the native object is a data-editable counterpart with PowerPoint-default styling that users restyle by hand after export. Never simplify the SVG design to match what a native object could show.
@@ -500,7 +500,7 @@ Auto-split `notes/total.md` into per-page files in `notes/`.
> **Auto-continuation**: After Visual Construction Phase (all SVG pages) and Logic Construction Phase (all notes) are complete, the Executor proceeds directly to the post-processing pipeline.
-**Post-processing & Export** (same canonical pipeline as [shared-standards.md §5](shared-standards.md)):
+**Post-processing & Export** (canonical workflow: [`SKILL.md` Step 7](../SKILL.md)):
```bash
# 1. Split speaker notes
diff --git a/skills/ppt-master/references/image-layout-patterns.md b/skills/ppt-master/references/image-layout-patterns.md
index 28d2224b..06476304 100644
--- a/skills/ppt-master/references/image-layout-patterns.md
+++ b/skills/ppt-master/references/image-layout-patterns.md
@@ -148,7 +148,7 @@ Stack any of these freely on top of a Primary structure. Multiple Modifiers per
24. **Custom path crop (blob, arrow, leaf, silhouette)** — `<clipPath><path d="…"/></clipPath>`; allows any curved or organic shape. PowerPoint export translates this to `custGeom` and survives roundtrip.
-25. **Layered paper-cut stack** — multiple image or shape layers each with `clipPath` + a small `<feDropShadow>` offset to fake physical layering depth. Each layer casts a shadow onto the next, producing real-looking craft depth.
+25. **Layered paper-cut stack** — clip each image layer under the image-only contract in [`shared-standards.md`](shared-standards.md) §1.2; draw vector layers directly in their final geometry. A small conditional shadow on each layer can create physical separation.
26. **Triptych baked into a single wide image** — one wide `<image width=1160 height=334>` whose internal composition already contains 2–3 scenes. Generate the triptych as one image (not three separate calls) when scene-to-scene consistency matters — the model preserves character identity, lighting continuity, and color grading far more reliably when panels are produced together.
@@ -170,9 +170,9 @@ Stack any of these freely on top of a Primary structure. Multiple Modifiers per
33. **Spotlight mask — clear region surrounded by darkness** — cover the canvas with `<rect>` filled by a `<radialGradient>` whose inner stop is fully transparent and outer stop is opaque dark. Reads as a flashlight beam on the focal area. Use sparingly — it kills everything outside the spotlight.
-34. **Gaussian-blur backdrop** — `<filter><feGaussianBlur stdDeviation="8–15"/></filter>` applied to the background image, with sharp content layered on top unblurred. Reads as depth-of-field. Be aware that filters have inconsistent PPT export support — if fidelity matters, bake the blur into the source image instead.
+34. **Gaussian-blur backdrop** — blur the background in the source image, then layer sharp SVG content above it. Native filter export maps the supported blur graph to a glow/shadow effect; it does not preserve a blurred-image backdrop.
-35. **Duotone treatment** — two-color mapping of a photograph (e.g. deep navy shadows + warm cream highlights). Most reliable when baked into the source image at generation time. Runtime SVG duotone via `<feColorMatrix>` + `<feComponentTransfer>` is possible but the filter chain is fragile through PPT export — only attempt if you control the renderer.
+35. **Duotone treatment** — two-color mapping of a photograph (e.g. deep navy shadows + warm cream highlights). Bake it into the source image; the native PPT route does not support a runtime duotone filter chain.
36. **Drop shadow under image panel** — `<filter><feDropShadow dx dy stdDeviation flood-color flood-opacity/></filter>` applied to the image's container `<rect>` (or to the `<image>` itself). Standard depth lift.
@@ -204,7 +204,7 @@ Stack any of these freely on top of a Primary structure. Multiple Modifiers per
67. **Image with knock-out / cut-out shape** — overlay a shape filled with the background color or another image, creating the impression of a hole punched through the underlying image.
-68. **Text-as-mask over image** — letterforms revealing image through them. SVG-level `<mask>` is forbidden in this project (PPT export breaks). The only reliable way: bake this effect into the image at generation time by prompting for "large lettering revealing the underlying scene through letterforms." Treat as a pre-rendered artistic choice, not a runtime effect.
+68. **Text-as-mask over image** — letterforms revealing image through them. Under the canonical SVG compatibility boundary in [`shared-standards.md`](shared-standards.md), realize this pattern as a pre-rendered image rather than a runtime effect. Prompt for "large lettering revealing the underlying scene through letterforms" and treat the result as a fixed artistic choice.
69. **Image rotated at a slight angle for editorial feel** — `transform="rotate(angle cx cy)"` on the `<image>` or its container `<g>`; 2–6 degrees typical. Adds dynamism without breaking layout.
@@ -252,12 +252,10 @@ Combine freely. The "AI-default" failure mode is the opposite: defaulting to bar
## Hard Constraints
- Long body copy, data points, numeric labels, and Chinese text always go in the SVG layer — never baked into the image.
-- `<clipPath>` on `<image>` and transparency encoding (CSS alpha colors or
- explicit opacity attributes) — authoritative form in
- [`shared-standards.md`](shared-standards.md) §1.2 and §2; do not restate or
- relax here.
-- No `<mask>`, no `<feComposite>` for alpha compositing. Alpha-effect routing (gradient overlays, clipPath crops, filter shadows, baked-in source image) is the table in [`shared-standards.md`](shared-standards.md) §1.0.
-- `<feDropShadow>` / `<feGaussianBlur>` are accepted but PPT export is inconsistent — bake into the source image when fidelity is critical.
+- All project-wide SVG compatibility exceptions and conditional mappings are
+ owned by [`shared-standards.md`](shared-standards.md). This catalog neither
+ restates nor relaxes that contract; each pattern records only its
+ scenario-specific rendering choice.
---
diff --git a/skills/ppt-master/references/shared-standards.md b/skills/ppt-master/references/shared-standards.md
index 1d084117..639f203c 100644
--- a/skills/ppt-master/references/shared-standards.md
+++ b/skills/ppt-master/references/shared-standards.md
@@ -1,12 +1,24 @@
# Shared Technical Standards
-Common technical constraints for PPT Master, eliminating cross-role file duplication.
+This file is the sole authoring authority for SVG constraints shared across PPT
+Master routes. Generated specs, templates, role prompts, and user-facing docs
+may link here, but must not restate the rules.
----
+The policy is intentionally negative:
+
+- **Required** entries exist only when every SVG needs the same foundation.
+- **Forbidden** entries identify constructs the pipeline rejects or cannot
+ preserve safely.
+- **Conditional** entries document features that work only through a restricted
+ syntax, an approximation, an opt-in flag, or PPT-specific metadata.
-## 1. SVG Banned Features and Conditional Allowances
+Anything else already handled by the converter is freely usable and is not
+listed as an "allowed feature." Unknown visual elements still fail quality
+checking/export rather than being dropped silently.
+
+---
-The following are **forbidden** in generated SVGs — PPT export breaks otherwise:
+## 1. Required Foundation, Forbidden Features, and Conditional Interfaces
### 1.0 Text characters: must be well-formed XML
@@ -17,7 +29,7 @@ SVG is strict XML. Two rules for all text and attribute values:
| Typography & symbols (em dash, en dash, ©, ®, →, ·, NBSP, full-width punctuation, emoji…) | **Raw Unicode characters** — write `—` `–` `©` `®` `→` directly | HTML named entities — `&mdash;` `&ndash;` `&copy;` `&reg;` `&rarr;` `&middot;` `&nbsp;` `&hellip;` `&bull;` etc. |
| XML reserved characters (`&`, `<`, `>`, `"`, `'`) | **XML entities only** — `&amp;` `&lt;` `&gt;` `&quot;` `&apos;` (e.g. `R&amp;D`, `error &lt; 5%`) | Bare `&` `<` `>` (e.g. `R&D`, `error < 5%`) |
-One offending character invalidates the file and aborts export. Numeric refs (`&#160;` / `&#xa0;`) are XML-legal but discouraged.
+One offending character invalidates the file and aborts export.
**Structural blacklist** (in addition to the character rules above):
@@ -25,7 +37,7 @@ One offending character invalidates the file and aborts export. Numeric refs (`&
|----------------|-------------|
| `mask` | Masks |
| `<style>` | Embedded stylesheets |
-| `class` | CSS selector attributes (`id` remains allowed for local references and semantic markers when no `<style>` selector is used) |
+| `class` | CSS selector attributes |
| External CSS | External stylesheet links |
| `<foreignObject>` | Embedded external content |
| `textPath` | Text along a path |
@@ -34,123 +46,70 @@ One offending character invalidates the file and aborts export. Numeric refs (`&
| `<script>` / event attributes | Scripts and interactivity |
| `<iframe>` | Embedded frames |
-> **`marker-start` / `marker-end` is conditionally allowed** — see §1.1 for constraints. The converter maps qualifying markers to native DrawingML `<a:headEnd>` / `<a:tailEnd>`.
->
-> **`clipPath` on `<image>` is conditionally allowed** — see §1.2 for constraints. The converter maps qualifying clip shapes to native DrawingML picture geometry (`<a:prstGeom>` or `<a:custGeom>`).
+The blacklist above is exhaustive for globally forbidden SVG syntax. Features
+that require a restricted form are not globally forbidden; they are documented
+under the conditional contracts below.
+
+> **`marker-start` / `marker-end` is conditional** — see §1.1.
>
-> **Static same-document `<use>` is conditionally allowed** — see §1.3. The
-> pipeline materializes qualifying references before SVG snapshot/native PPTX
-> conversion; PowerPoint does not retain the reference structure.
+> **`clipPath` on `<image>` is conditional** — see §1.2.
>
-> **`<pattern>` fills are conditionally allowed** — see §7 *Pattern Fill* for the required `data-pptx-pattern` annotation and the closed OOXML preset enum. Hand-drawn pattern geometry is NOT honored; the converter emits the named PPTX preset only. Missing or invalid preset values produce diagonal stripes (warning) or schema-failed PPTX (error).
+> **Static same-document `<use>` is conditional** — see §1.3.
>
-> **Replacing `<mask>` effects** — DrawingML has no per-pixel alpha. Route by effect:
-> - Image gradient overlay (vignette/fade/tint) → stacked `<rect>` with `<linearGradient>`/`<radialGradient>` (§6 Image Overlay)
-> - Non-rectangular image crop (circle/rounded/hexagon) → `clipPath` on `<image>` (§1.2)
-> - Inner glow / soft-edge → `<filter>` with `<feGaussianBlur>` (§6 Glow)
-> - Drop shadow → filter shadow or layered rect (§6 Shadow)
+> **Inline CSS geometry, group opacity, simple gradients, and filters are
+> conditional** — see §2 and §6.
>
-> Pixel-level alpha effects (text-knockout image fills, arbitrary alpha composites) have no PPT path — bake into the source image at Image_Generator stage.
-
----
+> **PPT preset patterns and native chart/table/template metadata are
+> conditional** — see §7.
-### 1.1 Line-end Markers (Conditionally Allowed)
+DrawingML has no arbitrary per-pixel alpha-compositing path. Effects that rely
+on one, including text-knockout image fills and arbitrary alpha composites,
+must be baked into a raster asset before SVG export.
-`marker-start` and `marker-end` on `<line>` and `<path>` elements are allowed **only** when the referenced `<marker>` satisfies all of the following:
-
-| Requirement | Reason |
-|-------------|--------|
-| Marker `<marker>` element defined inside `<defs>` | Converter looks up marker defs via id index |
-| `orient="auto"` | DrawingML arrow auto-rotates along the line tangent; other orient values will not round-trip |
-| Marker shape is **one of**: closed 3-vertex path/polygon (triangle), closed 4-vertex path/polygon (diamond), `<circle>` / `<ellipse>` (oval) | These three map cleanly to DrawingML `type="triangle" / "diamond" / "oval"`. Any other shape is silently dropped with a warning. |
-| Marker child's `fill` **matches** the parent line's `stroke` color | In DrawingML the arrow head inherits the line color — a mismatched marker fill will look wrong on export. |
-| `markerWidth` / `markerHeight` roughly in `3–15` range | Mapped to `sm` (<6) / `med` (6–12) / `lg` (>12) size buckets. |
-
-**Use boundary**:
-
-- `marker-start` / `marker-end`: only for connector arrows where the line is primary
-- For block / chunky / solid arrows (arrow body is the visual object), use standalone closed `<path>` / `<polygon>`; see `templates/charts/chevron_process.svg` or `templates/charts/process_flow.svg`
-
-**Supported DrawingML mapping**:
+---
-| SVG Marker Shape | DrawingML Output |
-|------------------|------------------|
-| `<path d="M0,0 L10,5 L0,10 Z"/>` (triangle) | `<a:tailEnd type="triangle" w="med" len="med"/>` |
-| `<polygon points="0,0 10,5 0,10"/>` | `<a:tailEnd type="triangle" w="med" len="med"/>` |
-| 4-vertex closed path/polygon | `<a:tailEnd type="diamond" .../>` |
-| `<circle cx="5" cy="5" r="4"/>` | `<a:tailEnd type="oval" .../>` |
+### 1.1 Line-end Markers (Conditional Contract)
-**Recommended template** — a standard arrow-head definition ready to reuse:
+`marker-start` and `marker-end` are supported on `<line>` and `<path>` only
+when the referenced marker fits this native-arrow contract:
-```xml
-<defs>
- <marker id="arrowHead" markerWidth="10" markerHeight="10" refX="9" refY="5"
- orient="auto" markerUnits="strokeWidth">
- <path d="M0,0 L10,5 L0,10 Z" fill="#1976D2"/>
- </marker>
-</defs>
-<line x1="100" y1="200" x2="400" y2="200" stroke="#1976D2" stroke-width="3"
- marker-end="url(#arrowHead)"/>
-```
+| Concern | Required form |
+|---|---|
+| Reference | Exact local `url(#id)` to a `<marker>` in `<defs>` |
+| Orientation | `orient="auto"` |
+| Shape | Closed 3-vertex path/polygon (triangle), closed 4-vertex path/polygon (diamond), or one `<circle>`/`<ellipse>` (oval) |
+| Color parity | Marker fill matches the parent line stroke; DrawingML arrows inherit the line color |
-> ⚠️ Unclassifiable marker shapes (curved paths, multi-segment, >4 vertices) are silently dropped — line renders without arrow. Use a manual `<polygon>` for exotic shapes.
+The converter maps the three shapes to DrawingML triangle, diamond, and oval
+line ends. Other marker shapes do not have a native mapping and are dropped
+with a warning.
---
-### 1.2 Image Clipping (Conditionally Allowed)
+### 1.2 Image Clipping (Conditional Contract)
-`clip-path` on `<image>` elements is allowed when the referenced `<clipPath>` satisfies the following:
+`clip-path` has a native picture-crop mapping only on `<image>` elements and
+only under this contract:
-| Requirement | Reason |
-|-------------|--------|
+| Concern | Required form |
+|---|---|
| `<clipPath>` element defined inside `<defs>` | Converter looks up clip defs via id index |
-| Contains a **single** shape child | First child is used; multiple children are not composited |
+| Contains a **single supported** shape child | The converter uses the first supported child; multiple shapes are not composited |
| Shape is one of: `<circle>`, `<ellipse>`, `<rect>` (with rx/ry), `<path>`, `<polygon>` | These map to DrawingML geometry (preset or custom) |
| Used **only on `<image>` elements** | Non-image elements with clip-path are **forbidden** |
-**Use boundary**:
-
-- Only on `<image>` for non-rectangular crops (circular avatars, rounded frames, hexagons)
-- NOT on shapes (`<rect>`/`<circle>`/`<path>`/`<g>`/`<text>`) — draw the target shape directly. A rect clipped to a circle is just a circle.
-- PowerPoint's SVG renderer doesn't handle `clipPath`; only the Native PPTX converter does.
-
-**Supported DrawingML mapping**:
-
-| SVG Clip Shape | DrawingML Output | Use Case |
-|----------------|------------------|----------|
-| `<circle>` / `<ellipse>` | `<a:prstGeom prst="ellipse"/>` | Circular avatar, oval frame |
-| `<rect rx="..."/>` | `<a:prstGeom prst="roundRect"/>` with adj value | Rounded rectangle photo frame |
-| `<path>` / `<polygon>` | `<a:custGeom>` with path commands | Hexagon, diamond, custom shape |
-
-**Recommended template** — circular image clip:
-
-```xml
-<defs>
- <clipPath id="avatarClip">
- <circle cx="200" cy="200" r="100"/>
- </clipPath>
-</defs>
-<image href="../images/photo.jpg" x="100" y="100" width="200" height="200"
- clip-path="url(#avatarClip)" preserveAspectRatio="xMidYMid slice"/>
-```
-
-**Rounded rectangle clip** — for card-style image frames:
-
-```xml
-<defs>
- <clipPath id="cardClip">
- <rect x="60" y="120" width="400" height="250" rx="16"/>
- </clipPath>
-</defs>
-<image href="../images/banner.jpg" x="60" y="120" width="400" height="250"
- clip-path="url(#cardClip)" preserveAspectRatio="xMidYMid slice"/>
-```
+| SVG clip shape | DrawingML output |
+|---|---|
+| `<circle>` / `<ellipse>` | `<a:prstGeom prst="ellipse"/>` |
+| `<rect rx="..."/>` | `<a:prstGeom prst="roundRect"/>` with adj value |
+| `<path>` / `<polygon>` | `<a:custGeom>` with path commands |
-> ⚠️ `clip-path` on non-image elements is FORBIDDEN — quality checker errors out. Draw target geometry directly.
+`clip-path` on shapes, groups, or text is forbidden; author the target geometry
+directly instead.
---
-### 1.3 Static Same-Document `<use>` (Conditionally Allowed)
+### 1.3 Static Same-Document `<use>` (Conditional Contract)
**Expansion contract**: Static local reuse is compile-time authoring shorthand. `finalize_svg.py` and
native export replace each qualifying instance with cloned primitive content;
@@ -178,7 +137,7 @@ the original `<use>` / `<symbol>` structure.
- Quoted/whitespace CSS fragment variants such as `url('#id')`; use exact
`url(#id)` when an internal paint/filter/clip reference must be rewritten
-**Supported example**:
+**Contract example**:
```xml
<svg xmlns="http://www.w3.org/2000/svg"
@@ -199,24 +158,16 @@ the original `<use>` / `<symbol>` structure.
---
-## 2. PPT Compatibility Mappings
+## 2. Conditional Compatibility Mappings
-**Allowed — CSS paint colors**: fills, strokes, gradient stops, and supported
-filter flood colors may use common named colors, `rgb()` / `rgba()` (legacy
-comma or modern space/slash syntax), `hsl()` / `hsla()`, `#RGB`, `#RGBA`,
-`#RRGGBB`, or `#RRGGBBAA`. Native export converts the color to DrawingML RGB
-and multiplies any embedded alpha with `opacity`, `fill-opacity`,
-`stroke-opacity`, `stop-opacity`, and supported effect alpha. Explicit opacity
-attributes remain valid when keeping palette and transparency separate is
-clearer. This guarantee applies to the SVG-derived DrawingML route; opt-in
-native table/chart payload styling follows its narrower native-object contract.
+### 2.1 Literal Inline Geometry
-**Allowed — literal inline geometry**: the following geometry properties may
-appear in the same element's `style="..."`. The pipeline materializes them as
+The following geometry properties may appear in the same element's
+`style="..."`. The pipeline materializes them as
XML geometry attributes before SVG post-processing and native PPTX conversion.
An inline geometry declaration overrides an existing same-name XML attribute.
-| Element | Supported properties |
+| Element | Recognized properties |
|---|---|
| `<rect>` | `x`, `y`, `width`, `height`, `rx`, `ry` |
| `<circle>` | `cx`, `cy`, `r` |
@@ -233,27 +184,20 @@ Do not put geometry on an unsupported element: line endpoints, text positions,
path data, and polygon/polyline points remain XML attributes.
**Forbidden — CSS geometry cascade**: `<style>`, `class`, selector rules,
-external stylesheets, and imported styles remain forbidden. This allowance is
+external stylesheets, and imported styles remain forbidden. This contract is
only for literal declarations in an element's own `style` attribute; PPT Master
does not compute CSS cascade or custom properties. Root canvas authority remains
the `viewBox`, regardless of root `<svg>` compatibility width/height values.
-**Allowed — group opacity (approximate)**: `<g opacity="0.3">...</g>` maps the
-group alpha onto each descendant shape, text run, picture, and supported
+### 2.2 Group Opacity Is Approximate
+
+`<g opacity="0.3">...</g>` maps the group alpha onto each descendant shape,
+text run, picture, and supported
shadow/glow effect. Nested group and child opacity values multiply. Overlapping
children may differ from SVG isolated-group compositing because DrawingML has no
equivalent group-alpha model. With `--native-objects`, transparent native
table/chart markers are rejected; omit that flag to export their SVG fallback.
-**Allowed — picture opacity**: `<image opacity="0.3"/>` maps to native DrawingML
-`a:alphaModFix` and round-trips back to SVG. Use a numeric value from `0` to
-`1`; use an overlay only when the design needs a color wash rather than simple
-transparency.
-
-**Mnemonic**: color and image alpha are native; group opacity is a per-object approximation.
-
-> Arrows: prefer `marker-end` for connector lines (§1.1) — converter produces native auto-rotating arrow heads. For block/chunky arrows, use standalone closed shapes; see `templates/charts/chevron_process.svg` and `templates/charts/process_flow.svg`.
-
---
## 3. Canvas Format Quick Reference
@@ -262,7 +206,7 @@ transparency.
---
-## 4. Basic SVG Rules
+## 4. Required Page Contract and Conditional Packaging
### 4.0 Complete Page-Design Contract
@@ -287,522 +231,102 @@ ordinary page content or move visible facts out of SVG attributes/text into
metadata. See
[`semantic-svg.md`](semantic-svg.md) for the canonical vocabulary and examples.
-- **viewBox** MUST match the canvas dimensions; it is the single source of truth for canvas size. Root `width`/`height` are optional compatibility attributes and are not used as PPT Master canvas authority.
-- **Background**: Use `<rect>` to define the page background color
-- **`<tspan>`** has two purposes: (1) manual line breaks (use `dy` or explicit `y`); (2) inline run formatting on the same line (color/weight/size). `<foreignObject>` is FORBIDDEN. See "Single logical line" rule below.
-- **Fonts**: every `font-family` stack MUST resolve to pre-installed exported Latin / EA typefaces (Microsoft YaHei / SimSun / Arial / Times New Roman / Consolas …); `@font-face` is FORBIDDEN. Full rule: [`strategist.md §g`](strategist.md).
-- **Styles**: per-element only (`fill=""`, `font-size=""`, or `style="..."`);
- literal inline geometry is restricted to §2. `<style>`/`class` are FORBIDDEN
- (`id` inside `<defs>` is fine)
-- **Colors**: common named colors, `rgb()` / `rgba()`, `hsl()` / `hsla()`, or
- 3/4/6/8-digit HEX; embedded and explicit opacity values multiply
-- **Images**: `<image href="../images/xxx.png" preserveAspectRatio="xMidYMid slice"/>`; optional `opacity="0..1"` maps to native picture transparency
-- **Icons**: `<use data-icon="<library>/<name>" x="" y="" width="48" height="48" fill="#HEX"/>` (auto-embedded post-processing). Always include library prefix. One stylistic library per deck (`chunk-filled`/`tabler-filled`/`tabler-outline`/`phosphor-duotone`); `simple-icons` only for real brand marks. See [`../templates/icons/README.md`](../templates/icons/README.md).
-- **Static local reuse**: `<use href="#id" .../>` / `<use xlink:href="#id" .../>` is allowed only under §1.3. This is separate from `data-icon` placeholders and is expanded before export.
-
-### Inline Text Runs (Single Logical Line = Single `<text>`)
-
-One logical line — even with mixed colors/weights/sizes — MUST be one `<text>` with inline `<tspan>` children. Never use multiple adjacent `<text>` elements. The converter maps each `<tspan>` to a `<a:r>` run within the same PPT text frame, keeping the line as one editable shape.
-
-✅ **DO** — one `<text>` → one text frame with three runs:
-
-```xml
-<text x="100" y="200" font-size="24" fill="#333333">
- 实现<tspan fill="#1A73E8" font-weight="bold">10倍</tspan>效率提升
-</text>
-```
-
-❌ **DON'T** — three side-by-side `<text>` elements become three separate text frames in PPT (breaks edit-as-one-line, risks alignment drift, makes spacing fragile):
-
-```xml
-<text x="100" y="200" font-size="24" fill="#333333">实现</text>
-<text x="160" y="200" font-size="24" fill="#1A73E8" font-weight="bold">10倍</text>
-<text x="240" y="200" font-size="24" fill="#333333">效率提升</text>
-```
-
-**⚠️ Inline tspans must NOT carry `x`/`y`/`dy`** — those mark a new line, and `flatten_tspan` will split into a separate text frame. `dx` is safe (kerning, stays inline). Only set `x`/`y`/`dy` on tspans that genuinely start a new line.
-
-**Multi-line `<text>` with per-line emphasis works**: an outer line-break tspan (with `x` + `dy` or `y`) MAY contain nested inline tspans for color/weight/size — converter walks nested tspans and emits one run per styled segment:
-
-```xml
-<text x="80" y="190" font-size="18" fill="#333333">
- <tspan x="80" dy="0">完成率<tspan fill="#4CAF50" font-weight="bold">98%</tspan>超预期</tspan>
- <tspan x="80" dy="35">成本降低<tspan fill="#F44336" font-weight="bold">¥120万</tspan></tspan>
-</text>
-```
-
-❌ **DON'T** — same-line column jump via `<tspan x="...">`:
-
-```xml
-<text x="100" y="200" font-size="18" fill="#333333">
- <tspan x="100">左列</tspan><tspan x="600" font-weight="bold">右列</tspan>
-</text>
-```
-
-`x` on a tspan starts a new line, splitting into two independent text frames. For two-column layouts, write two `<text>` elements.
-
-**Default — lift key information.** Uniform-styled paragraphs read as walls of text. Wrap these in `<tspan fill="..." font-weight="bold">`:
-
-- **Numerical results** — percentages, multipliers (`10x`), absolute amounts (`¥120万`)
-- **Contrasts** — gain/loss, before/after, target/actual
-- **One or two load-bearing nouns per sentence** — the term that carries the insight
-
-Do NOT highlight: connectives, common verbs, every noun, decorative adjectives, structural text (footer/axis/legend/page number/labels).
+- **Canvas authority**: `viewBox` MUST match the selected canvas dimensions.
+ Root `width` and `height` are optional and do not override it.
+- **Font portability**: font families used by the deck must resolve to installed
+ export faces. `@font-face` remains forbidden; the typography contract lives in
+ [`strategist.md §g`](strategist.md).
+- **Icon placeholders**: `<use data-icon="library/name">` is a pipeline-specific
+ form, distinct from local SVG reuse. Follow the contract in
+ [`../templates/icons/README.md`](../templates/icons/README.md).
+- **Local reuse**: ordinary same-document `<use>` follows §1.3.
-Color: use the deck's primary brand color for emphasis. Reserve green/red for actual positive/negative semantics.
+### 4.2 Conditional Editability and Package Promotion
-❌ **DON'T** — uniform-styled paragraph buries the insight:
+These forms are needed only when the stated PPT behavior matters:
-```xml
-<text x="80" y="200" font-size="20" fill="#333333">
- 2024年公司营收同比增长35%达到12亿元创历史新高
-</text>
-```
-
-✅ **DO** — same line, key data lifted:
-
-```xml
-<text x="80" y="200" font-size="20" fill="#333333">
- 2024年公司营收同比<tspan fill="#1A73E8" font-weight="bold">增长35%</tspan>达到<tspan fill="#1A73E8" font-weight="bold">12亿元</tspan>创历史新高
-</text>
-```
-
-### Element Grouping (Mandatory)
-
-Wrap logically related elements in top-level `<g id="...">` groups. Produces PowerPoint groups in PPTX, making slides easier to select/move/edit and providing stable anchors for optional per-element entrance animation.
-
-> `<g opacity="0..1">` is supported through the per-descendant alpha
-> approximation in §2. Plain `<g>` remains the normal grouping primitive.
-
-**Animation-ready rule**: direct children of `<svg>` should be semantic groups, not raw drawing atoms. Aim for **3–8 top-level content `<g id>` groups per slide** (the 3–8 budget excludes page chrome — see below); each content group becomes one entrance step under the chosen `--animation-trigger` mode (one click in `on-click`, one cascade slot in `after-previous`, parallel in `with-previous`).
-
-**Chrome groups are excluded automatically.** Existing `data-pptx-layer` and `data-pptx-placeholder="slide-number"` semantics are read first. Otherwise, explicit `data-pptx-role` values `background`, `decoration`, `header`, `footer`, `chrome`, `watermark`, `page-number`, and `logo` identify static page framing. For marker-free legacy SVGs, ids remain a compatibility fallback using these tokens after splitting on `-` / `_`: `background`, `bg`, `decoration` / `decorations` / `decor`, `header`, `footer`, `chrome`, `watermark`, `pagenumber` / `pagenum` / `page-number`, `nav`, `logo`, `rule`. Keep the `<g>` wrapper for editing/grouping.
-
-Minimal structural roles also drive slide-master promotion in the default native export: `logo` / `footer` / `header` / `watermark` / `chrome` elements drawn **before** content and repeated **verbatim** across pages may move into the slide master (pages without them, like covers, are isolated automatically). A `data-pptx-placeholder="slide-number"` text, or a free-design `data-pptx-role="page-number"` text, whose content exactly equals the page's display number becomes a self-renumbering PowerPoint field. Exact id tokens remain a fallback only when specialized/minimal markers are absent.
-
-**What to group**:
-
-| Grouping Unit | Contains |
-|---------------|----------|
-| Card / panel | Background rect + (optional shadow only if the card floats over a photo/colored panel — see §6) + icon + title + body text |
-| Process step | Number circle + icon + label + description |
-| List item | Bullet / number + icon + title + description |
-| Icon-text combo | Icon element + adjacent label |
-| Page header | Title + subtitle + accent decoration |
-| Page footer | Page number + branding |
-| Decorative cluster | Related decorative shapes (rings, orbs, dots) |
-
-**Do not**:
-
-- Put the whole slide into one giant `<g>`; that leaves only one animation step.
-- Leave many top-level `<rect>` / `<text>` / `<path>` elements ungrouped; fallback animation is capped at 8 primitives and dense flat pages may skip animation.
-- Split every icon, text line, or decorative mark into separate top-level groups; that creates too many click steps.
-- Use anonymous top-level groups. Every top-level semantic group needs a descriptive `id`.
-
-**Example**:
-
-```xml
-<g id="card-benefits-1">
- <!-- This card floats over a colored panel — shadow is appropriate. On a flat white canvas, omit the filter. -->
- <rect x="60" y="115" width="565" height="260" rx="20" fill="#FFFFFF" filter="url(#shadow)"/>
- <use data-icon="chunk-filled/bolt" x="108" y="163" width="44" height="44" fill="#0071E3"/>
- <text x="105" y="270" font-size="56" font-weight="bold" fill="#0071E3">10×</text>
- <text x="250" y="270" font-size="30" font-weight="bold" fill="#1D1D1F">Faster</text>
- <text x="105" y="310" font-size="18" fill="#6E6E73">Reduce production time from days to hours.</text>
-</g>
-```
-
-**Naming**: descriptive `id` on top-level `<g>` is **required** (e.g., `card-1`, `step-discover`, `header`, `footer`). Each top-level `<g id>` becomes one anchor for per-element entrance animation in PPTX export; without it, the exporter falls back to at most 8 top-level primitives or skips animation on dense pages.
-
----
-
-## 5. Post-processing Pipeline (3 Steps)
-
-Must be executed in order — skipping or adding extra flags is FORBIDDEN:
-
-```bash
-# 1. Split speaker notes into per-page note files
-python3 scripts/total_md_split.py <project_path>
-
-# 2. SVG post-processing (icon embedding, image crop/embed/optimization, text flattening, rounded rect to path)
-python3 scripts/finalize_svg.py <project_path>
-
-# 3. Export PPTX (embeds speaker notes by default)
-python3 scripts/svg_to_pptx.py <project_path>
-# Output (default-flow mode):
-# exports/<project_name>_<timestamp>.pptx ← native pptx (canonical output)
-# backup/<timestamp>/svg_output/ ← Executor SVG source backup (always written)
-#
-# Add --svg-snapshot to additionally emit:
-# exports/<project_name>_<timestamp>_svg.pptx ← SVG snapshot pptx (sibling of native pptx)
-```
-
-**Optional animation flags** (only when the user asks):
-- `-t <effect>` — page transition (`fade` / `push` / `wipe` / `split` / `strips` / `cover` / `random` / `none`; default `fade`)
-- `-a <effect>` — per-element entrance animation (`fade` / `auto` / `mixed` / `random` / one of 22 named effects / `none`; **default `none`** — pages appear as a whole, no auto element builds; opt in with `auto`, which maps effect from group id — image-like ids cycle zoom/dissolve/circle/box/diamond/wheel, other matches map to a single effect, unmatched ids cycle fade/wipe/fly/zoom). Anchors on top-level `<g id="...">` groups.
-- `--animation-trigger {on-click,with-previous,after-previous}` — Start mode matching PowerPoint's animation-pane Start dropdown. Default `after-previous` (cascade on slide entry; pace via `--animation-stagger <seconds>`); `on-click` advances per click; `with-previous` plays all groups together.
-- `--animation-config <path>` — optional object-level animation sidecar. Default: `<project>/animations.json` when present.
-- `--auto-advance <seconds>` — kiosk-style auto-play
-
-**Optional recorded narration** (only when the user asks for narrated/video export):
-
-```bash
-python3 scripts/notes_to_audio.py <project_path> --voice zh-CN-XiaoxiaoNeural
-python3 scripts/svg_to_pptx.py <project_path> --recorded-narration audio
-```
-
-- `notes_to_audio.py` reads split `notes/*.md` files and writes one audio file per slide to `audio/`. Default `edge` output is MP3; configured cloud providers may output MP3 or WAV depending on provider settings.
-- `--recorded-narration audio` prepares PowerPoint's recorded timings and narrations: every slide needs matching `m4a` / `mp3` / `wav` audio, every duration must be readable by `ffprobe`, and `on-click` object animation is rejected.
-- `--recorded-narration audio` embeds matching audio, keeps speaker notes, and sets slide timings from audio duration.
-- `--narration-audio-dir audio` is the lower-level embedding path for partial audio coverage; it does not prepare a complete recorded-timings export.
-- Long-audio import and automatic long-audio splitting are not supported.
-
-Full reference: [`animations.md`](animations.md).
-
-**Prohibited**:
-- NEVER use `cp` as a substitute for `finalize_svg.py`
-- NEVER force `-s output` for the legacy/preview pptx (PowerPoint's internal SVG parser drops icons and rounded corners). Default auto-split already gives native the high-fidelity source it needs without affecting legacy.
-- NEVER use `--only` in the standard pipeline; keep it for explicit one-product diagnostics or compatibility checks
-
-> Source-directory split: by default `svg_to_pptx.py` reads `svg_output/` for the native pptx (preserves icon `<use>`, image `preserveAspectRatio` as native picture-crop metadata, rounded rect `rx/ry` → `prstGeom roundRect`) and `svg_final/` for the legacy/preview pptx (PowerPoint's internal SVG parser needs the flattened form). Pass `-s output` or `-s final` only when you specifically want both products to read from a single source.
-
-**Default — raster size control**: `finalize_svg.py` optimizes raster images using a rendered-size budget of `2x` display pixels with a `2560px` maximum dimension; it may crop pixels for the flattened SVG snapshot. Native `svg_to_pptx.py` defaults to `--image-sizing cap`: it downscales only oversized full source images to `--image-max-dimension 2560`, keeps display cropping as editable PPT picture-crop metadata, and does not shrink a picture merely because its current SVG placement is small. Opaque PNG photos may become JPEG; transparent assets remain PNG. Use `finalize_svg.py --no-compress` / a higher `--max-dimension` only for diagnostic SVG snapshots, `svg_to_pptx.py --no-image-optimize` only when the native PPTX must retain original image bytes, and `svg_to_pptx.py --image-sizing display --image-scale 2` only for aggressive size reduction.
-
-**Re-run rule**: Any change to `svg_output/` after post-processing requires re-running Steps 2-3. Step 1 only re-runs if `notes/total.md` changed.
+| Desired behavior | Required form |
+|---|---|
+| One editable PPT text frame with mixed inline formatting | Put the logical line in one `<text>` and use non-positional `<tspan>` children. A `tspan` with `x`, `y`, or `dy` starts a new positioned line and is flattened to another text frame. Separate `<text>` elements remain valid when separate frames are intended. |
+| Stable object grouping or object-level animation anchor | Wrap the intended object in `<g id="...">`. Raw top-level primitives and anonymous groups remain valid when neither behavior is needed. |
+| Native PowerPoint background promotion | Use a direct, full-canvas, solid `<rect>` without transform, filter, clip, rounding, or visible stroke. Other SVG backgrounds remain ordinary slide shapes. Template routes add the ownership metadata in §7. |
+| Free-design page family/chrome extraction | Use the semantic markers in §4.1. Marker-free pages retain conservative filename/id fallbacks, but no visual content is inferred. |
---
-## 6. Shadow & Overlay Techniques
-
-> `<mask>` elements are banned. Use stacked `<rect>` or gradient overlays for
-> color washes; use `<image opacity="0..1">` for uniform picture transparency
-> (see §2).
-
-### Shadow
-
-> **Shadow is restraint, not default.** The "designed" feel comes from absence, not abundance.
-
-#### When to use
-
-Only when the element genuinely floats above another layer:
-- Card / quote bubble / annotation on a photo or colored panel
-- Single primary CTA or "recommended" item picked out from peers
-- Overlay layer (callout, tooltip, modal emphasis)
-- Floating image card on a textured background
-
-#### When NOT to use
-
-- Background panels / dividers / decorative bars — they are the floor
-- Equal peer cards in a 2/3/4-up grid — keep all flat
-- Containers with visible border, gradient fill, or strong tint — redundant
-- Body-text paragraph containers — disrupts scan rhythm
-- Decorative lines / dividers / icons — they are symbols, not objects
-- Pages with only one content container — no second layer to lift above
-- Dark backgrounds — black shadows vanish; use 1px low-opacity white stroke or outer glow
-
-**Reference — not a constraint**: 2-3 shadowed elements per page usually reads cleanest; before adding a 4th, check the extra layering earns its weight — a genuinely complex dashboard may justify more.
-
-#### Single light source per page
-
-All `feOffset` on a page must share the same `dx`/`dy` direction. Default: `dx="0"`, `dy="4"`-`dy="8"` (light from upper front).
-
-#### Restraint over visibility
-
-Standard: "the shadow is felt, not seen." If noticed, it's too strong.
-- Resting cards: `flood-opacity` 0.06-0.10
-- Raised elements (CTA, overlay): max `flood-opacity` 0.20
-- Above 0.20 = Office 2007 hard-shadow look
-- Color: near-black at low opacity, or a darker tint of background. Brand-color shadow only on accent elements sharing that hue.
-
-#### Two-tier elevation maximum
-
-A page may have at most two non-floor tiers.
-
-| Tier | When | dy | stdDeviation | flood-opacity |
-|------|------|----|--------------|---------------|
-| Floor (no shadow) | Backgrounds, peer-grid cards, dividers, body-text containers | — | — | — |
-| Resting | Cards on photos/panels, secondary callouts | 2-4 | 4-8 | 0.06-0.10 |
-| Raised | Primary CTA, focused/recommended card, overlay | 6-10 | 10-16 | 0.12-0.20 |
-
-#### Don't stack visual-weight tools
+## 5. Workflow Authority
-Pick **one** per container: shadow, border, gradient fill, or strong tint. Stacking = instant template look.
+The serial post-processing and export workflow belongs to
+[`SKILL.md` Step 7](../SKILL.md). This file defines SVG authoring boundaries
+and intentionally does not mirror commands, flags, or output behavior.
---
-#### Filter Soft Shadow — Recommended
+## 6. Conditional Paint Servers and Filters
-Best for: cards, floating panels, elevated elements. The `svg_to_pptx` converter automatically converts `feGaussianBlur` + `feOffset` into native PPTX `<a:outerShdw>`.
+### 6.1 Simple Gradients
-```xml
-<defs>
- <filter id="softShadow" x="-15%" y="-15%" width="140%" height="140%">
- <feGaussianBlur in="SourceAlpha" stdDeviation="12"/>
- <feOffset dx="0" dy="6" result="offsetBlur"/>
- <feFlood flood-color="#000000" flood-opacity="0.10" result="shadowColor"/>
- <feComposite in="shadowColor" in2="offsetBlur" operator="in" result="shadow"/>
- <feMerge>
- <feMergeNode in="shadow"/>
- <feMergeNode in="SourceGraphic"/>
- </feMerge>
- </filter>
-</defs>
-<rect x="60" y="60" width="400" height="240" rx="12" fill="#FFFFFF" filter="url(#softShadow)"/>
-```
-
-Recommended parameters (see "Two-tier elevation maximum" above for tier guidance):
-```
-stdDeviation: 4–16 (resting cards: 4–8; raised elements: 10–16)
-flood-opacity: 0.06–0.10 (resting cards — default)
- 0.12–0.20 (raised elements only — primary CTA, overlay)
- NEVER > 0.20 (Office 2007 hard-shadow look)
-dy: 2–10 (resting: 2–4; raised: 6–10)
-dx: 0–2 (must match every other shadow on the page — single light source)
-```
-
-#### Colored Shadow
-
-Best for: accent buttons, brand-colored cards. Use the element's own color family instead of black.
-
-```xml
-<filter id="colorShadow" x="-15%" y="-15%" width="140%" height="140%">
- <feGaussianBlur in="SourceAlpha" stdDeviation="10"/>
- <feOffset dx="0" dy="6" result="offsetBlur"/>
- <feFlood flood-color="#1A73E8" flood-opacity="0.20" result="shadowColor"/>
- <feComposite in="shadowColor" in2="offsetBlur" operator="in" result="shadow"/>
- <feMerge>
- <feMergeNode in="shadow"/>
- <feMergeNode in="SourceGraphic"/>
- </feMerge>
-</filter>
-```
-
-Replace `flood-color` with the element's brand color. Keep `flood-opacity` 0.12-0.20. Reserve for the single primary CTA per page — using on every button defeats the cue.
-
-#### Glow Effect
-
-Best for: title highlights, key metrics, hero text. The converter automatically converts `feGaussianBlur` without `feOffset` into native PPTX `<a:glow>`.
-
-```xml
-<defs>
- <filter id="titleGlow" x="-30%" y="-30%" width="160%" height="160%">
- <feGaussianBlur in="SourceAlpha" stdDeviation="6" result="blur"/>
- <feFlood flood-color="#1A73E8" flood-opacity="0.45" result="glowColor"/>
- <feComposite in="glowColor" in2="blur" operator="in" result="glow"/>
- <feMerge>
- <feMergeNode in="glow"/>
- <feMergeNode in="SourceGraphic"/>
- </feMerge>
- </filter>
-</defs>
-<text x="640" y="360" text-anchor="middle" font-size="48" fill="#1A73E8" filter="url(#titleGlow)">Key Insight</text>
-```
-
-Recommended parameters:
-```
-stdDeviation: 4–8 (smaller = subtle, larger = prominent)
-flood-color: brand color or accent color (NOT black)
-flood-opacity: 0.35–0.55 (stronger than shadow for visibility)
-```
-
-**vs shadow**: no `<feOffset>` (or dx=0/dy=0). The converter uses this to distinguish glow from shadow.
-
-#### Layered Rect Shadow — High-Compatibility Fallback
-
-Best for: maximum compatibility with older PowerPoint versions. Stack 2–3 semi-transparent rectangles behind the main card:
-
-```xml
-<!-- Shadow layers (back to front, largest offset first) -->
-<rect x="68" y="72" width="400" height="240" rx="16" fill="#000000" fill-opacity="0.03"/>
-<rect x="65" y="69" width="400" height="240" rx="14" fill="#000000" fill-opacity="0.05"/>
-<rect x="62" y="66" width="400" height="240" rx="12" fill="#1A73E8" fill-opacity="0.04"/>
-<!-- Main card -->
-<rect x="60" y="60" width="400" height="240" rx="12" fill="#FFFFFF"/>
-```
-
-### Image Overlay
-
-#### Linear Gradient Overlay — Most Common
-
-Best for: image+text pages. Gradient direction should match text position (text on left → gradient darkens toward left).
-
-```xml
-<image href="..." x="0" y="0" width="1280" height="720" preserveAspectRatio="xMidYMid slice"/>
-<defs>
- <linearGradient id="imgOverlay" x1="0" y1="0" x2="1" y2="0">
- <stop offset="0%" stop-color="#1A1A2E" stop-opacity="0.85"/>
- <stop offset="55%" stop-color="#1A1A2E" stop-opacity="0.30"/>
- <stop offset="100%" stop-color="#1A1A2E" stop-opacity="0"/>
- </linearGradient>
-</defs>
-<rect x="0" y="0" width="1280" height="720" fill="url(#imgOverlay)"/>
-```
+Gradient paint is conditional because the native route implements a simple
+DrawingML subset, not the full SVG paint-server model:
-#### Bottom Gradient Bar
+- Define `linearGradient` or `radialGradient` as a direct child of `<defs>`
+ with a unique `id`.
+- Reference it with the exact local form `url(#id)` from a supported
+ `fill`/`stroke` context.
+- Put the intended colors and offsets directly on its `<stop>` children.
+- Do not depend on external references, inherited gradient chains,
+ `gradientTransform`, or `spreadMethod`; those semantics are not preserved by
+ native export.
-Best for: cover slides and full-image pages with bottom title.
+Native export reduces a linear gradient to its angle. A radial gradient becomes
+a centered circular DrawingML gradient; SVG focal-point and radius geometry
+(`cx`, `cy`, `r`, `fx`, `fy`) remains useful in browser preview but is not
+preserved in the native object.
-```xml
-<defs>
- <linearGradient id="bottomBar" x1="0" y1="0" x2="0" y2="1">
- <stop offset="0%" stop-color="#000000" stop-opacity="0"/>
- <stop offset="100%" stop-color="#000000" stop-opacity="0.72"/>
- </linearGradient>
-</defs>
-<rect x="0" y="380" width="1280" height="340" fill="url(#bottomBar)"/>
-```
+The quality checker validates the definition location, reference, and
+fill/stroke context.
-#### Radial Gradient Overlay — Vignette Effect
+### 6.2 Shadow and Glow Filters
-Best for: full-screen atmosphere slides; draws attention to the center.
+Filters are conditional native-effect metadata, not a general SVG filter
+surface. An element's `filter` must be an exact local `url(#id)` reference to
+a direct `<defs><filter>` definition that can be reduced to one DrawingML
+outer shadow or glow.
-```xml
-<defs>
- <radialGradient id="vignette" cx="50%" cy="50%" r="70%">
- <stop offset="0%" stop-color="#000000" stop-opacity="0"/>
- <stop offset="100%" stop-color="#000000" stop-opacity="0.58"/>
- </radialGradient>
-</defs>
-<rect x="0" y="0" width="1280" height="720" fill="url(#vignette)"/>
-```
+The accepted graph may contain:
-#### Brand Color Overlay
+- `feDropShadow`; or `feGaussianBlur` with optional `feOffset` and `feFlood`
+- `feComposite`, `feMerge`, and `feMergeNode` for the standard composition
+- `feComponentTransfer` with a linear `feFuncA` for alpha adjustment
-Best for: slides needing strong visual brand identity.
-
-```xml
-<defs>
- <linearGradient id="brandOverlay" x1="0" y1="0" x2="1" y2="0">
- <stop offset="0%" stop-color="#005587" stop-opacity="0.80"/>
- <stop offset="100%" stop-color="#005587" stop-opacity="0.10"/>
- </linearGradient>
-</defs>
-<rect x="0" y="0" width="1280" height="720" fill="url(#brandOverlay)"/>
-```
-
-### Quick-Reference Table
-
-| Scenario | Recommended Technique | Avoid |
-|----------|-----------------------|-------|
-| Card / panel shadow (only when floating over photo/colored panel) | Filter soft shadow (`flood-opacity` 0.06–0.10, single light source) | Hard black shadow, full-page abundance |
-| Equal peer cards in a grid | All flat (no shadow) | Lifting every card uniformly |
-| Page-section background panel | Flat fill, no shadow | Treating panels as floating cards |
-| Accent / CTA button (one per page) | Colored shadow (same hue family, `flood-opacity` 0.12–0.20) | Generic gray shadow, applying to every button |
-| Title / metric highlight | Glow filter (brand color, no offset) | Overuse on body text |
-| Text over image | Linear gradient overlay (direction matches text side) | Uniform flat opacity over whole image |
-| Cover / full-image slide | Bottom gradient bar + brand color | Solid black overlay |
-| Atmosphere / hero slide | Radial vignette | Unprocessed raw image |
-| Max PPT compatibility needed | Layered rect shadow | Filter-based shadow |
+At least one `feDropShadow` or `feGaussianBlur` is required. A non-zero offset
+selects an outer shadow; otherwise the exporter emits a glow. Other filter
+primitives and arbitrary multi-effect graphs are forbidden because the
+converter would otherwise approximate or ignore them.
---
-## 7. Stroke, Text & Shape Effects
-
-### stroke-dasharray — Dashed / Dotted Lines
+## 7. Conditional PPT Interfaces
-Converts to native PPTX `<a:prstDash>`. Use preset patterns for best results:
-
-| SVG Value | PPTX Preset | Best For |
-|-----------|-------------|----------|
-| `4,4` | Dash | General dashed lines, separators |
-| `2,2` | Dot (sysDot) | Subtle dotted borders, placeholder outlines |
-| `8,4` | Long dash | Timeline connectors, flow arrows |
-| `8,4,2,4` | Long dash-dot | Technical drawings, dimension lines |
-
-```xml
-<rect x="60" y="60" width="400" height="240" rx="12"
- fill="none" stroke="#999999" stroke-width="2" stroke-dasharray="4,4"/>
-
-<line x1="100" y1="360" x2="1180" y2="360"
- stroke="#CCCCCC" stroke-width="1" stroke-dasharray="2,2"/>
-```
-
-### stroke-linejoin
-
-Controls how line segments join at corners. Supported values convert to native PPTX line join types:
-
-| SVG Value | PPTX Equivalent | Best For |
-|-----------|-----------------|----------|
-| `round` | Round join | Smooth polyline charts, organic shapes |
-| `bevel` | Bevel join | Technical diagrams |
-| `miter` | Miter join (default) | Sharp-cornered rectangles, arrows |
-
-```xml
-<polyline points="100,200 200,100 300,200" fill="none"
- stroke="#1A73E8" stroke-width="3" stroke-linejoin="round"/>
-```
-
-### text-decoration
-
-Supported text decorations convert to native PPTX text formatting:
-
-| SVG Value | PPTX Equivalent | Best For |
-|-----------|-----------------|----------|
-| `underline` | Single underline | Emphasis, links, key terms |
-| `line-through` | Strikethrough | Removed items, before/after comparisons |
-
-```xml
-<text x="100" y="200" font-size="20" fill="#333333" text-decoration="underline">Important Term</text>
-
-<!-- Per-tspan decoration -->
-<text x="100" y="240" font-size="18" fill="#333333">
- Regular text <tspan text-decoration="line-through" fill="#999999">old value</tspan> new value
-</text>
-```
-
-### Gradient Fill — linearGradient & radialGradient
-
-Gradients defined in `<defs>` and referenced via `fill="url(#id)"` convert to native PPTX `<a:gradFill>`. Use them as shape fills (not just overlays) for polished surfaces.
-
-**Linear gradient** — best for buttons, header bars, background panels:
-
-```xml
-<defs>
- <linearGradient id="btnGrad" x1="0" y1="0" x2="1" y2="0">
- <stop offset="0%" stop-color="#1A73E8"/>
- <stop offset="100%" stop-color="#0D47A1"/>
- </linearGradient>
-</defs>
-<rect x="540" y="600" width="200" height="48" rx="24" fill="url(#btnGrad)"/>
-```
-
-**Radial gradient** — best for spotlight backgrounds, circular accents:
-
-```xml
-<defs>
- <radialGradient id="spotBg" cx="50%" cy="50%" r="70%">
- <stop offset="0%" stop-color="#1A73E8" stop-opacity="0.15"/>
- <stop offset="100%" stop-color="#1A73E8" stop-opacity="0"/>
- </radialGradient>
-</defs>
-<circle cx="640" cy="360" r="300" fill="url(#spotBg)"/>
-```
+The interfaces below exist only for PPT behavior that ordinary SVG semantics
+cannot express. Use them only when the corresponding native capability is
+required.
### Pattern Fill — `<pattern>` with PPTX preset annotation
-`<pattern>` fills convert to native PPTX `<a:pattFill prst="...">` — but only PPTX's built-in preset patterns are reachable. The converter does **not** render hand-drawn `<path>` geometry inside the pattern; instead it reads two annotations off the `<pattern>` element and emits the matching DrawingML preset.
+`<pattern>` requests one fixed DrawingML preset; the converter does not render
+the tile's arbitrary geometry. Use this interface only when that preset mapping
+is intended.
-**Prefer explicit geometry when spacing matters.** A `<pattern>` renders at PowerPoint's **fixed preset density** — you cannot reproduce a specific tile size (e.g. a 40px grid). For grids / textures whose spacing or line weight is part of the design, draw the lines as **one `<path>` with all lines as subpaths** (`M40 0V720 M80 0V720 … M0 40H1280 …`, `fill="none" stroke=…`) — the converter supports `M/L/H/V` and multi-subpath, so it becomes **one editable vector shape that reproduces the exact spacing** across all four renderers. Reserve `<pattern>` + `data-pptx-pattern` for **round-tripping an existing PPTX** (decks imported via `pptx_to_svg`), where the source genuinely used a native preset fill. For pure display where no PPT-side editing is needed, `--svg-snapshot` is the other faithful option.
+`data-pptx-pattern="<preset>"` is required to select the intended preset from
+the enum below; without it, export falls back to `ltUpDiag`.
-**Required annotations** (only when you intentionally use a `<pattern>` preset):
-
-| Attribute | Purpose | Without it |
-|---|---|---|
-| `data-pptx-pattern="<preset>"` | Names the PPTX preset (one of the enum below) | Falls back to `ltUpDiag` — diagonal stripes, not your geometry |
-| Child `<rect fill="<bg-hex>"/>` | Background color of the pattern tile | `bg` falls back to `#FFFFFF`, painting over the page background |
-
-The child `<path>`'s `stroke` becomes the foreground color (the pattern's line color).
-
-```xml
-<defs>
- <pattern id="bpGrid" x="0" y="0" width="40" height="40"
- patternUnits="userSpaceOnUse" data-pptx-pattern="lgGrid">
- <rect width="40" height="40" fill="#0E2A47"/>
- <path d="M 40 0 L 0 0 0 40" fill="none" stroke="#2D4A6B" stroke-width="0.6"/>
- </pattern>
-</defs>
-<rect width="1280" height="720" fill="url(#bpGrid)"/>
-```
+Pattern colors may come from importer metadata (`data-pptx-fg` /
+`data-pptx-bg`) or from the pattern's child paint. Without metadata, the first
+child `<rect>` fill becomes the background and the first stroke (or other fill)
+becomes the foreground. A missing background defaults to white; a missing
+foreground means no native pattern fill can be emitted. The child geometry
+itself is never used as a repeatable tile.
**Valid `data-pptx-pattern` values** (OOXML `ST_PresetPatternVal` — closed enum, anything outside makes PowerPoint open with "needs to be repaired"):
@@ -815,7 +339,8 @@ The child `<path>`'s `stroke` becomes the foreground color (the pattern's line c
| Checks & confetti | `smCheck` · `lgCheck` · `smConfetti` · `lgConfetti` |
| Decorative | `horzBrick` · `diagBrick` · `weave` · `plaid` · `trellis` · `zigZag` · `wave` · `sphere` · `divot` · `shingle` · `solidDmnd` · `openDmnd` · `dotDmnd` |
-> `svg_quality_checker.py` warns on missing `data-pptx-pattern` and errors on values outside the enum. Catch these pre-export — PowerPoint's repair dialog hides which pattern broke.
+`svg_quality_checker.py` warns when the annotation is missing and errors when
+the preset is outside this enum.
### Native PPTX Table / Chart Markers (Opt-in)
@@ -932,22 +457,12 @@ match fallback `stroke-width`.
**XY chart schema**: `scatter` and `bubble` use `series[].x` + `series[].y`; `bubble` also requires one `series[].size` / `series[].sizes` value per point. `series[].points` is also accepted as `[x, y]` / `[x, y, size]` tuples or `{x, y, size}` objects.
-**Chart typography**: Native classic chart typography mirrors the visible SVG
-fallback. Copy fallback chart text sizes into metadata using the same px-style
-unit as SVG text (`1px = 0.75pt`). Put the shared visible chart font in
-`style.font_family`, and override local chart text objects or `data_labels`
-with `font_family` only when the fallback visibly differs. If omitted, the
-exporter infers the shared font family and base chart text size from visible
-fallback text inside the native marker, but explicit metadata remains the
-stable contract when roles differ. Typical mappings are chart title
-(`title_font_size`), chart subtitle (`subtitle_font_size`), chart labels
-(`axis_font_size`, shared by axis titles / ticks / legend unless the fallback
-differs), and notes (`note_font_size`). Use `axis_title_font_size`,
-`legend_font_size`, or per-entry companion `font_size` only when the fallback
-visibly uses a separate size. When no explicit fallback size exists for a role,
-default to compact PowerPoint text: `title_font_size: 16` (12pt),
-`subtitle_font_size: 12` (9pt), `axis_font_size: 12` (9pt), and
-`note_font_size: 12` (9pt).
+**Chart typography**: Metadata sizes use the same px-style unit as SVG text
+(`1px = 0.75pt`). `style.font_family` and the role-specific
+`title_font_size`, `subtitle_font_size`, `axis_font_size`,
+`axis_title_font_size`, `legend_font_size`, and `note_font_size` fields are
+required only when the native object must preserve typography that cannot be
+inferred unambiguously from the visible fallback.
**Chart chrome metadata**: Text that is visually part of the chart must be in
metadata, not only in SVG fallback children; metadata MUST still match visible
@@ -1040,13 +555,10 @@ implemented and validated one by one.
- `stock`: open / high / low / close series
3D chart aliases (`3DColumn`, `3DBar`, `3DLine`, `3DArea`, `3DPie`, cone,
-cylinder, pyramid variants, and `surface`) are intentionally unsupported. They
-add compatibility risk without meaningful presentation value.
+cylinder, pyramid variants, and `surface`) are unsupported.
-Native chart legends are off by default because right-side legends routinely
-steal plot area in PPT. Add `show_legend: true` only when the legend is needed;
-`legend_position` defaults to `bottom` and also accepts `top`, `left`, or
-`right`.
+Native legends are opt-in through `show_legend: true`; `legend_position`
+defaults to `bottom` and accepts `top`, `left`, or `right`.
**Forbidden — native marker transforms**: Do not rotate, skew, or matrix-transform native table/chart marker groups. Translate / scale is accepted; complex transforms fail export because PowerPoint native table/chart frames do not preserve arbitrary SVG transforms.
@@ -1088,64 +600,6 @@ image relationships must match exactly, no animation may target the shapes,
and moving them behind Slide content must preserve z-order. Keep page numbers
and every non-identical object Slide-local.
-### Theme Font Inheritance (Baseline and Template Export)
-
-New projects derive PowerPoint theme fonts from `spec_lock.md` typography when
-native export uses `baseline` or `template` structure mode:
-
-- `title_family` (falling back to `font_family`) becomes the theme major font.
-- `body_family` (falling back to `font_family`) becomes the theme minor font.
-- SVG text whose resolved exported face matches either locked family emits
- DrawingML `+mj-*` / `+mn-*` tokens instead of a fixed typeface.
-- When major and minor resolve to the same face, ordinary slide-local text uses
- the minor role; semantic `title` placeholders are forced to major, while all
- other semantic placeholders are forced to minor.
-- Local emphasis, code, brand, or other families that do not match the locked
- title/body faces remain concrete per-run fonts and do not change with the
- theme.
-
-This substitution is package-only: the SVG stays the live-preview truth, and
-the installed theme resolves the tokens to the same concrete fonts on initial
-open. Changing the PowerPoint theme later can therefore update matching text
-without changing the SVG geometry or the first export's visual design.
-
-`preserve` mode never rewrites source theme fonts, and `flat` remains the
-diagnostic slide-local/fixed-font comparison path. A project without a usable
-`spec_lock.md` typography section keeps the legacy concrete-font behavior.
-
-### Theme Color Inheritance (Baseline and Template Export)
-
-Native `baseline` and `template` export also derive the PowerPoint color scheme
-from `spec_lock.md` colors. The canonical mapping is:
-
-| Lock role | PowerPoint scheme slot |
-|---|---|
-| `bg` / `background` / `master_bg` | `lt1` |
-| `secondary_bg` / `bg_secondary` | `lt2` |
-| `text` / `body_text` | `dk1` |
-| `text_secondary` | `dk2` |
-| `primary` | `accent1` |
-| `accent` | `accent2` |
-| `secondary_accent` | `accent3` |
-| `border` | `accent4` |
-| First two additional non-black/non-white roles | `accent5` / `accent6` |
-
-The converter promotes an exact locked HEX to `a:schemeClr` only when its
-usage is compatible with the role: backgrounds prefer background roles, text
-prefers text/accent roles, strokes prefer `border`, and chart series use only
-the primary/accent family. This prevents the same literal HEX from coupling
-unrelated semantics such as a white page background and fixed white inverse
-text. Gradients, patterns, bullets, native tables, and exact native-chart
-series colors follow the same rule. Shadows, effects, unmatched local colors,
-and additional palette roles remain concrete `a:srgbClr` values.
-
-The initial rendering is unchanged because every scheme slot resolves to the
-same locked HEX. A later PowerPoint theme edit can update only the promoted
-roles; it does not rewrite the SVG or local exceptions. `preserve` never
-rewrites the imported source color scheme, `flat` keeps concrete colors for
-diagnostics, and projects without a usable colors section retain legacy fixed
-colors.
-
### Explicit PPTX Master / Layout / Placeholder Metadata (Template Export)
**Trigger**: Deck/layout template routes set `spec_lock.md`
@@ -1278,90 +732,10 @@ video or audio media from a decorative SVG group.
</svg>
```
-### transform: rotate — Element Rotation
-
-Rotation converts to native PPTX `<a:xfrm rot="...">`. Supported on all element types: `rect`, `circle`, `ellipse`, `line`, `path`, `polygon`, `polyline`, `image`, and `text`.
-
-```xml
-<!-- Rotated decorative element -->
-<rect x="100" y="100" width="60" height="60" fill="#1A73E8" fill-opacity="0.1"
- transform="rotate(45, 130, 130)"/>
-
-<!-- Rotated text label -->
-<text x="50" y="400" font-size="14" fill="#999999"
- transform="rotate(-90, 50, 400)">Y-Axis Label</text>
-```
-
-**Syntax**: `rotate(angle)` or `rotate(angle, cx, cy)` where `cx,cy` is the rotation center. Positive angles rotate clockwise.
-
-### Arc Paths — Donut / Pie Charts
-
-Calculate arc endpoint coordinates precisely with trigonometry. Never estimate — small errors produce wildly wrong shapes.
-
-**Calculation formula** (center `cx,cy`, radius `r`, angle `θ` in degrees):
-```
-x = cx + r × cos(θ × π / 180)
-y = cy + r × sin(θ × π / 180)
-```
-
-**Key rules**:
-1. Start at **-90°** (12 o'clock position) and go clockwise
-2. Each sector spans `percentage × 360°`
-3. Use **large-arc flag = 1** when the sector is > 180°, **0** otherwise
-4. sweep-direction = 1 (clockwise) for outer arc, 0 (counter-clockwise) for inner arc returning
-5. **Always verify** that the sum of all sector angles equals 360° and that the last sector's end point matches the first sector's start point
-
-**Example — 75% donut sector** (center 400,400, outer r=180, inner r=100):
-```
-Start angle: -90° → outer(400, 220), inner(400, 300)
-End angle: -90+270=180° → outer(220, 400), inner(300, 400)
-Large-arc flag: 1 (270° > 180°)
-
-<path d="M 400,220 A 180,180 0 1,1 220,400 L 300,400 A 100,100 0 1,0 400,300 Z"/>
-```
-
-### Polygon Arrows on Diagonal Lines
-
-> For connector lines prefer `marker-end`/`marker-start` (§1.1). For chunky/wide solid/non-connector arrows, use standalone polygon or path.
-
-Horizontal/vertical lines can use simple point offsets for `<polygon>` arrowheads. Diagonal lines need triangle vertices rotated to match line direction.
-
-**Method** — calculate triangle points using the line's direction vector:
-
-```
-Given line from (x1,y1) to (x2,y2):
-1. Direction vector: dx = x2-x1, dy = y2-y1
-2. Normalize: len = √(dx²+dy²), ux = dx/len, uy = dy/len
-3. Perpendicular: px = -uy, py = ux
-4. Arrow tip = (x2, y2)
-5. Back point 1 = (x2 - ux×12 + px×5, y2 - uy×12 + py×5)
-6. Back point 2 = (x2 - ux×12 - px×5, y2 - uy×12 - py×5)
-```
-
-**Example — diagonal line** from (260,310) to (370,430):
-```
-dx=110, dy=120, len≈162.8, ux=0.676, uy=0.737
-px=-0.737, py=0.676
-Tip: (370, 430)
-Back1: (370-8.1-3.7, 430-8.8+3.4) = (358.2, 424.6)
-Back2: (370-8.1+3.7, 430-8.8-3.4) = (365.6, 417.8)
-
-<polygon points="370,430 365.6,417.8 358.2,424.6" fill="#C8A96E"/>
-```
-
-⚠️ Never use a fixed downward/rightward triangle on a diagonal line — arrow will point wrong.
-
---
-## 8. Project Directory Structure
+## 8. Scope Boundary
-```
-project/
-├── svg_output/ # Raw SVGs (Executor output, contains placeholders)
-├── svg_final/ # Post-processed final SVGs (finalize_svg.py output)
-├── images/ # Image assets (user-provided + AI-generated)
-├── notes/ # Speaker notes (.md files matching SVG names)
-│ └── total.md # Complete speaker notes document (before splitting)
-├── templates/ # Project templates (if any)
-└── *.pptx # Exported PPT file
-```
+Project structure, commands, quality-gate order, and export products are owned
+by [`SKILL.md`](../SKILL.md). They are intentionally outside this SVG
+authoring policy.
diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.md
index a22f8f81..80bb18e8 100644
--- a/skills/ppt-master/references/strategist.md
+++ b/skills/ppt-master/references/strategist.md
@@ -20,7 +20,7 @@ As a top-tier AI presentation strategist, receive source documents, perform cont
## 1. Strategist Confirmation Stage
-🚧 **GATE — Mandatory read first**: `read_file templates/design_spec_reference.md` before any analysis or writing. The design_spec.md output MUST follow that template's 11-section structure exactly. After writing, self-check each section is present: I Project Info → II Canvas → III Visual Theme → IV Typography → V Layout → VI Icon → VII Visualization → VIII Image → IX Outline → X Speaker Notes → XI Tech Constraints.
+🚧 **GATE — Mandatory read first**: `read_file templates/design_spec_reference.md` before any analysis or writing. The design_spec.md output MUST follow that template's 10-section structure exactly. After writing, self-check each section is present: I Project Info → II Canvas → III Visual Theme → IV Typography → V Layout → VI Icon → VII Visualization → VIII Image → IX Outline → X Speaker Notes.
⛔ **BLOCKING**: After the read, present professional recommendations for the confirmation fields below and wait for explicit user confirmation.
@@ -826,7 +826,7 @@ This is what makes the axis meaningful: a `presentation` deck and a `text` deck
> Note: §IX is the only content copy the Executor re-reads after context compression — what you write there is what survives.
-### 6.2 Outline Output Specification (Must include 11 chapters)
+### 6.2 Outline Output Specification (Must include 10 sections)
| Chapter | Content Requirements |
|---------|---------------------|
@@ -840,7 +840,6 @@ This is what makes the axis meaningful: a `presentation` deck and a `text` deck
| VIII. Image Resource List | Filename, dimensions, ratio, purpose, status, generation description |
| IX. Content Outline | Grouped by chapter; each page includes layout, title, core message (the page's one idea), content blocks (in the selected phrasing mode), visualization type (if applicable) |
| X. Speaker Notes Requirements | File naming rules, content structure description |
-| XI. Technical Constraints Reminder | SVG generation rules, PPT compatibility rules |
**Generation steps**:
1. Read reference template: `templates/design_spec_reference.md`
diff --git a/skills/ppt-master/references/svg-image-embedding.md b/skills/ppt-master/references/svg-image-embedding.md
index f21a3314..aeaf730c 100644
--- a/skills/ppt-master/references/svg-image-embedding.md
+++ b/skills/ppt-master/references/svg-image-embedding.md
@@ -53,7 +53,7 @@ Defined in the Design Specification & Content Outline; each image carries an `Ac
├── Rendered formula → <image href="../images/formula_001.png" preserveAspectRatio="xMidYMid meet" .../>
└── Placeholder / Needs-Manual without file → Dashed border + description text
4. Preview: python3 -m http.server -d <project_path> 8000 → /svg_output/<filename>.svg
-5. Post-processing & Export → follow shared-standards.md §5
+5. Post-processing & Export → follow [`SKILL.md` Step 7](../SKILL.md)
```
> Keep external references in `svg_output/` during generation. `finalize_svg.py` auto-embeds images into `svg_final/`; export PPTX from `svg_final/`.
@@ -128,7 +128,7 @@ python3 -m http.server -d <project_path> 8000
## Conversion Process
-Use the unified pipeline in [shared-standards.md §5](shared-standards.md). `finalize_svg.py` runs before export so image references in `svg_output/` become embedded assets in `svg_final/`.
+Use the unified pipeline in [`SKILL.md` Step 7](../SKILL.md). `finalize_svg.py` runs before export so image references in `svg_output/` become embedded assets in `svg_final/`.
```bash
python3 scripts/finalize_svg.py <project_path>
diff --git a/skills/ppt-master/references/template-designer.md b/skills/ppt-master/references/template-designer.md
index 5ee419ef..a4db2f20 100644
--- a/skills/ppt-master/references/template-designer.md
+++ b/skills/ppt-master/references/template-designer.md
@@ -121,7 +121,7 @@ When the brief sets `Replication mode: mirror`, preserve literal page appearance
**Scope rule — personality only.** A template `design_spec.md` describes **what makes this template recognizable**: brand colors, signature decorative motifs, page-by-page visual character, bundled assets. It does **not** restate generic constraints — those live in the canonical references and are already loaded by every downstream role:
-- SVG technical constraints, PPT compatibility rules → [`shared-standards.md`](shared-standards.md)
+- General SVG required / forbidden / conditional interfaces → [`shared-standards.md`](shared-standards.md)
- Generic layout pattern library, spacing bands, font-size ratio bands → [`templates/design_spec_reference.md`](../templates/design_spec_reference.md) (read by Strategist when authoring the **project** design_spec)
- Canonical placeholder vocabulary → §4 below
- Content methodology (pyramid / SCQA / MECE) → [`strategist.md`](strategist.md)
@@ -189,8 +189,7 @@ Sections to **omit** from template `design_spec.md` (sourced elsewhere — listi
| Don't write | Source |
|---|---|
-| SVG technical constraints / Mandatory rules / Prohibited elements | `shared-standards.md` §1 |
-| PPT compatibility rules (opacity mapping, inline-styles-only, etc.) | `shared-standards.md` |
+| General SVG technical / compatibility rules | `shared-standards.md` |
| Generic layout pattern library (centered card / 三栏 / timeline / …) | `design_spec_reference.md` §V |
| Generic spacing bands (margin 40-60px, card gap 20-32px, etc.) | `design_spec_reference.md` §V |
| Generic font-size hierarchy (cover 2.5-5x body, page title 1.5-2x, …) | `design_spec_reference.md` §IV |
@@ -199,7 +198,10 @@ Sections to **omit** from template `design_spec.md` (sourced elsewhere — listi
| "Usage Instructions" boilerplate (copy template / select page / …) | `create-template.md` |
| Created Date / Page Count rows | not a library-level field |
-When rewriting an existing template that contains the omitted sections, delete them — do not leave a "see XXX" pointer behind. The pointer is what this scope rule replaces.
+When rewriting an existing template that contains an omitted generic section,
+delete it rather than leaving a pointer. Keep a template-specific boundary only
+inside the personality section it qualifies (asset system, motif, image
+treatment, or page roster); do not preserve a generic technical-rules heading.
### 2. Inherit Design Specification
diff --git a/skills/ppt-master/references/visual-styles/blueprint.md b/skills/ppt-master/references/visual-styles/blueprint.md
index ed6fd3fc..5e80ea4a 100644
--- a/skills/ppt-master/references/visual-styles/blueprint.md
+++ b/skills/ppt-master/references/visual-styles/blueprint.md
@@ -26,7 +26,7 @@ Engineering schematic — thin line work on dark blueprint paper, isometric proj
## 4. Texture / elevation
-- Flat line work, not material elevation. Depth reads from isometric projection and layered line weights, not shadows. Optional subtle corner vignette / accent glow on the dark paper — keep it faint. (Dark-field legibility: [`shared-standards.md §6`](../shared-standards.md).)
+- Flat line work, not material elevation. Depth reads from isometric projection and layered line weights, not shadows. Optional subtle corner vignette / accent glow on the dark paper — keep it faint.
## 5. Paired image-rendering
diff --git a/skills/ppt-master/references/visual-styles/chalkboard.md b/skills/ppt-master/references/visual-styles/chalkboard.md
index 9dbc6af3..dba8deee 100644
--- a/skills/ppt-master/references/visual-styles/chalkboard.md
+++ b/skills/ppt-master/references/visual-styles/chalkboard.md
@@ -21,7 +21,7 @@ Classroom chalkboard — a dark slate field, soft chalk-stroke line work, powder
- Dark slate field; off-white chalk carries most marks; the deck's colors appear as soft, powdery pastel chalk accents, used sparingly.
- Restrained and powdery — never saturated fills.
-> HEX values come from confirmation `e`; this style only governs the chalk-on-slate, powdery-accent discipline — it names no colors. (Dark-field legibility: [`shared-standards.md §6`](../shared-standards.md).)
+> HEX values come from confirmation `e`; this style only governs the chalk-on-slate, powdery-accent discipline — it names no colors.
## 4. Texture / elevation
diff --git a/skills/ppt-master/references/visual-styles/dark-tech.md b/skills/ppt-master/references/visual-styles/dark-tech.md
index f7b50dbb..09f7a677 100644
--- a/skills/ppt-master/references/visual-styles/dark-tech.md
+++ b/skills/ppt-master/references/visual-styles/dark-tech.md
@@ -26,7 +26,7 @@ Dark canvas, luminous accents, geometric precision. For tech, AI, dev tools, dat
## 4. Texture / elevation
-- Depth via glow and layering on dark, not drop shadows. Outer glow / light strokes mark elevation; gradients stay same-hue and subtle. (Dark-theme legibility — prefer light stroke / outer glow over black shadow: [`shared-standards.md §6`](../shared-standards.md).)
+- Depth via glow and layering on dark, not drop shadows. Outer glow / light strokes mark elevation; gradients stay same-hue and subtle.
## 5. Paired image-rendering
diff --git a/skills/ppt-master/references/visual-styles/data-journalism.md b/skills/ppt-master/references/visual-styles/data-journalism.md
index 4ba2f3cb..7d883be1 100644
--- a/skills/ppt-master/references/visual-styles/data-journalism.md
+++ b/skills/ppt-master/references/visual-styles/data-journalism.md
@@ -21,7 +21,7 @@ Bloomberg / Economist news-infographic — publication-grade information density
- A restrained field — light publication paper or dark graphite both fit (Economist vs Bloomberg-terminal); the deck's accent marks risk / key figures, an optional secondary distinguishes a second series; charts use tints of the same family, never a rainbow.
- Numbers are colored to *mean* (up / down / risk / focus), not to decorate.
-> HEX values come from confirmation `e`; this style only governs the restrained-field, meaning-coded-data discipline — it names no colors. (Dark-field legibility, if dark: [`shared-standards.md §6`](../shared-standards.md).)
+> HEX values come from confirmation `e`; this style only governs the restrained-field, meaning-coded-data discipline — it names no colors.
## 4. Texture / elevation
diff --git a/skills/ppt-master/references/visual-styles/glassmorphism.md b/skills/ppt-master/references/visual-styles/glassmorphism.md
index 7398a460..40d94192 100644
--- a/skills/ppt-master/references/visual-styles/glassmorphism.md
+++ b/skills/ppt-master/references/visual-styles/glassmorphism.md
@@ -25,7 +25,7 @@ Frosted-glass SaaS — translucent layered panels, flowing gradient light, float
## 4. Texture / elevation
-- Depth via translucency, layering, bright edge highlights, and soft background glow — not hard drop shadows. Smooth multi-stop gradients are intrinsic here (the one style where generous gradient use is on-brand); keep them luminous, not muddy. (Dark-field legibility: [`shared-standards.md §6`](../shared-standards.md).)
+- Depth via translucency, layering, bright edge highlights, and soft background glow — not hard drop shadows. Smooth multi-stop gradients are intrinsic here (the one style where generous gradient use is on-brand); keep them luminous, not muddy.
## 5. Paired image-rendering
diff --git a/skills/ppt-master/references/visual-styles/paper-cut.md b/skills/ppt-master/references/visual-styles/paper-cut.md
index 61f305d8..fb5a45cd 100644
--- a/skills/ppt-master/references/visual-styles/paper-cut.md
+++ b/skills/ppt-master/references/visual-styles/paper-cut.md
@@ -25,7 +25,7 @@ Layered paper-craft — scissor-cut shapes stacked in tactile layers, soft shado
## 4. Texture / elevation
-- Real layered depth — a soft 8-12% drop shadow under each cut layer is core here (the one style where layered shadow is the point, not a violation). Matte paper grain on each sheet. (Shadow rules: [`shared-standards.md §6`](../shared-standards.md).)
+- Real layered depth — a soft 8-12% drop shadow under each cut layer is core here (the one style where layered shadow is the point, not a violation). Matte paper grain on each sheet.
## 5. Paired image-rendering
diff --git a/skills/ppt-master/references/visual-styles/soft-rounded.md b/skills/ppt-master/references/visual-styles/soft-rounded.md
index 1ee66378..9e7a88a5 100644
--- a/skills/ppt-master/references/visual-styles/soft-rounded.md
+++ b/skills/ppt-master/references/visual-styles/soft-rounded.md
@@ -26,7 +26,7 @@ Approachable and modern. Rounded cards, gentle elevation, friendly rhythm. For p
## 4. Texture / elevation
-- Gentle elevation: soft shadows on floating cards (resting tier), subtle tints, optional same-hue gradients. Two-tier elevation max; keep peer-grid cards flat. (Full shadow rules: [`shared-standards.md §6`](../shared-standards.md).)
+- Gentle elevation: soft shadows on floating cards (resting tier), subtle tints, optional same-hue gradients. Two-tier elevation max; keep peer-grid cards flat.
## 5. Paired image-rendering
diff --git a/skills/ppt-master/scripts/config.py b/skills/ppt-master/scripts/config.py
index 733f0399..bd35ae92 100644
--- a/skills/ppt-master/scripts/config.py
+++ b/skills/ppt-master/scripts/config.py
@@ -486,59 +486,15 @@ LAYOUT_MARGINS = {
# ============================================================
-# SVG Technical Specifications
+# SVG Policy Reference
# ============================================================
+# Do not mirror element/attribute rules here. The shared standard is the
+# authoring authority and the quality checker enforces it.
+# Keep the exported key for compatibility with existing config consumers.
SVG_CONSTRAINTS = {
- # Forbidden elements - PPT incompatible
- 'forbidden_elements': [
- # Clipping / Masking
- # Note: `clipPath` on <image> elements is conditionally allowed — the
- # converter maps qualifying clip shapes to DrawingML picture geometry.
- # See references/shared-standards.md §1.2. It is NOT listed here
- # because this flat list has no per-parent-element semantics; the
- # actual validation is in svg_quality_checker._check_forbidden_elements.
- 'mask',
- # Style system
- 'style',
- # Structure / Nesting
- 'foreignObject',
- # Text / Fonts
- 'textPath',
- # Animation / Interaction
- 'animate',
- 'animateMotion',
- 'animateTransform',
- 'animateColor',
- 'set',
- 'script',
- # Others
- 'iframe',
- ],
- # Forbidden attributes
- # Note: marker-start / marker-end are NOT banned — they are conditionally
- # allowed (see references/shared-standards.md §1.1). The svg_to_pptx
- # converter maps qualifying <marker> defs to native DrawingML
- # <a:headEnd>/<a:tailEnd>.
- 'forbidden_attributes': [
- 'class',
- 'onclick', 'onload', 'onmouseover', 'onmouseout',
- 'onfocus', 'onblur', 'onchange',
- ],
- # Forbidden patterns (regex matching)
- 'forbidden_patterns': [
- r'@font-face', # Web fonts
- r'<\?xml-stylesheet\b', # External CSS
- r'<link[^>]*rel\s*=\s*["\']stylesheet["\']',
- r'@import\s+', # External CSS
- r'\bon\w+\s*=', # Event attributes
- ],
- 'recommended_fonts': [
- 'system-ui',
- '-apple-system',
- 'BlinkMacSystemFont',
- 'Segoe UI'
- ]
+ 'authority': 'skills/ppt-master/references/shared-standards.md',
+ 'validator': 'skills/ppt-master/scripts/svg_quality_checker.py',
}
@@ -637,19 +593,6 @@ class Config:
"""
return FONT_SIZES.get(size_name, FONT_SIZES['body'])
- @staticmethod
- def validate_svg_element(element_name: str) -> bool:
- """
- Validate whether an SVG element is allowed.
-
- Args:
- element_name: Element name
-
- Returns:
- Whether the element is allowed
- """
- return element_name.lower() not in [e.lower() for e in SVG_CONSTRAINTS['forbidden_elements']]
-
@staticmethod
def get_project_path(subdir: str = '') -> Path:
"""
diff --git a/skills/ppt-master/scripts/docs/svg-pipeline.md b/skills/ppt-master/scripts/docs/svg-pipeline.md
index 062f1706..23b897df 100644
--- a/skills/ppt-master/scripts/docs/svg-pipeline.md
+++ b/skills/ppt-master/scripts/docs/svg-pipeline.md
@@ -221,49 +221,13 @@ python3 scripts/svg_finalize/embed_icons.py --dry-run svg_output/*.svg
Replaces `<use data-icon="chunk-filled/name" .../>`, `<use data-icon="tabler-filled/name" .../>` and `<use data-icon="tabler-outline/name" .../>` placeholders with actual SVG path elements. Use for manual icon embedding checks outside `finalize_svg.py`.
-## PPT Compatibility Rules
-
-Supported CSS paint colors include named colors, `rgb()` / `rgba()`, `hsl()` /
-`hsla()`, and 3/4/6/8-digit HEX. Alpha embedded in the color multiplies with
-`opacity`, `fill-opacity`, `stroke-opacity`, `stop-opacity`, or supported
-effect alpha during native export. Explicit opacity attributes remain valid
-when they make palette reuse clearer.
-
-Literal inline geometry is compiled before finalize and native conversion.
-Supported pairs are `rect` (`x/y/width/height/rx/ry`), `circle` (`cx/cy/r`),
-`ellipse` (`cx/cy/rx/ry`), and `image` / `svg` / `use`
-(`x/y/width/height`). A declaration in `style="..."` overrides the same XML
-attribute. Non-zero values must be finite `px` literals; exact zero may omit the
-unit, and sizes/radii cannot be negative. Percentages, `auto`, `calc()`,
-`var()`, `!important`, `inherit`, other units, unsupported element/property
-pairs, stylesheets, selectors, and CSS cascade are rejected. Use XML attributes
-for line endpoints, text positions, path data, and polygon/polyline points. See
-[`shared-standards.md`](../../references/shared-standards.md) §2.
-
-`<g opacity="0..1">` is supported as a per-descendant alpha approximation.
-Nested values multiply; overlapping children may differ from isolated SVG
-group compositing. Transparent native table/chart markers require the default
-SVG fallback rather than `--native-objects`.
-
-`<image opacity="0..1">` is supported directly. Native export writes
-DrawingML `a:alphaModFix`, and PPTX import restores the SVG opacity value.
-
-Static same-document `<use>` is supported as compile-time reuse. Use exact
-`href="#id"` or `xlink:href="#id"` references to `symbol`, `g`, `use`, `rect`,
-`circle`, `ellipse`, `line`, `path`, `polygon`, `polyline`, `text`, or `image`;
-internal subtree references use exact `url(#id)` syntax. `x` / `y` accept only
-finite unitless or `px` values. A symbol needs a valid four-number `viewBox`
-with positive width/height and a positive unitless/`px` instance `width` /
-`height`; aligned `meet` and plain `none` are supported, while `slice`, `refX`,
-and `refY` are rejected. Symbol artwork must stay inside the `viewBox` because
-overflow clipping is not reproduced. External, missing, conflicting, circular,
-and duplicate-ID references fail, as does reuse of `data-pptx-layer*`,
-`data-pptx-native*`, or `data-pptx-placeholder*` metadata. Finalize and native
-export recursively materialize the subtree with rewritten instance-local IDs.
-Reference depth is capped at 64 and expansion at 10,000 instances per SVG;
-PPTX import does not reconstruct `<use>` / `<symbol>`.
-
-PowerPoint also has trouble with unsupported filters and direct SVG features
-not mapped to DrawingML. Connector arrows may use qualified
-`marker-start` / `marker-end`; chunky or exotic arrows should be standalone
-`<path>` / `<polygon>` shapes.
+## SVG Compatibility Contract
+
+The canonical SVG authoring and native-mapping contract lives exclusively in
+[`shared-standards.md`](../../references/shared-standards.md). This tool guide
+does not repeat accepted syntax, rejected constructs, or conditional limits.
+
+`svg_quality_checker.py` validates source SVG before finalization.
+`finalize_svg.py` and native export apply the preprocessing required by that
+contract, while native conversion fails on unsupported visual elements rather
+than silently dropping them.
diff --git a/skills/ppt-master/scripts/svg_quality_checker.py b/skills/ppt-master/scripts/svg_quality_checker.py
index b511daf5..8770cb51 100644
--- a/skills/ppt-master/scripts/svg_quality_checker.py
+++ b/skills/ppt-master/scripts/svg_quality_checker.py
@@ -1294,9 +1294,8 @@ class SVGQualityChecker:
`dkUpDiag`). Two failure modes worth catching pre-export:
1. Missing annotation → converter silently falls back to `ltUpDiag`
- (diagonal stripes) and picks `bg = #FFFFFF` when the pattern has
- no child <rect>, turning a hand-authored grid into white-on-stripes
- in PPTX.
+ (diagonal stripes). Color metadata or child paints still resolve,
+ with white as the final background fallback.
2. Invalid preset name → PPTX schema rejects the file; PowerPoint
opens it with "needs to be repaired". OOXML
`ST_PresetPatternVal` is a closed enum — only the names in
@@ -1311,9 +1310,9 @@ class SVGQualityChecker:
result['warnings'].append(
f"<pattern id=\"{pat_id}\"> has no data-pptx-pattern attribute — "
"PPTX export will fall back to `ltUpDiag` (diagonal stripes), "
- "not your custom geometry. Add data-pptx-pattern=\"lgGrid\" / "
- "\"smGrid\" / etc. plus a <rect fill=\"<bg>\"/> child so the "
- "preset and bg color match your design."
+ "not your custom geometry. Add a valid data-pptx-pattern; "
+ "set data-pptx-fg/data-pptx-bg or matching child paints "
+ "when explicit pattern colors are required."
)
continue
if prst not in self._OOXML_PATTERN_PRESETS:
@@ -1323,8 +1322,8 @@ class SVGQualityChecker:
"will fail schema validation ('needs to be repaired'). "
"Use one of: smGrid / lgGrid / dotGrid (grids), "
"ltUpDiag / dkUpDiag / cross / diagCross / weave / plaid / "
- "horzBrick (others); full enum in svg_quality_checker.py "
- "_OOXML_PATTERN_PRESETS."
+ "horzBrick (others); see references/shared-standards.md §7 "
+ "for the full authoring enum."
)
def _check_native_object_markers(self, root: ET.Element, result: Dict) -> None:
diff --git a/skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.md b/skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.md
index 19bd4c86..03fcd09f 100644
--- a/skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.md
+++ b/skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.md
@@ -5,11 +5,10 @@
## 0. 上游规范引用
-本文档是 **图表模板专用** 的美学与实现规范。所有图表同时必须遵守项目级通用技术约束:
-
-> **[`references/shared-standards.md`](../../references/shared-standards.md)** — SVG 禁用特性黑名单、PPT 兼容性替代、Canvas 格式、tspan 内联规则、分组规范、阴影/叠加技术、后处理管线
-
-以下章节摘录了 shared-standards 中与图表模板最密切相关的条目。完整细节(如 marker 条件约束、clipPath 条件约束、弧线路径计算公式等)请查阅上游文档。
+本文档只定义 **图表模板专用** 的美学与实现配方。项目级 SVG
+创作、兼容性例外与条件映射统一以
+[`references/shared-standards.md`](../../references/shared-standards.md)
+为权威;本指南不摘录、不放宽该合同。
---
@@ -75,7 +74,6 @@ font-family="-apple-system, BlinkMacSystemFont, 'Segoe UI', 'PingFang SC', 'Micr
```
- 纯英文场景可省略 `'PingFang SC', 'Microsoft YaHei'`
-- **禁止** 使用 `@font-face`、外部字体、`<style>` 标签
### 2.2 字号层级
@@ -90,23 +88,9 @@ font-family="-apple-system, BlinkMacSystemFont, 'Segoe UI', 'PingFang SC', 'Micr
> **最小字号下限:12px**。所有文本不得小于 12px。
-### 2.3 tspan 规范
+### 2.3 同一图表标签的内联格式
-所有 `<text>` 元素的文本内容 **必须** 包裹在 `<tspan>` 中:
-
-```xml
-<!-- 正确 -->
-<text x="60" y="80" font-size="34" fill="#0F172A">
- <tspan>图表标题</tspan>
-</text>
-
-<!-- 错误 -->
-<text x="60" y="80" font-size="34" fill="#0F172A">图表标题</text>
-```
-
-### 2.4 内联格式化规则(shared-standards SS4)
-
-**单逻辑行 = 单 `<text>`**。同一行内需要多色/多粗细时,用内联 `<tspan>` 实现,**不要**用多个并排 `<text>`:
+当一个图表标签需要在 PPT 中保持为单一可编辑文本框时,把同一逻辑行写进一个 `<text>`,并用内联 `<tspan>` 表达多色或多粗细。若本来就需要多个独立文本框,则可使用多个 `<text>`:
```xml
<!-- 正确:一个 text frame,三个 run -->
@@ -114,15 +98,15 @@ font-family="-apple-system, BlinkMacSystemFont, 'Segoe UI', 'PingFang SC', 'Micr
实现<tspan fill="#3B82F6" font-weight="bold">10倍</tspan>效率提升
</text>
-<!-- 错误:三个独立 text frame,PPT 中无法作为一行编辑 -->
+<!-- 若目标是单一文本框,则不适用:下面会生成三个独立 text frame -->
<text x="100" y="200">实现</text>
<text x="160" y="200" fill="#3B82F6">10倍</text>
<text x="240" y="200">效率提升</text>
```
-> 内联 tspan **不得** 携带 `x` / `y` / `dy`,否则后处理会将其拆分为独立 text frame。`dx` 可用于微调字距。
+> 只有需要留在同一文本框内的 inline tspan 才不带 `x` / `y` / `dy`;带这些定位属性的 tspan 会按独立文本框处理。`dx` 可用于微调字距。
-### 2.5 数据高亮默认行为
+### 2.4 数据高亮默认行为
图表中的关键数据文本应默认高亮:
- **数值结果** — 百分比、倍数、金额 → `<tspan fill="主题色" font-weight="bold">`
@@ -133,7 +117,9 @@ font-family="-apple-system, BlinkMacSystemFont, 'Segoe UI', 'PingFang SC', 'Micr
## 3. 阴影滤镜
-`<filter>` 本身是允许的、且是 PPT 阴影/发光的官方推荐路径(详见本节末尾的"禁用列表"说明)。本节统一阴影 primitive 写法——使用 `feFlood` 方案,**禁止** `<filter>` 内部使用 `<feComponentTransfer>`:
+本节只规定图表模板库采用的阴影配方,不定义项目级 filter
+支持边界。图表阴影统一使用 `feFlood` 方案,本指南不采用
+`<feComponentTransfer>`:
```xml
<filter id="chartShadow" x="-15%" y="-15%" width="130%" height="130%">
@@ -156,19 +142,20 @@ font-family="-apple-system, BlinkMacSystemFont, 'Segoe UI', 'PingFang SC', 'Micr
| 中型元素(柱子、箱体) | 2-3 | 1-2 | 0.10-0.15 |
| 轻型元素(底部卡片) | 4-6 | 2-4 | 0.06-0.08 |
-### 禁用列表
+### 本指南实现约定
- `flood-color="#000000"` → 必须用 `#0F172A`
- `<feComponentTransfer>` + `<feFuncA slope=...>` → 用 `<feFlood flood-color flood-opacity>` 替代
- `flood-opacity > 0.20` → 阴影过重,最大 0.15-0.20
-> **被禁的是 sub-element,不是 `<filter>` 本身。** `<filter>` 是 PPT Master 允许的、官方推荐的阴影/发光路径(见 [`shared-standards.md`](../../references/shared-standards.md) §1 黑名单不含 filter、§6 把 filter shadow 列为 drop-shadow 的官方实现),转换器 [`svg_to_pptx/drawingml/styles.py`](../../scripts/svg_to_pptx/drawingml/styles.py) 也主动把 `feGaussianBlur` + `feOffset` + `feFlood` + `feComposite` + `feMerge`(以及 `feDropShadow` 简写)映射成 DrawingML `<a:outerShdw>`。
->
-> 单独禁 `feComponentTransfer/feFuncA(slope)` 的原因:**它物理上只能调透明度、无法携带颜色**。转换器读到 `feFuncA slope` 时只把它当作 alpha,颜色字段保持默认 `'000000'`——SVG 端看起来阴影颜色正常(因为 SourceAlpha 本身是黑),但导出到 PPTX 后阴影颜色会被定死成纯黑 `#000000`,与同页其他用 `feFlood flood-color="#0F172A"` 的卡片产生肉眼可见的冷暖色差。
+> 这是图表模板的色彩一致性约定,不是项目级 SVG 黑名单。单独排除
+> `feComponentTransfer/feFuncA(slope)`,是因为它只能调透明度、无法携带
+> 颜色,容易让阴影退回纯黑,与同页使用 `feFlood`
+> `flood-color="#0F172A"` 的卡片产生肉眼可见的冷暖色差。
>
-> 简言之:**用 filter 没问题,但 primitive 必须能把"颜色"显式表达出来;只能表达"透明度"的 primitive 是被禁的。**
+> 简言之:本库的图表阴影必须显式表达颜色,而不能只表达透明度。
-### 阴影使用原则(shared-standards SS6)
+### 图表阴影使用原则
> **阴影是美学成分,不是默认处理。** 克制而非丰富才能产生"经过设计"的感觉。 "阴影被感知而非被看见" 是高端美学标准。
@@ -222,7 +209,7 @@ font-family="-apple-system, BlinkMacSystemFont, 'Segoe UI', 'PingFang SC', 'Micr
## 5. 结构规范
-### 5.1 层级分组(shared-standards SS4 Grouping)
+### 5.1 图表层级分组
使用 `<g id="...">` 进行语义分组,便于 PPT 中逐个操作/动画:
@@ -241,7 +228,7 @@ font-family="-apple-system, BlinkMacSystemFont, 'Segoe UI', 'PingFang SC', 'Micr
</g>
```
-**分组单元参考**(来自 shared-standards):
+**图表模板分组单元**:
| 分组单元 | 包含内容 |
|---------|---------|
@@ -254,8 +241,6 @@ font-family="-apple-system, BlinkMacSystemFont, 'Segoe UI', 'PingFang SC', 'Micr
**命名约定**:使用描述性 `id`(如 `card-1`、`step-discover`、`header`、`footer`)。
-> `<g opacity="0..1">` 可按 SS2 近似转换;纯结构 `<g>` 仍是常规分组方式。
-
### 5.2 viewBox
固定为 `0 0 1280 720`(PPT 16:9),不可修改。
@@ -278,57 +263,11 @@ font-family="-apple-system, BlinkMacSystemFont, 'Segoe UI', 'PingFang SC', 'Micr
---
-## 6. SVG 禁用特性与兼容性(shared-standards SS1-2)
-
-### 6.1 绝对禁止
-
-| 禁用特性 | 替代方案 |
-|---------|---------|
-| HTML 命名实体(`&nbsp;` `&mdash;` `&copy;` `&ndash;` `&reg;` `&hellip;` `&bull;` …) | 直接写原生 Unicode 字符(`—` `–` `©` `®` `→` NBSP …) |
-| 文本/属性值中裸写 `& < > " '` | 必须写成 XML 实体 `&amp;` `&lt;` `&gt;` `&quot;` `&apos;` |
-| `<style>` / `class` | 内联属性(`id` 可用于本地引用和语义标记) |
-| `<foreignObject>` | `<text>` + `<tspan>` |
-| `mask` | 叠加遮罩矩形 / gradient overlay |
-| `textPath` | 手动排列 `<text>` |
-| `@font-face` | 系统字体栈 |
-| `<animate*>` / `<set>` | 无(PPT 侧处理动画) |
-| `<script>` / event 属性 | 无 |
-| `<iframe>` | 无 |
-
-### 6.2 PPT 颜色语法
-
-支持常用命名色、`rgb()` / `rgba()`、`hsl()` / `hsla()` 以及 3/4/6/8 位
-HEX。颜色内嵌 alpha 会与 `opacity`、`fill-opacity`、`stroke-opacity`、
-`stop-opacity` 继续相乘;需要复用同一色板时,也可继续采用独立透明度属性。
-
-### 6.3 条件允许
-
-| 特性 | 条件 | 转换结果 |
-|------|------|----------|
-| `<g opacity="...">` | 数值范围 `0..1`;不包裹 `data-pptx-native` 图表/表格 | 后代对象分别写入 DrawingML alpha;重叠区域为近似 |
-| `<image opacity="...">` | 数值范围 `0..1` | DrawingML `<a:alphaModFix>` |
-| 本文档内静态 `<use href="#id">` / `xlink:href="#id"` | 目标为 `symbol/g/use/rect/circle/ellipse/line/path/polygon/polyline/text/image`;`x/y` 仅 unitless/`px`;`symbol` 还需合法 `viewBox` 与正数 unitless/`px` `width/height` | 导出前递归展开为带独立 ID 的完整元素 |
-| `marker-start` / `marker-end` | `<marker>` 在 `<defs>` 中,`orient="auto"`,形状为三角/菱形/圆 | DrawingML `<a:headEnd>` / `<a:tailEnd>` |
-| `clipPath` on `<image>` | `<clipPath>` 在 `<defs>` 中,单子元素,**仅用于 image** | DrawingML `<a:prstGeom>` / `<a:custGeom>` |
-| `stroke-dasharray` | 使用预设值 `4,4` / `2,2` / `8,4` / `8,4,2,4` | PPTX `<a:prstDash>` |
-| `text-decoration` | `underline` / `line-through` | PPTX 原生文本格式 |
-| `transform="rotate(...)"` | 所有元素类型均支持 | PPTX `<a:xfrm rot="...">` |
-
-> 本地 `<use>` 只接受精确 `#id` / `url(#id)` 内部片段。外部、缺失、
-> 冲突、循环、重复 ID,`symbol` 的 `slice` / `refX` / `refY`,以及对
-> `data-pptx-layer*` / `data-pptx-native*` / `data-pptx-placeholder*` 结构元数据的
-> 复用均禁止;PPTX 回导不重建 `<use>`。完整条件约束见
-> [`shared-standards.md`](../../references/shared-standards.md) SS1.1(marker)、
-> SS1.2(clipPath)和 SS1.3(本地 use)。
-
-### 6.4 虚线预设对照
-
-| SVG 值 | PPTX 预设 | 适用场景 |
-|--------|-----------|---------|
-| `4,4` | Dash | 通用虚线、分隔线 |
-| `2,2` | Dot (sysDot) | 占位轮廓、细边框 |
-| `8,4` | Long dash | 时间线连接、流程箭头 |
-| `8,4,2,4` | Long dash-dot | 技术图纸、尺寸线 |
+## 6. 通用 SVG 技术约束
+
+本指南不定义或摘录项目级 SVG 允许项、禁用项与条件映射。当前合同统一见
+[`shared-standards.md`](../../references/shared-standards.md);新增或修改模板时,
+必须对目标文件运行 `svg_quality_checker.py` 并通过校验。
---
@@ -418,15 +357,12 @@ HEX。颜色内嵌 alpha 会与 `opacity`、`fill-opacity`、`stroke-opacity`、
### 排版
- [ ] 无 `font-size < 12` 的文本
-- [ ] 所有 `<text>` 内容包裹 `<tspan>`
-- [ ] 同一行多格式用内联 `<tspan>`,**非**多个并排 `<text>`
-- [ ] 内联 `<tspan>` 不携带 `x` / `y` / `dy`
+- [ ] 需要保持为单一 PPT 文本框的多格式标签使用 inline `<tspan>`;只有这类 inline run 不携带 `x` / `y` / `dy`
- [ ] 标题 34px、副标题 18px、来源 14px
### 结构
- [ ] 主要元素有语义化 `<g id="...">`
-- [ ] 无 `<style>`、`class`、`<foreignObject>`、`mask`
-- [ ] 文本字符为原生 Unicode(`—` `©` `→` NBSP 等),无 HTML 命名实体(`&nbsp;` `&mdash;` `&copy;` 等);裸 `& < >` 已转义为 `&amp; &lt; &gt;`
+- [ ] `svg_quality_checker.py` 对目标模板通过;通用 SVG 合同不在本清单复述
### 阴影
- [ ] 使用 `feFlood` 方案(非 `feComponentTransfer`)
@@ -644,4 +580,3 @@ echo "Small fonts:" && grep -c 'font-size="[0-9]"' "skills/ppt-master/templates/
| §11.5 倾斜虚线连接箭头 | `matrix_2x2.svg` |
| §11.6 接地椭圆 | `team_roster.svg` |
| §11.7 双向交互箭头 | `client_server_flow.svg` |
-
diff --git a/skills/ppt-master/templates/decks/README.md b/skills/ppt-master/templates/decks/README.md
index 9900ce11..7c1b4ee8 100644
--- a/skills/ppt-master/templates/decks/README.md
+++ b/skills/ppt-master/templates/decks/README.md
@@ -42,7 +42,7 @@ primary_color: "#XXXXXX"
## VIII. SVG Page Roster # Structure — file list + per-file purpose
```
-Decks may include additional supporting sections (Voice & Tone, Icon Style, Layout Modes, Spacing Specification, SVG Technical Constraints, Placeholder Specification, Asset Specification, Usage Notes). Use them when meaningful for the replica.
+Decks may include additional supporting sections (Voice & Tone, Icon Style, Layout Modes, Spacing Specification, Placeholder Specification, Asset Specification, Usage Notes). Put a template-specific required / forbidden / conditional boundary inside the personality section it qualifies. General SVG/PPT authoring rules belong only in [`shared-standards.md`](../../references/shared-standards.md); do not add a generic technical-rules section or pointer to a deck spec.
---
diff --git "a/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\344\277\241/design_spec.md" "b/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\344\277\241/design_spec.md"
index 0e5fd4f2..c2a0b0f0 100644
--- "a/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\344\277\241/design_spec.md"
+++ "b/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\344\277\241/design_spec.md"
@@ -99,6 +99,7 @@ primary_color: "#C00000"
- Chapter pages are cleaner section-divider pages and should not inherit the content-page header ribbon.
- Each page should contain at most one formal logo mark; sidebars should rely on slogan and skyline imagery instead of repeated logo lockups.
- The content page remains open-canvas by default and should not reserve a large fixed sidebar.
+- Repeated telecom motifs use one reusable structure family rather than unrelated decorative variants.
---
@@ -180,18 +181,7 @@ primary_color: "#C00000"
---
-## X. SVG Technical Constraints
-
-1. `viewBox` must remain `0 0 1280 720`
-2. Do not use `mask`, `<style>`, `class`, or `foreignObject`. `clipPath` is allowed only on `<image>` under `shared-standards.md` §1.2
-3. Use plain vector geometry and `<image>` references to packaged assets only
-4. CSS alpha colors and explicit `fill-opacity` / `stroke-opacity` are both supported; values multiply
-5. Text wrapping should be handled with `<tspan>` if needed
-6. Avoid PPT-fragile decorative complexity; simplify repeated motifs into reusable structures
-
----
-
-## XI. Placeholder Specification
+## X. Placeholder Specification
| Placeholder | Purpose | Applicable Page |
| --- | --- | --- |
@@ -214,8 +204,9 @@ primary_color: "#C00000"
---
-## XII. Usage Guide
+## XI. Usage Guide
1. Reuse `logo.png` and `footer_ribbon.png` as fixed brand assets; `slogan_red.png` and `skyline_bg.png` should be used selectively and only on the cover / ending pages.
2. Keep generated text inside the documented safe areas; only chapter pages use a strong left/right split.
3. Prefer red emphasis only for structure and key figures; do not over-saturate the content area.
+4. Reference only assets packaged with this template.
diff --git "a/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\345\273\272/design_spec.md" "b/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\345\273\272/design_spec.md"
index 62585cb0..e3612125 100644
--- "a/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\345\273\272/design_spec.md"
+++ "b/skills/ppt-master/templates/decks/\344\270\255\345\233\275\347\224\265\345\273\272/design_spec.md"
@@ -98,6 +98,8 @@ primary_color: "#00418D"
| **Content** | y=100, h=560px | Main content area |
| **Footer** | y=680, h=40px | Page number, company name, bottom decorative line |
+**Required background layer**: Every page retains the template's full-canvas background layer.
+
---
## VI. Page Types
@@ -178,27 +180,7 @@ primary_color: "#00418D"
---
-## X. SVG Technical Constraints
-
-### Mandatory Rules
-
-1. viewBox fixed at `0 0 1280 720`
-2. Background must include a full-screen `<rect>`
-3. Text wrapping via `<tspan>`
-4. Opacity must use `fill-opacity` / `stroke-opacity`
-5. `marker-start` / `marker-end` conditionally allowed — see shared-standards.md §1.1 (marker in `<defs>`, `orient="auto"`, shape = triangle/diamond/oval)
-
-### Forbidden Elements (Blacklist)
-
-- `mask` (masking); `clipPath` is allowed only on `<image>` under `shared-standards.md` §1.2
-- `<style>`, `class` (stylesheets; `id` within `<defs>` is allowed)
-- `foreignObject` (foreign objects)
-- `textPath` (text on path)
-- `animate`, `animateTransform`, `set` (animations)
-
----
-
-## XI. Placeholder Specification
+## X. Placeholder Specification
| Placeholder | Description |
| -------------------- | ------------------ |
@@ -219,7 +201,7 @@ primary_color: "#00418D"
---
-## XII. Usage Notes (Recommended)
+## XI. Usage Notes (Recommended)
1. **Logo Adaptation**: Cover and ending pages use inverted (white) Logo; content page upper-right uses color or inverted Logo.
2. **Image Assets**: Ensure the `images/` folder under the template directory contains necessary Logo files.
diff --git "a/skills/ppt-master/templates/decks/\344\270\255\346\261\275\347\240\224/design_spec.md" "b/skills/ppt-master/templates/decks/\344\270\255\346\261\275\347\240\224/design_spec.md"
index ec7df49a..76ecd4a7 100644
--- "a/skills/ppt-master/templates/decks/\344\270\255\346\261\275\347\240\224/design_spec.md"
+++ "b/skills/ppt-master/templates/decks/\344\270\255\346\261\275\347\240\224/design_spec.md"
@@ -183,27 +183,7 @@ primary_color: "#004098"
---
-## X. SVG Technical Constraints
-
-### Mandatory Rules
-
-1. viewBox: `0 0 1280 720`
-2. Use `<rect>` elements for backgrounds
-3. Text wrapping via `<tspan>` (no `<foreignObject>`)
-4. CSS alpha colors and explicit `fill-opacity` / `stroke-opacity` are both supported; values multiply
-5. Forbidden: `mask`, `<style>`, `class`, `foreignObject`. `clipPath` is allowed only on `<image>` under `shared-standards.md` §1.2
-6. Forbidden: `textPath`, `animate*`, `script`
-7. `marker-start` / `marker-end` conditionally allowed (marker in `<defs>`, `orient="auto"`, shape = triangle/diamond/oval) — see shared-standards.md §1.1
-
-### PPT Compatibility Rules
-
-- `<g opacity="0..1">` is allowed as per-descendant alpha; overlapping children may composite differently
-- `<image opacity="0..1">` maps to native picture transparency; use overlays only for color washes
-- Inline styles only — no external CSS or `@font-face`
-
----
-
-## XI. Placeholder Specification
+## X. Placeholder Specification
Templates use `{{PLACEHOLDER}}` format. Common placeholders:
@@ -226,7 +206,7 @@ Templates use `{{PLACEHOLDER}}` format. Common placeholders:
---
-## XII. Usage Notes (Recommended)
+## XI. Usage Notes (Recommended)
1. **Template Deployment**: Copy the template to your project directory.
2. **Asset Replacement**: Replace `大型 logo.png` (592×238) and `右上角 logo.png` (113×50) in the `images` directory.
diff --git "a/skills/ppt-master/templates/decks/\346\213\233\345\225\206\351\223\266\350\241\214/design_spec.md" "b/skills/ppt-master/templates/decks/\346\213\233\345\225\206\351\223\266\350\241\214/design_spec.md"
index aedbc19f..67021daf 100644
--- "a/skills/ppt-master/templates/decks/\346\213\233\345\225\206\351\223\266\350\241\214/design_spec.md"
+++ "b/skills/ppt-master/templates/decks/\346\213\233\345\225\206\351\223\266\350\241\214/design_spec.md"
@@ -140,15 +140,7 @@ Reference slides read before generation: `1, 2, 3, 4, 6, 9, 11, 13, 16, 18`.
| **Title to Body** | 44px |
| **Footer Offset** | 32px from bottom |
-## X. SVG Technical Constraints
-
-1. `viewBox` must stay `0 0 1280 720`
-2. No `mask`, `<style>`, `class`, `foreignObject`, `textPath`, or animation tags. `clipPath` is allowed only on `<image>` under `shared-standards.md` §1.2
-3. Use supported CSS colors or HEX; embedded alpha multiplies with `fill-opacity` / `stroke-opacity`
-4. Keep image assets semantic and minimal
-5. Prefer vector reconstruction over embedding PPT-export fragments
-
-## XI. Placeholder Specification
+## X. Placeholder Specification
| Placeholder | Description |
| --- | --- |
@@ -184,7 +176,7 @@ Reference slides read before generation: `1, 2, 3, 4, 6, 9, 11, 13, 16, 18`.
| `{{CONTACT_EMAIL}}` | Ending email address |
| `{{CONTACT_PHONE}}` | Ending phone number |
-## XII. Asset Specification
+## XI. Asset Specification
### Core Assets
@@ -206,7 +198,10 @@ Reference slides read before generation: `1, 2, 3, 4, 6, 9, 11, 13, 16, 18`.
Core assets are wired into SVG templates. `logo_dark.png` is used on light pages (TOC, content); `logo_white.png` and `cover_bg.png` on dark pages (cover, chapter, ending). Optional assets are available for project-specific customization.
-## XIII. Chart Specifications
+- Keep bundled image assets semantic and minimal.
+- Reconstruct editable template geometry instead of embedding fragments exported from PowerPoint.
+
+## XII. Chart Specifications
### Recommended Chart Dimensions
@@ -228,7 +223,7 @@ Core assets are wired into SVG templates. `logo_dark.png` is used on light pages
| Negative indicator | `#E74C3C` |
| Neutral | `#666666` |
-## XIV. Usage Instructions
+## XIII. Usage Instructions
1. Copy the template directory to the project `templates/` folder
2. Read this design specification to understand the visual system
diff --git "a/skills/ppt-master/templates/decks/\351\207\215\345\272\206\345\244\247\345\255\246/design_spec.md" "b/skills/ppt-master/templates/decks/\351\207\215\345\272\206\345\244\247\345\255\246/design_spec.md"
index f03b44c3..00ab14c9 100644
--- "a/skills/ppt-master/templates/decks/\351\207\215\345\272\206\345\244\247\345\255\246/design_spec.md"
+++ "b/skills/ppt-master/templates/decks/\351\207\215\345\272\206\345\244\247\345\255\246/design_spec.md"
@@ -196,6 +196,8 @@ Small circle elements representing the nighttime lights of the Mountain City:
- Content page header: Width 160-200px
- Ending page: Width 320-400px
+Use the packaged university logo assets through the standard project image pipeline.
+
---
## IX. Spacing Specification
@@ -210,24 +212,7 @@ Small circle elements representing the nighttime lights of the Mountain City:
---
-## X. SVG Technical Constraints
-
-### Mandatory Rules
-
-1. viewBox: `0 0 1280 720`
-2. Define gradients using `<linearGradient>` inside `<defs>`
-3. Use `fill-opacity` / `stroke-opacity` for transparency
-4. Use `<tspan>` for text wrapping
-5. Use Base64 inline or `<image>` reference for logos
-
-### Prohibited Elements
-
-- `mask`, `<style>`, `class`; `clipPath` is allowed only on `<image>` under `shared-standards.md` §1.2
-- `foreignObject`, `textPath`, `animate*`
-
----
-
-## XI. Placeholder Specification
+## X. Placeholder Specification
| Placeholder | Description |
| -------------------- | ---------------------- |
diff --git a/skills/ppt-master/templates/design_spec_reference.md b/skills/ppt-master/templates/design_spec_reference.md
index 1885b139..45f83eb8 100644
--- a/skills/ppt-master/templates/design_spec_reference.md
+++ b/skills/ppt-master/templates/design_spec_reference.md
@@ -349,26 +349,3 @@ One speaker note file per page, saved to `notes/`:
- **Filename**: match SVG name (e.g., `01_cover.md`)
- **Content**: script key points, timing cues, transition phrases
-
----
-
-## XI. Technical Constraints Reminder
-
-### SVG Generation Must Follow:
-
-1. viewBox: `{canvas_info['viewbox']}`
-2. Background uses `<rect>` elements
-3. Text wrapping uses `<tspan>` (`<foreignObject>` FORBIDDEN)
-4. Colors may use named, `rgb()` / `rgba()`, `hsl()` / `hsla()`, or
- 3/4/6/8-digit HEX forms; embedded alpha multiplies with explicit opacity
-5. FORBIDDEN: `mask`, `<style>`, `class`, `foreignObject`
-6. FORBIDDEN: `textPath`, `animate*`, `script`
-7. Text characters: write typography & symbols as raw Unicode (em dash `—`, en dash `–`, `©`, `®`, `→`, NBSP, etc.); HTML named entities (`&nbsp;`, `&mdash;`, `&copy;`, `&reg;` …) are FORBIDDEN. XML reserved chars in text MUST be escaped as `&amp;` `&lt;` `&gt;` `&quot;` `&apos;` (e.g. `R&amp;D`, `error &lt; 5%`). See shared-standards.md §1.0
-7. `marker-start` / `marker-end` conditionally allowed: `<marker>` must be in `<defs>`, `orient="auto"`, shape must be triangle / diamond / circle (see shared-standards.md §1.1)
-8. `clipPath` conditionally allowed **only on `<image>` elements**: `<clipPath>` in `<defs>`, single shape child (circle / ellipse / rect with rx,ry / path / polygon). Do NOT apply to shapes / groups / text — draw the target geometry directly with the matching native element (`<circle>` / `<ellipse>` / `<rect rx>` / `<polygon>` / `<path>`). See shared-standards.md §1.2
-
-### PPT Compatibility Rules:
-
-- `<g opacity="0..1">` is allowed as per-descendant alpha; overlapping children may composite differently
-- Image transparency may use `<image opacity="0..1">`; use overlays only for a color wash
-- Inline styles only; external CSS and `@font-face` FORBIDDEN
diff --git a/skills/ppt-master/templates/layouts/README.md b/skills/ppt-master/templates/layouts/README.md
index 66e8d152..39344659 100644
--- a/skills/ppt-master/templates/layouts/README.md
+++ b/skills/ppt-master/templates/layouts/README.md
@@ -39,7 +39,7 @@ page_types: [cover, toc, chapter, content, ending]
## V. SVG Page Roster # File list + per-file purpose
```
-Layouts may include additional supporting sections (Layout Patterns, Spacing Guidelines, SVG Technical Constraints, Placeholder Specification, Usage Notes). Do **not** include Color Scheme or Typography sections — those are identity-segment fields owned by `templates/brands/` and `templates/decks/`.
+Layouts may include additional supporting sections (Layout Patterns, Spacing Guidelines, Placeholder Specification, Usage Notes). Put a layout-specific required / forbidden / conditional boundary inside the personality section it qualifies. Do **not** include Color Scheme or Typography sections — those are identity-segment fields owned by `templates/brands/` and `templates/decks/`. General SVG/PPT authoring rules belong only in [`shared-standards.md`](../../references/shared-standards.md); do not add a generic technical-rules section or pointer to a layout spec.
---
@@ -75,6 +75,6 @@ The register step updates [`layouts_index.json`](./layouts_index.json) — the s
---
-## SVG technical constraints
+## SVG technical authority
-See [`shared-standards.md`](../../references/shared-standards.md) for the authoritative ban list (PPT incompatibilities, raw-character rules, clipPath conditional allowance, etc.). Layouts must comply.
+[`shared-standards.md`](../../references/shared-standards.md) is authoritative for general SVG/PPT required, forbidden, and conditional rules. Layout specs add only constraints unique to that layout.
diff --git a/skills/ppt-master/templates/layouts/academic_defense/design_spec.md b/skills/ppt-master/templates/layouts/academic_defense/design_spec.md
index aa99cb0a..b1ae9d61 100644
--- a/skills/ppt-master/templates/layouts/academic_defense/design_spec.md
+++ b/skills/ppt-master/templates/layouts/academic_defense/design_spec.md
@@ -142,27 +142,7 @@ page_types: [cover, toc, chapter, content, ending]
---
-## VIII. SVG Technical Constraints
-
-### Mandatory Rules
-
-1. viewBox: `0 0 1280 720`
-2. Use `<rect>` elements for backgrounds
-3. Use `<tspan>` for text wrapping (no `<foreignObject>`)
-4. CSS alpha colors and explicit `fill-opacity` / `stroke-opacity` are both supported; values multiply
-5. Prohibited: `mask`, `<style>`, `class`, `foreignObject`. `clipPath` is allowed only on `<image>` under `shared-standards.md` §1.2
-6. Prohibited: `textPath`, `animate*`, `script`
-7. `marker-start` / `marker-end` conditionally allowed (marker in `<defs>`, `orient="auto"`, shape = triangle/diamond/oval) — see shared-standards.md §1.1
-
-### PPT Compatibility Rules
-
-- `<g opacity="0..1">` is allowed as per-descendant alpha; overlapping children may composite differently
-- `<image opacity="0..1">` maps to native picture transparency; use overlays only for color washes
-- Inline styles only; no external CSS or `@font-face`
-
----
-
-## IX. Placeholder Specification
+## VIII. Placeholder Specification
Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
@@ -194,7 +174,7 @@ Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
---
-## X. Component Specifications
+## IX. Component Specifications
### 1. Tag
@@ -227,7 +207,7 @@ Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
---
-## XI. Usage Instructions
+## X. Usage Instructions
1. Copy the template to the project directory
2. Select the appropriate page template based on defense content needs
diff --git a/skills/ppt-master/templates/layouts/ai_ops/design_spec.md b/skills/ppt-master/templates/layouts/ai_ops/design_spec.md
index 5c73d993..a45a90d2 100644
--- a/skills/ppt-master/templates/layouts/ai_ops/design_spec.md
+++ b/skills/ppt-master/templates/layouts/ai_ops/design_spec.md
@@ -256,31 +256,7 @@ This template emulates the visual language of telecom technical reports. The cor
---
-## X. SVG Technical Constraints
-
-### Mandatory Rules
-
-1. viewBox: `0 0 1280 720`
-2. Use `<rect>` elements for backgrounds
-3. Use `<tspan>` for text wrapping (**`<foreignObject>` is strictly prohibited**)
-4. CSS alpha colors and explicit `fill-opacity` / `stroke-opacity` are both supported; values multiply
-5. Prohibited: `mask`, `<style>`, `class`, `foreignObject` (`id` is allowed for local references and semantic markers). `clipPath` is allowed only on `<image>` under `shared-standards.md` §1.2
-6. Prohibited: `textPath`, `animate*`, `script`
-7. Static same-document `<use>` / `<symbol>` reuse is allowed only under `shared-standards.md` §1.3: exact `href="#id"` / `xlink:href="#id"` and `url(#id)` fragments; targets limited to `symbol/g/use/rect/circle/ellipse/line/path/polygon/polyline/text/image`; unitless/`px` `x/y`; valid symbol `viewBox` plus positive unitless/`px` use `width/height`; aligned `meet` or plain `none`. External/missing/conflicting/circular/duplicate-ID references, `slice` / `refX` / `refY`, and reused `data-pptx-layer*` / `data-pptx-native*` / `data-pptx-placeholder*` metadata are prohibited. PPTX import does not reconstruct `<use>`
-8. Prohibited: `<iframe>`, `@font-face`
-9. `<g opacity="0..1">` is allowed as per-descendant alpha; overlapping children may composite differently
-10. `marker-start` / `marker-end` conditionally allowed (marker in `<defs>`, `orient="auto"`, shape = triangle/diamond/oval) — see shared-standards.md §1.1
-11. Use only system fonts and inline styles
-
-### PPT Compatibility Rules
-
-- `<image opacity="0..1">` maps to native picture transparency; use overlays only for color washes
-- Define gradients using `<linearGradient>` inside `<defs>`
-- Use `rx`/`ry` attributes for rounded rectangles (post-processing converts to Path)
-
----
-
-## XI. Placeholder Specification
+## X. Placeholder Specification
The template uses `{{PLACEHOLDER}}` format placeholders:
@@ -305,7 +281,7 @@ The template uses `{{PLACEHOLDER}}` format placeholders:
---
-## XII. Usage Notes
+## XI. Usage Notes
1. Copy this template directory to the project `templates/` directory
2. Review `reference_style.svg` to understand the core visual style
@@ -316,7 +292,7 @@ The template uses `{{PLACEHOLDER}}` format placeholders:
---
-## XIII. Design Highlights
+## XII. Design Highlights
- **Telecom DNA**: Derived from real telecom AI operations architecture reports, naturally suited for telecom/enterprise presentation styles
- **High Information Density**: A single page can accommodate a complete architecture view (objectives → results → scenarios → orchestration → foundational capabilities)
diff --git a/skills/ppt-master/templates/layouts/government_blue/design_spec.md b/skills/ppt-master/templates/layouts/government_blue/design_spec.md
index 90b08f38..69ddcfd2 100644
--- a/skills/ppt-master/templates/layouts/government_blue/design_spec.md
+++ b/skills/ppt-master/templates/layouts/government_blue/design_spec.md
@@ -140,27 +140,7 @@ page_types: [cover, toc, chapter, content, ending]
---
-## VIII. SVG Technical Constraints
-
-### Mandatory Rules
-
-1. viewBox: `0 0 1280 720`
-2. Use `<rect>` elements for backgrounds
-3. Use `<tspan>` for text wrapping (no `<foreignObject>`)
-4. CSS alpha colors and explicit `fill-opacity` / `stroke-opacity` are both supported; values multiply
-5. Prohibited: `mask`, `<style>`, `class`, `foreignObject`. `clipPath` is allowed only on `<image>` under `shared-standards.md` §1.2
-6. Prohibited: `textPath`, `animate*`, `script`
-7. `marker-start` / `marker-end` conditionally allowed (marker in `<defs>`, `orient="auto"`, shape = triangle/diamond/oval) — see shared-standards.md §1.1
-
-### PPT Compatibility Rules
-
-- `<g opacity="0..1">` is allowed as per-descendant alpha; overlapping children may composite differently
-- `<image opacity="0..1">` maps to native picture transparency; use overlays only for color washes
-- Use inline styles only; external CSS and `@font-face` are prohibited
-
----
-
-## IX. Placeholder Specification
+## VIII. Placeholder Specification
Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
@@ -184,7 +164,7 @@ Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
---
-## X. Usage Instructions
+## IX. Usage Instructions
1. Copy the template to the project directory
2. Replace logo files in the images directory (if applicable)
@@ -194,7 +174,7 @@ Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
---
-## XI. Design Highlights
+## X. Design Highlights
- **Tech Gradient**: Bright-to-deep blue gradient reflects a modern tech aesthetic
- **Geometric Decorative Elements**: Circles and grids add a tech atmosphere
diff --git a/skills/ppt-master/templates/layouts/government_red/design_spec.md b/skills/ppt-master/templates/layouts/government_red/design_spec.md
index d2a611cb..a7da6407 100644
--- a/skills/ppt-master/templates/layouts/government_red/design_spec.md
+++ b/skills/ppt-master/templates/layouts/government_red/design_spec.md
@@ -135,27 +135,7 @@ page_types: [cover, toc, chapter, content, ending]
---
-## VIII. SVG Technical Constraints
-
-### Mandatory Rules
-
-1. viewBox: `0 0 1280 720`
-2. Use `<rect>` elements for backgrounds
-3. Use `<tspan>` for text wrapping (no `<foreignObject>`)
-4. CSS alpha colors and explicit `fill-opacity` / `stroke-opacity` are both supported; values multiply
-5. Prohibited: `mask`, `<style>`, `class`, `foreignObject`. `clipPath` is allowed only on `<image>` under `shared-standards.md` §1.2
-6. Prohibited: `textPath`, `animate*`, `script`
-7. `marker-start` / `marker-end` conditionally allowed (marker in `<defs>`, `orient="auto"`, shape = triangle/diamond/oval) — see shared-standards.md §1.1
-
-### PPT Compatibility Rules
-
-- `<g opacity="0..1">` is allowed as per-descendant alpha; overlapping children may composite differently
-- `<image opacity="0..1">` maps to native picture transparency; use overlays only for color washes
-- Use inline styles only; external CSS and `@font-face` are prohibited
-
----
-
-## IX. Placeholder Specification
+## VIII. Placeholder Specification
Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
@@ -178,7 +158,7 @@ Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
---
-## X. Usage Instructions
+## IX. Usage Instructions
1. Copy the template to the project directory
2. Replace logo files in the images directory (if applicable)
@@ -188,7 +168,7 @@ Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
---
-## XI. Design Highlights
+## X. Design Highlights
- **Dual-Color Gradient Top Decoration**: Red-blue gradient reflects a government style
- **Gold Accent Elements**: Adds a sense of dignity
diff --git a/skills/ppt-master/templates/layouts/medical_university/design_spec.md b/skills/ppt-master/templates/layouts/medical_university/design_spec.md
index 749b563e..4b620ae3 100644
--- a/skills/ppt-master/templates/layouts/medical_university/design_spec.md
+++ b/skills/ppt-master/templates/layouts/medical_university/design_spec.md
@@ -142,33 +142,7 @@ page_types: [cover, toc, chapter, content, ending]
---
-## VIII. SVG Technical Constraints
-
-### Mandatory Rules
-
-- viewBox fixed at `0 0 1280 720`
-- Use `<rect>` elements for backgrounds
-- Use `<tspan>` for text wrapping
-- Use supported CSS colors or HEX; embedded alpha multiplies with
- `fill-opacity` / `stroke-opacity`
-
-### Prohibited Elements (PPT Incompatible)
-
-| Prohibited Item | Alternative |
-| -------------------- | ------------------------------ |
-| `clipPath` | Allowed only on `<image>` under `shared-standards.md` §1.2 |
-| `mask` | Do not use masking |
-| `<style>` | Use inline styles |
-| `class` | Use inline attributes (`id` inside `<defs>` is allowed) |
-| `foreignObject` | Use `<tspan>` for wrapping |
-| `textPath` | Use standard `<text>` |
-| `animate*` / `set` | Do not use animations |
-
-> `marker-start` / `marker-end` are conditionally allowed — see `shared-standards.md` §1.1 (marker must be in `<defs>`, `orient="auto"`, shape = triangle / diamond / oval). The converter maps them to native DrawingML arrow heads.
-
----
-
-## IX. Placeholder Specification
+## VIII. Placeholder Specification
| Placeholder | Usage |
| ------------------- | ---------------------------- |
@@ -196,7 +170,7 @@ page_types: [cover, toc, chapter, content, ending]
---
-## X. Usage Notes
+## IX. Usage Notes
### 1. Copy Template to Project
@@ -212,7 +186,7 @@ cp templates/layouts/medical_university/* projects/<project>/templates/
---
-## XI. Medical Content-Specific Components
+## X. Medical Content-Specific Components
### Data Card (Vital Signs)
diff --git a/skills/ppt-master/templates/layouts/pixel_retro/design_spec.md b/skills/ppt-master/templates/layouts/pixel_retro/design_spec.md
index 237ac4a6..8bd64bc1 100644
--- a/skills/ppt-master/templates/layouts/pixel_retro/design_spec.md
+++ b/skills/ppt-master/templates/layouts/pixel_retro/design_spec.md
@@ -173,7 +173,7 @@ Apply glow filters to key text/elements:
<text filter="url(#glowGreen)" fill="#39FF14">Glowing Text</text>
```
-> **Note**: `filter` effects are typically ignored in PPT, but render well in SVG-compatible viewers.
+> **Conditional enhancement**: Glow filters may enrich the retro treatment, but the core pixel composition must remain legible without them.
### Emoji Usage
@@ -192,28 +192,7 @@ Apply glow filters to key text/elements:
---
-## IX. SVG Technical Constraints
-
-### Mandatory Rules
-
-1. viewBox: `0 0 1280 720`
-2. Use `<rect>` elements for backgrounds
-3. Use `<tspan>` for text wrapping (no `<foreignObject>`)
-4. CSS alpha colors and explicit `fill-opacity` / `stroke-opacity` are both supported; values multiply
-5. Prohibited: `mask`, `<style>`, `class`, `foreignObject`. `clipPath` is allowed only on `<image>` under `shared-standards.md` §1.2
-6. Prohibited: `textPath`, `animate*`, `script`
-7. `marker-start` / `marker-end` conditionally allowed (marker in `<defs>`, `orient="auto"`, shape = triangle/diamond/oval) — see shared-standards.md §1.1
-
-### PPT Compatibility Rules
-
-- `<g opacity="0..1">` is allowed as per-descendant alpha; overlapping children may composite differently
-- `<image opacity="0..1">` maps to native picture transparency; use overlays only for color washes
-- Use inline styles only; external CSS and `@font-face` are prohibited
-- `filter` effects serve as enhancements (allowed) and do not affect baseline display
-
----
-
-## X. Placeholder Specification
+## IX. Placeholder Specification
Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
@@ -235,7 +214,7 @@ Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
---
-## XI. Usage Instructions
+## X. Usage Instructions
1. Copy the template to the project `templates/` directory
2. Select the appropriate page template based on content requirements
@@ -246,7 +225,7 @@ Templates use `{{PLACEHOLDER}}` format placeholders. Common placeholders:
---
-## XII. Color Quick Reference
+## XI. Color Quick Reference
```
Background Layer:
diff --git a/skills/ppt-master/templates/layouts/psychology_attachment/design_spec.md b/skills/ppt-master/templates/layouts/psychology_attachment/design_spec.md
index 3191e0be..91df03d7 100644
--- a/skills/ppt-master/templates/layouts/psychology_attachment/design_spec.md
+++ b/skills/ppt-master/templates/layouts/psychology_attachment/design_spec.md
@@ -269,37 +269,7 @@ Use `tabler-outline` as the stylistic icon library for this template. It matches
---
-## IX. SVG Technical Constraints
-
-### viewBox Specification
-
-```xml
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1280 720">
-```
-
-### Prohibited Features (Blocklist)
-
-| Category | Prohibited Items |
-| ------------------ | --------------------------------------- |
-| **Clipping/Masking** | `mask` is forbidden; `clipPath` is allowed only on `<image>` under `shared-standards.md` §1.2 |
-| **Style System** | `<style>`, `class` (`id` inside `<defs>` is allowed) |
-| **Structure/Nesting** | `<foreignObject>` |
-| **Text/Font** | `textPath`, `@font-face` |
-| **Animation/Interaction** | `<animate*>`, `<set>`, `on*` |
-
-> `marker-start` / `marker-end` are conditionally allowed — see `shared-standards.md` §1.1 (marker must be in `<defs>`, `orient="auto"`, shape = triangle / diamond / oval).
-
-### PPT Compatibility Rules
-
-Supported CSS alpha colors and explicit `fill-opacity` / `stroke-opacity`
-both export to DrawingML; when combined, their alpha values multiply.
-
-`<g opacity="0..1">` is supported as per-descendant alpha; overlapping
-children may composite differently from an isolated SVG group.
-
----
-
-## X. Placeholder Specification
+## IX. Placeholder Specification
| Placeholder | Usage |
| -------------------- | -------------------- |
@@ -322,7 +292,7 @@ children may composite differently from an isolated SVG group.
---
-## XI. Usage Notes
+## X. Usage Notes
### Template Usage Steps
diff --git a/skills/ppt-master/templates/spec_lock_reference.md b/skills/ppt-master/templates/spec_lock_reference.md
index 91a9ab35..e346456b 100644
--- a/skills/ppt-master/templates/spec_lock_reference.md
+++ b/skills/ppt-master/templates/spec_lock_reference.md
@@ -191,16 +191,7 @@
## forbidden
- Mixing icon libraries
-- `<style>`, `class`, `<foreignObject>`, `textPath`, `@font-face`, `<animate*>`, `<script>`, `<iframe>`
-- HTML named entities in text (`&nbsp;`, `&mdash;`, `&copy;`, `&ndash;`, `&reg;`, `&hellip;`, `&bull;` …) — write as raw Unicode (`—`, `©`, `→`, NBSP, etc.); XML reserved chars `& < > " '` must be escaped as `&amp; &lt; &gt; &quot; &apos;`. See shared-standards.md §1.0
-
-> Static same-document `<use>` / `<symbol>` is allowed only under
-> `shared-standards.md` §1.3: exact `href="#id"` / `xlink:href="#id"` and
-> `url(#id)` fragments; targets limited to
-> `symbol/g/use/rect/circle/ellipse/line/path/polygon/polyline/text/image`;
-> unitless/`px` `x/y`; valid symbol `viewBox` plus positive unitless/`px`
-> `width/height`; aligned `meet` or plain `none`. External, missing,
-> conflicting, circular, or duplicate-ID references; `slice` / `refX` / `refY`;
-> and reused `data-pptx-layer*` / `data-pptx-native*` /
-> `data-pptx-placeholder*` metadata remain forbidden. PPTX import does not
-> reconstruct `<use>`.
+- `mask`, `<style>`, `class`, external CSS, `<foreignObject>`, `textPath`, `@font-face`, `<animate*>`, `<set>`, `<script>` / event attributes, `<iframe>`
+- HTML named entities in text; write typography as raw Unicode and escape XML reserved characters
+
+> **Execution reminder — not authoring authority**: the baseline blacklist above is intentionally terse. Add only deck-specific execution locks. General SVG required / forbidden / conditional rules are owned by [`shared-standards.md`](../references/shared-standards.md); do not copy its feature matrix or parameter contracts into `spec_lock.md`.
diff --git a/skills/ppt-master/workflows/refine-spec.md b/skills/ppt-master/workflows/refine-spec.md
index 715768a8..63fcba49 100644
--- a/skills/ppt-master/workflows/refine-spec.md
+++ b/skills/ppt-master/workflows/refine-spec.md
@@ -26,7 +26,7 @@ The user **explicitly asks** to refine / review / revise the spec before generat
## Step 1: Produce the full spec
-Run the default Strategist output exactly as SKILL.md Step 4 specifies: write `design_spec.md` (§I–XI) and `spec_lock.md`. Read the relevant `sources/` files so the content outline (`§IX`) carries real facts, not skeleton points. Nothing special here — this is the normal spec, just produced under the knowledge that the user is about to review it.
+Run the default Strategist output exactly as SKILL.md Step 4 specifies: write `design_spec.md` (§I–X) and `spec_lock.md`. Read the relevant `sources/` files so the content outline (`§IX`) carries real facts, not skeleton points. Nothing special here — this is the normal spec, just produced under the knowledge that the user is about to review it.
---