ppt-master

Live Preview Stage

(1) Start/reopen the browser SVG editor when no preview service is running; (2) apply user-submitted annotations after Step 7 export. Executor’s mandatory auto-startup lives in generate-pptx Step 6 — never re-launch a preview that is already running. Editor behavior, lifecycle, ports, and remote access are documented in svg_editor.md.

When to Run

Step 1 — no preview service is running and the user wants to look at the deck or click an element (post-export re-entry in a fresh chat, or the user clicked Exit preview earlier).
Step 2 — Step 7 has produced at least one PPTX and the user signals that annotations should be applied: quoting the browser prompt (Changes saved to svg_output... / 修改已保存到 svg_output...) or saying apply my annotations / apply my edits / 应用注解 / 开始应用.

When not to run: the service is already running → give the URL; a precise chat edit (“change page 3 title to X”) → edit the SVG directly; a full regeneration → main workflow; Step 7 has never run → finish the main pipeline first.

Step 1: Start / reopen the editor

python3 ${SKILL_DIR}/scripts/svg_editor/server.py <project_path> --daemon

Plain mode, no --live (reserved for Step 6). Launch immediately — the user already asked. Report the actual URL from the launch output or <project_path>/live_preview/lock.json, never an inferred 6060; on a remote host add --no-browser and forward the port. Then tell the user, in their language, in one short message:

the editor URL;
Direct edit for deterministic tweaks (wording, color, coordinates, attributes): select an element → change the right-panel controls → preview updates immediately, nothing is written until Apply changes; Ctrl+Z / Undo drops staged edits; re-export stays chat-driven (“re-export” / “重新导出”);
Annotate for changes needing AI judgement or re-layout: select an element → write the instruction (optionally from a quick type such as move / resize / replace image / copy / relayout) → Add annotation → Apply changes → return to chat and say apply my annotations;
to skip the editor, describe the change in chat.

Step 2: Apply submitted annotations

🚧 GATE: <project_path>/exports/ contains at least one *.pptx; otherwise tell the user to finish the main pipeline first.

python3 ${SKILL_DIR}/scripts/check_annotations.py <project_path> — its output lists each pending change as file → element_id → annotation text → content preview; use it directly as the to-do list. If it reports none, tell the user and stop.
For each annotation: edit the targeted element in <project_path>/svg_output/<file> per the text; remove data-edit-target and data-edit-annotation from it; append one annotation_applied JSONL record (ts, file, element_id, original text) to <project_path>/live_preview/annotations.jsonl.
Re-enter generate-pptx Step 7.2, wait for its success criterion, then run Step 7.3; rerun Step 7.1 only when speaker notes changed.
Tell the user, in their language: annotations applied, new PPTX exported, preview still running (refresh or reselect the page if the browser shows the old slide).
More annotations → repeat from 1; “done” or “stop preview” → end.

This site is open source. Improve this page.