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

docs(native-shapes): establish compound page geometry authoring

hugohe304a360a96088
diff --git a/docs/roadmap.md b/docs/roadmap.md
index 89dbc87a..ee4ffd2e 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -37,7 +37,7 @@ A presentation is four layers: what is on the slide, how it is arranged, how it
|---|---|---|
| Text | Systematized | Role anchors deck-wide, bounded per-occurrence adjustment, hierarchy and paragraph rules, natively editable runs |
| Native WordArt & warped text | Not planned | AI-generated decorative lettering is the preferred visual carrier, with ordinary editable text as the fallback. Native WordArt, text warp, and text-on-path would add a separate authoring and compatibility surface without improving that path, so they are not generated |
-| Vector shapes | Systematized | primitive → Office preset → Boolean → freeform construction ladder, with native conversion rules |
+| Vector shapes | Systematized | primitive / Office-preset atoms → independent composition → Boolean only when one contour requires it → necessary freeform construction ladder, with native conversion rules |
| Lines & connectors | Asymmetric by design | Native `p:cxnSp` export is implemented, and endpoint attachment is restored on the preserve/mirror round-trip from a source deck. Newly authored connectors stay unconnected. Binding them would first require deciding which lines are real edges and which are decoration — an intent judgment that no geometric threshold settles, and one that is made by the AI wherever it is placed, so moving it upstream to authoring buys no reliability. The result would be some arrows in a diagram following their node and others not |
| Icons | Systematized | Bundled SVG libraries with per-project sync; project icons are prepared material. Illustrated semantic cues remain generated slices under `images/` for ordinary image composition and never become icon-library entries |
| Logo | Bounded by design | A logo is always existing artwork, never designed here: brand workspaces install officially supplied files as prepared assets — bundled brand presets ship official marks with recorded usage rules — and the simple-icons library covers real company / product marks |
diff --git a/docs/zh/roadmap.md b/docs/zh/roadmap.md
index e26ce9c2..d7dcfeea 100644
--- a/docs/zh/roadmap.md
+++ b/docs/zh/roadmap.md
@@ -37,7 +37,7 @@
|---|---|---|
| 文字 | 系统化 | 全 deck 字号角色锚点、逐处受限微调、层级与段落规则、原生可编辑文本 |
| 原生 WordArt 与文字变形 | 暂不考虑 | 艺术字首选 AI 生成的装饰文字图片,普通可编辑文字负责兜底。原生 WordArt、文字变形与路径文字会额外引入一套创作和兼容性表面,却不能改善这条主路径,因此不生成 |
-| 矢量形状 | 系统化 | primitive → Office preset → Boolean → freeform 构造阶梯,附原生转换规范 |
+| 矢量形状 | 系统化 | primitive / Office preset 原子 → 独立组合 → 仅在单一轮廓需要时使用 Boolean → 必要 freeform 构造阶梯,附原生转换规范 |
| 线条 / 连接符 | 有意的不对称 | 原生 `p:cxnSp` 导出已实现,端点绑定在来源 deck 的 preserve/mirror 往返路径上会被还原。新创作的连接符保持不连接。要绑定就得先判断哪些线是真实的边、哪些是装饰——这是意图判断,任何几何阈值都定不下来;而无论把这个判断放在导出期还是创作期,做判断的都是 AI,往上游挪并不会更可靠。结果只会是同一张图里有的箭头跟着节点走、有的不走 |
| 图标 | 系统化 | 内置 SVG 图标库 + 逐项目同步;项目图标属于已准备材料。插图式语义提示仍是 `images/` 下用于普通图片构图的生成切片,不进入图标库 |
| Logo | 有意边界 | Logo 永远来自既有素材,不在这里设计:brand 工作区把官方提供的文件安装为已准备资产——内置品牌预设附带官方标识及记录在案的使用规则——真实公司 / 产品标识另有 simple-icons 图标库覆盖 |
diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.md
index d332b65d..ab443e24 100644
--- a/skills/ppt-master/references/executor-base.md
+++ b/skills/ppt-master/references/executor-base.md
@@ -167,7 +167,7 @@ Before drawing each page, look up its entry in `page_rhythm` (key format `P<NN>`
- **Default — stage each page with the style's composition geometry (may override when the content genuinely calls for a plain grid)**: an SVG page is a canvas, not a DOM. Resolve the page-scale move from `spec_lock.md`: a preset uses that selected style's §1 `Composition geometry`; `custom` executes `visual_style_behavior` first, then uses §1 geometry only from exact `visual_style_references` that the behavior assigns a shape or composition job. Other bases contribute only their assigned job, and an unreferenced novel custom follows its behavior alone. Before defaulting to stacked rounded-rect cards or uniform equal columns, use that resolved geometry to stage the page's primary zone. Card grids are one option among many, not the house layout.
- **Default — realize the planned motif system's reuse mode (may omit where it has no page job)**: when §III `Theme` names a cross-page motif or element family, exact repetition is valid for deliberate title/corner chrome; adaptive elements may vary scale, crop, density, position, and content interaction by page role. Preserve the named invariant, apply it only where it supports hierarchy or continuity, and do not invent a competing recurring identity.
- **Inherited containers**: preserve meaningful template frames; restyle radius, fill, stroke, and depth from the active Design Spec and `spec_lock.md`. Selected Chart/Table reference adaptation is owned by [`executor-visualization.md`](./executor-visualization.md); preview effects never override project styling or structural roles.
-- **Reference — prefer semantic geometry over preset stacks**: for relationships such as ascending, converging, breaking through, or stacking, first seek a basic primitive, one exact preset, or a clear Boolean result. Only when none can faithfully express the relationship should one page-specific polygon/path replace a stack of generic arrows.
+- **Reference — prefer semantic geometry over preset stacks**: for relationships such as ascending, converging, breaking through, or stacking, first compose faithful primitives and exact presets as one page geometry system; use a Boolean only when the contour itself must merge, open, or fragment. Only when neither construction works should one page-specific polygon/path replace a stack of generic arrows.
- **Reference — create depth with restraint**: use rhythm, spacing, typography, accent bars, and subtle tints before shadows. Reserve lift for a few genuinely floating elements; keep peer grids, dividers, and ordinary body containers flat. When material layering itself is part of the resolved visual style, follow that style's hierarchy instead of flattening its body planes.
- **Phased generation** (recommended):
1. **Visual Construction Phase**: generate all SVG pages sequentially for visual consistency. Apply every triggered information-model branch while drawing. **MUST embed one object-scoped plot-area marker** per §IX-named or Quick-promoted value-driven chart object under [`executor-chart.md`](./executor-chart.md) §2; coordinate calibration is a post-generation step (see [`verify-charts`](../workflows/stages/verify-charts.md)). Write every `<object-key>=yes` native marker plus JSON metadata atomically under [`native-data-interface.md`](./native-data-interface.md) §2. **Reach for native presets** per §3.0 as you draw each page: a block arrow, chevron, banner/ribbon, callout, standard flowchart node, or star is authored through `preset_shape_svg.py` at draw time — decided by the object's intent as you create it, never by scanning finished paths, and never committed to a bare `<path>`/`<polygon>` when a preset expresses it (a gradient fill/stroke or a pattern fill is the one paint exception — keep those ordinary SVG; when justified, one registered [`svg-effects.md`](./svg-effects.md) §6.4 shadow/glow stays on the helper-authored shape). **First-page gate (Mandatory)**: after completing the first page, run `python3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path> --stage first-page --json` directly without output filtering. Review the whole P01 issue set, make one consolidated edit pass for every error and any selected warnings, then perform one verification rerun. If it still fails, treat that complete output as the next batch; never check between individual fixes. After it passes, draw P02 through the last page without checker calls.
@@ -177,10 +177,10 @@ Before drawing each page, look up its entry in `page_rhythm` (key format `P<NN>`
### 3.0 Native Shape Selection
**Use the highest-level native construction that faithfully expresses the
-object.** Basic primitives already export as editable PowerPoint shapes. For
-anything beyond them, an exact Office preset is the default; when no single
-preset suffices but closed operands can express the result, materialize a
-Merge Shapes Boolean result. Hand-authored freeform geometry is the final
+page and each atom.** Basic primitives and exact Office presets already export
+as editable PowerPoint shapes; compose them independently when one contour is
+unnecessary. Materialize a Merge Shapes Boolean result only for contour
+semantics that independent atoms cannot express. Hand-authored freeform is the final
fallback, not the first drawing convenience. Block arrows, chevrons, banners /
ribbons, callouts, flowchart nodes, stars, and other Office symbols should be
**authored as presets** via `preset_shape_svg.py`, not redrawn as plain
@@ -190,24 +190,51 @@ object.
§IX `Native shape suggestion` records a semantic opportunity, not a literal
tool command. Decide from the actual page construction whether a basic
-primitive, preset, Boolean result, or necessary freeform best realizes it; a
+primitive, preset, independent compound construction, Boolean result, or necessary freeform best realizes it; a
different implementation is valid when it preserves the intended object and
content.
+**Compound-shape check (automatic, not a quota)**: after structure resolves and
+before drawing, test whether a page-level native geometry system would organize
+the background, zones, hierarchy, or reading path better than a uniform card
+grid. If yes, build it through [`native-shape-authoring.md`](./native-shape-authoring.md)
+§2.1; otherwise keep the simpler composition. There is no per-page or per-deck
+coverage target and no required explanation for declining it.
+
+**Default — do not use rectangles as the universal carrier (may use when a
+neutral field is the best fit)**: before drawing another `<rect>` / rounded
+`<rect>` container, test whether the content job calls for a more expressive
+preset, outline contour, or compound geometry. Choose one coherent shape
+language for the page; do not assign unrelated novelty shapes item by item.
+
+**Default — give floating text a geometric owner when useful (may omit when
+typography and negative space already establish deliberate hierarchy)**: before
+leaving a key or repeated text cluster unbounded, consider a native outline,
+frame, arc, bracket, band, spine, or other content-fit carrier. `fill="none"`
+with a visible stroke is a first-class option and does not imply a filled card.
+
+**Reference — use visual nesting for depth**: a larger field may contain or be
+crossed by an inset contour, secondary surface, badge, port, or focal shape.
+Keep these as independently editable siblings in the ordinary semantic group;
+visual containment never authorizes placing content inside an atomic preset
+fragment or merging shapes that do not require one contour.
+
| Decision | Action |
|---|---|
| Plain rect / symmetric round rect / circle / ellipse | Keep the ordinary SVG primitive; it is already natively editable. |
| Straight relationship / divider / leader | Use `<line>`; add a registered marker only when direction is meaningful. |
| Exact single-preset match | Call `preset_shape_svg.py render` and paste its complete stdout fragment into the current hand-authored SVG. |
| Bent / curved relationship exactly expressed by a stock Connector contour, with no required endpoint attachment | Use the matching `bentConnector*` / `curvedConnector*` preset through the helper as an unconnected native Connector shape. |
+| Text/content zone needs containment or emphasis without a filled surface | Use a faithful primitive or exact preset with `fill="none"` and a visible stroke; keep text and other content independent. |
+| Two or more native shapes should form one page-level geometry system | Follow [`native-shape-authoring.md`](./native-shape-authoring.md) §2.1: compose faithful primitives and presets as independent siblings first, then materialize only contours that require Boolean semantics. |
| Supported closed-shape / resolvable-text operands need union, cutout, overlap, symmetric difference, or fragmentation | Use `shape_boolean_svg.py` when Boolean materialization is the clearest faithful construction; follow [`native-shape-authoring.md`](./native-shape-authoring.md) §6. |
| Stock shape that needs a gradient fill/stroke or a pattern fill | Keep ordinary SVG — the helper paints `none` or a solid HEX on both fill and stroke only ([`native-shape-authoring.md`](./native-shape-authoring.md) §5). |
-| Page-specific freeform, organic, branded, icon, data geometry, or relationship contour that primitives, one preset, and Boolean materialization cannot faithfully express | Keep ordinary SVG path/polygon geometry. |
+| Page-specific freeform, organic, branded, icon, data geometry, or relationship contour that primitives, exact presets, their independent composition, and Boolean materialization cannot faithfully express | Keep ordinary SVG path/polygon geometry. |
| Similar-looking contour only | Never infer a preset; continue to the Boolean gate, then use freeform only if no faithful construction exists. |
**Hard rule — freeform is the last construction tier**: before hand-authoring a
-stock-looking `<path>` / `<polygon>`, complete the primitive → exact preset →
-Boolean-result decision order above. A freeform is permitted only when those
+stock-looking `<path>` / `<polygon>`, complete the primitive / exact-preset atom
+→ independent composition → required Boolean-result decision order above. A freeform is permitted only when those
tiers cannot faithfully express the object; avoiding a helper or drawing the
browser-visible contour faster is not a valid exception. Data-defined geometry
and a genuinely locked organic / hand-drawn contour satisfy the exception by
diff --git a/skills/ppt-master/references/executor-structure.md b/skills/ppt-master/references/executor-structure.md
index 74f6545b..6b358995 100644
--- a/skills/ppt-master/references/executor-structure.md
+++ b/skills/ppt-master/references/executor-structure.md
@@ -50,8 +50,9 @@ Combine atoms as needed; never force a named business model. Numbers used only a
**Hard rule — realization enters the construction gate**: Decide whether each
role is implicit/direct content or drawn geometry. Every drawn field, spine,
node carrier, or edge uses the first faithful tier under
-[`native-shape-authoring.md`](./native-shape-authoring.md) §1: primitive → exact
-preset → Boolean → necessary freeform. Text styling/rules cannot replace
+[`native-shape-authoring.md`](./native-shape-authoring.md) §§1–2.1: primitive /
+exact-preset atoms → independent compound system → required Boolean result →
+necessary freeform. Text styling/rules cannot replace
required geometry; implicit/direct roles need no container. Decoration cannot
invent a relationship.
@@ -93,7 +94,7 @@ inapplicable operations; implicit/direct roles remain container-free.
| Attachment | Labels/evidence belong to the correct node, edge, or region |
| Removal | Without color/effects/icons/garnish, placement still communicates |
| Fidelity | All required units, qualifiers, values, and caveats remain |
-| Construction | Drawn fields/spines/node carriers/edges pass §2; implicit/direct roles need no carrier; freeform follows failed primitive/preset/Boolean tiers |
+| Construction | Drawn fields/spines/node carriers/edges pass §2; implicit/direct roles need no carrier; freeform follows failed primitive/preset/independent-compound/Boolean tiers |
| Composition | Every used contact, void, overlap, cutout, occlusion, or canvas-edge crossing maps to an atom/role or remains removable garnish; none obscures ownership or reading path |
Load Chart/Table branches independently for embedded objects. Keep one dominant reading path while allowing secondary atoms whose ownership stays clear.
diff --git a/skills/ppt-master/references/native-shape-authoring.md b/skills/ppt-master/references/native-shape-authoring.md
index 1980a616..10bee060 100644
--- a/skills/ppt-master/references/native-shape-authoring.md
+++ b/skills/ppt-master/references/native-shape-authoring.md
@@ -5,12 +5,12 @@
Use this reference during Executor SVG construction or project-owned canonical
template maintenance when basic primitives, one standard PowerPoint shape, or
supported shape/text operands can express the intended object. Prefer, in order:
-editable basic primitives, one exact Office preset, then a PowerPoint-style
-Boolean result from closed shapes and/or resolvable text. Hand-authored freeform
-geometry is allowed only when those
-constructions cannot faithfully express the object. Neither helper writes a
-page. The preset helper does not create the shape's own `p:txBody`; keep visible
-text outside the atomic fragment.
+editable basic primitives, one exact Office preset per atom, an independent
+composition of those faithful atoms, then a PowerPoint-style Boolean result
+only for contours that must become one object. Hand-authored freeform geometry
+is allowed only when those constructions cannot faithfully express the object.
+Neither helper writes a page. The preset helper does not create the shape's own
+`p:txBody`; keep visible text outside the atomic fragment.
## 1. Selection Gate
@@ -22,11 +22,13 @@ Apply this decision order before drawing any new geometric contour.
| Condition | Action |
|---|---|
| Plain rectangle, symmetric rounded rectangle, circle, or ellipse | Write the ordinary SVG primitive; the exporter already emits an editable native shape. |
+| A text/content zone needs a visible boundary but not a filled surface | Use a faithful primitive or exact preset with `fill="none"` and a visible stroke; keep its content as independent siblings. |
| Straight relationship, divider, or leader | Write `<line>`; use a registered marker only when direction is meaningful. |
| One DrawingML preset exactly expresses the intended object | Run `preset_shape_svg.py render`, then insert its complete stdout fragment into the hand-authored page or canonical template. |
| A stock `bentConnector*` / `curvedConnector*` contour exactly expresses a bent or curved relationship and endpoint attachment is not required | Run `preset_shape_svg.py render --object-kind connector`; the result is an unconnected native Connector shape. |
+| Two or more faithful primitives / presets form the page construction but do not need one contour | Keep them as independently editable siblings in one ordinary semantic group; use §2.1 to compose the page-level geometry system. |
| Two or more supported closed-shape / resolvable-text operands require Union, Combine, Fragment, Intersect, or Subtract | Run `shape_boolean_svg.py render`, then replace the operands with every stdout path; the result remains ordinary editable custom geometry. |
-| Basic primitives, one preset, and Boolean materialization cannot faithfully express the visual meaning or contour | Write ordinary `<path>` / `<polygon>` geometry; export keeps it as editable custom geometry. |
+| Basic primitives, exact presets, their independent composition, and Boolean materialization cannot faithfully express the visual meaning or contour | Write ordinary `<path>` / `<polygon>` geometry; export keeps it as editable custom geometry. |
| The shape only resembles a preset | Never infer a preset; continue to the Boolean gate, then use freeform only if no faithful construction exists. |
| Mirror/preserve input already owns native-shape metadata | Keep the existing object and metadata; never reselect its preset. |
@@ -39,9 +41,10 @@ rerun the helper whenever its geometry, paint, or filter reference changes.
## 2. Semantic Preset Candidate Guide
-Use the table below as the **go-to menu**: match the page's visual intent to a
-candidate preset *before* defaulting to a plain rect or path. Reaching here
-first is exactly how presets get used instead of forgotten.
+Use the table below as a high-frequency entry, not a whitelist: match the
+page's visual intent to a candidate preset *before* defaulting to a plain rect
+or path. A neutral rect remains valid when neutrality is the job; otherwise
+search the registry rather than forgetting the broader preset vocabulary.
"Automatic" means the Executor independently applies this semantic decision
gate before drawing a new object. It does not scan existing SVG, classify
@@ -81,6 +84,62 @@ owned by the preserve/mirror round-trip contract.
- `chartX`, `chartStar`, or `chartPlus` as a substitute for native charts;
- logo, icon glyph, illustration, brand contour, or data-chart marks.
+### 2.1 Compound page geometry
+
+**Trigger**: after [`executor-structure.md`](./executor-structure.md) resolves the
+page topology, use this method when two or more native shapes can strengthen its
+background field, content zoning, focal hierarchy, or reading path. This is a
+construction method, not a requirement to decorate every page.
+
+| Pass | Action | Result |
+|---|---|---|
+| Page job | Name the geometric jobs already implied by the resolved page: surface, boundary, direction, reveal, focal mark, shared region, or counterweight. | A small set of functional zones; no shape names yet. |
+| Decompose | Separate visible content from geometric atoms. Identify which atoms need independent movement, paint, or reuse and which contour must become one object. | Editable siblings plus any explicit Boolean operand set. |
+| Select | Apply §1 to every atom: primitive first, then one exact preset; use freeform only after faithful preset and Boolean routes fail. | The highest-level faithful native construction per atom. |
+| Compose | Establish page frame, scale, z-order, and negative space with independent atoms. Keep text, images, icons, data marks, and non-merged accents outside Boolean operands. | One page-level geometry system, not a collection of unrelated decorations. |
+| Materialize | Run the preset helper for each adopted preset. Run the Boolean helper only for contours that require Merge Shapes semantics, then replace those operands with its stdout paths. | Valid authoring SVG ready for native export. |
+
+**Composition lenses — not a checklist**:
+
+| Lens | Use when it strengthens the resolved page |
+|---|---|
+| Page field | Let one large surface, outline, aperture, or off-canvas contour organize major zones instead of wrapping every content unit in a card. |
+| Outline carrier | Use `fill="none"` plus a coherent stroke on a frame, arc, bracket, band, or other faithful contour when bare text needs ownership without a heavy filled card. |
+| Nested fields | Visually nest an inset contour, secondary surface, badge, port, or focal shape inside / across a larger field to create hierarchy; keep them as siblings unless one contour must merge. |
+| Continuity | Align or overlap independent shapes across zones so geometry reinforces the intended reading path. |
+| Depth and contrast | Combine filled, outlined, offset, and negative-space atoms; use Boolean only when the contour itself must change. |
+| Deck language | Reuse a corner, arc, slant, notch, or layering logic with page-fit variation rather than cloning one composition. |
+
+**Boolean decision gate**:
+
+| Required result | Construction |
+|---|---|
+| Stock contour already expresses the job | One exact preset; do not rebuild it from primitives or Boolean operands. |
+| Shapes overlap or layer but must remain independently editable | Keep separate primitives / presets in one ordinary semantic group; do not merge them. |
+| One continuous outer silhouette | `union`; use `combine` only for intentional symmetric negative regions. |
+| A true hole, edge cut, or reveal | `subtract`, with the visible body first and cutout operands after it. |
+| Only the common covered region should remain | `intersect`. |
+| Exclusive and shared regions need separate styling or motion | `fragment`, retaining every required result path as an independent shape. |
+
+**Authoring-to-export map**:
+
+| SVG authoring form | Native PPTX result |
+|---|---|
+| Ordinary `<rect>`, rounded `<rect>`, `<circle>`, `<ellipse>`, or `<line>` | Editable primitive / line shape. |
+| Complete `preset_shape_svg.py` fragment | One exact `a:prstGeom` shape, or `p:cxnSp` for an authored connector preset. |
+| `shape_boolean_svg.py` result path | Editable `a:custGeom`; the final contour is retained, not replayable Merge Shapes history. |
+| Parent semantic group containing independent atoms and content | A grouped page construction whose child shapes remain separately editable. |
+
+**Reference — not a constraint**: derive the operand count, preset choices,
+geometry, paint, rotation, and grouping from the current page. A strong compound
+construction may use only independent presets, only one Boolean result, or a mix;
+there is no Boolean quota and no catalog of allowed combinations.
+
+**Hard rule — merge only geometry that must become one contour**: never merge
+text, images, icons, or otherwise independent accents merely to simplify the
+SVG tree. Boolean materialization discards editable operand history; preserve
+siblings whenever one-object contour semantics are unnecessary.
+
---
## 3. Fragment Generation
diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.md
index b319f17d..7391e48a 100644
--- a/skills/ppt-master/references/strategist.md
+++ b/skills/ppt-master/references/strategist.md
@@ -359,7 +359,7 @@ user/template requirements bind.
| Image composition | Image-as-canvas, editorial crop, collage, cutout, or meaningful focus / comparison / evidence units carry the page better than an adjacent rectangle | Propose a permitted source; when selected, apply the already-loaded [`strategist-image.md`](./strategist-image.md) resource contract plus the conditional image-layout references, record a concise §VIII `Layout pattern` suggestion, and describe page-level image/overlay relationships in §IX `Layout` / `Images` |
| Composable illustration family | One or more pages benefit from coherent reusable title/corner ornaments, dominant anchors, supporting figures, compact illustrated-icon cues, or accents that can mix with text, shapes, photos, or lettering | Apply [`strategist-image.md`](./strategist-image.md): plan transparent elements by compatible family, record fixed reuse or adaptive variation in §VIII `Reference`, and describe each used page's carrier relationships in §IX `Layout` / `Images` |
| Native paint / overlay | Gradient, translucency, scrim, vignette, or wash supports focus, hierarchy, depth, legibility, or image integration | Record purpose/layering in §IX `Layout`, plus `Images` when imagery participates; no new field or type/stops/opacity/coordinates—Executor chooses realization |
-| Native shape / Merge Shapes | A literal Office symbol, a stock bent/curved relationship contour, or a compound silhouette, negative-space cutout, overlap-only region, or meaningful fragmentation strengthens the visual idea | Add an optional §IX `Native shape suggestion` with the semantic result plus a candidate preset/Connector family or Boolean operation/operands |
+| Native shape system / Merge Shapes | A page field, outline carrier, visual nesting, literal Office symbol, stock bent/curved contour, or compound silhouette/cutout/overlap region strengthens the visual idea | Add an optional §IX `Native shape suggestion` with the semantic geometry jobs and relationship; identify independent atom roles, a candidate preset/Connector family, or Boolean operation/operands only where useful |
| AI decorative lettering asset | Any stable display string in the deck — including a complete long or multi-line title, cover hook, chapter word, place or product name, dish or exhibit name, year, hero number, pull quote, or motif word — reads better with a material, dimensional, hand-rendered, or otherwise illustrative treatment than as ordinary text | Apply [`strategist-image.md`](./strategist-image.md): preserve every complete exact string, group compatible marks when useful, and keep chrome/body as native text. The lettering asset may carry the complete long or multi-line title as its display layer; keep an ordinary native title/subtitle in a separate text frame wherever the page needs a searchable, selectable, or outline-visible heading. Never shorten copy to make it look more like a wordmark |
| Page transition | A section/state change, spatial continuity, recorded/self-running flow, or the same semantic object changing position, scale, crop, or state across adjacent pages benefits from motion | Add an optional §IX `Motion suggestion` describing the communication job and any continuing object's initial state → action → end state; leave effect, ids, pairing names, and timing to Executor |
| Object animation | Progressive reveal, emphasis, movement, removal, or deliberate stillness clarifies sequence, causality, comparison, hierarchy, narration order, full-view → detail, atmosphere → evidence, or hotspot/annotation order | Add an optional §IX `Motion suggestion` naming each relevant semantic unit's lifecycle duty and initial state → communication action → end state, plus any meaningful order/relationship; leave group ids, effects, options, and timing to Executor |
@@ -427,16 +427,16 @@ Correct failed selections by recall; `no-template-match` never enters `page_visu
| P03 | chart | line_chart | Compare the source metrics over time |
```
-**Native-geometry candidate detail**: Add `Native shape suggestion` to the
-affected §IX page when the content calls for a literal stock PowerPoint
-chevron, block arrow, standard flowchart node, callout, banner, star, or a
-stock bent/curved Connector contour. Describe a relationship by its semantic
-route and candidate family, not an exact preset key, endpoint/site metadata, or
-attachment promise. For a compound silhouette, cutout, common region, or
-meaningful fragmentation, name the candidate Union / Combine / Fragment /
-Intersect / Subtract operation, semantic operands, and intended result.
-Executor still decides the exact basic primitive, preset, Boolean construction,
-or necessary freeform under its native-shape branch; the recommendation never
+**Native-geometry candidate detail**: Add `Native shape suggestion` when a
+page-level field, boundary, direction, reveal, visual nesting, literal stock
+shape, or stock bent/curved Connector contour may strengthen the page. Describe
+the semantic jobs and whether atoms should remain independent, not coordinates,
+an exact preset key, endpoint/site metadata, or attachment promises. Only when
+one contour, cutout, common region, or meaningful fragmentation is intended,
+name the candidate Union / Combine / Fragment / Intersect / Subtract operation,
+semantic operands, and result.
+Executor still decides the exact basic primitive, preset, independent compound
+construction, Boolean result, or necessary freeform under its native-shape branch; the recommendation never
creates a §VII row or lock field.
### Speaker Notes Requirements
diff --git a/skills/ppt-master/references/svg-effects.md b/skills/ppt-master/references/svg-effects.md
index 779ad06f..a47afa75 100644
--- a/skills/ppt-master/references/svg-effects.md
+++ b/skills/ppt-master/references/svg-effects.md
@@ -699,8 +699,9 @@ preserve deliberate tangent continuity.
Command identity, relative coordinates, shorthand, arc parameters, and original
handles are not retained. Geometry needs non-zero bounds. Before authoring a
freeform, apply [`native-shape-authoring.md`](./native-shape-authoring.md):
-prefer an editable basic primitive, one exact Office preset, or a Boolean
-materialization. Use a closed cubic path only for an organic silhouette those
+prefer editable primitives and exact Office presets, independently composed
+when possible; materialize a Boolean only when one contour requires it. Use a
+closed cubic path only for an organic silhouette those
cannot express, polygon/closed path for unmatched ribbons/facets, and an open
path only for a required data curve, custom route, or locked or Quick-resolved
hand-drawn / organic style. Straight relationships use `<line>`; exact stock bends/curves
diff --git a/skills/ppt-master/references/template-designer.md b/skills/ppt-master/references/template-designer.md
index bb64acc8..b3f5be7b 100644
--- a/skills/ppt-master/references/template-designer.md
+++ b/skills/ppt-master/references/template-designer.md
@@ -64,7 +64,7 @@ ownership.
| Mode | Output structure contract |
|---|---|
-| `standard` / `fidelity` | Author project-canonical SVG prototypes and an intentional new Master/Layout/slot system. Source visual language and assets may guide the design, but source ownership, keys, picker names, parent relationships, placeholders, and repeated Slide-local elements do not define or seed the output topology. For every new contour, use an editable basic primitive, then an exact compact authored preset, then a Boolean result; use freeform only when those cannot express it faithfully. |
+| `standard` / `fidelity` | Author project-canonical SVG prototypes and an intentional new Master/Layout/slot system. Source visual language and assets may guide the design, but source ownership, keys, picker names, parent relationships, placeholders, and repeated Slide-local elements do not define or seed the output topology. Build new geometry from editable primitives and exact compact presets as independent atoms; materialize a Boolean result only where one contour requires it, and use freeform last. |
| `mirror` | Materialize a new workspace from the validated source graph one-to-one: keep the Master/Layout identities and parentage, slide assignments, placeholder type/index/bounds, and supported visual/native-object facts that are actually present. Edit the authoring IR; materialization may rehydrate converter-supported native payload only for unchanged source refs. Mechanical normalization maps fixed-layer source groups into the direct atoms required by the current explicit SVG contract while preserving ownership, paint order, and appearance; it must not invent missing facts or semantically redesign the graph. |
Every page remains a complete standalone SVG preview.
@@ -83,8 +83,9 @@ bundle into an authored template. `mirror` instead preserves the supported
expanded lossless source representation. The exact syntax and validation
contract remain owned by
[`shared-standards-core.md`](./shared-standards-core.md) and the native-shape reference.
-When one preset is insufficient, apply the same reference's Boolean gate before
-hand-authoring a freeform.
+When one preset is insufficient, apply the same reference's compound-page gate:
+keep faithful atoms independent unless one contour requires Boolean
+materialization, then use freeform only if neither construction succeeds.
**Hard rule — complete mirror graph**: Preserve every supported source Layout represented by the validated import,
including Layouts unused by source Slides. Emit one complete source-page
@@ -375,7 +376,7 @@ template.
|---|---|---|
| Lossless import SVG | Native-payload backing | Retain complete imported metadata, native object boundaries, hidden carriers, and source-scope identity. Keep it immutable and resolve it only through validated source refs. |
| Authoring IR bundle | Editable template-creation source | Omit opaque native payload and duplicate hidden carriers from model context; retain visible shape intent and stable document-local source refs. Models read `authoring_summary.json`; tools read `authoring_manifest.json` for source paths and initial hashes. |
-| `standard` / `fidelity` output | Newly authored contract | Use editable basic primitives directly, `preset_shape_svg.py` compact canonical `<g>` output for exact preset matches, and `shape_boolean_svg.py` for compound closed contours before allowing a necessary freeform. Paint comes from the confirmed brief / `design_spec.md`. Reuse exported image/vector assets, not opaque source shape payload or source topology. |
+| `standard` / `fidelity` output | Newly authored contract | Use editable basic primitives directly and `preset_shape_svg.py` compact canonical `<g>` output for exact preset matches. Keep faithful atoms independently composed when one contour is unnecessary; use `shape_boolean_svg.py` only where one compound closed contour must become an object, then allow a necessary freeform only if neither construction is faithful. Paint comes from the confirmed brief / `design_spec.md`. Reuse exported image/vector assets, not opaque source shape payload or source topology. |
| `mirror` output | Materialized preserved contract | Preserve currently supported imported metadata on unchanged Slide-local/slot refs, use the edited SVG fallback otherwise, and normalize fixed structural layers into semantic atoms. Strip IR-only source refs from final templates. |
**Validation**: Mirror does not silently use stale metadata. Materialization
@@ -384,7 +385,8 @@ hash before reusing native payload. If an imported object cannot use the
converter's supported native metadata after normalization, keep its current SVG fallback and report the
limitation. For exact registered preset matches, `standard` / `fidelity`
regenerate the compact helper group instead of transplanting opaque source
-payload; otherwise they apply the Boolean/freeform fallback gate above.
+payload; otherwise they keep faithful atoms independently composed unless one
+contour requires the Boolean gate, with necessary freeform last.
`data-pptx-replace-with` remains reserved for optional PowerPoint-native
Chart/Table replacement markers.
diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.json
index 8daf5128..8440f870 100644
--- a/skills/ppt-master/scripts/prompt_audit_manifest.json
+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json
@@ -18,7 +18,7 @@
"file_budgets": {
"AGENTS.md": 2750,
"skills/ppt-master/SKILL.md": 1250,
- "skills/ppt-master/references/executor-base.md": 10000,
+ "skills/ppt-master/references/executor-base.md": 12000,
"skills/ppt-master/references/executor-structured.md": 5500,
"skills/ppt-master/references/executor-chart.md": 3500,
"skills/ppt-master/references/executor-visualization.md": 1250,
@@ -246,7 +246,7 @@
"registry": "image-renderings"
}
],
- "max_tokens": 92000
+ "max_tokens": 105000
},
"route.generate.quick-generate.beautify": {
"description": "Quick Generate with the shared strict 1:1 Beautify profile.",
@@ -256,7 +256,7 @@
"profile.generate.beautify-pptx"
],
"files": [],
- "max_tokens": 100000
+ "max_tokens": 115000
},
"route.generate.quick-generate.image-to-pptx": {
"description": "Codex-supported Quick-only Image to PPTX with registered reference-image layers and shared plates.",
@@ -302,7 +302,7 @@
"stage.generate.topic-research"
],
"files": [],
- "max_tokens": 94000
+ "max_tokens": 105000
},
"route.generate.quick-generate.icon": {
"description": "Quick Generate with project-local bundled icon selection and synchronization.",
@@ -313,7 +313,7 @@
"files": [
"skills/ppt-master/templates/icons/README.md"
],
- "max_tokens": 94000
+ "max_tokens": 105000
},
"route.generate.quick-generate.in-hand-image": {
"description": "Quick Generate with supplied, extracted, or placeholder image resources prepared before SVG authoring.",
@@ -977,7 +977,7 @@
"files": [
"skills/ppt-master/references/native-shape-authoring.md"
],
- "max_tokens": 5000
+ "max_tokens": 6500
},
"route.generate.planning-template": {
"description": "Generate-PPTX planning context after an explicit template workspace is installed.",
@@ -1108,7 +1108,7 @@
"files": [
"skills/ppt-master/references/native-shape-authoring.md"
],
- "max_tokens": 5000
+ "max_tokens": 6500
},
"stage.shared.svg-effects": {
"description": "Advanced SVG paint, effects, transforms, and geometry authority, always included in Generate Executor contexts and conditionally loaded by other SVG-authoring routes.",
diff --git a/skills/ppt-master/templates/design_spec_reference.md b/skills/ppt-master/templates/design_spec_reference.md
index 47066632..98aa9174 100644
--- a/skills/ppt-master/templates/design_spec_reference.md
+++ b/skills/ppt-master/templates/design_spec_reference.md
@@ -224,11 +224,11 @@ Append either or both optional lines only when the capability earns a place;
never write an empty or `none` placeholder:
```markdown
-- **Native shape suggestion**: <semantic object/result plus candidate preset/Connector family or Boolean operation/operand roles>
+- **Native shape suggestion**: <semantic page/object geometry jobs plus independent atom roles, candidate preset/Connector family, or Boolean operation/operand roles as applicable>
- **Motion suggestion**: <communication job plus desired page-entry or reveal relationship/order>
```
-Add `Mathematical content` whenever a Slide needs a mathematical expression preserved exactly. Store the expression body as valid LaTeX without `$...$`, `$$...$$`, `\(...\)`, or `\[...\]` source delimiters; the field does not classify inline versus structural use. This is content authority for [`native-formula.md`](../references/native-formula.md), not a formula policy, marker, or implementation request; Executor chooses ordinary text, inline native math, or block native math. Add `Visualization` / `Images` when a Slide consumes §VII/§VIII or uses a page-local visual model. Name every value-driven geometry, qualitative relationship, cell grid, and child visual here; only independent Chart/Table entries use object keys. Describe qualitative order, linkage, hierarchy, grouping, contrast, overlap, and reading path freely—not as a model name or grammar enum. §IX may choose a custom Chart/Table fallback. Add `Native shape suggestion` only when a preset, stock Connector, or compound silhouette/cutout/intersection/fragment may help; name the semantic result plus candidate family or Boolean operands, never implementation geometry or keys. Executor chooses the primitive, preset, Boolean construction, or necessary freeform. Add `Motion suggestion` whenever transition/reveal advice strengthens communication, regardless of the Custom Animations outcome; state purpose and semantic order/relationship, not registry keys, options, timing, ids, or coverage. The suggestion never activates animation execution by itself, creates content, or binds implementation. Describe required visible image states in `Layout` / `Images` only for an explicit motion requirement or an enabled Custom Animations outcome. Add keyed `Native-ready` only for independent data charts or pure text-grid tables, `Fact IDs` for sourced claims, and `Data class: scenario` for invented demo values. Except on preservation paths, `Cover impact` carries a binding hook and adaptable composition; apply the same split to `Closing impact` only when the deck genuinely resolves. Roster/order/content stay authoritative. §VIII image layout is non-empty free prose with optional library ids; §VII Chart/Table rows are references. Executor owns geometry, hierarchy, treatment, and sparse local garnish.
+Add `Mathematical content` whenever a Slide needs a mathematical expression preserved exactly. Store the expression body as valid LaTeX without `$...$`, `$$...$$`, `\(...\)`, or `\[...\]` source delimiters; the field does not classify inline versus structural use. This is content authority for [`native-formula.md`](../references/native-formula.md), not a formula policy, marker, or implementation request; Executor chooses ordinary text, inline native math, or block native math. Add `Visualization` / `Images` when a Slide consumes §VII/§VIII or uses a page-local visual model. Name every value-driven geometry, qualitative relationship, cell grid, and child visual here; only independent Chart/Table entries use object keys. Describe qualitative order, linkage, hierarchy, grouping, contrast, overlap, and reading path freely—not as a model name or grammar enum. §IX may choose a custom Chart/Table fallback. Add `Native shape suggestion` only when a page-level shape system, preset, stock Connector, or compound silhouette/cutout/intersection/fragment may help; name semantic geometry jobs and relationships plus independent atom roles, a candidate family, or Boolean operands as applicable, never implementation geometry or keys. Executor chooses the primitive, preset, independent compound construction, Boolean result, or necessary freeform. Add `Motion suggestion` whenever transition/reveal advice strengthens communication, regardless of the Custom Animations outcome; state purpose and semantic order/relationship, not registry keys, options, timing, ids, or coverage. The suggestion never activates animation execution by itself, creates content, or binds implementation. Describe required visible image states in `Layout` / `Images` only for an explicit motion requirement or an enabled Custom Animations outcome. Add keyed `Native-ready` only for independent data charts or pure text-grid tables, `Fact IDs` for sourced claims, and `Data class: scenario` for invented demo values. Except on preservation paths, `Cover impact` carries a binding hook and adaptable composition; apply the same split to `Closing impact` only when the deck genuinely resolves. Roster/order/content stay authoritative. §VIII image layout is non-empty free prose with optional library ids; §VII Chart/Table rows are references. Executor owns geometry, hierarchy, treatment, and sparse local garnish.
For free-design pages, describe `Layout` through relationships, hierarchy, regions, and column spans; do not prescribe element-level `x`, `y`, `width`, or `height` or duplicate the global geometry in §II/§V. Exact coordinates belong to Executor SVG authoring. Preserve literal geometry only when the user explicitly requires it or a mirror/template preservation contract owns it.
diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.md
index b1c353db..872a173c 100644
--- a/skills/ppt-master/workflows/generate-pptx.md
+++ b/skills/ppt-master/workflows/generate-pptx.md
@@ -652,7 +652,7 @@ sidecars, or guessed family paths.
**Visual Construction Phase**: generate SVG pages sequentially, one at a time, in one continuous pass → `<project_path>/svg_output/`
-Each completed SVG MUST be a standalone, complete representation of that slide's visible design. Template SVGs and locked planning artifacts may guide construction, but export must not reach back to them to add visible objects omitted from `svg_output/`. Speaker notes, animation, narration, transitions, and direct native-PPTX workflows remain separately owned artifacts/capabilities. Treat §IX `Native shape suggestion` as a candidate, not a command: inspect the actual page construction, then choose the highest-level faithful construction in this order — editable basic primitive, exact Office preset, Merge Shapes Boolean result, and only then a necessary freeform. Apply [`native-shape-authoring.md`](../references/native-shape-authoring.md) before materializing an adopted native treatment. Diagram relationships follow the same Shape-first order; do not infer a preset from contour similarity.
+Each completed SVG MUST be a standalone, complete representation of that slide's visible design. Template SVGs and locked planning artifacts may guide construction, but export must not reach back to them to add visible objects omitted from `svg_output/`. Speaker notes, animation, narration, transitions, and direct native-PPTX workflows remain separately owned artifacts/capabilities. Treat §IX `Native shape suggestion` as a candidate, not a command: inspect the actual page construction, then follow [`native-shape-authoring.md`](../references/native-shape-authoring.md) — compose editable primitives and exact Office presets as independent atoms when possible, materialize a Merge Shapes Boolean result only where contour semantics require it, and use necessary freeform last. Diagram relationships follow the same Shape-first gate; do not infer a preset from contour similarity.
**Motion-ready image composition**: Only when an explicit user motion
instruction, the effective Custom Animations outcome in `design_spec.md §I` is
diff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.md
index 60c323f0..35843b01 100644
--- a/skills/ppt-master/workflows/profiles/quick-generate.md
+++ b/skills/ppt-master/workflows/profiles/quick-generate.md
@@ -381,7 +381,7 @@ generation capability is resolved during resource preparation, not eligibility.
| Reusable title/corner decoration, a dominant illustrated anchor, supporting figure, or accent strengthens one or more page compositions | A coherent AI illustration family prepared as transparent `slice` assets and combined freely with other carriers |
| A compact semantic cue clarifies a category, process, KPI, state, or navigation item | Prepared project-local SVG/emoji icon, an illustrated-icon `slice`, or a coherent combination |
| A real company, product, service, or social brand must appear as itself | Prepare the exact brand mark from `simple-icons` or supplied project assets as needed; it is not a user-facing library choice |
-| Editable geometry can express a relationship, flow, emphasis, callout, symbol, or diagram | Basic SVG primitive, exact Office preset, Boolean result, then necessary freeform |
+| Editable geometry can express a relationship, flow, emphasis, callout, symbol, or diagram | Basic primitives and exact Office presets, independently composed when possible; Boolean only for required contour semantics; necessary freeform last |
| Values, categories, time, weights, or duration determine mark geometry | Value-driven chart |
| Sequence, hierarchy, role, region, or relationship determines page-local topology | Qualitative structure |
| Rows, columns, cells, headers, merges, and alignment form the information model | Cell-grid table |