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
feat(prompts): author native chart markers by default on supported data charts
hugohe3ce8a8850af5f
diff --git a/docs/roadmap.md b/docs/roadmap.mdindex bfbfd3c8..0fc1bb38 100644--- a/docs/roadmap.md+++ b/docs/roadmap.md@@ -116,7 +116,7 @@ PPT Master's main route is "AI generates SVG from scratch → DrawingML", with tPixel-fidelity across the four renderers (PowerPoint / Keynote / LibreOffice / WPS) is the project's spine. Switching the default route to native PowerPoint charts breaks that — the same PPTX renders different chart layouts across renderers. Charts as SVG is **by design**, not a capability gap.-The narrow exception under exploration is an explicit `data-pptx-native` marker for pages that deliberately trade cross-renderer fidelity for PowerPoint-side editability. It is opt-in metadata inside the SVG export path, not a replacement for the default SVG chart/table system.+The narrow exception is the `data-pptx-native` marker: supported data charts carry dormant native-chart metadata at generation time, and exporting with `--native-objects` activates it for users who deliberately trade cross-renderer fidelity for PowerPoint-side editability on those objects. The default export path and the SVG chart/table system are unchanged.### uv as default / required dependencydiff --git a/docs/zh/roadmap.md b/docs/zh/roadmap.mdindex 5a8d0e54..8a2a9c14 100644--- a/docs/zh/roadmap.md+++ b/docs/zh/roadmap.md@@ -116,7 +116,7 @@ PPT Master 主路线是「AI 从零生成 SVG → DrawingML」,整条管线围跨四渲染器(PowerPoint / Keynote / LibreOffice / WPS)的位置保真是项目主轴。把默认路线改成 PowerPoint 原生图表会让「像素级一致性」破功——同一个 PPTX 在不同渲染器里图表会显示不同布局。图表默认用 SVG 是 **by design**,不是能力缺失。-目前探索的窄例外是显式 `data-pptx-native` marker:只有页面主动声明愿意用跨渲染器保真换取 PowerPoint 内可编辑性时,才在 SVG 导出路径里生成原生对象。它是 opt-in 元数据,不替代默认 SVG 图表 / 表格系统。+窄例外是 `data-pptx-native` marker:受支持的数据图表在生成时默认携带休眠的原生图表元数据,导出加 `--native-objects` 才激活——供主动用跨渲染器保真换取 PowerPoint 内可编辑性的用户使用。默认导出路径与 SVG 图表 / 表格系统不变。### uv 作为默认 / 必需依赖diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.mdindex 32eeff5f..248c7d3c 100644--- a/skills/ppt-master/SKILL.md+++ b/skills/ppt-master/SKILL.md@@ -665,12 +665,14 @@ python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path>> layout-tight page must keep every dy-stacked line as its own text frame. The> merge detector is conservative; mixed-layout text falls back to per-line frames.-> **Native table/chart objects** — explicit `data-pptx-native="table|chart"`-> markers are dormant by default. Add `--native-objects` only when the user-> explicitly wants PowerPoint-editable native tables/charts and accepts that-> those objects may render differently across PowerPoint / Keynote /-> LibreOffice / WPS. Without the flag, marked groups export through their SVG-> fallback children like ordinary SVG content.+> **Native table/chart objects** — supported data charts carry+> `data-pptx-native` markers by default (Executor transcribes them at draw+> time; see `references/executor-base.md` §3.2) and the markers stay dormant.+> Add `--native-objects` only when the user explicitly wants+> PowerPoint-editable native tables/charts and accepts that those objects may+> render differently across PowerPoint / Keynote / LibreOffice / WPS. Without+> the flag, marked groups export through their SVG fallback children like+> ordinary SVG content.**Optional animation flags** (page transitions are on by default; per-element entrance is off by default — turn it on only when the user asks for it):- `-t <effect>` — page transition. Default `fade`. Options: `fade` / `push` / `wipe` / `split` / `strips` / `cover` / `random` / `none`.diff --git a/skills/ppt-master/references/executor-base.md b/skills/ppt-master/references/executor-base.mdindex 17f54feb..d17c220b 100644--- a/skills/ppt-master/references/executor-base.md+++ b/skills/ppt-master/references/executor-base.md@@ -171,7 +171,7 @@ Before drawing each page, look up its entry in `page_charts` to decide which cha- **Generation rhythm**: lock global design context first, then generate pages sequentially in one continuous context. No batched groups (e.g., 5 at a time).- **Reference — image-led promotional pages (not a constraint)**: for travel, venue, product-introduction, hospitality, event, real-estate, and brochure-style decks, let images define the page skeleton before placing text. Consult [`image-layout-patterns.md`](image-layout-patterns.md) §Imported Deck Patterns and prefer patterns such as `#74` TOC image-navigation cards, `#75` asymmetric chapter banners, `#77` photo mosaic with a text cell, `#78` ambient banner + evidence photo + text panel, `#79` ribbon-header image cards, and `#80` side hero image + staggered evidence cards before falling back to plain left/right image-text splits.- **Phased batch 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 §3.1 below on every chart page — coordinate calibration is a post-generation step (see [`workflows/verify-charts.md`](../workflows/verify-charts.md)) that depends on these markers.+ 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 §3.1 below on every chart page — coordinate calibration is a post-generation step (see [`workflows/verify-charts.md`](../workflows/verify-charts.md)) that depends on these markers — and **native object metadata** per §3.2 on every eligible data-chart page.2. **Quality Check Gate**: run `python3 scripts/svg_quality_checker.py <project_path>` on `svg_output/`. Any `error` (banned features, viewBox mismatch, spec_lock drift, non-PPT-safe font, etc.) MUST be fixed on the offending page before proceeding — regenerate and re-check. Address `warning`s when straightforward. Do NOT defer to after `finalize_svg.py` — finalize rewrites SVG and masks some violations.3. **Logic Construction Phase**: after SVGs pass the quality check, batch-generate speaker notes for narrative continuity.@@ -218,6 +218,24 @@ grep "chart-plot-area" <project_path>/svg_output/<current_page>.svg- **Reference — prefer semantic shapes over preset stacks (not a constraint)**: when a slide needs to express "ascending / converging / breaking through / stacking" — i.e., a relationship that goes beyond a generic arrow — prefer a single custom `<polygon>` or `<path>` that encodes the semantics geometrically, rather than stacking multiple preset arrows. A converging-tip path or a podium polygon reads faster than three arrows pointing at a label. Examples of this technique appear in many imported corporate decks; see `projects/01_template_import/svg_output/slide_01.svg` shape-158 for a reference (gradient-filled inward-pointing arrow). Do not codify these as templates — they are page-specific; the rule is just "consider polygon before stacking presets."- **Reference — visual depth through restraint (not a constraint)**: layered depth comes from rhythm (flat vs lifted, dense vs spacious), not from shadows everywhere. Shadow typically suits 2-3 genuinely floating elements per page (cards on photos, primary CTA, overlays); keep peer-grid cards, dividers, body containers flat. Reach for typography weight, spacing, accent bars, subtle tints **before** shadow. Full rules in shared-standards.md §6.+### 3.2 Native Object Metadata Marker (MANDATORY on eligible data-chart pages)++> `svg_to_pptx.py --native-objects` converts marked groups into real PowerPoint chart objects with an embedded Excel workbook. Markers stay dormant in the default export — pages render from their SVG children — but a deck without markers can never form native charts. Write the marker at draw time: the data is already in hand, and recovering it later costs a full re-read pass.++**Hard rule**: every data chart whose type appears in the **Supported chart types** list of [shared-standards.md](shared-standards.md) "Native PPTX Table / Chart Markers" (the single authority for the eligible set, marker contract, and JSON schemas) gets `data-pptx-native="chart"` plus a `<metadata data-pptx-native="chart">` JSON child on its top-level `<g>`, transcribing the same data just plotted.++- Chart types absent from that list and conceptual/diagrammatic graphics (process flows, cycles, quadrant cards, timelines, KPI cards) get **no marker** — `svg_quality_checker.py` rejects unsupported marker types.+- Transcribe, don't restyle: `categories` / `series[].values` are the numbers just plotted; `style.colors` carries the series HEX values already used on the page (from `spec_lock.colors`). Omit `x`/`y`/`width`/`height` — the exporter infers the frame from the drawn fallback geometry.+- The marker group's transform stays translate/scale only (no rotate / matrix / skew).+- Visual parity is not a goal: the SVG drawing remains the designed visual; the native chart is a data-editable counterpart with PowerPoint-default styling that users restyle by hand after export. Never simplify the SVG design to match what a native chart could show.+- Data tables MAY carry `data-pptx-native="table"` the same way, but only when the user asks for natively editable tables — table text is already editable as text frames in the default export.++**Per-page verification** — after writing each eligible data-chart page, confirm the marker exists:++```bash+grep "data-pptx-native" <project_path>/svg_output/<current_page>.svg+```+### SVG File Naming ConventionFormat: `<NN>_<page_name>.svg` (two-digit number from 01; name matches the deck's language and the page title in the Design Spec).diff --git a/skills/ppt-master/references/shared-standards.md b/skills/ppt-master/references/shared-standards.mdindex 92c0667e..6b01eb4a 100644--- a/skills/ppt-master/references/shared-standards.md+++ b/skills/ppt-master/references/shared-standards.md@@ -692,11 +692,11 @@ The child `<path>`'s `stroke` becomes the foreground color (the pattern's line c### Native PPTX Table / Chart Markers (Experimental)-Native PowerPoint tables and Excel-backed charts are opt-in only. The default chart/table route remains hand-authored SVG geometry so the deck stays pixel-stable across PowerPoint / Keynote / LibreOffice / WPS.+Native PowerPoint tables and Excel-backed charts activate at export time only. The default chart/table route remains hand-authored SVG geometry so the deck stays pixel-stable across PowerPoint / Keynote / LibreOffice / WPS.-**Hard rule**: Use a native object marker only when editability in PowerPoint matters more than cross-renderer layout fidelity. The marker group supplies both: visible SVG fallback children for browser/live-preview rendering, and JSON metadata for `svg_to_pptx` native export.+**Authoring — markers are standard on supported data charts**: Executor writes the marker at draw time on every data chart whose type falls in the supported set ([executor-base.md §3.2](executor-base.md)), so any deck can later form native charts without regeneration. Table markers are author-optional. The marker group supplies both: visible SVG fallback children for browser/live-preview rendering, and JSON metadata for `svg_to_pptx` native export.-**Default — dormant unless exported with `--native-objects`**: A marker only declares that a group is eligible for native export. Normal `svg_to_pptx.py` runs keep the fallback SVG children. Passing `--native-objects` emits the PowerPoint object and skips the fallback children to avoid duplicates.+**Hard rule — activation is the opt-in, dormant unless exported with `--native-objects`**: A marker only declares that a group is eligible for native export. Normal `svg_to_pptx.py` runs keep the fallback SVG children. Pass `--native-objects` only when editability in PowerPoint matters more than cross-renderer layout fidelity: it emits the PowerPoint object and skips the fallback children to avoid duplicates. Native styling is PowerPoint-default plus the marker's palette colors — visual parity with the SVG drawing is not a goal; users restyle natively exported objects by hand.| Marker | Native output | Required metadata ||---|---|---|