{"id":"246f3b79-765f-499e-97ac-260dcf8b49fb","entityType":"agent","slug":"clawhub-vincentlau2046-sudo-pptx-master","name":"Pptx Master V1.2.3 20260507","canonicalUrl":"https://www.xpersona.co/agent/clawhub-vincentlau2046-sudo-pptx-master","canonicalPath":"/agent/clawhub-vincentlau2046-sudo-pptx-master","generatedAt":"2026-10-10T10:43:16.412Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T07:49:46.914Z","emptyReason":null},"description":"专业级 AI 驱动 SVG 内容生成系统。支持 PDF/DOCX/URL/Markdown 转换为原生可编辑的 PPTX。 多角色协作流程，输出高质量演示文稿，适合财报分析、技术汇报、商业演示等专业场景。 版本 v1.2.3，新增 XML 实体自动转义（修复孤立 & 符号导致解析失败），支持 HUAWEI、red... Skill: Pptx Master V1.2.3 20260507 Owner: vincentlau2046-sudo Summary: 专业级 AI 驱动 SVG 内容生成系统。支持 PDF/DOCX/URL/Markdown 转换为原生可编辑的 PPTX。 多角色协作流程，输出高质量演示文稿，适合财报分析、技术汇报、商业演示等专业场景。 版本 v1.2.3，新增 XML 实体自动转义（修复孤立 & 符号导致解析失败），支持 HUAWEI、red... Tags: latest:1.2.3, ppt:1.0.2, presentation:1.0.2 Version history: v1.2.3 | 2026-05-07T07:20:42.569Z | user XML实体自动转义 v1.0.2 | 2026-04-24T16:23:36.705Z | user ClawHub适配版本，基于github开源ppt-mas","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.6K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s177qxxtwn13trxmgd54c7a6wh83h7rc:pptx-master","sourceUrl":"https://clawhub.ai/vincentlau2046-sudo/pptx-master","homepage":"https://clawhub.ai/vincentlau2046-sudo/skills/pptx-master","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/vincentlau2046-sudo/pptx-master","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/vincentlau2046-sudo/skills/pptx-master","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":64,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"专业级 AI 驱动 SVG 内容生成系统。支持 PDF/DOCX/URL/Markdown 转换为原生可编辑的 PPTX。 多角色协作流程，输出高质量演示文稿，适合财报分析、技术汇报、商业演示等专业场景。 版本 v1.2.3，新增 XML 实体自动转义（修复孤立 & 符号导致解析失败），支持 HUAWEI、red..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T07:49:46.914Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T07:49:46.914Z","emptyReason":null},"stars":null,"forks":null,"downloads":1580,"packageName":null,"latestVersion":"1.2.3","tractionLabel":"1.6K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T07:49:46.776Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T07:49:46.914Z","lastCrawledAt":"2026-10-10T07:49:46.776Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T07:49:46.776Z","lastVerifiedAt":null,"highlights":[{"version":"1.2.3","createdAt":"2026-05-07T07:20:42.569Z","changelog":"XML实体自动转义","fileCount":258,"zipByteSize":611559},{"version":"1.0.2","createdAt":"2026-04-24T16:23:36.705Z","changelog":"ClawHub适配版本，基于github开源ppt-master，新增HUAWEI和red grey两个layout模板","fileCount":97,"zipByteSize":299196},{"version":"1.0.1","createdAt":"2026-04-24T16:21:17.552Z","changelog":"ClawHub适配版本","fileCount":97,"zipByteSize":299196}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s177qxxtwn13trxmgd54c7a6wh83h7rc:pptx-master","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-vincentlau2046-sudo-pptx-master/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-vincentlau2046-sudo-pptx-master/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-vincentlau2046-sudo-pptx-master/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-vincentlau2046-sudo-pptx-master/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-vincentlau2046-sudo-pptx-master/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-vincentlau2046-sudo-pptx-master/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T10:43:16.408Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-vincentlau2046-sudo-pptx-master/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-vincentlau2046-sudo-pptx-master/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-vincentlau2046-sudo-pptx-master/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-vincentlau2046-sudo-pptx-master/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-10T07:49:46.914Z","emptyReason":null},"readme":"Skill: Pptx Master V1.2.3 20260507\n\nOwner: vincentlau2046-sudo\n\nSummary: 专业级 AI 驱动 SVG 内容生成系统。支持 PDF/DOCX/URL/Markdown 转换为原生可编辑的 PPTX。 多角色协作流程，输出高质量演示文稿，适合财报分析、技术汇报、商业演示等专业场景。 版本 v1.2.3，新增 XML 实体自动转义（修复孤立 & 符号导致解析失败），支持 HUAWEI、red...\n\nTags: latest:1.2.3, ppt:1.0.2, presentation:1.0.2\n\nVersion history:\n\nv1.2.3 | 2026-05-07T07:20:42.569Z | user\n\nXML实体自动转义\n\nv1.0.2 | 2026-04-24T16:23:36.705Z | user\n\nClawHub适配版本，基于github开源ppt-master，新增HUAWEI和red grey两个layout模板\n\nv1.0.1 | 2026-04-24T16:21:17.552Z | user\n\nClawHub适配版本\n\nArchive index:\n\nArchive v1.2.3: 258 files, 611559 bytes\n\nFiles: CHANGELOG.md (4207b), README.md (3830b), references/canvas-formats.md (2902b), references/executor-base.md (11829b), references/executor-consultant-top.md (10349b), references/executor-consultant.md (7180b), references/executor-general.md (6070b), references/image-generator.md (18038b), references/image-layout-spec.md (5620b), references/shared-standards.md (18394b), references/strategist.md (18574b), references/svg-image-embedding.md (6089b), references/template-designer.md (8483b), RESOURCES.md (4297b), scripts/analyze_images.py (8226b), scripts/batch_validate.py (10419b), scripts/config.py (16611b), scripts/doc_to_md.py (7467b), scripts/docs/conversion.md (2206b), scripts/docs/image.md (2861b), scripts/docs/project.md (2627b), scripts/docs/svg-pipeline.md (4601b), scripts/docs/troubleshooting.md (1388b), scripts/error_helper.py (16161b), scripts/finalize_svg.py (13052b), scripts/gemini_watermark_remover.py (6825b), scripts/generate_examples_index.py (8311b), scripts/image_backends/__init__.py (57b), scripts/image_backends/backend_bfl.py (5784b), scripts/image_backends/backend_common.py (7366b), scripts/image_backends/backend_fal.py (4198b), scripts/image_backends/backend_gemini.py (8808b), scripts/image_backends/backend_ideogram.py (4875b), scripts/image_backends/backend_openai.py (8135b), scripts/image_backends/backend_qwen.py (6333b), scripts/image_backends/backend_replicate.py (5908b), scripts/image_backends/backend_siliconflow.py (5718b), scripts/image_backends/backend_stability.py (4889b), scripts/image_backends/backend_volcengine.py (6004b), scripts/image_backends/backend_zhipu.py (5911b), scripts/image_gen.py (13130b), scripts/pdf_to_md.py (26621b), scripts/pptx_animations.py (8269b), scripts/pptx_template_import.py (18066b), scripts/project_manager.py (24802b), scripts/project_utils.py (15378b), scripts/README.md (3296b), scripts/rotate_images.py (20980b), scripts/svg_content_checker.py (18598b), scripts/svg_finalize/__init__.py (88b), scripts/svg_finalize/crop_images.py (10973b), scripts/svg_finalize/embed_icons.py (10938b), scripts/svg_finalize/embed_images.py (6370b), scripts/svg_finalize/fix_image_aspect.py (13656b), scripts/svg_finalize/flatten_tspan.py (16205b), scripts/svg_finalize/svg_rect_to_path.py (10698b), scripts/svg_position_calculator.py (54811b), scripts/svg_quality_checker.py (18782b), scripts/svg_repair_coordinator.py (15822b), scripts/svg_to_pptx.py (449b), scripts/svg_to_pptx/__init__.py (465b), scripts/svg_to_pptx/drawingml_context.py (3812b), scripts/svg_to_pptx/drawingml_converter.py (7655b), scripts/svg_to_pptx/drawingml_elements.py (29068b), scripts/svg_to_pptx/drawingml_paths.py (13801b), scripts/svg_to_pptx/drawingml_styles.py (11889b), scripts/svg_to_pptx/drawingml_utils.py (10052b), scripts/svg_to_pptx/pptx_builder.py (17409b), scripts/svg_to_pptx/pptx_cli.py (7591b), scripts/svg_to_pptx/pptx_dimensions.py (4188b), scripts/svg_to_pptx/pptx_discovery.py (2938b), scripts/svg_to_pptx/pptx_media.py (2418b), scripts/svg_to_pptx/pptx_notes.py (4625b), scripts/svg_to_pptx/pptx_slide_xml.py (4736b), scripts/total_md_split.py (10941b), scripts/update_repo.py (4289b), scripts/web_to_md.cjs (27305b), scripts/web_to_md.py (25871b), skill-card.md (2756b), SKILL.md (17217b)\n\nFile v1.2.3:SKILL.md\n\n---\nname: pptx-master\ndescription: >-\n 专业级 AI 驱动 SVG 内容生成系统。支持 PDF/DOCX/URL/Markdown 转换为原生可编辑的 PPTX。\n 多角色协作流程，输出高质量演示文稿，适合财报分析、技术汇报、商业演示等专业场景。\n 版本 v1.2.3，新增 XML 实体自动转义（修复孤立 & 符号导致解析失败），支持 HUAWEI、red grey 等新模板。\n\nread_when:\n - 用户说\"生成 PPT\"、\"做 PPT\"、\"制作演示文稿\"、\"做个 PPT\"\n - 用户提供 PDF 文件要求转换成 PPT\n - 用户提供 DOCX/Word 文档要求转换成 PPT\n - 用户提供 URL 要求提取内容生成 PPT\n - 用户需要专业演示文稿（财报、技术汇报、商业演示）\n - 用户明确要求\"原生可编辑\"、\"可修改\"的 PPT\n - 用户提到\"pptx-master\"、\"ppt pro\"\n\nmetadata:\n openclaw:\n emoji: 📊\n priority: high\n category: content-generation\n tags:\n - ppt\n - presentation\n - slides\n - 演示文稿\n conflicts_with:\n - ppt-video\n - fireworks-tech-graph\n clawhub:\n license: MIT-0\n tags: latest=1.2.3\n---\n\n# PPT Master Skill\n\n> AI-driven multi-format SVG content generation system. Converts source documents into high-quality SVG pages through multi-role collaboration and exports to PPTX.\n\n**Core Pipeline**: `Source Document → Create Project → Template Option → Strategist → [Image_Generator] → Executor → Post-processing → Export`\n\n> [!CAUTION]\n> ## 🚨 Global Execution Discipline (MANDATORY)\n>\n> **This workflow is a strict serial pipeline. The following rules have the highest priority — violating any one of them constitutes execution failure:**\n>\n> 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\"\n> 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\n> 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)\n> 4. **GATE BEFORE ENTRY** — Each Step has prerequisites (🚧 GATE) listed at the top; these MUST be verified before starting that Step\n> 5. **NO SPECULATIVE EXECUTION** — \"Pre-preparing\" content for subsequent Steps is FORBIDDEN (e.g., writing SVG code during the Strategist phase)\n> 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\n> 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\n\n> [!IMPORTANT]\n> ## 🌐 Language & Communication Rule\n>\n> - **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.\n> - **Explicit override**: If the user explicitly requests a specific language (e.g., \"请用英文回答\" or \"Reply in Chinese\"), use that language instead.\n> - **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.\n\n> [!IMPORTANT]\n> ## 🔌 Compatibility With Generic Coding Skills\n>\n> - `pptx-master` is a repository-specific workflow skill, not a general application scaffold\n> - Do NOT create or require `.worktrees/`, `tests/`, branch workflows, or other generic engineering structure by default\n> - If another generic coding skill suggests repository conventions that conflict with this workflow, follow this skill first unless the user explicitly asks otherwise\n\n## Main Pipeline Scripts\n\n| Script | Purpose |\n|--------|---------|\n| `${SKILL_DIR}/scripts/pdf_to_md.py` | PDF to Markdown |\n| `${SKILL_DIR}/scripts/doc_to_md.py` | Documents to Markdown via Pandoc (DOCX, EPUB, HTML, LaTeX, RST, etc.) |\n| `${SKILL_DIR}/scripts/web_to_md.py` | Web page to Markdown |\n| `${SKILL_DIR}/scripts/web_to_md.cjs` | WeChat / high-security sites to Markdown |\n| `${SKILL_DIR}/scripts/project_manager.py` | Project init / validate / manage |\n| `${SKILL_DIR}/scripts/analyze_images.py` | Image analysis |\n| `${SKILL_DIR}/scripts/image_gen.py` | AI image generation (multi-provider) |\n| `${SKILL_DIR}/scripts/svg_quality_checker.py` | SVG quality check |\n| `${SKILL_DIR}/scripts/total_md_split.py` | Speaker notes splitting |\n| `${SKILL_DIR}/scripts/finalize_svg.py` | SVG post-processing (unified entry) |\n| `${SKILL_DIR}/scripts/svg_to_pptx.py` | Export to PPTX |\n\nFor complete tool documentation, see `${SKILL_DIR}/scripts/README.md`.\n\n## Template Index\n\n| Index | Path | Purpose |\n|-------|------|---------|\n| Layout templates | `${SKILL_DIR}/templates/layouts/layouts_index.json` | Query available page layout templates |\n| Chart templates | `${SKILL_DIR}/templates/charts/charts_index.json` | Query available chart SVG templates |\n| Icon library | `${SKILL_DIR}/templates/icons/` | Search icons on demand: `ls templates/icons// \\| grep ` (libraries: `chunk/`, `tabler-filled/`, `tabler-outline/`) |\n\n## Standalone Workflows\n\n| Workflow | Path | Purpose |\n|----------|------|---------|\n| `create-template` | `workflows/create-template.md` | Standalone template creation workflow |\n\n---\n\n## Workflow\n\n### Step 1: Source Content Processing\n\n🚧 **GATE**: User has provided source material (PDF / DOCX / EPUB / URL / Markdown file / text description / conversation content — any form is acceptable).\n\nWhen the user provides non-Markdown content, convert immediately:\n\n| User Provides | Command |\n|---------------|---------|\n| PDF file | `python3 ${SKILL_DIR}/scripts/pdf_to_md.py ` |\n| DOCX / Word / Office document | `python3 ${SKILL_DIR}/scripts/doc_to_md.py ` |\n| EPUB / HTML / LaTeX / RST / other | `python3 ${SKILL_DIR}/scripts/doc_to_md.py ` |\n| Web link | `python3 ${SKILL_DIR}/scripts/web_to_md.py ` |\n| WeChat / high-security site | `node ${SKILL_DIR}/scripts/web_to_md.cjs ` |\n| Markdown | Read directly |\n\n**✅ Checkpoint — Confirm source content is ready, proceed to Step 2.**\n\n---\n\n### Step 2: Project Initialization\n\n🚧 **GATE**: Step 1 complete; source content is ready (Markdown file, user-provided text, or requirements described in conversation are all valid).\n\n```bash\npython3 ${SKILL_DIR}/scripts/project_manager.py init --format \n```\n\nFormat options: `ppt169` (default), `ppt43`, `xhs`, `story`, etc. For the full format list, see `references/canvas-formats.md`.\n\nImport source content (choose based on the situation):\n\n| Situation | Action |\n|-----------|--------|\n| Has source files (PDF/MD/etc.) | `python3 ${SKILL_DIR}/scripts/project_manager.py import-sources --move` |\n| User provided text directly in conversation | No import needed — content is already in conversation context; subsequent steps can reference it directly |\n\n> ⚠️ **MUST use `--copy`**: All source files (original PDF / MD / images) MUST be **copied** (not moved) into `sources/` for archiving.\n> - Markdown files generated in Step 1, original PDFs, original MDs — **all** must be copied into the project via `import-sources --copy`\n> - Intermediate artifacts (e.g., `_files/` directories) are handled automatically by `import-sources`\n> - Original source files remain at their original location after copying\n\n**✅ Checkpoint — Confirm project structure created successfully, `sources/` contains all source files, converted materials are ready. Proceed to Step 3.**\n\n---\n\n### Step 3: Template Selection\n\n🚧 **GATE**: Step 2 complete; project directory structure is ready.\n\n⛔ **BLOCKING**: If the user has not yet clearly expressed whether to use a template, you MUST present options and **wait for an explicit user response** before proceeding. If the user has previously stated \"no template\" or specified a particular template, skip this prompt and proceed directly.\n\n**⚡ Early-exit**: If the user has already stated \"no template\" / \"不使用模板\" / \"自由设计\" (or equivalent) at any prior point in the conversation, **do NOT query `layouts_index.json`** — skip directly to Step 4. This avoids unnecessary token consumption.\n\n**Template recommendation flow** (only when the user has NOT yet decided):\nQuery `${SKILL_DIR}/templates/layouts/layouts_index.json` to list available templates and their style descriptions. Note: New templates include HUAWEI and red grey layouts.\n**When presenting options, you MUST provide a professional recommendation based on the current PPT topic and content** (recommend a specific template or free design, with reasoning), then ask the user:\n\n> 💡 **AI Recommendation**: Based on your content topic (brief summary), I recommend **[specific template / free design]** because...\n>\n> Which approach would you prefer?\n> **A) Use an existing template** (please specify template name or style preference - note: new options include HUAWEI and red grey templates)\n> **B) No template** — free design\n\nAfter the user confirms option A, copy template files to the project directory:\n```bash\ncp ${SKILL_DIR}/templates/layouts//*.svg /templates/\ncp ${SKILL_DIR}/templates/layouts//design_spec.md /templates/\ncp ${SKILL_DIR}/templates/layouts//*.png /images/ 2>/dev/null || true\ncp ${SKILL_DIR}/templates/layouts//*.jpg /images/ 2>/dev/null || true\n```\n\nAfter the user confirms option B, proceed directly to Step 4.\n\n> To create a new global template, read `workflows/create-template.md`\n\n**✅ Checkpoint — User has responded with template selection, template files copied (if option A). Proceed to Step 4.**\n\n---\n\n### Step 4: Strategist Phase (MANDATORY — cannot be skipped)\n\n🚧 **GATE**: Step 3 complete; user has confirmed template selection.\n\nFirst, read the role definition:\n```\nRead references/strategist.md\n```\n\n**Must complete the Eight Confirmations** (refer to `templates/design_spec_reference.md` for the template structure):\n\n⛔ **BLOCKING**: The Eight Confirmations MUST be presented to the user as a bundled set of recommendations, and you MUST **wait for the user to confirm or modify** before outputting the Design Specification & Content Outline. This is one of only two core confirmation points in the workflow (the other is template selection). Once confirmed, all subsequent script execution and slide generation should proceed fully automatically.\n\n1. Canvas format\n2. Page count range\n3. Target audience\n4. Style objective\n5. Color scheme\n6. Icon usage approach\n7. Typography plan\n8. Image usage approach\n\nIf the user has provided images, run the analysis script **before outputting the design spec** (do NOT directly read/open image files — use the script output only):\n```bash\npython3 ${SKILL_DIR}/scripts/analyze_images.py /images\n```\n\n> ⚠️ **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.\n\n**Output**: `/design_spec.md`\n\n**✅ Checkpoint — Phase deliverables complete, auto-proceed to next step**:\n```markdown\n## ✅ Strategist Phase Complete\n- [x] Eight Confirmations completed (user confirmed)\n- [x] Design Specification & Content Outline generated\n- [ ] **Next**: Auto-proceed to [Image_Generator / Executor] phase\n```\n\n---\n\n### Step 5: Image_Generator Phase (Conditional)\n\n🚧 **GATE**: Step 4 complete; Design Specification & Content Outline generated and user confirmed.\n\n> **Trigger condition**: Image approach includes \"AI generation\". If not triggered, skip directly to Step 6 (Step 6 GATE must still be satisfied).\n\nRead `references/image-generator.md`\n\n1. Extract all images with status \"pending generation\" from the design spec\n2. Generate prompt document → `/images/image_prompts.md`\n3. Generate images (CLI tool recommended):\n ```bash\n python3 ${SKILL_DIR}/scripts/image_gen.py \"prompt\" --aspect_ratio 16:9 --image_size 1K -o /images\n ```\n\n**✅ Checkpoint — Confirm all images are ready, proceed to Step 6**:\n```markdown\n## ✅ Image_Generator Phase Complete\n- [x] Prompt document created\n- [x] All images saved to images/\n```\n\n---\n\n### Step 6: Executor Phase\n\n🚧 **GATE**: Step 4 (and Step 5 if triggered) complete; all prerequisite deliverables are ready.\n\nRead the role definition based on the selected style:\n```\nRead references/executor-base.md # REQUIRED: common guidelines\nRead references/executor-general.md # General flexible style\nRead references/executor-consultant.md # Consulting style\nRead references/executor-consultant-top.md # Top consulting style (MBB level)\n```\n\n> Only need to read executor-base + one style file.\n\n**Design Parameter Confirmation (Mandatory)**: Before generating the first SVG, the Executor MUST review and output key design parameters from the Design Specification (canvas dimensions, color scheme, font plan, body font size) to ensure spec adherence. See executor-base.md Section 2 for details.\n\n> ⚠️ **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.\n> ⚠️ **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.\n\n**Visual Construction Phase**:\n- Generate SVG pages sequentially, one page at a time, in one continuous pass → `/svg_output/`\n\n**Logic Construction Phase**:\n- Generate speaker notes → `/notes/total.md`\n\n**✅ Checkpoint — Confirm all SVGs and notes are fully generated. Proceed directly to Step 7 post-processing**:\n```markdown\n## ✅ Executor Phase Complete\n- [x] All SVGs generated to svg_output/\n- [x] Speaker notes generated at notes/total.md\n```\n\n---\n\n### Step 7: Post-processing & Export\n\n🚧 **GATE**: Step 6 complete; all SVGs generated to `svg_output/`; speaker notes `notes/total.md` generated.\n\n> ⚠️ 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.\n> ❌ **NEVER** put all three commands in a single code block or single shell invocation.\n\n**Step 7.1** — Split speaker notes:\n```bash\npython3 ${SKILL_DIR}/scripts/total_md_split.py \n```\n\n**Step 7.2** — SVG post-processing (icon embedding / image crop & embed / text flattening / rounded rect to path):\n```bash\npython3 ${SKILL_DIR}/scripts/finalize_svg.py \n```\n\n**Step 7.3** — Export PPTX (embeds speaker notes by default):\n```bash\npython3 ${SKILL_DIR}/scripts/svg_to_pptx.py -s final\n# Default: generates two files — native shapes (.pptx) + SVG reference (_svg.pptx)\n# Use --only native to skip SVG reference version\n# Use --only legacy to only generate SVG image version\n```\n\n> ❌ **NEVER** use `cp` as a substitute for `finalize_svg.py` — it performs multiple critical processing steps\n> ❌ **NEVER** export directly from `svg_output/` — MUST use `-s final` to export from `svg_final/`\n> ❌ **NEVER** add extra flags like `--only`\n\n---\n\n## Role Switching Protocol\n\nBefore switching roles, you **MUST first read** the corresponding reference file — skipping is FORBIDDEN. Output marker:\n\n```markdown\n## [Role Switch: ]\n📖 Reading role definition: references/.md\n📋 Current task: \n```\n\n---\n\n## Reference Resources\n\n| Resource | Path |\n|----------|------|\n| Shared technical constraints | `references/shared-standards.md` |\n| Canvas format specification | `references/canvas-formats.md` |\n| Image layout specification | `references/image-layout-spec.md` |\n| SVG image embedding | `references/svg-image-embedding.md` |\n\n---\n\n## Notes\n\n- Do NOT add extra flags like `--only` to the post-processing commands — run them as-is\n- Local preview: `python3 -m http.server -d /svg_final 8000`\n\nFile v1.2.3:README.md\n\n# PPT Master\n\nAI-driven multi-format SVG content generation system for professional presentations.\n\n## Version History\n\n### v1.2.1 (2026-04-19) - XML Validation Enhancement\n\n**Fixed:**\n- **SVG Content Checker** now validates XML syntax before content analysis\n- Detects mismatched tags (e.g., `...`)\n- Catches malformed SVG that would cause rendering failures\n\n**Technical Details:**\n- Added `xml.etree.ElementTree.fromstring()` validation in `_check_content_elements()`\n- XML parse errors now block the workflow with clear error messages\n- Prevents false-positive \"passes\" on malformed SVG files\n\n**Issue Resolved:**\n- Page 7 of AI Weekly Report PPT was blank due to XML tag mismatch\n- Root cause: `` closed with `` instead of ``\n- Old checker missed it because it only counted string occurrences\n\n---\n\n### v1.2.0 (2026-04-18) - Content Review & Auto-Repair\n\n**Added:**\n- **SVG Content Checker** (`scripts/svg_content_checker.py`)\n - Blank page detection (text elements < 2 AND file size < 500 bytes)\n - Content density scoring (0-100%)\n - Design consistency checking (colors, fonts)\n - Structure completeness evaluation\n- **SVG Repair Coordinator** (`scripts/svg_repair_coordinator.py`)\n - Automatic repair workflow\n - Regeneration prompt generation for blank pages\n - Fallback to placeholder pages when repair fails\n- **Step 6.5** in workflow: Content Review & Auto-Repair\n - Automatic check after SVG generation\n - Non-blocking: warnings allow continuation\n - Blocking: blank pages trigger repair workflow\n\n**Changed:**\n- `SKILL.md`: Added Step 6.5 between SVG generation and post-processing\n- Tool list: Added svg_content_checker.py and svg_repair_coordinator.py\n\n**Use Case:**\n- Automatically detect blank pages before PPTX export\n- Generate repair prompts for manual regeneration\n- Ensure presentation quality before delivery\n\n---\n\n### v1.1.1 (2026-04-11) - Huawei Template Integration\n\n**Added:**\n- Huawei Technologies brand template (`华为技术`)\n- New `enterprise` quick lookup category in template index\n- Template count updated to 21\n\n**Changed:**\n- `layouts_index.json`: Added Huawei template to brand category and technology/enterprise lookups\n- `README.md`: Updated template index with Huawei template details\n\n**Use Case:**\n- Enterprise reports, solution showcases, annual reports, B2B client communication\n- Minimalist tech style with Huawei red accents and professional gray tones\n\n---\n\n### v1.1.0 (2026-04-09) - Source File Handling Update\n\n**Changed:**\n- Source files are now **copied** (not moved) to `sources/` directory by default\n- Original files are preserved at their source location\n- Use `--move` flag if you want to move files instead of copying\n\n**Previous behavior (v1.0.x):**\n- Source files were moved to `sources/`, removing them from original location\n\n**Rationale:**\n- Safer default behavior - originals are preserved\n- Users can still opt-in to move behavior with `--move` flag\n- Reduces risk of accidental data loss\n\n---\n\n### v1.0.0 (2026-04-08) - Initial Release\n\n**Features:**\n- Multi-format input support (PDF, DOCX, EPUB, HTML, URL, Markdown)\n- Professional SVG generation with design system\n- Template-based and free-design modes\n- Eight Confirmations design specification\n- PPTX export with speaker notes\n- Icon embedding and image processing\n\n---\n\n## Usage\n\n```bash\n# Initialize project\npython3 scripts/project_manager.py init --format ppt169\n\n# Import source files (default: copy, preserve originals)\npython3 scripts/project_manager.py import-sources \n\n# Import source files (move mode - remove originals)\npython3 scripts/project_manager.py import-sources --move\n\n# Generate PPTX\npython3 scripts/svg_to_pptx.py -s final\n```\n\n## License\n\nMIT\n\nFile v1.2.3:scripts/README.md\n\n# PPT Master Toolset\n\nThis directory contains user-facing scripts for conversion, project setup, SVG processing, export, and image generation.\n\n## Directory Layout\n\n- Top-level `scripts/`: runnable entry scripts\n- `scripts/image_backends/`: internal provider implementations used by `image_gen.py`\n- `scripts/svg_finalize/`: internal post-processing helpers used by `finalize_svg.py`\n- `scripts/docs/`: topic-focused script documentation\n- `scripts/assets/`: static assets consumed by scripts\n\n## Quick Start\n\nTypical end-to-end workflow:\n\n```bash\npython3 scripts/pdf_to_md.py \npython3 scripts/project_manager.py init --format ppt169\npython3 scripts/project_manager.py import-sources --move\npython3 scripts/total_md_split.py \npython3 scripts/finalize_svg.py \npython3 scripts/svg_to_pptx.py -s final\n```\n\nRepository update:\n\n```bash\npython3 scripts/update_repo.py\n```\n\n## Script Index\n\n| Area | Primary scripts | Documentation |\n|------|-----------------|---------------|\n| Conversion | `pdf_to_md.py`, `doc_to_md.py`, `web_to_md.py`, `web_to_md.cjs` | [docs/conversion.md](./docs/conversion.md) |\n| Project management | `project_manager.py`, `batch_validate.py`, `generate_examples_index.py`, `error_helper.py`, `pptx_template_import.py` | [docs/project.md](./docs/project.md) |\n| SVG pipeline | `finalize_svg.py`, `svg_to_pptx.py`, `total_md_split.py`, `svg_quality_checker.py` | [docs/svg-pipeline.md](./docs/svg-pipeline.md) |\n| Image tools | `image_gen.py`, `analyze_images.py`, `gemini_watermark_remover.py` | [docs/image.md](./docs/image.md) |\n| Repo maintenance | `update_repo.py` | README install/update section |\n| Troubleshooting | validation, preview, export, dependency issues | [docs/troubleshooting.md](./docs/troubleshooting.md) |\n\n## High-Frequency Commands\n\nProject setup:\n\n```bash\npython3 scripts/project_manager.py init --format ppt169\npython3 scripts/project_manager.py import-sources --move\npython3 scripts/project_manager.py validate \n```\n\nTemplate source import:\n\n```bash\npython3 scripts/pptx_template_import.py \n```\n\nPost-processing and export:\n\n```bash\npython3 scripts/total_md_split.py \npython3 scripts/finalize_svg.py \npython3 scripts/svg_to_pptx.py -s final\n```\n\nImage generation:\n\n```bash\npython3 scripts/image_gen.py \"A modern futuristic workspace\"\npython3 scripts/image_gen.py --list-backends\npython3 scripts/analyze_images.py /images\n```\n\nRepository update:\n\n```bash\npython3 scripts/update_repo.py\npython3 scripts/update_repo.py --skip-pip\n```\n\n## Recommendations\n\n- Keep new runnable scripts at the top level of `scripts/`\n- Move provider-specific or helper internals into subdirectories\n- Prefer the unified entry points `project_manager.py`, `finalize_svg.py`, and `image_gen.py`\n- Prefer `svg_final/` over `svg_output/` when exporting\n\n## Related Docs\n\n- [Conversion Tools](./docs/conversion.md)\n- [Project Tools](./docs/project.md)\n- [SVG Pipeline Tools](./docs/svg-pipeline.md)\n- [Image Tools](./docs/image.md)\n- [Troubleshooting](./docs/troubleshooting.md)\n- [AGENTS Guide](../../../AGENTS.md)\n\n_Last updated: 2026-03-26_\n\nFile v1.2.3:templates/charts/README.md\n\n# SVG Chart Template Library (33 Types)\n\nThis directory provides **33 standardized SVG chart templates** for use as chart selection references in PPT Master.\n\n- **Full Index**: [README.md](./README.md) (human browsing)\n- **JSON Index**: [charts_index.json](./charts_index.json) (AI / programmatic lookup — preferred)\n\nBefore generating chart pages, review the corresponding template file to understand its structure and layout.\n\n## Quick Selection\n\n> **AI / Programmatic recommendation**: Prefer reading `charts_index.json`; use this README for human browsing and quick comparison.\n\n| I want to show... | Recommended Template | Filename |\n|-------------------|---------------------|----------|\n| Key numeric metrics | KPI Cards | `kpi_cards.svg` |\n| Category value comparison | Bar Chart | `bar_chart.svg` |\n| Long-label rankings | Horizontal Bar Chart | `horizontal_bar_chart.svg` |\n| Multi-series comparison | Grouped Bar Chart | `grouped_bar_chart.svg` |\n| Time trends | Line Chart | `line_chart.svg` |\n| Cumulative trends | Area Chart | `area_chart.svg` |\n| Proportional composition | Pie / Donut Chart | `pie_chart.svg` / `donut_chart.svg` |\n| Goal completion rate | Progress Bar / Gauge | `progress_bar_chart.svg` / `gauge_chart.svg` |\n| Conversion funnel | Funnel Chart | `funnel_chart.svg` |\n| Project scheduling | Gantt Chart | `gantt_chart.svg` |\n| Milestone events | Timeline | `timeline.svg` |\n| Multi-dimensional assessment | Radar Chart | `radar_chart.svg` |\n| Bidirectional comparison | Butterfly Chart | `butterfly_chart.svg` |\n| Incremental breakdown | Waterfall Chart | `waterfall_chart.svg` |\n| Flow / fund allocation | Sankey Chart | `sankey_chart.svg` |\n| Strategic analysis | SWOT / Porter's Five Forces | `swot_analysis.svg` / `porter_five_forces.svg` |\n| Quadrant analysis | Matrix (2x2) | `matrix_2x2.svg` |\n\n## Full Chart Index\n\n### Comparison\n\n| Filename | Purpose | Use Cases |\n|----------|---------|-----------|\n| `bar_chart.svg` | Vertical bar comparison (3-8 bars) | Sales comparison, regional ranking |\n| `horizontal_bar_chart.svg` | Horizontal bar ranking (5-12 bars) | Brand ranking, satisfaction scores |\n| `grouped_bar_chart.svg` | Multi-series grouped comparison | Quarterly product line comparison, YoY/QoQ |\n| `stacked_bar_chart.svg` | Stacked composition comparison | Revenue composition, market share changes |\n| `butterfly_chart.svg` | Bidirectional comparison | Population pyramid, A/B testing, income vs expense |\n| `bullet_chart.svg` | Target vs actual | KPI achievement, performance evaluation |\n| `dumbbell_chart.svg` | Multi-dimension score comparison | Competitive analysis, composite index |\n| `waterfall_chart.svg` | Incremental change breakdown | Profit decomposition, budget variance |\n\n### Trends\n\n| Filename | Purpose | Use Cases |\n|----------|---------|-----------|\n| `line_chart.svg` | Line trend (multi-line support) | Time series, growth trends |\n| `area_chart.svg` | Area cumulative trend | Traffic trends, user growth |\n| `stacked_area_chart.svg` | Multi-series stacked trend | Revenue sources, traffic source changes |\n| `dual_axis_line_chart.svg` | Dual Y-axis different-unit comparison | Sales vs profit margin, traffic vs conversion rate |\n\n### Proportions\n\n| Filename | Purpose | Use Cases |\n|----------|---------|-----------|\n| `pie_chart.svg` | Basic proportion (3-6 slices) | Market share, budget allocation |\n| `donut_chart.svg` | Ring proportion (with center data) | Structural proportion, category composition |\n| `treemap_chart.svg` | Hierarchical area proportion | Budget allocation, market share composition |\n\n### Metrics\n\n| Filename | Purpose | Use Cases |\n|----------|---------|-----------|\n| `kpi_cards.svg` | Key metric cards (2x2 / 1x4) | Financial overview, data dashboard |\n| `gauge_chart.svg` | Gauge completion rate | KPI completion, performance monitoring |\n| `progress_bar_chart.svg` | Multi-item progress bars | OKR progress, project completion |\n\n### Analysis\n\n| Filename | Purpose | Use Cases |\n|----------|---------|-----------|\n| `radar_chart.svg` | Multi-dimensional assessment (4-8 axes) | Capability assessment, competitive comparison |\n| `scatter_chart.svg` | Correlation / distribution | Input-output analysis, price-demand |\n| `funnel_chart.svg` | Conversion funnel (3-5 stages) | Sales funnel, user conversion |\n| `matrix_2x2.svg` | Four-quadrant analysis | BCG matrix, priority analysis |\n| `bubble_chart.svg` | 3D bubble (X/Y/Size) | Market size vs growth rate vs share |\n| `heatmap_chart.svg` | Matrix heatmap | User activity periods, correlation matrix |\n| `pareto_chart.svg` | 80/20 Pareto analysis | Quality attribution, sales contribution |\n| `box_plot_chart.svg` | Box plot distribution | Salary distribution, quality control |\n\n### Project Management / Relationships\n\n| Filename | Purpose | Use Cases |\n|----------|---------|-----------|\n| `gantt_chart.svg` | Gantt schedule (6-12 tasks) | Project management, product roadmap |\n| `timeline.svg` | Timeline events (3-8 nodes) | Milestones, historical evolution |\n| `process_flow.svg` | Process flow steps | Business processes, operational guides |\n| `org_chart.svg` | Org structure (2-4 levels) | Company structure, reporting relationships |\n| `sankey_chart.svg` | Data flow (three-tier) | Budget flow, user conversion paths |\n\n### Strategic Frameworks\n\n| Filename | Purpose | Use Cases |\n|----------|---------|-----------|\n| `swot_analysis.svg` | SWOT four-quadrant analysis | Strategic planning, competitive analysis |\n| `porter_five_forces.svg` | Porter's Five Forces model | Industry analysis, market entry assessment |\n\nFile v1.2.3:templates/icons/README.md\n\n# SVG Icon Library\n\nThis directory provides **6000+ high-quality SVG icons** from [Tabler Icons](https://tabler.io/icons) that can be directly embedded into SVG files generated by PPT Master.\n\n## Libraries\n\n| Library | Style | Count | viewBox | Prefix |\n|---------|-------|-------|---------|--------|\n| `tabler-filled` | fill / solid | 1000+ | `0 0 24 24` | `tabler-filled/` |\n| `tabler-outline` | stroke / line | 5000+ | `0 0 24 24` | `tabler-outline/` |\n\n> `chunk/` exists only for backward compatibility with older projects. Do **not** use it in new work.\n\n---\n\n## Usage\n\nUse placeholder syntax **during SVG generation**:\n\n```xml\n\n\n\n\n\n```\n\n**Attributes**:\n- `data-icon` — `/` (filename without `.svg`)\n- `x`, `y` — Position\n- `width`, `height` — Size (base 24px; `width=48` → `scale(2)`)\n- `fill` — Color\n\n`finalize_svg.py` auto-embeds all placeholders during post-processing. To run manually:\n\n```bash\npython3 scripts/svg_finalize/embed_icons.py svg_output/*.svg\n```\n\n---\n\n## Searching for Icons\n\nUse `ls | grep` — zero token cost:\n\n```bash\nls skills/pptx-master/templates/icons/tabler-filled/ | grep home\nls skills/pptx-master/templates/icons/tabler-outline/ | grep chart\n```\n\n---\n\n## Style Rules\n\n- **Fill / Solid**: use `tabler-filled`\n- **Stroke / Line**: use `tabler-outline`\n- ⚠️ Do **not** mix fill and outline icons in the same presentation\n\nFile v1.2.3:templates/layouts/README.md\n\n# Page Layout Template Library (20 Templates)\n\nPre-built PPT page layout templates supporting multiple styles and use cases.\n\n- **Full Index**: [README.md](./README.md) (human browsing)\n- **JSON Index**: [layouts_index.json](./layouts_index.json) (AI / programmatic lookup — preferred)\n\n> **AI / Programmatic recommendation**: Prefer reading `layouts_index.json`; use this README for human browsing and quick comparison.\n\n---\n\n## Quick Template Index\n\n| Template Name | Category | Use Cases | Primary Color | Design Tone |\n|---------------|----------|-----------|---------------|-------------|\n| `google_style` | Brand | Annual reports, tech sharing, data presentation | Google Four Colors `#4285F4` `#EA4335` `#FBBC04` `#34A853` | Modern clean, data-driven, ample whitespace |\n| `mckinsey` | Brand | Strategic consulting, executive reports, investment analysis | McKinsey Blue `#005587` | Structured thinking, minimalist premium, MECE principle |\n| `anthropic` | Brand | AI tech sharing, developer conferences, product launches | Anthropic Orange `#D97757` | Tech-forward, conclusion-first, dark cover |\n| `中汽研_常规` | Brand | Product certification, evaluation & testing | Deep Blue `#004098` | [Standard] Professional authority, consulting style |\n| `中汽研_商务` | Brand | Business visits, technical exchanges | Blue Gradient `#003366` | [Business] Modern tech, composed and sophisticated |\n| `中汽研_现代` | Brand | Strategic launches, future tech | Deep Blue `#001529` | [Future] Future Tech, neon glow |\n| `中国电建_常规` | Brand | Power & energy, engineering, state-owned enterprise reports | PowerChina Blue `#00418D` | Craftsmanship, steady and reliable |\n| `中国电建_现代` | Brand | International engineering, premium roadshows, tech innovation | Deep Sea Blue `#001F45` | [Modern] Grand narrative, digital tech |\n| `招商银行` | Brand | Premium reports, VIP services, annual reports | CMB Red `#C41230` | Minimalist luxury, financial texture, borderless |\n| `exhibit` | General | Exhibit-driven strategic reports, executive presentations, board briefings | Gradient top bar + Gold accents | Conclusion-first, data-driven, confidential |\n| `academic_defense` | Scenario | Thesis defense, academic reports, grant proposals | Deep Blue + Red accents | Clear hierarchy, academic standards |\n| `psychology_attachment` | Scenario | Psychotherapy training, counseling lectures | Blue-green gradient + Colorful semantic colors | Warm professional, therapeutic feel |\n| `medical_university` | Scenario | Medical reports, case discussions, research presentations | Medical Blue `#0066B3` | Professional rigorous, life-affirming |\n| `government_red` | Government/Enterprise | Government work reports, party-building presentations | Government Red `#8B0000` | Solemn authority, grand and imposing |\n| `government_blue` | Government/Enterprise | Smart cities, open governance, digital transformation | Tech Blue `#0050B3` | Modern tech, rigorous and rational |\n| `ai_ops` | Government/Enterprise | Telecom AI ops, IT system overview, digital intelligence solutions | Telecom Red `#C00000` + Blue `#2E75B6` | High information density, modular layout, telecom style |\n| `pixel_retro` | Special | Git/tech introductions, retro gaming themes | Neon colors `#00FF41` `#FF0080` | Pixel art, cyberpunk |\n| `科技蓝商务` | General | Corporate reports, product launches, proposals | Tech Blue `#0078D7` | Tech, business, professional, clean |\n| `smart_red` | General | Tech company profiles, education solutions | Smart Red-Orange `#DE3545` | Modern, vibrant, geometric |\n| `重庆大学` | Scenario | Academic defense, research presentations | CQU Blue `#006BB7` | Academic solidity, mountain-city character |\n---\n\n## Template Categories\n\n### 1. Brand Style Templates\n\nTemplates mimicking **specific well-known brands/institutions** with their exclusive design style.\n> **Characteristics**: Distinctive brand identity (specific logos, color schemes, VI standards), suitable for internal or external presentations of that organization. Examples: Google, McKinsey, PowerChina.\n\n| Template | Description |\n|----------|-------------|\n| `google_style` | Google Material Design style, four-color brand identity |\n| `mckinsey` | McKinsey consulting style, data-driven and structured |\n| `anthropic` | Anthropic AI style, dark tech-forward aesthetic |\n| `中汽研_常规` | CATARC standard style (v1), suitable for certification and evaluation |\n| `中汽研_商务` | CATARC business style (v2), modern tech business, composed and sophisticated |\n| `中汽研_现代` | CATARC modern style (v3 Future), Future Tech style, deep blue + neon cyan |\n| `中国电建_常规` | PowerChina standard style (v1), suitable for power, energy, and engineering SOEs |\n| `中国电建_现代` | PowerChina modern style (v2), emphasis on grand narrative and digital tech |\n| `招商银行` | China Merchants Bank v2.0, minimalist luxury, borderless open layout |\n\n### 2. General Style Templates\n\nUniversal business styles not tied to any specific brand, broadly applicable.\n\n| Template | Description |\n|----------|-------------|\n| `exhibit` | Exhibit-driven style, conclusion-first layout with Exhibit takeaway bar, gradient top bar, grid decoration |\n| `科技蓝商务` | Tech business style, rigorous and professional, hexagonal texture |\n| `smart_red` | Smart red-orange business style, modern and vibrant, geometric cutaway design |\n\n### 3. Scenario-Specific Templates\n\nDesigned for **specific use cases**, with content structures tailored to scenario requirements.\n\n| Template | Description |\n|----------|-------------|\n| `academic_defense` | Academic defense, clear research content hierarchy |\n| `psychology_attachment` | Psychotherapy theme, warm and professional color palette |\n| `medical_university` | Hospital / medical university template, suitable for medical reports |\n| `重庆大学` | Chongqing University template, blending mountain-city layered imagery with modern academic style |\n\n### 4. Government & Enterprise Templates\n\nIndustry-standard designs for **government agencies and general state-owned enterprises**.\n> **Distinction**: Unlike brand styles, these are not targeted at specific organizations but provide templates matching the common aesthetic preferences of government/SOE contexts (e.g., official document red, smart governance blue).\n\n| Template | Description |\n|----------|-------------|\n| `government_red` | Red government style, suitable for government work reports, party-building events |\n| `government_blue` | Blue government style, suitable for smart cities, digital governance reports |\n| `ai_ops` | Enterprise digital intelligence style, telecom AI ops architecture, high-density reports (includes `reference_style.svg` style reference) |\n\n### 5. Special Style Templates\n\nUnconventional visual styles for specific creative scenarios.\n\n| Template | Description |\n|----------|-------------|\n| `pixel_retro` | Pixel retro style, cyberpunk / gaming themes |\n\n> **Design philosophy**: Style and scenario are **orthogonal** concepts. Scenario templates define content structure; style templates define visual presentation. In theory, scenario templates can be combined with different styles.\n\n---\n\n## Template File Structure\n\nEach template should contain the following standard files (TOC page is optional):\n\n| Filename | Required | Purpose | Description |\n|----------|----------|---------|-------------|\n| `design_spec.md` | Yes | Design specification | Complete color, typography, and layout specs |\n| `01_cover.svg` | Yes | Cover page | Title, subtitle, date, organization |\n| `02_toc.svg` | Optional | Table of contents | Chapter list, navigation |\n| `02_chapter.svg` | Yes | Chapter page | Chapter number, chapter title |\n| `03_content.svg` | Yes | Content page | Fixed header/footer, flexible content area |\n| `04_ending.svg` | Yes | Ending page | Thank-you message, contact info |\n\n> **Design philosophy**: Templates define visual consistency and structural pages; content pages maintain maximum flexibility, letting AI determine layout based on actual content.\n\n---\n\n## design_spec.md Standard Structure\n\nAll template design specification documents should follow this chapter structure:\n\n```markdown\n# [Template Name] - Design Specification\n\n> One-line description of applicable scenarios\n\n## I. Template Overview\n## II. Canvas Specification\n## III. Color Scheme\n## IV. Typography System\n## V. Page Structure\n## VI. Page Types\n## VII. Layout Modes (Recommended)\n## VIII. Spacing Specification\n## IX. SVG Technical Constraints\n## X. Placeholder Specification\n## XI. Usage Guide (Recommended)\n```\n\n---\n\n## Placeholder Specification\n\nTemplates use `{{PLACEHOLDER}}` format to mark replaceable content:\n\n> For **newly created library templates**, use the canonical placeholder contract below. Some existing templates still contain legacy placeholder variants; those should be treated as historical exceptions rather than the standard for new assets.\n\n### General Placeholders\n\n| Placeholder | Purpose | Applicable Pages |\n|-------------|---------|-----------------|\n| `{{TITLE}}` | Main title | Cover |\n| `{{SUBTITLE}}` | Subtitle | Cover |\n| `{{DATE}}` | Date | Cover, Ending |\n| `{{AUTHOR}}` | Author / Organization (Chinese) | Cover |\n| `{{AUTHOR_EN}}` | Author / Organization (English) | Cover |\n\n### Chapter-Related\n\n| Placeholder | Purpose | Applicable Pages |\n|-------------|---------|-----------------|\n| `{{CHAPTER_NUM}}` | Chapter number | Chapter, Content |\n| `{{CHAPTER_TITLE}}` | Chapter title | Chapter |\n| `{{CHAPTER_TITLE_EN}}` | Chapter English subtitle | Chapter |\n\n### Content Page\n\n| Placeholder | Purpose | Applicable Pages |\n|-------------|---------|-----------------|\n| `{{PAGE_TITLE}}` | Page title | Content |\n| `{{CONTENT_AREA}}` | Content area placeholder | Content |\n| `{{PAGE_NUM}}` | Page number | Content, Ending |\n| `{{SOURCE}}` | Data source | Content footer |\n\n### Table of Contents\n\n| Placeholder | Purpose |\n|-------------|---------|\n| `{{TOC_ITEM_1_TITLE}}` ~ `{{TOC_ITEM_N_TITLE}}` | TOC item titles |\n| `{{TOC_ITEM_1_DESC}}` ~ `{{TOC_ITEM_N_DESC}}` | Optional TOC item descriptions |\n| `{{TOC_ITEM_1}}` ~ `{{TOC_ITEM_N}}` | Legacy simple TOC items; do not use for new templates unless no description field is needed |\n\n### Ending Page\n\n| Placeholder | Purpose |\n|-------------|---------|\n| `{{THANK_YOU}}` | Thank-you message |\n| `{{ENDING_SUBTITLE}}` | Ending page subtitle |\n| `{{CLOSING_MESSAGE}}` | Closing message |\n| `{{CONTACT_INFO}}` | Contact information |\n\n---\n\n## Usage\n\n### Copy from Template Library to Project\n\n```bash\n# Copy exhibit style template to project\ncp templates/layouts/exhibit/* projects//templates/\n\n# Copy Google style template to project\ncp templates/layouts/google_style/* projects//templates/\n\n# Copy government style template to project (e.g., government red)\ncp templates/layouts/government_red/* projects//templates/\n```\n\n### After Copying\n\n1. Read `design_spec.md` to understand the design specification\n2. Adjust colors based on project requirements (if needed)\n3. Place logo files in the `images/` directory\n4. Use the Executor role to generate SVG pages based on templates\n\n---\n\n## Template Development Guide\n\n### Creating New Templates\n\n1. Create a new directory under `templates/layouts/`\n2. Create required files following the existing template structure\n3. Ensure `design_spec.md` follows the standard chapter structure\n4. All SVGs use `viewBox=\"0 0 1280 720\"`\n5. Follow SVG technical constraints (see below)\n6. Validate the template directory with `python3 scripts/svg_quality_checker.py templates/layouts/ --format ppt169`\n7. Register the new template in `templates/layouts/layouts_index.json`\n\n`layouts_index.json` is the primary machine-readable source for template discovery. A template folder without an index entry is considered incomplete.\n\n### SVG Technical Constraints (All Templates Must Comply)\n\n#### Required\n\n- viewBox: `0 0 1280 720`\n- Backgrounds use `` elements\n- Text wrapping uses ``\n- Transparency uses `fill-opacity` / `stroke-opacity`\n- Gradients use `` with ``\n\n#### Forbidden (PPT Incompatible)\n\n| Banned Element | Alternative |\n|----------------|-------------|\n| `` | Use `` + `` |\n| `clipPath` | Redesign layout |\n| `mask` | Use `fill-opacity` |\n| `