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

fix(shape-authoring): enforce native-first geometry selection

hugohe32ca1d3194735
diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.md
index c534e70d..f7850482 100644
--- a/skills/ppt-master/references/executor-base.md
+++ b/skills/ppt-master/references/executor-base.md
@@ -35,7 +35,7 @@ Always-loaded Executor authority for flat SVG page authoring and behavior shared
| Elevation | shadow, glow, explicit highlights |
| Image integration | scrim, vignette, brand wash, clipping, faux glass |
| Line / type | dash/cap/join, markers, gradient stroke; tracking, outline, alpha/gradient text |
-| Space / constructed style | transform/reuse, curves/arcs, hand-drawn, ink/Riso, halftone, isometric, paper cut |
+| Space / constructed style | transform/reuse, hand-drawn, ink/Riso, halftone, isometric, paper cut; custom curves/arcs only when meaning or the locked style requires them |
| Continuous action across pages | Paired pages that differ in one property, exported with morph |
**Hard rule — discovery does not expand compatibility**: Follow `svg-effects.md` syntax and fallbacks; unsupported blur, blend, mask, dense texture, or skew remains baked/alternative-only.
@@ -145,7 +145,7 @@ Before drawing each page, look up its entry in `page_rhythm` (key format `P<NN>`
- **Fact provenance**: when a §IX page lists `Fact IDs`, resolve each ID from `sources/*.facts.json` and keep the claim/value unchanged. Render a compact source footnote using the source name and a short URL/domain when space permits; state the attribution naturally in speaker notes. When §IX says `Data class: scenario`, place a visible localized `Scenario data` / `情景数据` label adjacent to the affected KPI/chart and state naturally in notes that the number is illustrative. Never attach an external fact ID to scenario data or let an unlabeled invented KPI look factual.
- **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. Before defaulting to stacked rounded-rect cards or uniform equal columns, pick one page-scale move from the locked visual style's §1 `Composition geometry` (a bleed shape, diagonal split, oversized numeral, orbit rings, …) to stage the page's primary zone. Card grids are one option among many, not the house layout.
- **Containers are structural**: cards and grids express grouping, hierarchy, or capacity, not a house style. Preserve meaningful template frames; restyle radius, fill, stroke, and depth from the active Design Spec and `spec_lock.md`. Chart-catalog adaptation is owned by [`executor-chart.md`](./executor-chart.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, consider one page-specific polygon/path that expresses the relationship before stacking generic arrows. This does not override §3.0 when one literal stock shape is the semantic object.
+- **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 — 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 body containers flat.
- **Phased generation** (recommended):
1. **Visual Construction Phase**: generate all SVG pages sequentially for visual consistency. Use layout judgment for chart marks during the draft. **MUST embed plot-area markers** per [`executor-chart.md`](./executor-chart.md) §2.1 on every §IX-planned data-chart page — coordinate calibration is a post-generation step (see [`verify-charts`](../workflows/stages/verify-charts.md)) that depends on these markers — and **native object metadata** per [`executor-chart.md`](./executor-chart.md) §2.2 on every planned native-ready object. **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). **First-page gate (Mandatory)**: after completing the first page, run `python3 scripts/svg_quality_checker.py <project_path> --stage first-page --json` 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.
@@ -154,29 +154,42 @@ Before drawing each page, look up its entry in `page_rhythm` (key format `P<NN>`
### 3.0 Native Shape Selection
-**Reach for a native preset whenever one expresses a complete object — this is
-the default, not the exception.** Block arrows, chevrons, banners / ribbons,
-callouts, flowchart nodes, stars, and other Office symbols should be **authored
-as presets** via `preset_shape_svg.py`, not drawn as plain `<path>`s or faked
-with rectangles: presets are what give the slide real PowerPoint shapes with
-adjustment handles and the designed, non-flat-card look. When a page calls for
-one of these, use the preset. Apply the decision gate in
-[`native-shape-authoring.md`](./native-shape-authoring.md) to pick the right
-shape and to keep only the exceptions below as ordinary SVG.
+**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
+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
+`<path>`s or faked with rectangles. Apply the decision gate in
+[`native-shape-authoring.md`](./native-shape-authoring.md) before drawing the
+object.
§IX `Native shape suggestion` records a semantic opportunity, not a literal
-tool command. Decide from the actual page construction whether a preset,
-Boolean result, or ordinary SVG best realizes it; a different implementation
-is valid when it preserves the intended object and content.
+tool command. Decide from the actual page construction whether a basic
+primitive, preset, Boolean result, or necessary freeform best realizes it; a
+different implementation is valid when it preserves the intended object and
+content.
| 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. |
| Two or more closed operands whose final semantic object depends on union, cutout, overlap-only coverage, symmetric difference, or fragmentation | Evaluate `shape_boolean_svg.py` at draw time and use it 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 overlaps that remain separate objects | Keep ordinary SVG path/polygon geometry. |
-| Similar-looking contour only | Never guess; keep ordinary SVG. |
+| 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. |
+| 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
+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
+semantics, not by convenience.
This decision applies only while drawing a new object. A suggestion never
triggers retrospective scanning, contour classification, or automatic
@@ -188,14 +201,19 @@ generates one compact atomic `<g>` from the shared 187-shape registry, with
semantic metadata and base paint written once. Rerun that helper when geometry
or paint changes; never edit one of its direct paths.
-For chart-template and diagram authoring, thin relationships use ordinary
-`<line>` / supported open `<path>` geometry with registered arrow markers;
-solid directional blocks use ordinary `shape` presets such as `rightArrow` or
-`chevron`. Do not select a connector-family preset merely because two nodes are
-related, and never hand-add endpoint/site metadata. Connector-family presets
-remain available only for an explicit request for a standalone unconnected
-`p:cxnSp`; imported Connector topology stays under the preserve/mirror contract.
-`actionButton*` presets provide visual geometry only, not actions or hyperlinks.
+**Default — relationship geometry**: use `<line>` for a straight relationship.
+When a relationship genuinely needs a bend or curve and a stock Connector
+contour fits, prefer the matching `bentConnector*` / `curvedConnector*` preset
+over a hand-authored SVG Bézier. Use an open freeform path only when a straight
+line and the native Connector families cannot faithfully express the required
+route, data geometry, or locked hand-drawn / organic style. A directional solid
+object remains an ordinary `shape` preset such as `rightArrow` or `chevron`.
+
+Authored Connector presets export as unconnected `p:cxnSp` objects: they do not
+bind to node sites or follow moved nodes. Never hand-add endpoint/site metadata
+or claim attachment semantics. Imported Connector topology stays under the
+preserve/mirror contract. `actionButton*` presets provide visual geometry only,
+not actions or hyperlinks.
**Hard rule — narrow helper scope**: Both helpers print only their documented
stdout fragment(s); neither writes a page or chooses layout. Read every returned
diff --git a/skills/ppt-master/references/image-layout-patterns.md b/skills/ppt-master/references/image-layout-patterns.md
index 39cc1452..fa2c9716 100644
--- a/skills/ppt-master/references/image-layout-patterns.md
+++ b/skills/ppt-master/references/image-layout-patterns.md
@@ -109,15 +109,15 @@ Pick one or more of these as the page's bones. Cross-primary combinations are en
This is the family that opens up the largest design space and the one AI is most likely to skip. The shared pattern: image fills the slide (or a large region), native SVG elements are layered on top to carry the actual information. None of the overlay elements need to be generated by the image model — they are vector primitives you draw yourself.
-38. **Background image + annotation cards with bezier leader lines** — full-bleed `<image>` + 2–4 small info cards (`<rect rx>` + icon + title + one-line text) placed in the image's calm regions. From each card, draw a bezier `<path>` ending in a `marker-end` arrow that points to the specific object in the image being annotated. Card text and leader lines are editable; image is the scene.
+38. **Background image + annotation cards with Shape-first leaders** — full-bleed `<image>` + 2–4 small info cards (`<rect rx>` + icon + title + one-line text) placed in the image's calm regions. Point to each subject with a straight `<line>` by default, or an authored native bent/curved Connector when its stock contour fits. Use a custom Bézier leader only when neither can route around the subject faithfully. Card text and leader lines remain editable; image is the scene.
-39. **Background image + flow nodes drawn over the scene** — the image is a real or rendered scene (workshop, control room, landscape). On top, draw a dashed `<path>` route that traces a workflow through the scene, with numbered `<circle>` nodes at each stop. Each node = number + icon + label. The flow is fully editable; the image is atmosphere.
+39. **Background image + flow nodes drawn over the scene** — the image is a real or rendered scene (workshop, control room, landscape). On top, connect numbered `<circle>` stops with straight `<line>` segments or exact native bent/curved Connector contours. Use a custom dashed route only when the workflow must follow meaningful scene geometry those shapes cannot express. Each node = number + icon + label. The flow is fully editable; the image is atmosphere.
40. **Background image + floating KPI metric cards** — full-bleed image (often an operations photo) + dark scrim + multiple `<rect>` cards in negative-space regions. Each card = icon + small label + large metric number. Image gives context; cards give the data.
41. **Background image + measurement lines and module tags (engineering overlay)** — used on technical / blueprint / cross-section images. Draw measurement lines with end-caps (`<line>` + perpendicular ticks) spanning a feature, with a centered label box reading dimensions or part names. Add tagged callouts with `<rect>` + monospace text. Reads as engineering drawing markup.
-42. **Background image + glassmorphism UI panels** — image is the visual world; on top, draw UI elements (semi-transparent panels, progress arcs, status badges, indicators). Panels use `fill-opacity="0.6–0.8"` + thin light-color strokes; arcs via `<path d="…A…">`. Looks like a live dashboard floating above the scene.
+42. **Background image + glassmorphism UI panels** — image is the visual world; on top, draw UI elements (semi-transparent panels, progress arcs, status badges, indicators). Panels use `fill-opacity="0.6–0.8"` + thin light-color strokes; use exact native `arc` / `blockArc` presets when they fit, and custom `A` geometry only for data-defined arcs they cannot express. Looks like a live dashboard floating above the scene.
43. **Background image + native data chart on top** — AI image generation cannot produce accurate data charts. Solution: use an AI-generated dashboard image as **visual reference only** (clearly labeled as such in a caption), and draw the actual chart with native SVG primitives (`<line>` axes, `<path>` series, `<circle>` data points) directly on or next to it. Required marker if exporting: `<!-- chart-plot-area: x_min,y_min,x_max,y_max -->` inside the chart group.
@@ -202,7 +202,7 @@ Stack any of these freely on top of a Primary structure. Multiple Modifiers per
20–23. **Basic shape crops** — `<clipPath>` holding one shape, referenced by `<image clip-path="url(#id)"/>`: `<circle>` (**#20**), `<rect rx ry>` (**#21**, `rx` sets roundness), `<ellipse>` (**#22**), `<polygon points>` (**#23**, keep every vertex inside the image's display rect). #24 supersedes all four whenever the contour is curved or organic.
-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.
+24. **Custom path crop (blob, leaf, silhouette)** — use `<clipPath><path d="…"/></clipPath>` only when circle, ellipse, rounded-rect, and polygonal crops cannot faithfully express the silhouette. PowerPoint export translates the necessary custom contour to `custGeom` and survives roundtrip.
25. **Layered paper-cut stack** — clip each image layer under the image-only contract in [`shared-standards-core.md`](./shared-standards-core.md) §1.2; draw vector layers directly in their final geometry. A small conditional shadow on each layer can create physical separation.
@@ -301,7 +301,7 @@ Stack any of these freely on top of a Primary structure. Multiple Modifiers per
## Special Techniques
-62. **Same image, two references — full view + zoom-callout** — reference the same image file twice in two `<image>` elements: one shows the full scene at normal size; the second uses `clipPath` (circle or rectangle) plus a larger display size to "zoom into" a sub-region. Connect them with a bezier `<path>` ending in `marker-end`; ring the zoom with a `<circle stroke>` so it reads as a magnifying lens. No special asset needed — the zoom effect comes from same-source-different-display.
+62. **Same image, two references — full view + zoom-callout** — reference the same image file twice in two `<image>` elements: one shows the full scene at normal size; the second uses `clipPath` (circle or rectangle) plus a larger display size to "zoom into" a sub-region. Connect them with a straight `<line>` or an exact native bent/curved Connector contour; use a custom Bézier only when the leader must avoid meaningful image content. Ring the zoom with a `<circle stroke>` so it reads as a magnifying lens. No special asset needed — the zoom effect comes from same-source-different-display.
63. **Transparent PNG sticker / cutout** — an RGBA PNG placed via plain `<image>`; the transparency lives in the file, so no `clipPath` is needed. Sources: `slice_images.py --alpha` output (see [image-generator.md](./image-generator.md) §4.3), an AI backend with native transparent output, or a user asset.
@@ -360,7 +360,7 @@ Stack any of these freely on top of a Primary structure. Multiple Modifiers per
A page is built by layering. Pick one or more **Primary Structures** (Part 1) as the page's bones, then add any number of **Modifier Layers** (Part 2) for finish. Both stack — the question on each page is "is the next layer still earning its place", not "have I exceeded a quota".
-**Cross-primary combinations are encouraged.** A side-by-side comparison (#48) where each side is annotated with bezier-leader cards (#38) is one page, not a violation. A 3×3 grid (#9) whose center cell is upgraded to an image-as-canvas with KPI overlay (#40) reads as one composition. The old reflex "one primary per page" tends to under-use the catalog — combine when the page asks for it.
+**Cross-primary combinations are encouraged.** A side-by-side comparison (#48) where each side is annotated with Shape-first leader cards (#38) is one page, not a violation. A 3×3 grid (#9) whose center cell is upgraded to an image-as-canvas with KPI overlay (#40) reads as one composition. The old reflex "one primary per page" tends to under-use the catalog — combine when the page asks for it.
**Modifier stacking pattern that works in practice** — observed on real content pages combining one Primary with four Modifiers:
diff --git a/skills/ppt-master/references/native-shape-authoring.md b/skills/ppt-master/references/native-shape-authoring.md
index 8fa02e69..082ef46a 100644
--- a/skills/ppt-master/references/native-shape-authoring.md
+++ b/skills/ppt-master/references/native-shape-authoring.md
@@ -3,27 +3,30 @@
# Native Shape Authoring Reference
Use this reference during Executor SVG construction or project-owned canonical
-template maintenance when one standard PowerPoint shape can express one
-complete object or multiple closed shapes require a PowerPoint-style Boolean
-result. Neither helper writes a page. The preset helper does not create the
-shape's own `p:txBody`; keep visible text outside the atomic fragment.
+template maintenance when basic primitives, one standard PowerPoint shape, or
+multiple closed shapes can express the intended object. Prefer, in order:
+editable basic primitives, one exact Office preset, then a PowerPoint-style
+Boolean result. 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
-Apply this decision order before drawing a stock geometric object.
+Apply this decision order before drawing any new geometric contour.
-> This gate is for picking the **right** native shape, not for avoiding presets.
-> When a page needs an arrow, chevron, callout, banner, flowchart node, or a
-> literal Office symbol, authoring it as a preset is the **default** — the
-> ordinary-SVG rows below are deliberate exceptions, not the norm.
+> This gate is for picking the **highest-level faithful native construction**.
+> Do not hand-author a freeform merely because an SVG path is convenient.
| Condition | Action |
|---|---|
| Plain rectangle, symmetric rounded rectangle, circle, or ellipse | Write the ordinary SVG primitive; the exporter already emits an editable native shape. |
+| 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 closed authored shapes 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. |
-| The visual meaning or contour exceeds one stock shape | Write ordinary `<path>` / `<polygon>` geometry; export keeps it as editable custom geometry. |
-| The shape only resembles a preset | Keep ordinary SVG; never infer a preset from contour similarity. |
+| 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. |
+| 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. |
**Hard rule**: `preset_shape_svg.py` is the only authoring entry for
@@ -46,10 +49,10 @@ paths or contours, or upgrade ordinary SVG during export.
| Visual intent | Candidate presets | Boundary |
|---|---|---|
| Literal geometric body | `triangle`, `diamond`, `pentagon`, `hexagon`, `octagon`, `star5` | Use only when the named geometry itself is the intent. |
-| Solid block direction | `rightArrow`, `leftArrow`, `upArrow`, `downArrow`, `leftRightArrow`, `upDownArrow`, `chevron` | Thin relationship geometry remains an ordinary SVG `<line>` / `<path>` with no attachment semantics. |
+| Solid block direction | `rightArrow`, `leftArrow`, `upArrow`, `downArrow`, `leftRightArrow`, `upDownArrow`, `chevron` | Use `<line>` for a thin straight relationship; do not fake a solid directional object with a stroked path. |
| Standard flowchart node | `flowChartProcess`, `flowChartDecision`, `flowChartInputOutput`, `flowChartTerminator`, `flowChartDocument` | Use only for an actual flowchart; ordinary content cards remain cards. |
-| Explicit standalone connector | `straightConnector1`, `bentConnector*`, `curvedConnector*` | Use only when the user explicitly requests a PowerPoint Connector object. Diagram relationships otherwise stay ordinary SVG line/path shapes with no attachment semantics. |
-| Stock callout | `wedgeRectCallout`, `wedgeRoundRectCallout`, `wedgeEllipseCallout`, `cloudCallout` | Brand-specific or custom-tail callouts remain free SVG. |
+| Stock bent / curved relationship contour | `bentConnector*`, `curvedConnector*` | Prefer when the contour fits and endpoint attachment is not required. The authored object is an unconnected native Connector, so moving nodes does not reroute it. |
+| Stock callout | `wedgeRectCallout`, `wedgeRoundRectCallout`, `wedgeEllipseCallout`, `cloudCallout` | For a brand-specific or custom tail, continue through the Boolean gate; use freeform only if the result still cannot be expressed faithfully. |
| Stock ribbon or scroll | `ribbon*`, `ellipseRibbon*`, `verticalScroll`, `horizontalScroll` | Select only when the stock contour is visually acceptable. |
| Standalone math symbol | `mathPlus`, `mathMinus`, `mathMultiply`, `mathDivide`, `mathEqual`, `mathNotEqual` | Inline formulas and prose symbols remain text/formula assets. |
| Literal Office symbol | `heart`, `sun`, `moon`, `lightningBolt`, `gear6`, `gear9` | Never replace an icon required by `spec_lock.icons`. |
@@ -61,13 +64,14 @@ python3 ${SKILL_DIR}/scripts/preset_shape_svg.py list --search arrow
python3 ${SKILL_DIR}/scripts/preset_shape_svg.py describe rightArrow
```
-**Shape-first diagram rule**: chart-template adaptations use ordinary line/path
-shapes for thin relationships and ordinary `shape` presets for solid block
-directions. Connector-family presets are reserved for an explicit request for
-a standalone PowerPoint Connector; they are not the default for architecture,
-process, hierarchy, or framework diagrams and do not gain attachment semantics.
-Existing Connector topology imported from a source PPTX remains owned by the
-preserve/mirror round-trip contract.
+**Shape-first diagram rule**: use `<line>` for straight thin relationships;
+use an exact connector-family preset for a stock bent or curved contour; use a
+block-arrow / chevron preset for a solid direction. Resort to an open freeform
+path only when those native constructions cannot faithfully express the
+relationship, data geometry, or locked hand-drawn / organic style. Newly
+authored connector-family presets remain unconnected and do not gain attachment
+semantics. Existing Connector topology imported from a source PPTX remains
+owned by the preserve/mirror round-trip contract.
**Forbidden — false native semantics**:
@@ -95,7 +99,7 @@ python3 ${SKILL_DIR}/scripts/preset_shape_svg.py render rightArrow \
--adjust "adj1=val 50000"
```
-For an explicitly requested standalone native connector only:
+For a stock bent / curved contour that does not require endpoint attachment:
```bash
python3 ${SKILL_DIR}/scripts/preset_shape_svg.py render bentConnector3 \
diff --git a/skills/ppt-master/references/strategist.md b/skills/ppt-master/references/strategist.md
index ce9445b0..863e2185 100644
--- a/skills/ppt-master/references/strategist.md
+++ b/skills/ppt-master/references/strategist.md
@@ -284,7 +284,7 @@ and intent; explicit user/template requirements remain binding.
| Capability | Opportunity signal | Design Spec handoff |
|---|---|---|
| Image composition | Image-as-canvas plus native overlay, editorial crop, collage, cutout, or another image-led composition carries the page better than an adjacent rectangle | Propose a permitted image source; when selected, load [`strategist-image.md`](./strategist-image.md) and record an exact catalog §VIII `Layout pattern` as the preferred composition |
-| Native preset / Merge Shapes | A literal Office symbol 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 or Boolean operation/operands |
+| 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 |
| Page transition | A section/state change, spatial continuity, or recorded/self-running flow benefits from motion between pages | Add an optional §IX `Motion suggestion` describing the communication job; leave effect and timing to Executor |
| Object animation | Progressive reveal clarifies sequence, causality, comparison, hierarchy, or narration order | Add an optional §IX `Motion suggestion` describing reveal units/order; leave group ids, effect, and timing to Executor |
@@ -332,12 +332,15 @@ A failed validation must be corrected with a recalled key. `no-template-match` i
**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, or star. 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 preset,
-Boolean construction, or ordinary SVG under its native-shape branch; the
-recommendation never creates a §VII row or lock field.
+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
+creates a §VII row or lock field.
### Speaker Notes Requirements (Default — no discussion needed)
diff --git a/skills/ppt-master/references/svg-effects.md b/skills/ppt-master/references/svg-effects.md
index b48c9ed2..d70428b5 100644
--- a/skills/ppt-master/references/svg-effects.md
+++ b/skills/ppt-master/references/svg-effects.md
@@ -564,12 +564,19 @@ least two.
bounds reuse its normalized commands rather than a second path grammar.
Command identity, relative coordinates, shorthand, arc parameters, and original
-handles are not retained. Geometry needs non-zero bounds. Use a closed cubic
-path for organic silhouettes, polygon/closed path for ribbons/facets, open path
-for curved connectors, multi-`M` path for exact linework, and a [`shared-standards-core.md`](./shared-standards-core.md) §1.2 path clip
-for organic pictures. Filled silhouettes end with `Z`; open paths use
-`fill="none"`. Do not depend on `fill-rule="evenodd"`; build explicit visible
-geometry or bake an essential knockout.
+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
+cannot express, polygon/closed path for unmatched ribbons/facets, and an open
+path only for a required data curve, custom route, or locked hand-drawn /
+organic style. Straight relationships use `<line>`; exact stock bends/curves
+use an authored native Connector preset. Multi-`M` paths remain available for
+exact linework, and a [`shared-standards-core.md`](./shared-standards-core.md)
+§1.2 path clip for unmatched organic pictures. Filled silhouettes end with
+`Z`; open paths use `fill="none"`. Do not depend on
+`fill-rule="evenodd"`; build explicit visible geometry or bake an essential
+knockout.
For a fixed background, a background-colored overlay is also valid.
| Rounded rect input | Result |
@@ -657,6 +664,8 @@ filled `Native-normalized` arrowhead. Example:
browser-filter permissions.
**Reference — not a constraint**: use them only when they match the locked style.
+Their curve recipes are explicit exceptions to the Shape-first default above;
+they do not authorize decorative freeforms in another style.
| Intent | Construction | Boundary / fidelity |
|---|---|---|
@@ -744,9 +753,9 @@ subsection; this table only routes scenarios.
| Hand/print | Annotation → highlighter/curve; ink wash → layered alpha paths; Riso → offset duplicate | §6.11; no turbulence, true bleed, or blend mode |
| Pixel/halftone | Pixel accent → integer rect grid; sparse screen → circles | §6.11; dense screen → §6.12 |
| Faceted/layered | Pseudo-3D → 2D facets; paper cut → direct shadow per layer | §6.11; no 3D transform/group composite shadow |
-| Data/freeform | Series depth → area first + line above; organic card → closed cubic; shaped image → [`shared-standards-core.md`](./shared-standards-core.md) §1.2 path clip | §6.11 / §6.9 |
+| Data/freeform | Series depth → area first + line above; unmatched organic silhouette → closed cubic; shaped image → [`shared-standards-core.md`](./shared-standards-core.md) §1.2 path clip | §6.11 / §6.9 |
| Radial | Donut/gauge → explicit arcs; sunburst → sector per node; position-insensitive ring → shorthand | §6.10; shorthand has 90° preview/native offset |
-| Arrow | Manual diagonal arrowhead → calculated triangle; ordinary connector → marker | §6.10 / §1.1 |
+| Arrow | Straight relationship → `<line>` + marker; stock bend/curve → native Connector; unmatched custom route → separate calculated arrowhead if needed | §6.10 / §1.1 / native-shape authoring |
| Unsupported | Dense grain, complex composite, or skew → explicit alternative or baked asset | §6.12; foreground text/data stay editable SVG |
---
diff --git a/skills/ppt-master/references/template-designer.md b/skills/ppt-master/references/template-designer.md
index 6ddc367b..d3c16571 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. Use the compact authored-preset group only for exact registered preset matches. |
+| `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. |
| `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,6 +83,8 @@ 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.
**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
@@ -372,7 +374,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 `preset_shape_svg.py` compact canonical `<g>` output for exact preset matches, with paint from the confirmed brief / `design_spec.md`; use ordinary project SVG for other geometry. Reuse exported image/vector assets, not opaque source shape payload or source topology. |
+| `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. |
| `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
@@ -381,8 +383,9 @@ 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; other geometry stays ordinary project SVG. `data-pptx-replace-with` remains
-reserved for optional PowerPoint-native Chart/Table replacement markers.
+payload; otherwise they apply the Boolean/freeform fallback gate above.
+`data-pptx-replace-with` remains reserved for optional PowerPoint-native
+Chart/Table replacement markers.
**Explicit template SVG contract**:
diff --git a/skills/ppt-master/references/visual-styles/soft-rounded.md b/skills/ppt-master/references/visual-styles/soft-rounded.md
index a66073a9..1caf771b 100644
--- a/skills/ppt-master/references/visual-styles/soft-rounded.md
+++ b/skills/ppt-master/references/visual-styles/soft-rounded.md
@@ -7,7 +7,7 @@ Approachable and modern. Rounded cards, gentle elevation, friendly rhythm. For p
## 1. Shape & decoration
- Shape language: rounded rectangles (`rx` 12-16), pill tags, soft containers. Consistent radius deck-wide.
-- Composition geometry: a large soft disc or blob bleeding off one edge as the color field; a pill chain or arc path replacing the boxed step row; one hero panel overlapping a full-width tinted band; an oversized rounded numeral behind the point. Cards are the container language, not the composition — vary the stage they sit on.
+- Composition geometry: a large soft disc or blob bleeding off one edge as the color field; a pill chain or exact native `arc` / `blockArc` preset replacing the boxed step row; one hero panel overlapping a full-width tinted band; an oversized rounded numeral behind the point. Use a custom arc path only when the presets cannot faithfully express the intended contour. Cards are the container language, not the composition — vary the stage they sit on.
- Decoration: cards as the primary container; icon accents; numbered circles; gentle dividers. Moderate, in service of clarity.
- Whitespace: comfortable padding inside cards; even gutters; balanced rather than austere.
diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.json
index 5cec815e..5d13d083 100644
--- a/skills/ppt-master/scripts/prompt_audit_manifest.json
+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json
@@ -12,12 +12,12 @@
"skills/ppt-master/templates/schemas/*.json"
],
"exclude": [],
- "max_tokens": 367500
+ "max_tokens": 368700
},
"file_budgets": {
"AGENTS.md": 2350,
"skills/ppt-master/SKILL.md": 850,
- "skills/ppt-master/references/executor-base.md": 7650,
+ "skills/ppt-master/references/executor-base.md": 7925,
"skills/ppt-master/references/executor-structured.md": 5300,
"skills/ppt-master/references/executor-chart.md": 3100,
"skills/ppt-master/references/executor-image.md": 900,
@@ -25,13 +25,13 @@
"skills/ppt-master/references/executor-notes.md": 900,
"skills/ppt-master/references/shared-standards.md": 250,
"skills/ppt-master/references/shared-standards-core.md": 10950,
- "skills/ppt-master/references/svg-effects.md": 11600,
+ "skills/ppt-master/references/svg-effects.md": 11725,
"skills/ppt-master/references/native-data-interface.md": 6200,
"skills/ppt-master/references/pptx-structure-interface.md": 4300,
- "skills/ppt-master/references/strategist.md": 13900,
+ "skills/ppt-master/references/strategist.md": 13975,
"skills/ppt-master/references/strategist-image.md": 2300,
"skills/ppt-master/references/strategist-template.md": 2100,
- "skills/ppt-master/templates/design_spec_reference.md": 2975,
+ "skills/ppt-master/templates/design_spec_reference.md": 3000,
"skills/ppt-master/templates/spec_lock_reference.md": 2350,
"skills/ppt-master/workflows/generate-pptx.md": 12700,
"skills/ppt-master/workflows/stages/apply-template-workspace.md": 1800
@@ -93,7 +93,7 @@
"skills/ppt-master/templates/README.md",
"skills/ppt-master/templates/decks/README.md"
],
- "max_tokens": 57775
+ "max_tokens": 57825
},
"route.create-template.layout": {
"description": "Create Layout path through Template_Designer, SVG core, and the structured PPTX interface.",
@@ -111,7 +111,7 @@
"skills/ppt-master/templates/README.md",
"skills/ppt-master/templates/layouts/README.md"
],
- "max_tokens": 57950
+ "max_tokens": 58000
},
"route.enhance-native-pptx": {
"description": "Finished-PPTX native enhancement route.",
@@ -322,7 +322,7 @@
"stage.generate.executor.notes"
],
"files": [],
- "max_tokens": 83800
+ "max_tokens": 84200
},
"route.generate.flat-ai-two-types": {
"description": "Generate-PPTX context with AI images, representative multi-source custom rendering, and two local types.",
@@ -335,7 +335,7 @@
"stage.generate.image.ai-two-types"
],
"files": [],
- "max_tokens": 124375
+ "max_tokens": 124850
},
"route.generate.flat-in-hand-image": {
"description": "Generate-PPTX context with provided, placeholder, or formula images and no acquisition role.",
@@ -347,7 +347,7 @@
"stage.generate.executor.notes"
],
"files": [],
- "max_tokens": 97675
+ "max_tokens": 98175
},
"route.generate.flat-web-image": {
"description": "Generate-PPTX context with web image acquisition.",
@@ -360,7 +360,7 @@
"stage.generate.image.web"
],
"files": [],
- "max_tokens": 104925
+ "max_tokens": 105400
},
"route.enhance-native-pptx.audio": {
"description": "Enhance Native PPTX with the shared narration-audio stage.",
@@ -380,7 +380,7 @@
"profile.generate.beautify-pptx"
],
"files": [],
- "max_tokens": 90700
+ "max_tokens": 91100
},
"route.generate.flat-no-image-chart": {
"description": "Default flat Generate-PPTX path with chart authoring, native-data replacement, and verification.",
@@ -393,7 +393,7 @@
"stage.generate.verify-charts"
],
"files": [],
- "max_tokens": 107875
+ "max_tokens": 108550
},
"route.generate.brand-flat-no-image": {
"description": "Brand-preset flat Generate-PPTX path without image acquisition.",
@@ -405,7 +405,7 @@
"stage.generate.template.brand"
],
"files": [],
- "max_tokens": 90825
+ "max_tokens": 91225
},
"route.generate.deck-structured-no-image": {
"description": "Deck-preset structured Generate-PPTX path without image acquisition.",
@@ -417,7 +417,7 @@
"stage.generate.template.deck"
],
"files": [],
- "max_tokens": 100750
+ "max_tokens": 101150
},
"route.generate.layout-structured-no-image": {
"description": "Layout-preset structured Generate-PPTX path without image acquisition.",
@@ -429,7 +429,7 @@
"stage.generate.template.layout"
],
"files": [],
- "max_tokens": 101200
+ "max_tokens": 101600
},
"route.generate.topic-only-flat-no-image": {
"description": "Topic research followed by the default flat no-image Generate-PPTX path.",
@@ -439,7 +439,7 @@
"route.generate.flat-no-image"
],
"files": [],
- "max_tokens": 85200
+ "max_tokens": 85600
},
"stage.generate.executor.flat": {
"description": "Incremental flat Executor core with representative multi-source custom mode/style execution.",
@@ -549,7 +549,7 @@
"stage.generate.executor.image"
],
"files": [],
- "max_tokens": 59550
+ "max_tokens": 59950
},
"stage.generate.topic-research": {
"description": "Gap-targeted factual intake stage.",
@@ -675,7 +675,7 @@
"files": [
"skills/ppt-master/references/native-shape-authoring.md"
],
- "max_tokens": 3100
+ "max_tokens": 3250
},
"route.generate.planning-template": {
"description": "Generate-PPTX planning context after an explicit template workspace is installed.",
@@ -685,7 +685,7 @@
"stage.generate.strategist.template"
],
"files": [],
- "max_tokens": 61100
+ "max_tokens": 61200
},
"route.generate.planning-template-ai": {
"description": "Explicit template workspace plus confirmed AI-image planning.",
@@ -695,7 +695,7 @@
"route.generate.planning-ai"
],
"files": [],
- "max_tokens": 73575
+ "max_tokens": 73775
},
"stage.generate.executor.chart": {
"description": "Conditional chart/table page execution rules.",
@@ -722,7 +722,7 @@
"files": [
"skills/ppt-master/references/image-layout-patterns.md"
],
- "max_tokens": 8250
+ "max_tokens": 8350
},
"stage.generate.strategist.template": {
"description": "Conditional Strategist module for an explicitly installed template workspace.",
@@ -749,7 +749,7 @@
"skills/ppt-master/references/image-layout-spec.md",
"skills/ppt-master/references/svg-image-embedding.md"
],
- "max_tokens": 11625
+ "max_tokens": 11725
},
"stage.generate.executor.web-image": {
"description": "Conditional sourced-image attribution layered on image execution.",
@@ -760,7 +760,7 @@
"files": [
"skills/ppt-master/references/executor-web-image.md"
],
- "max_tokens": 12050
+ "max_tokens": 12150
},
"stage.generate.executor.notes": {
"description": "Post-SVG speaker-notes generation rules.",
@@ -776,7 +776,7 @@
"files": [
"skills/ppt-master/references/native-shape-authoring.md"
],
- "max_tokens": 3100
+ "max_tokens": 3250
},
"stage.shared.svg-effects": {
"description": "Conditional advanced SVG paint, effects, transforms, and geometry for Generate Executor or Create Template.",
@@ -784,7 +784,7 @@
"files": [
"skills/ppt-master/references/svg-effects.md"
],
- "max_tokens": 11600
+ "max_tokens": 11725
}
},
"duplicates": {
diff --git a/skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.md b/skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.md
index b84546fb..24553d21 100644
--- a/skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.md
+++ b/skills/ppt-master/templates/charts/CHART_STYLE_GUIDE.md
@@ -209,9 +209,11 @@
| 对象 | 模板表达 |
|---|---|
| 基础节点/容器 | `<rect>`、`<circle>`、`<ellipse>` |
-| 细关系线 | `<line>` 或少量开放 `<path>` |
+| 直线关系/分隔/引线 | `<line>` |
+| 预设可精确表达的弯折/曲线关系 | 完整 compact authored `bentConnector*` / `curvedConnector*` `<g>`;端点不附着 |
| 标准块箭头/流程节点 | 仅在 preset 精确匹配时使用完整 compact authored-preset `<g>` |
-| 自定义数据几何 | `<path>`、`<polygon>`、`<polyline>` |
+| 单一预设不能表达、但封闭形状可组合的对象 | 优先用 `shape_boolean_svg.py` 物化 Merge Shapes 结果 |
+| 图元、预设、Boolean 都不能表达的数据/语义/锁定风格几何 | `<path>`、`<polygon>`、`<polyline>` |
| 数据图表 | 默认 Shape fallback;符合条件时附带 native replacement marker |
**Forbidden — inferred native semantics**: 概念图、流程图和框架图不添加 `data-pptx-replace-with="chart"`;普通关系线不添加 Connector attachment metadata。
@@ -440,7 +442,7 @@ python3 skills/ppt-master/scripts/compact_svg_coordinates.py \
**Reference — not a constraint**: 半圆标签只在“标签从属于当前信息块”是结构信息时使用。颜色、圆角和高度由项目适配;它不是卡片的默认装饰。
-**Forbidden — cover hack**: 不用“全圆角矩形 + 同色覆盖矩形”拼接单侧圆角;需要时直接使用一个可编辑 path。
+**Forbidden — cover hack**: 不把“全圆角矩形 + 同色覆盖矩形”作为两个未合并对象叠放来伪造单侧圆角。需要时优先以封闭的圆角矩形和矩形为 operands,通过 `shape_boolean_svg.py` 物化 Union 结果;只有 Boolean 仍不能忠实表达时才手写可编辑 path。
### 11.2 Nested Card Border
diff --git a/skills/ppt-master/templates/charts/README.md b/skills/ppt-master/templates/charts/README.md
index 521b8cad..b1c335a5 100644
--- a/skills/ppt-master/templates/charts/README.md
+++ b/skills/ppt-master/templates/charts/README.md
@@ -18,10 +18,13 @@ This library is **Shape-first**. Infographics, process diagrams, architecture
diagrams, frameworks, and the default rendering of data charts export as
independently editable PowerPoint shapes:
-- Use ordinary SVG primitives for basic nodes and containers. Thin directional
- relationships use `<line>` / supported open `<path>` geometry with registered
- arrow markers; they remain static editable shapes and do not create node
- attachment or automatic routing.
+- Use ordinary SVG primitives for basic nodes, containers, and straight
+ relationships; they export as editable PowerPoint shapes. A straight
+ directional relationship uses `<line>` with a registered arrow marker.
+- When a bent or curved relationship exactly matches a stock Connector contour,
+ prefer a compact authored `bentConnector*` / `curvedConnector*` preset. It is
+ an unconnected native Connector shape and does not create node attachment or
+ automatic routing.
- Use a stock PowerPoint preset for a solid block arrow, chevron, or standard
flowchart node when it exactly expresses the intended object. A template may
retain the complete compact atomic `<g>` generated by `preset_shape_svg.py`,
@@ -32,13 +35,17 @@ independently editable PowerPoint shapes:
adjustments, or paint changes, regenerate the whole group instead of editing
metadata or paths. PPTX import and `mirror` retain their separate expanded
lossless representation; do not copy that transport form into new templates.
-- Keep custom contours, branded geometry, and data-driven marks as ordinary
- `<path>` / `<polygon>` geometry. They still export as editable DrawingML
- shapes; native preset identity is not required for editability.
-- Do not put authored Connector metadata or endpoint attachment metadata in
- this template library. Existing Connector topology imported from a source
- PPTX belongs to the preserve/mirror round-trip contract, not chart-template
- authoring.
+- When no single preset suffices but closed operands can express the object,
+ materialize the Union / Combine / Fragment / Intersect / Subtract result with
+ `shape_boolean_svg.py` before considering a hand-authored contour.
+- Keep a hand-authored `<path>` / `<polygon>` only for branded, data-defined,
+ locked organic / hand-drawn, or other contours that primitives, an exact
+ preset, and Boolean materialization cannot faithfully express. They still
+ export as editable DrawingML shapes.
+- Authored Connector metadata comes only from `preset_shape_svg.py`; never
+ hand-write endpoint attachment metadata. Existing attached Connector topology
+ imported from a source PPTX belongs to the preserve/mirror round-trip
+ contract, not chart-template authoring.
Data-backed charts retain the separate opt-in replacement route described
below. Conceptual diagrams and frameworks are never labeled as native charts.
diff --git a/skills/ppt-master/templates/charts/mind_map.svg b/skills/ppt-master/templates/charts/mind_map.svg
index 22db1c31..1a186fb4 100644
--- a/skills/ppt-master/templates/charts/mind_map.svg
+++ b/skills/ppt-master/templates/charts/mind_map.svg
@@ -20,15 +20,15 @@
<g id="branch-skeleton" data-pptx-bounds="120 108 1040 489">
<circle cx="640" cy="360" r="112" fill="none" stroke="#6366F1" stroke-width="1.5" stroke-opacity="0.12"/>
<circle cx="640" cy="360" r="160" fill="none" stroke="#6366F1" stroke-width="1.5" stroke-opacity="0.06"/>
- <!-- Main curves: center to branches -->
+ <!-- Main straight relationships: center to branches -->
<!-- Top Right -->
- <path d="M 703,330 C 795,280 880,225 930,195" stroke="#10B981" stroke-width="3" fill="none" stroke-opacity="0.35"/>
+ <line x1="703" y1="330" x2="930" y2="195" stroke="#10B981" stroke-width="3" stroke-opacity="0.35"/>
<!-- Bottom Right -->
- <path d="M 703,390 C 795,440 880,495 930,525" stroke="#F59E0B" stroke-width="3" fill="none" stroke-opacity="0.35"/>
+ <line x1="703" y1="390" x2="930" y2="525" stroke="#F59E0B" stroke-width="3" stroke-opacity="0.35"/>
<!-- Top Left -->
- <path d="M 577,330 C 485,280 400,225 350,195" stroke="#3B82F6" stroke-width="3" fill="none" stroke-opacity="0.35"/>
+ <line x1="577" y1="330" x2="350" y2="195" stroke="#3B82F6" stroke-width="3" stroke-opacity="0.35"/>
<!-- Bottom Left -->
- <path d="M 577,390 C 485,440 400,495 350,525" stroke="#F43F5E" stroke-width="3" fill="none" stroke-opacity="0.35"/>
+ <line x1="577" y1="390" x2="350" y2="525" stroke="#F43F5E" stroke-width="3" stroke-opacity="0.35"/>
<!-- ===== Thin Lines: Branches to Sub-items ===== -->
<!-- Top Right (Product) -->
<line x1="1050" y1="195" x2="1075" y2="156" stroke="#10B981" stroke-width="1.5" stroke-opacity="0.3"/>
diff --git a/skills/ppt-master/templates/design_spec_reference.md b/skills/ppt-master/templates/design_spec_reference.md
index 058a9b42..84e3a575 100644
--- a/skills/ppt-master/templates/design_spec_reference.md
+++ b/skills/ppt-master/templates/design_spec_reference.md
@@ -198,11 +198,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 family or Boolean operation/operand roles>
+- **Native shape suggestion**: <semantic object/result plus candidate preset/Connector family or Boolean operation/operand roles>
- **Motion suggestion**: <communication job plus desired page-entry or reveal relationship/order>
```
-Add `Visualization` and `Images` to a Slide block when it consumes §VII/§VIII rows or uses a page-local visualization. State whether `Visualization` is data-driven when source values determine geometry; this page-level declaration remains authoritative even when no catalog reference fits. Add `Native shape suggestion` only when a literal PowerPoint preset or a compound silhouette/cutout/intersection/fragment may strengthen the page; describe the semantic object/result and candidate family or Boolean operation/operands, not coordinates, paths, or commands. Executor chooses the actual preset, Boolean construction, or ordinary SVG. Add `Motion suggestion` only when a page transition or progressive reveal would strengthen communication; describe its purpose and semantic order/relationship in natural language, not registry keys, Effect Options, durations, group ids, or coverage. It remains a recommendation: Executor owns the exact native behavior and may simplify it or choose no motion unless that would violate an explicit user requirement. Add `Native-ready: yes|no` only for independent data charts or pure text-grid tables. Add `Fact IDs` for sourced claims and `Data class: scenario` for invented demo values. Add `Cover impact` to P01 except on preservation paths; add `Closing impact` only when the final page genuinely resolves the deck. Roster ids/count/order and final content are authoritative. §VIII image patterns are preferred composition references; chart rows only offer page-local references. Executor owns geometry, hierarchy, treatment, and sparse local garnish.
+Add `Visualization` and `Images` to a Slide block when it consumes §VII/§VIII rows or uses a page-local visualization. State whether `Visualization` is data-driven when source values determine geometry; this page-level declaration remains authoritative even when no catalog reference fits. Add `Native shape suggestion` only when a literal PowerPoint preset, a stock bent/curved Connector contour, or a compound silhouette/cutout/intersection/fragment may strengthen the page; describe the semantic object/result and candidate family or Boolean operation/operands, not coordinates, paths, exact preset keys, endpoint/site metadata, or attachment promises. Executor chooses the actual basic primitive, preset, Boolean construction, or necessary freeform. Add `Motion suggestion` only when a page transition or progressive reveal would strengthen communication; describe its purpose and semantic order/relationship in natural language, not registry keys, Effect Options, durations, group ids, or coverage. It remains a recommendation: Executor owns the exact native behavior and may simplify it or choose no motion unless that would violate an explicit user requirement. Add `Native-ready: yes|no` only for independent data charts or pure text-grid tables. Add `Fact IDs` for sourced claims and `Data class: scenario` for invented demo values. Add `Cover impact` to P01 except on preservation paths; add `Closing impact` only when the final page genuinely resolves the deck. Roster ids/count/order and final content are authoritative. §VIII image patterns are preferred composition references; chart rows only offer page-local 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 e028f7e6..673fe3aa 100644
--- a/skills/ppt-master/workflows/generate-pptx.md
+++ b/skills/ppt-master/workflows/generate-pptx.md
@@ -357,7 +357,7 @@ Read references/visual-styles/<resolved-id>.md # one preset id, or each `visu
| `spec_lock.md images` or §VIII contains at least one image/formula row, or an active template carries bundled images | `executor-image.md` + `image-layout-patterns.md` + `image-layout-spec.md` + `svg-image-embedding.md` |
| At least one placed image has `Status: Sourced` | `executor-web-image.md` after the image branch |
| The locked style/current page calls for noncanonical or alpha paint, dash/cap/join, tracking/decoration/outline, gradient/filter/glow/shadow, path/transform/clipping, or another constructed effect | `svg-effects.md` before authoring that value or effect |
-| §IX contains `Native shape suggestion`, or a page calls for a literal PowerPoint stock shape, an explicit Merge Shapes operation, or shape-built dimensional form (cylinder/pedestal, layered diagram, reflection, ground plane) | `native-shape-authoring.md` before selecting or materializing that geometry. This trigger is image-independent: a text-only, data-only, or icon-only page reaches it the same way |
+| §IX contains `Native shape suggestion`, or current page construction calls for a literal PowerPoint stock shape, a stock Connector contour, an explicit Merge Shapes operation or result, or a shape-built dimensional form (cylinder/pedestal, layered diagram, reflection, ground plane), or Executor is about to hand-author a freeform not already required by data geometry or the locked organic / hand-drawn style | `native-shape-authoring.md` before selecting or materializing that geometry. This trigger is image-independent: a text-only, data-only, or icon-only page reaches it the same way |
| All SVG pages and SVG quality gates are complete | `executor-notes.md` before generating speaker notes |
No branch is loaded by analogy. Evaluate these triggers from `spec_lock.md`, §VII/§VIII, the selected style, and the current page plan.
@@ -386,7 +386,7 @@ python3 ${SKILL_DIR}/scripts/svg_editor/server.py <project_path> --live --daemon
**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 precise preset/Boolean result or ordinary SVG. Load and apply [`native-shape-authoring.md`](../references/native-shape-authoring.md) before materializing an adopted native treatment. Diagram relationships remain Shape-first; 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 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. Load and 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.
`template_reuse_scope: mirror|layout` pages MUST start from the complete `page_layouts` SVG, keep inherited visible objects, and preserve root Master/Layout identity plus stable atoms/slots. Strict preserves that reusable contract; under `layout`, the once-loaded Design Spec's `Template Application` may still authorize carrier text/tspan reflow inside unchanged slot bounds. Adaptive uses the current or new Layout key/name already declared by Strategist. If construction proves that fixed atoms or slot topology/bounds must change, stop and return upstream for Strategist to repair the owning plan and lock, validate and read back the affected fragments, then resume; Executor never mutates `spec_lock.md`. `mirror` changes only visible text values while preserving text/tspan topology and attributes. `style` follows the flat paragraph below without structure metadata.