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): require page-local semantic recall

hugohe3be35d98209be
diff --git a/skills/ppt-master/references/native-shape-authoring.md b/skills/ppt-master/references/native-shape-authoring.md
index f99d4901..48ecc733 100644
--- a/skills/ppt-master/references/native-shape-authoring.md
+++ b/skills/ppt-master/references/native-shape-authoring.md
@@ -25,13 +25,16 @@ python3 ${SKILL_DIR}/scripts/preset_shape_svg.py list --grouped
```
The plain `list` command remains a compatibility view of exact registry names;
-it does not replace grouped discovery. For each page, run `recommend` from the
-actual page role and applicable relationship, direction, aspect, text capacity,
-scope, or intent terms, then run `describe <name>` on the serious candidates.
-Those page-local commands supply the full match reasons, intended uses, and
-misuse boundaries omitted from the compact entry index. Recommendation is
-diverse candidate recall, not a whitelist, automatic choice, or shape quota.
-Each page still resolves the final contour through §§1–2.1.
+it does not replace grouped discovery. For each page entering ordinary contour
+selection, run `recommend --limit 6` from the actual page role and applicable
+relationship, direction, aspect, text capacity, scope, or intent terms before
+choosing a contour, then run `describe <name>` on the serious candidates. Grouped
+discovery followed by direct `describe` does not satisfy page-local recall.
+Those commands supply the full match reasons, intended uses, and misuse
+boundaries omitted from the compact entry index. Recommendation is diverse
+candidate recall, not a whitelist, automatic choice, or shape quota; a neutral
+primitive remains valid when it fits best. Each page still resolves the final
+contour through §§1–2.1.
## 1. Contour Selection and Materialization Gate
@@ -110,11 +113,12 @@ Example recall and inspection commands:
```bash
python3 ${SKILL_DIR}/scripts/preset_shape_svg.py recommend \
- --role spine --relationship order --directionality horizontal --aspect wide
+ --role spine --relationship order --directionality horizontal --aspect wide \
+ --limit 6
python3 ${SKILL_DIR}/scripts/preset_shape_svg.py describe chevron
python3 ${SKILL_DIR}/scripts/preset_shape_svg.py recommend \
- --scope flowchart --role node --relationship flow --query decision
+ --scope flowchart --role node --relationship flow --query decision --limit 6
```
**Hard rule — semantic fit, not name association**: a preset name, topic word,
diff --git a/skills/ppt-master/scripts/README.md b/skills/ppt-master/scripts/README.md
index afb37b89..b86d31b9 100644
--- a/skills/ppt-master/scripts/README.md
+++ b/skills/ppt-master/scripts/README.md
@@ -198,12 +198,14 @@ Native preset shape authoring (one or more registry-backed fragments on stdout):
```bash
python3 scripts/preset_shape_svg.py list --grouped
-python3 scripts/preset_shape_svg.py recommend --role spine --relationship order --directionality horizontal --aspect wide
+python3 scripts/preset_shape_svg.py recommend --role spine --relationship order \
+ --directionality horizontal --aspect wide --limit 6
python3 scripts/preset_shape_svg.py describe rightArrow
python3 scripts/preset_shape_svg.py render rightArrow --id process-arrow --frame 120 180 240 96 --fill '#2563EB'
python3 scripts/preset_shape_svg.py render-batch --input - <<'JSON'
[
- {"preset":"chevron","id":"step-1","frame":[120,180,220,96],"fill":"#2563EB","stroke":"none"},
+ {"preset":"chevron","id":"step-1","frame":[120,180,220,96],
+ "fill":"#2563EB","stroke":"none","adjustments":{"adj":"val 42000"}},
{"preset":"leftBrace","id":"group-brace","frame":[380,170,48,240],"fill":"none","stroke":"#111827","stroke_width":3}
]
JSON
@@ -237,7 +239,8 @@ accepts a non-empty JSON array using the snake_case forms of the single-render
options; it validates every item and duplicate id before printing, so one
invalid item produces no partial fragment output. The batch remains
fragment-only input for one current construction, not a page generator or
-project manifest.
+project manifest. `adjustments` is a JSON object keyed by guide name, unlike
+the repeatable single-render `--adjust NAME=FORMULA` option.
Quality check and export rerender the registry instead of relying on a hidden
carrier, preview wrapper, or stored preview fingerprint. PPTX import and
round-trip SVGs deliberately keep their expanded carrier/preview evidence and
diff --git a/skills/ppt-master/scripts/preset_shape_svg.py b/skills/ppt-master/scripts/preset_shape_svg.py
index 4f3cacc8..c7b5d8cf 100644
--- a/skills/ppt-master/scripts/preset_shape_svg.py
+++ b/skills/ppt-master/scripts/preset_shape_svg.py
@@ -256,7 +256,9 @@ def build_parser() -> argparse.ArgumentParser:
metavar="FILE_OR_DASH",
help=(
"UTF-8 JSON array of shape objects; use - to read stdin. "
- "The command prints no fragments when any item is invalid."
+ "Use an 'adjustments' object such as "
+ "{\"adj\": \"val 42000\"}; the command prints no fragments "
+ "when any item is invalid."
),
)
return parser
@@ -453,7 +455,11 @@ def _render_batch_items(items: Sequence[object]) -> list[str]:
raise ValueError(f"{label} must be a JSON object")
unknown = sorted(set(raw_item) - _BATCH_ITEM_FIELDS)
if unknown:
- raise ValueError(f"{label} has unsupported fields: {', '.join(unknown)}")
+ supported = ", ".join(sorted(_BATCH_ITEM_FIELDS))
+ raise ValueError(
+ f"{label} has unsupported fields: {', '.join(unknown)}; "
+ f"supported fields: {supported}"
+ )
missing = [
name for name in ("preset", "id", "frame")
if name not in raw_item
diff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.md
index 7c80e0b3..7136f0e6 100644
--- a/skills/ppt-master/workflows/profiles/quick-generate.md
+++ b/skills/ppt-master/workflows/profiles/quick-generate.md
@@ -562,14 +562,19 @@ This decision is mandatory on every page and cannot be satisfied by the
capability menu, visualization recall, template geometry, or a later check.
**Mandatory — independent per-page geometry move**: after the Structure result
-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 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.
+and any applicable topology resolve, but before choosing any contour, run the
+page-local `recommend --limit 6` defined by
+[`native-shape-authoring.md`](../../references/native-shape-authoring.md) from
+the actual job, then `describe` only serious candidates. Registry discovery
+followed by direct `describe` does not satisfy this recall. Apply §2.1 to the
+transient geometry job, actual content, resolved style, and complete 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. A
+primitive remains valid when it wins this comparison; there is no preset quota.
+Apply the move to both `no` and `yes`; keep the current decision in active
+context and never change the Structure result.
| Deterministic trigger | Additional authority |
|---|---|
@@ -737,7 +742,7 @@ or lock.
- [x] All required source/resource preparation is complete
- [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] The complete native preset registry was read unfiltered before P01; every page entering ordinary contour selection ran job-derived `recommend` before choosing a contour and described only serious candidates
- [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, 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