终极融合PPT大师 Skill

Ultimate Fusion PPT Master: a Codex skill that fuses editable PPTX generation with magazine-style web deck generation.

Core Pipeline: Request → Output Mode Selection → Source Document → Project Setup → Design Workflow → Generate → Verify → Export/Preview

Output Mode Selection (MANDATORY FIRST STEP)

When the user makes a generic PPT request such as "做一个 PPT", "做个 PPT", "帮我做 PPT", "make a deck", or "turn this into slides", first present the two 终极融合PPT大师 modes and wait for the user's choice. Do not start content conversion, project creation, outline writing, or slide generation before this choice.

Use this concise chooser in the user's language:

我可以做两种 PPT，先选一种：

1. 可编辑 PowerPoint（PPTX）
   适合：正式汇报、咨询/商业报告、培训课件、需要交给别人继续改的文件。
   特点：输出 .pptx，里面是真实文字、形状和图表，PowerPoint 里可继续编辑。

2. 杂志风网页 PPT（HTML）
   适合：线下分享、发布会、个人演讲、demo day、想要强视觉风格的展示。
   特点：输出单个 index.html，横向翻页，电子杂志/电子墨水风格，有 WebGL 背景和动效；不适合多人在 PowerPoint 里继续编辑。

你想做哪一种？如果不确定，我建议正式材料选 1，演讲分享选 2。

Selection rules:

• If the user explicitly asks for editable PPTX, PowerPoint, .pptx, business/report/consulting/training deck, or "可编辑", choose Mode 1: Editable PPTX.
• If the user explicitly asks for magazine style, web PPT, HTML slides, horizontal swipe deck, editorial magazine, e-ink/electronic ink, Swiss Style, 瑞士风, keynote/showcase/demo-day visual deck, choose Mode 2: Magazine Web Deck.
• If the user has already selected "1", "PPTX", "可编辑", "2", "网页", "杂志风", or equivalent, proceed with that mode without asking again.
• If the user asks for both modes, complete them as separate deliverables and keep their project folders separate.

[!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
8. SPEC_LOCK RE-READ PER PAGE — Before generating each SVG page, Executor MUST read_file <project_path>/spec_lock.md. All colors / fonts / icons / images MUST come from this file — no values from memory or invented on the fly. Executor MUST also look up the current page's page_rhythm tag and apply the matching layout discipline (anchor / dense / breathing — see executor-base.md §2.1). This rule exists to resist context-compression drift on long decks and to break the uniform "every page is a card grid" default
9. SVG MUST BE HAND-WRITTEN, NOT SCRIPT-GENERATED — Editable PPTX SVG pages are written by the main agent directly, one page at a time. Do not batch-generate deck SVGs with Python / Node / shell scripts.

[!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

• ultimate-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

[!IMPORTANT]

Local Runtime Rule

• Resolve SKILL_DIR to this skill directory before running scripts.
• Prefer the bundled virtual environment when it exists: ${SKILL_DIR}/.venv/bin/python.
• Otherwise use a Python 3.10+ interpreter (python3.13, python3.12, python3.11, or python3.10). Do not run PPT Master scripts with Python 3.9 or older.
• When command examples below say python3, substitute the resolved Python interpreter.

Main Pipeline Scripts

For complete tool documentation, see ${SKILL_DIR}/scripts/README.md.

Template Index