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(native-shapes): separate page geometry from relationship topology

hugohe348f72c106e5f
diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.md
index 15c9b08a..2e093bf2 100644
--- a/skills/ppt-master/references/executor-base.md
+++ b/skills/ppt-master/references/executor-base.md
@@ -165,7 +165,7 @@ Before drawing each page, look up its entry in `page_rhythm` (key format `P<NN>`
- **Generation rhythm**: P01 → first-page gate → uninterrupted remaining pages → final gate, in one context without batches or mid-run checker calls.
- **Fact provenance**: when a §IX page lists `Fact IDs`, resolve each ID from `sources/*.facts.json` and keep the claim/value unchanged. Render a compact source footnote using the source name and a short URL/domain when space permits; when speaker notes are enabled, state the attribution naturally there too. When §IX says `Data class: scenario`, place a visible localized `Scenario data` / `情景数据` label adjacent to the affected KPI/chart and, when notes are enabled, state naturally there that the number is illustrative. Never attach an external fact ID to scenario data or let an unlabeled invented KPI look factual.
- **Default — compose compatible carriers by page job (may use any suitable subset)**: background paint, native shapes, editable text, prepared photos/scenes, transparent illustration slices, decorative lettering, icons, and visualizations may share one page. Use only prepared resources; choose their combination, visual weight, and z-order from the page message and hierarchy. The resolved style controls treatment and emphasis, never carrier eligibility, image source, or the complete native construction vocabulary.
-- **Default — stage each page with the style's composition geometry (may override when another page-fit move is stronger)**: an SVG page is a canvas, not a DOM. Resolve the page-scale move from `spec_lock.md`: a preset uses that selected style's §1 `Composition geometry`; `custom` executes `visual_style_behavior` first, then uses §1 geometry only from exact `visual_style_references` that the behavior assigns a shape or composition job. Other bases contribute only their assigned job, and an unreferenced novel custom follows its behavior alone. Treat every listed move as generative vocabulary rather than a finite menu, then apply [`native-shape-authoring.md`](./native-shape-authoring.md) §2.1's shared semantic-before-neutral gate.
+- **Default — stage each page with the style's composition geometry (may override when another page-fit move is stronger)**: an SVG page is a canvas, not a DOM. Resolve the page-scale move from `spec_lock.md`: a preset uses that selected style's §1 `Composition geometry`; `custom` executes `visual_style_behavior` first, then uses §1 geometry only from exact `visual_style_references` that the behavior assigns a shape or composition job. Other bases contribute only their assigned job, and an unreferenced novel custom follows its behavior alone. Treat every listed move as generative vocabulary rather than a finite menu, then apply [`native-shape-authoring.md`](./native-shape-authoring.md) §2.1's shared exact-fit geometry gate.
- **Default — consider the planned motif direction (may override when another coherent expression better serves the deck)**: when §III `Theme` recommends a cross-page motif or element family, decide whether it earns a continuity job. If adopted, keep its reuse coherent while varying scale, crop, density, position, and content interaction by page role; otherwise adapt or decline it and establish a more fitting style-consistent expression. An explicit user/template motif remains binding.
- **Inherited containers**: preserve meaningful template frames; restyle radius, fill, stroke, and depth from the active Design Spec and `spec_lock.md`. Selected Chart/Table reference adaptation is owned by [`executor-visualization.md`](./executor-visualization.md); preview effects never override project styling or structural roles.
- **Reference — prefer semantic geometry over preset stacks**: for relationships such as ascending, converging, breaking through, or stacking, first compose faithful primitives and exact presets as one page geometry system; use a Boolean only when the contour itself must merge, open, or fragment. Only when neither construction works should one page-specific polygon/path replace a stack of generic arrows.
@@ -195,15 +195,16 @@ no Design Spec construction selection or material inventory gates this choice.
**Mandatory — independent per-page geometry move**: after the Structure result
and any applicable topology resolve, apply
[`native-shape-authoring.md`](./native-shape-authoring.md) §2.1 before writing
-coordinates. It owns the semantic-before-neutral comparison, composition
-lenses, positive fit for a neutral result, running topology signature, and
+coordinates. It owns the exact-fit geometry comparison, composition lenses,
+independent relationship / carrier fit, contour-family / exact-result choice,
+reader effect for a generic or undrawn result, running geometry signature, and
materialization boundary for both `Structure=no` and `Structure=yes`. Keep the
current decision in active context and never change the Structure result.
| Selected result | Authoring form |
|---|---|
| Selected exact non-Connector stock contour | Use ordinary SVG only when the exporter maps it to that same contour; otherwise call `preset_shape_svg.py render` and paste its complete stdout fragment. |
-| Straight relationship / divider / leader | Use `<line>`; add a registered marker only when direction is meaningful. |
+| Straight relationship / divider / leader | Use `<line>`; add a registered marker under [`shared-standards-core.md`](./shared-standards-core.md) §1.1 only when direction is meaningful. |
| 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. |
| Selected text/content boundary needs no filled surface | Use its exact authoring form 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. |
diff --git a/skills/ppt-master/references/native-shape-authoring.md b/skills/ppt-master/references/native-shape-authoring.md
index 5df40ed1..1ef07486 100644
--- a/skills/ppt-master/references/native-shape-authoring.md
+++ b/skills/ppt-master/references/native-shape-authoring.md
@@ -35,13 +35,16 @@ considering authoring syntax. Rectangle, rounded-rectangle, circle, and ellipse
contours are not an earlier visual tier merely because SVG has short primitive
syntax for them. Easier syntax is never the reason to select a contour.
-**Default — semantic native geometry before neutral fallback (may override when
-neutrality itself serves the page)**: Use a relationship-bearing preset or
-compound construction for direction, sequence, membership, hierarchy,
-convergence, reveal, or contrast. Select a neutral contour, grid, or equal-column
-system only when neutrality or equivalence positively serves the page; retain
-that fit in active context. Quick speed, restrained style, readability, equal
-importance, precedent, and shorter syntax are not such a fit.
+**Default — exact page-fit geometry before generic neutrality (may override when
+neutrality itself communicates the page)**: Resolve relationship fit when the
+content carries direction, sequence, membership, hierarchy, convergence, reveal,
+or contrast. Independently resolve page-field / carrier fit from ownership,
+focal hierarchy, boundary strength, and the active deck's edge / opening
+language; `Structure=no` removes only relationship topology. Choose a plain
+primitive, uniform grid, or no drawn carrier only when that lack of inflection
+gives the reader a concrete benefit or avoids a false inference; retain that
+effect in active context. Quick speed, restrained style, readability, equal
+importance, precedent, and shorter syntax alone do not qualify.
**Hard rule — style does not narrow capability**: the active visual system may
weight contour fit and control paint, stroke, texture, density, and recurrence.
@@ -58,7 +61,7 @@ hand-author a freeform merely because an SVG path is convenient.
| Mirror/preserve input already owns native-shape metadata | Keep the existing object and metadata; never reselect its preset. |
| One exact non-Connector stock contour | Use an ordinary SVG primitive only when the exporter maps it to that same contour; otherwise run `preset_shape_svg.py render` and insert its complete stdout fragment. |
| 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. |
-| A straight relationship, divider, or leader | Write `<line>`; use a registered marker only when direction is meaningful. |
+| A straight relationship, divider, or leader | Write `<line>`; use a registered marker under [`shared-standards-core.md`](./shared-standards-core.md) §1.1 only when direction is meaningful. |
| A selected text/content boundary needs no filled surface | Use its exact authoring form with `fill="none"` and a visible stroke; keep its content as independent siblings. |
| Two or more selected native contours 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. |
@@ -74,19 +77,18 @@ rerun the helper whenever its geometry, paint, or filter reference changes.
## 2. Semantic Preset Candidate Guide
-Use the table below as semantic navigation, not a shortlist: match the page's
-visual intent against the complete inventory already loaded above before
-settling on a neutral rectangle / ellipse or a freeform path. Do not let the
-examples, selected style, or authoring convenience hide a more specific
-registered contour. A style's composition examples are generative vocabulary,
-not the set of permitted page moves.
+Use this table as navigation, not a shortlist. Match intent against the loaded
+inventory before selecting a neutral primitive or freeform; examples, style,
+and syntax never hide a more specific contour. Style composition examples
+remain vocabulary, not a menu.
-"Automatic" means the Executor independently applies this semantic decision
-gate before drawing a new object. It does not scan existing SVG, classify
-paths or contours, or upgrade ordinary SVG during export.
+"Automatic" means the Executor applies this gate before drawing. Export never
+scans or upgrades existing geometry.
| Visual intent | Candidate presets | Boundary |
|---|---|---|
+| Page field, outline, or content carrier | `rect`, `round*Rect`, `snip*Rect`, `plaque`, `bevel`, `frame`, `halfFrame`, `corner`, `foldedCorner`, `homePlate` | Match edge, corner, and opening behavior to ownership, hierarchy, or deck language; keep `rect` when no inflection helps. |
+| Grouping or ownership boundary | `leftBrace`, `rightBrace`, `bracePair`, `leftBracket`, `rightBracket`, `bracketPair` | Use a brace / bracket when one visible boundary must collect or assign content without becoming a filled card. |
| 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` | 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. |
@@ -126,18 +128,19 @@ anchors, and any applicable topology under
[`executor-structure.md`](./executor-structure.md) are resolved, but before
writing coordinates, resolve the page-scale geometry move that best carries its
background field, content zoning, focal hierarchy, or reading path. Apply §1's
-semantic-before-neutral default and compare the useful lenses below. Before
-falling back to stacked rectangles / rounded cards or uniform equal columns,
-use a relationship-bearing construction to stage the primary zone. Readability
-of the first workable arrangement does not close this gate.
+exact-fit decision and compare the useful lenses below. Before repeating stacked
+rectangles / rounded cards or uniform equal columns, compare a page-field,
+outline, nesting, or continuity construction and the relevant contour family's
+exact members. Readability of the first workable arrangement does not close this
+gate.
This applies whether the per-page Structure result is `no` or `yes`; it never
creates a decoration requirement.
| Pass | Action | Result |
|---|---|---|
-| Page job | Name the page-scale geometry move, then the geometric jobs already implied by the resolved page: surface, boundary, direction, reveal, focal mark, shared region, or counterweight. | One composition direction and a small set of functional zones; no shape names yet. |
+| Page job | Name the page-scale geometry move and its jobs: surface, boundary, focal mark, shared region, counterweight, or any source-backed direction / reveal. | One composition direction and 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 | Choose each atom's contour from its job and the full native vocabulary, then apply §1's simplest exact materialization; retain the positive page-job fit when the final result is neutral. | Page-fit native atoms without syntax bias. |
+| Select | Choose the contour family, then its exact member from the job, full native vocabulary, and edge / corner / opening behavior; retain the reader effect when the result is generic or undrawn. | Page-fit native atoms without syntax bias. |
| 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. |
@@ -152,12 +155,13 @@ creates a decoration requirement.
| 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. |
-**Default — running deck topology check (may override for literal pages or
+**Default — running deck geometry check (may override for literal pages or
isolated template prototypes)**: After each generated page, retain
-`relationship → topology → contour vocabulary` and compare it before the next.
-Repeat only for the same semantic relationship or deliberate continuity;
-section, equal weight/density, style, and precedent are insufficient. Create no
-artifact or second pass.
+`page job → composition move → contour / edge language`; append `relationship →
+topology` only for `Structure=yes`, then compare before the next. Repeat only for
+the same page job / relationship or deliberate continuity; section, equal
+weight/density, style, and precedent are insufficient. Create no artifact or
+second pass.
**Boolean decision gate**:
diff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.md
index 2432192c..3b2666dc 100644
--- a/skills/ppt-master/workflows/profiles/quick-generate.md
+++ b/skills/ppt-master/workflows/profiles/quick-generate.md
@@ -282,7 +282,7 @@ the roster after the whole-roster check:
- the canvas, visual direction, wording, intended viewing distance, and effective reading mode: choose `presentation` for distance-first projected or recorded viewing, `balanced` for mixed viewing, or `text` for close content-heavy reading. Take the initial body anchor and sanity band from [`canvas-formats.md`](../../references/canvas-formats.md) § "Typography Scale Start" for the resolved canvas—PPT remains reading-mode-driven, while registered/custom non-PPT canvases use their canvas-derived start—then resolve one concrete typography plan for the delivery target defined by [`shared-standards-core.md`](../../references/shared-standards-core.md) §4.1, never from the authoring host's font inventory, with stable size anchors for title, body, annotation, and every other recurring role the roster uses. When content does not fit, preserve its core message and apply only fitting actions the source/profile invariants permit—restructure, shorten, or split; if none is permitted, surface the unresolved fit instead of shrinking a recurring role. Explicit user, template, fidelity-profile, or resolved-style requirements may call for a deliberate exception;
- the semantic color roles actually needed by the roster, each with a concrete active-context color anchor, including background/surface, primary/secondary text, dominant/accent, and status roles as applicable. Honor explicit user, installed template/brand, fidelity-profile source-identity, and resolved-style color semantics before deriving only the missing roles that the active profile permits; decide which roles dominate, support, or remain rare, and preserve sufficient contrast for meaning-bearing text. Pair newly authored color-coded states, categories, or relationships with a label, symbol, line, or geometry cue; when fidelity forbids adding one, preserve the source encoding;
- an ordinary body-content frame and a density judgment for every page, adapted to the canvas and any user / template / style geometry; use `anchor`, `dense`, `breathing`, or an equivalent active-context distinction instead of one uniform fill level;
-- for each page not bound to literal supplied geometry, a primary visual zone and one compact page-scale geometry job tied to its core message—what geometry must organize and which semantic relationship it carries, without naming a preset or encoding form; keep it only in the transient roster for §3's authoring-time move;
+- for each page not bound to literal supplied geometry, a primary visual zone and one compact page-scale geometry job tied to its core message—what geometry must organize, without naming a preset or encoding form; keep it only in the transient roster for §3's authoring-time move;
- for each page, preserve its semantic units, source-stated qualitative relationships, intended entry, and outcome so §3 can make the sole Structure decision before geometry;
- when useful, a transient deck-level visual motif system with an identity or
communication job, a recognizable invariant, and a reuse mode: fixed chrome,
@@ -318,15 +318,14 @@ a floating cutout may use `#A2-01`. Finish assets before SVG per
**Mandatory — whole-roster rhythm check**: During the same active-context
resolution, compare neighbors and section arcs to judge whether chapter entries
-visibly reset, extended same-density runs are intentional, extended same-carrier
-or same-topology runs form an intentional semantic sub-arc, repeated dominant
-geometry carries a continuity job, each section follows a mode-fitting
+visibly reset, extended same-density runs are intentional, extended repetitions
+of one carrier or composition move form an intentional page-job arc, repeated
+dominant geometry carries a continuity job, each section follows a mode-fitting
progression—including framework → explanation/evidence → judgment/action when
it serves the objective—and the final arc resolves the communication objective
before a genuine ending lowers information load. Same section, equal weight or
-density, one style, and prior-page precedent do not establish a semantic
-sub-arc. Repair
-the transient roster, density, and composition choices in place. This is
+density, one style, and prior-page precedent do not establish a page-job arc.
+Repair the transient roster, density, and composition choices in place. This is
judgment, not quota; preserve intentional continuity, legitimately all-`dense`
material, and 1:1/literal order. Add no filler page: a `breathing` page marks a
meaningful pause—chapter transition, standalone emphasis, or SCQA bridge—and
@@ -551,8 +550,9 @@ capability menu, visualization recall, template geometry, or a later check.
and any applicable topology resolve, apply
[`native-shape-authoring.md`](../../references/native-shape-authoring.md) §2.1
to the transient geometry job, actual content, resolved style, and complete
-native vocabulary before writing coordinates. It owns the semantic-before-
-neutral gate, positive fit for a neutral result, running actual-topology
+native vocabulary before writing coordinates. It owns the exact-fit geometry
+gate, independent relationship / carrier fit, contour-family / exact-result
+choice, reader effect for a generic or undrawn result, running actual-geometry
signature, and materialization boundary. Apply it to both `no` and `yes`; keep
the current decision in active context and never change the Structure result.
@@ -715,7 +715,7 @@ or lock.
- [x] The fixed planning-capability batch was read before the roster, and every selected detail source was read
- [x] The complete native preset registry was read unfiltered before P01 and consumed during contour selection
- [x] Every page considered suitable carrier combinations without a coverage quota or single-carrier assumption
-- [x] Every page not bound to literal supplied geometry carried its geometry job into authoring, retained positive fit for any neutral result, and compared its actual topology signature before the next page; repetition served the same semantic relationship or continuity motif
+- [x] Every page not bound to literal supplied geometry carried its geometry job into authoring, resolved each drawn contour from its exact family and job, retained the reader effect for any generic or undrawn result, and compared its actual geometry signature before the next page; repetition served the same page job / relationship or continuity motif
- [x] Image need was decided independently of credentials; any zero-image deck is backed by an explicit no-image requirement or a roster whose visual burden is fully carried by charts / native SVG
- [x] Every `slice_names` output exists after an exit-0 strict-alpha run, and no page whose chosen composition depends on a slice was authored or exported without it
- [x] Every image-bearing page made its one pre-geometry composition decision