AI-driven multi-format SVG content generation system. Converts source documents into high-quality SVG pages through multi-role collaboration and exports to PPTX.

Source Document → Create Project → Template Option → Strategist → [Image_Generator] → Executor → Post-processing → Export

[!CAUTION]

🚨 Global Execution Discipline (MANDATORY)

This workflow is a strict serial pipeline. The following rules have the highest priority — violating any one of them constitutes execution failure:

1. SERIAL EXECUTION — Steps MUST be executed in order; the output of each step is the input for the next. Non-BLOCKING adjacent steps may proceed continuously once prerequisites are met, without waiting for the user to say "continue"
2. BLOCKING = HARD STOP — Steps marked ⛔ BLOCKING require a full stop; the AI MUST wait for an explicit user response before proceeding and MUST NOT make any decisions on behalf of the user
3. NO CROSS-PHASE BUNDLING — Cross-phase bundling is FORBIDDEN. (Note: the Eight Confirmations in Step 4 are ⛔ BLOCKING — the AI MUST present recommendations and wait for explicit user confirmation before proceeding. Once the user confirms, all subsequent non-BLOCKING steps — design spec output, SVG generation, speaker notes, and post-processing — may proceed automatically without further user confirmation)
4. GATE BEFORE ENTRY — Each Step has prerequisites (🚧 GATE) listed at the top; these MUST be verified before starting that Step
5. NO SPECULATIVE EXECUTION — "Pre-preparing" content for subsequent Steps is FORBIDDEN (e.g., writing SVG code during the Strategist phase)
6. NO SUB-AGENT SVG GENERATION — Executor Step 6 SVG generation is context-dependent and MUST be completed by the current main agent end-to-end. Delegating page SVG generation to sub-agents is FORBIDDEN
7. SEQUENTIAL PAGE GENERATION ONLY — In Executor Step 6, after the global design context is confirmed, SVG pages MUST be generated sequentially page by page in one continuous pass. Grouped page batches (for example, 5 pages at a time) are FORBIDDEN

[!IMPORTANT]

🌐 Language & Communication Rule

• Response language: Always match the language of the user's input and provided source materials. For example, if the user asks in Chinese, respond in Chinese; if the source material is in English, respond in English.
• Explicit override: If the user explicitly requests a specific language (e.g., "请用英文回答" or "Reply in Chinese"), use that language instead.
• Template format: The

  design_spec.md

  file MUST always follow its original English template structure (section headings, field names), regardless of the conversation language. Content values within the template may be in the user's language.

[!IMPORTANT]

🔌 Compatibility With Generic Coding Skills

• ppt-master

  is a repository-specific workflow skill, not a general application scaffold
• Do NOT create or require

  .worktrees/

  ,

  tests/

  , branch workflows, or other generic engineering structure by default
• If another generic coding skill suggests repository conventions that conflict with this workflow, follow this skill first unless the user explicitly asks otherwise

python3 ${SKILL_DIR}/scripts/project_manager.py init <project_name> --format <format>

ppt169

ppt43

xhs

story

references/canvas-formats.md

python3 ${SKILL_DIR}/scripts/project_manager.py import-sources <project_path> <source_files...> --move

⚠️ MUST use

--move

: All source files (original PDF / MD / images) MUST be moved (not copied) into

sources/

for archiving.

• Markdown files generated in Step 1, original PDFs, original MDs — all must be moved into the project via

  import-sources --move

• Intermediate artifacts (e.g.,

  _files/

  directories) are handled automatically by

  import-sources

• After execution, source files no longer exist at their original location

sources/

layouts_index.json

${SKILL_DIR}/templates/layouts/layouts_index.json

💡 AI Recommendation: Based on your content topic (brief summary), I recommend [specific template / free design] because...

Which approach would you prefer? A) Use an existing template (please specify template name or style preference) B) No template — free design

cp ${SKILL_DIR}/templates/layouts/<template_name>/*.svg <project_path>/templates/
cp ${SKILL_DIR}/templates/layouts/<template_name>/design_spec.md <project_path>/templates/
cp ${SKILL_DIR}/templates/layouts/<template_name>/*.png <project_path>/images/ 2>/dev/null || true
cp ${SKILL_DIR}/templates/layouts/<template_name>/*.jpg <project_path>/images/ 2>/dev/null || true

To create a new global template, read

workflows/create-template.md

Read references/strategist.md

templates/design_spec_reference.md

1. Canvas format
2. Page count range
3. Target audience
4. Style objective
5. Color scheme
6. Icon usage approach
7. Typography plan
8. Image usage approach

python3 ${SKILL_DIR}/scripts/analyze_images.py <project_path>/images

⚠️ Image handling rule: The AI must NEVER directly read, open, or view image files (

.jpg

,

.png

, etc.). All image information must come from the

analyze_images.py

script output or the Design Specification's Image Resource List.

<project_path>/design_spec.md

undefined

• Eight Confirmations completed (user confirmed)
• Design Specification & Content Outline generated
• Next: Auto-proceed to [Image_Generator / Executor] phase

---

Trigger condition: Image approach includes "AI generation". If not triggered, skip directly to Step 6 (Step 6 GATE must still be satisfied).

references/image-generator.md

1. Extract all images with status "pending generation" from the design spec
2. Generate prompt document →

   <project_path>/images/image_prompts.md

3. Generate images (CLI tool recommended):
   bash

   python3 ${SKILL_DIR}/scripts/image_gen.py "prompt" --aspect_ratio 16:9 --image_size 1K -o <project_path>/images

undefined

• Prompt document created
• All images saved to images/

---

Read references/executor-base.md          # REQUIRED: common guidelines
Read references/executor-general.md       # General flexible style
Read references/executor-consultant.md    # Consulting style
Read references/executor-consultant-top.md # Top consulting style (MBB level)

Only need to read executor-base + one style file.

⚠️ Main-agent only rule: SVG generation in Step 6 MUST remain with the current main agent because page design depends on full upstream context (source content, design spec, template mapping, image decisions, and cross-page consistency). Do NOT delegate any slide SVG generation to sub-agents. ⚠️ Generation rhythm rule: After confirming the global design parameters, the Executor MUST generate pages sequentially, one page at a time, while staying in the same continuous main-agent context. Do NOT split Step 6 into grouped page batches such as 5 pages per batch.

• Generate SVG pages sequentially, one page at a time, in one continuous pass →

  <project_path>/svg_output/

• Generate speaker notes →

  <project_path>/notes/total.md

undefined

• All SVGs generated to svg_output/
• Speaker notes generated at notes/total.md

---

svg_output/

notes/total.md

⚠️ The following three sub-steps MUST be executed individually one at a time. Each command must complete and be confirmed successful before running the next. ❌ NEVER put all three commands in a single code block or single shell invocation.

python3 ${SKILL_DIR}/scripts/total_md_split.py <project_path>

python3 ${SKILL_DIR}/scripts/finalize_svg.py <project_path>

python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path> -s final

• Do NOT add extra flags like

  --only

  to the post-processing commands — run them as-is
• Local preview:

  python3 -m http.server -d <project_path>/svg_final 8000