codewave-openclaw-installer 1.0.2 → 2.1.1

package/skills/popo-robot-api/SKILL.md

@@ -0,0 +1,232 @@
+---
+name: popo-robot-api
+description: POPO (NetEase) 机器人 API。通过 razel-cli popo robot 发送消息、管理群组、处理文件。支持文本/富文本/卡片/图片/文件消息、群组 CRUD、消息撤回/已读查询、可见范围管理。
+---
+
+# POPO Robot API
+
+基于 `razel-cli popo robot` 的 POPO 机器人 API 集成。
+
+## Pre-flight
+
+```bash
+razel-cli --version
+# 认证（三选一，按优先级）
+# 1. 命令行参数 --key / --secret
+# 2. ~/.razel/config.json 中的 popo_app_id / popo_app_secret
+# 3. 环境变量 POPO_APP_KEY / POPO_APP_SECRET
+```
+
+Token 自动获取并缓存到 `~/.razel/popo/config.json`，无需手动管理。
+
+---
+
+## 消息发送
+
+### 文本消息
+
+```bash
+razel-cli popo robot send text <receiver> "消息内容"
+razel-cli popo robot send text "user@corp.netease.com" "Hello World" --json
+```
+
+### 富文本消息
+
+```bash
+razel-cli popo robot send rich <receiver> '<json_array>'
+razel-cli popo robot send rich "user@corp.netease.com" '[
+  {"tag":"text","style":["bold"],"text":"标题"},
+  {"tag":"text","text":"\n正文内容"},
+  {"tag":"text","style":["font_color"],"fontColor":"red","text":"\n【高风险】红色文字"}
+]' --json
+```
+
+#### 富文本标签
+
+| tag | 说明 | 示例 |
+|-----|------|------|
+| `text` | 文本（可带样式） | `{"tag":"text","text":"hello"}` |
+| `at` | @用户 | `{"tag":"at","email":"user@corp.netease.com"}` |
+| `image` | 行内图片 | `{"tag":"image","url":"https://..."}` |
+
+#### 文本样式
+
+| style | 附加字段 | 说明 |
+|-------|---------|------|
+| `bold` | — | 粗体 |
+| `italic` | — | 斜体 |
+| `underline` | — | 下划线 |
+| `strikethrough` | — | 删除线 |
+| `font_color` | `fontColor`: red/orange/green/purple | 字体颜色 |
+| `background_color` | `backgroundColor`: 颜色值 | 背景色 |
+| `link` | `href`: URL | 超链接 |
+
+### 卡片消息
+
+```bash
+razel-cli popo robot send card <receiver> --template <uuid> --instance <uuid> [--vars '<json>']
+razel-cli popo robot send card "user@corp.netease.com" \
+  --template "tpl_xxx" \
+  --instance "inst_$(date +%s)" \
+  --vars '{"title":{"zh-CN":"通知"},"content":"内容"}' --json
+```
+
+### 图片消息
+
+```bash
+# 本地文件（自动上传）
+razel-cli popo robot send image <receiver> /path/to/image.png
+
+# URL（内嵌文本发送）
+razel-cli popo robot send image <receiver> "https://example.com/img.png"
+```
+
+### 文件消息
+
+```bash
+razel-cli popo robot send file <receiver> /path/to/file.pdf
+```
+
+文件自动执行：计算 MD5 → 注册上传 → 上传内容 → 发送消息。
+
+---
+
+## 群组管理
+
+### 创建群组
+
+```bash
+razel-cli popo robot group create \
+  --name "群名" \
+  --owner "owner@corp.netease.com" \
+  --members "user1@corp.netease.com,user2@corp.netease.com" --json
+```
+
+至少 2 个成员（不含群主）。
+
+### 查询群信息
+
+```bash
+razel-cli popo robot group info --tid <team_id> --json
+```
+
+### 查询群成员
+
+```bash
+razel-cli popo robot group members --tid <team_id> --json
+```
+
+### 邀请入群
+
+```bash
+razel-cli popo robot group invite --tid <team_id> --members "user@corp.netease.com" --json
+```
+
+### 解散群组
+
+```bash
+razel-cli popo robot group delete --tid <team_id> --json
+```
+
+---
+
+## 消息管理
+
+### 撤回消息
+
+```bash
+razel-cli popo robot msg recall --msgId <msg_id> --sessionId <session_id> --json
+```
+
+### 已读状态查询
+
+```bash
+razel-cli popo robot msg status --msgId <msg_id> --json
+```
+
+---
+
+## 可见范围
+
+```bash
+razel-cli popo robot scope get --json
+razel-cli popo robot scope publish --uid <uid> --json
+```
+
+---
+
+## 认证管理
+
+```bash
+razel-cli popo robot auth login
+razel-cli popo robot auth status
+razel-cli popo robot auth logout
+```
+
+---
+
+## receiver 格式
+
+| 场景 | 格式 | 示例 |
+|------|------|------|
+| 个人 | 邮箱 | `user@corp.netease.com` |
+| 群组 | team_id | `8194891`（从 group create 或 group info 获取） |
+
+---
+
+## 错误码
+
+| errcode | 说明 | 处理 |
+|---------|------|------|
+| 42001 | Token 过期 | CLI 自动刷新，通常无需处理 |
+| 42002 | Refresh token 过期 | 重新获取 |
+| 65338 | 消息过长 | 文本 ≤3000 字符，富文本 ≤5000 字符 |
+| 65341 | 非 POPO 用户 | 检查 receiver |
+| 65347 | 无 API 权限 | 检查机器人权限配置 |
+| 65605/65612 | 不在可见范围 | 更新可见范围 |
+| 65611 | 接收者不存在 | 检查 receiver |
+
+## 限制
+
+| 项目 | 限制 |
+|------|------|
+| 文本消息 | ≤3000 字符 |
+| 富文本消息 | ≤5000 字符（含标签） |
+| 文件上传 | ≤20MB |
+| 发送频率 | 60 条/分钟/机器人 |
+| Token 有效期 | 24 小时（自动刷新） |
+| Refresh Token | 30 天 |
+
+## 常用工作流
+
+### 发送带格式的周报摘要
+
+```bash
+CONTENT='[
+  {"tag":"text","style":["bold"],"text":"【周报摘要】"},
+  {"tag":"text","text":"\n\n• 项目A：联调完成，下周 UAT\n"},
+  {"tag":"text","style":["font_color"],"fontColor":"red","text":"• 【高风险】项目B：接口延期，阻塞上线\n"},
+  {"tag":"text","style":["font_color"],"fontColor":"green","text":"• 【进展良好】项目C：已交付验收"}
+]'
+razel-cli popo robot send rich "user@corp.netease.com" "$CONTENT" --json
+```
+
+### 上传文件并发送
+
+```bash
+razel-cli popo robot send file "user@corp.netease.com" /tmp/report.pdf --json
+```
+
+### 创建群 → 邀请 → 发消息
+
+```bash
+# 创建
+RESULT=$(razel-cli popo robot group create --name "项目A群" --owner "pm@corp.netease.com" --members "dev1@corp.netease.com,dev2@corp.netease.com" --json)
+TID=$(echo "$RESULT" | jq -r '.tid')
+
+# 邀请更多人
+razel-cli popo robot group invite --tid "$TID" --members "qa@corp.netease.com"
+
+# 发消息到群
+razel-cli popo robot send text "$TID" "群已创建，请各位确认"
+```

package/skills/ppt-master/SKILL.md

@@ -0,0 +1,314 @@
+---
+name: ppt-master
+description: >
+  AI-driven multi-format SVG content generation system. Converts source documents
+  (PDF/DOCX/URL/Markdown) into high-quality SVG pages and exports to PPTX through
+  multi-role collaboration. Use when user asks to "create PPT", "make presentation",
+  "生成PPT", "做PPT", "制作演示文稿", or mentions "ppt-master".
+---
+
+# PPT Master Skill
+
+> AI-driven multi-format SVG content generation system. Converts source documents into high-quality SVG pages through multi-role collaboration and exports to PPTX.
+
+**Core Pipeline**: `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
+
+## Main Pipeline Scripts
+
+| Script | Purpose |
+|--------|---------|
+| `${SKILL_DIR}/scripts/pdf_to_md.py` | PDF to Markdown |
+| `${SKILL_DIR}/scripts/doc_to_md.py` | Documents to Markdown via Pandoc (DOCX, EPUB, HTML, LaTeX, RST, etc.) |
+| `${SKILL_DIR}/scripts/web_to_md.py` | Web page to Markdown |
+| `${SKILL_DIR}/scripts/web_to_md.cjs` | WeChat / high-security sites to Markdown |
+| `${SKILL_DIR}/scripts/project_manager.py` | Project init / validate / manage |
+| `${SKILL_DIR}/scripts/analyze_images.py` | Image analysis |
+| `${SKILL_DIR}/scripts/image_gen.py` | AI image generation (multi-provider) |
+| `${SKILL_DIR}/scripts/svg_quality_checker.py` | SVG quality check |
+| `${SKILL_DIR}/scripts/total_md_split.py` | Speaker notes splitting |
+| `${SKILL_DIR}/scripts/finalize_svg.py` | SVG post-processing (unified entry) |
+| `${SKILL_DIR}/scripts/svg_to_pptx.py` | Export to PPTX |
+
+For complete tool documentation, see `${SKILL_DIR}/scripts/README.md`.
+
+## Template Index
+
+| Index | Path | Purpose |
+|-------|------|---------|
+| Layout templates | `${SKILL_DIR}/templates/layouts/layouts_index.json` | Query available page layout templates |
+| Chart templates | `${SKILL_DIR}/templates/charts/charts_index.json` | Query available chart SVG templates |
+| Icon library | `${SKILL_DIR}/templates/icons/icons_index.json` | Query available icon names and categories |
+
+## Standalone Workflows
+
+| Workflow | Path | Purpose |
+|----------|------|---------|
+| `create-template` | `workflows/create-template.md` | Standalone template creation workflow |
+
+---
+
+## Workflow
+
+### Step 1: Source Content Processing
+
+🚧 **GATE**: User has provided source material (PDF / DOCX / EPUB / URL / Markdown file / text description / conversation content — any form is acceptable).
+
+When the user provides non-Markdown content, convert immediately:
+
+| User Provides | Command |
+|---------------|---------|
+| PDF file | `python3 ${SKILL_DIR}/scripts/pdf_to_md.py <file>` |
+| DOCX / Word / Office document | `python3 ${SKILL_DIR}/scripts/doc_to_md.py <file>` |
+| EPUB / HTML / LaTeX / RST / other | `python3 ${SKILL_DIR}/scripts/doc_to_md.py <file>` |
+| Web link | `python3 ${SKILL_DIR}/scripts/web_to_md.py <URL>` |
+| WeChat / high-security site | `node ${SKILL_DIR}/scripts/web_to_md.cjs <URL>` |
+| Markdown | Read directly |
+
+**✅ Checkpoint — Confirm source content is ready, proceed to Step 2.**
+
+---
+
+### Step 2: Project Initialization
+
+🚧 **GATE**: Step 1 complete; source content is ready (Markdown file, user-provided text, or requirements described in conversation are all valid).
+
+```bash
+python3 ${SKILL_DIR}/scripts/project_manager.py init <project_name> --format <format>
+```
+
+Format options: `ppt169` (default), `ppt43`, `xhs`, `story`, etc. For the full format list, see `references/canvas-formats.md`.
+
+Import source content (choose based on the situation):
+
+| Situation | Action |
+|-----------|--------|
+| Has source files (PDF/MD/etc.) | `python3 ${SKILL_DIR}/scripts/project_manager.py import-sources <project_path> <source_files...> --move` |
+| User provided text directly in conversation | No import needed — content is already in conversation context; subsequent steps can reference it directly |
+
+> ⚠️ **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
+
+**✅ Checkpoint — Confirm project structure created successfully, `sources/` contains all source files, converted materials are ready. Proceed to Step 3.**
+
+---
+
+### Step 3: Template Selection
+
+🚧 **GATE**: Step 2 complete; project directory structure is ready.
+
+⛔ **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.
+
+**⚡ 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.
+
+**Template recommendation flow** (only when the user has NOT yet decided):
+Query `${SKILL_DIR}/templates/layouts/layouts_index.json` to list available templates and their style descriptions.
+**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:
+
+> 💡 **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
+
+After the user confirms option A, copy template files to the project directory:
+```bash
+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
+```
+
+After the user confirms option B, proceed directly to Step 4.
+
+> To create a new global template, read `workflows/create-template.md`
+
+**✅ Checkpoint — User has responded with template selection, template files copied (if option A). Proceed to Step 4.**
+
+---
+
+### Step 4: Strategist Phase (MANDATORY — cannot be skipped)
+
+🚧 **GATE**: Step 3 complete; user has confirmed template selection.
+
+First, read the role definition:
+```
+Read references/strategist.md
+```
+
+**Must complete the Eight Confirmations** (refer to `templates/design_spec_reference.md` for the template structure):
+
+⛔ **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.
+
+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
+
+If 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):
+```bash
+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.
+
+**Output**: `<project_path>/design_spec.md`
+
+**✅ Checkpoint — Phase deliverables complete, auto-proceed to next step**:
+```markdown
+## ✅ Strategist Phase Complete
+- [x] Eight Confirmations completed (user confirmed)
+- [x] Design Specification & Content Outline generated
+- [ ] **Next**: Auto-proceed to [Image_Generator / Executor] phase
+```
+
+---
+
+### Step 5: Image_Generator Phase (Conditional)
+
+🚧 **GATE**: Step 4 complete; Design Specification & Content Outline generated and user confirmed.
+
+> **Trigger condition**: Image approach includes "AI generation". If not triggered, skip directly to Step 6 (Step 6 GATE must still be satisfied).
+
+Read `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
+   ```
+
+**✅ Checkpoint — Confirm all images are ready, proceed to Step 6**:
+```markdown
+## ✅ Image_Generator Phase Complete
+- [x] Prompt document created
+- [x] All images saved to images/
+```
+
+---
+
+### Step 6: Executor Phase
+
+🚧 **GATE**: Step 4 (and Step 5 if triggered) complete; all prerequisite deliverables are ready.
+
+Read the role definition based on the selected style:
+```
+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.
+
+**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.
+
+> ⚠️ **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.
+
+**Visual Construction Phase**:
+- Generate SVG pages sequentially, one page at a time, in one continuous pass → `<project_path>/svg_output/`
+
+**Logic Construction Phase**:
+- Generate speaker notes → `<project_path>/notes/total.md`
+
+**✅ Checkpoint — Confirm all SVGs and notes are fully generated. Proceed directly to Step 7 post-processing**:
+```markdown
+## ✅ Executor Phase Complete
+- [x] All SVGs generated to svg_output/
+- [x] Speaker notes generated at notes/total.md
+```
+
+---
+
+### Step 7: Post-processing & Export
+
+🚧 **GATE**: Step 6 complete; all SVGs generated to `svg_output/`; speaker notes `notes/total.md` generated.
+
+> ⚠️ 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.
+
+**Step 7.1** — Split speaker notes:
+```bash
+python3 ${SKILL_DIR}/scripts/total_md_split.py <project_path>
+```
+
+**Step 7.2** — SVG post-processing (icon embedding / image crop & embed / text flattening / rounded rect to path):
+```bash
+python3 ${SKILL_DIR}/scripts/finalize_svg.py <project_path>
+```
+
+**Step 7.3** — Export PPTX (embeds speaker notes by default):
+```bash
+python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path> -s final
+# Default: generates two files — native shapes (.pptx) + SVG reference (_svg.pptx)
+# Use --only native  to skip SVG reference version
+# Use --only legacy  to only generate SVG image version
+```
+
+> ❌ **NEVER** use `cp` as a substitute for `finalize_svg.py` — it performs multiple critical processing steps
+> ❌ **NEVER** export directly from `svg_output/` — MUST use `-s final` to export from `svg_final/`
+> ❌ **NEVER** add extra flags like `--only`
+
+---
+
+## Role Switching Protocol
+
+Before switching roles, you **MUST first read** the corresponding reference file — skipping is FORBIDDEN. Output marker:
+
+```markdown
+## [Role Switch: <Role Name>]
+📖 Reading role definition: references/<filename>.md
+📋 Current task: <brief description>
+```
+
+---
+
+## Reference Resources
+
+| Resource | Path |
+|----------|------|
+| Shared technical constraints | `references/shared-standards.md` |
+| Canvas format specification | `references/canvas-formats.md` |
+| Image layout specification | `references/image-layout-spec.md` |
+| SVG image embedding | `references/svg-image-embedding.md` |
+
+---
+
+## Notes
+
+- 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`

package/skills/ppt-master/references/canvas-formats.md

@@ -0,0 +1,73 @@
+# Canvas Format Specification
+
+> See shared-standards.md for SVG basic rules.
+
+## Format Quick Reference
+
+| Format | viewBox | Ratio | Use Case |
+|--------|---------|-------|----------|
+| PPT 16:9 | `0 0 1280 720` | 16:9 | Business presentations, meetings |
+| PPT 4:3 | `0 0 1024 768` | 4:3 | Traditional projectors, academic talks |
+| Xiaohongshu (RED) | `0 0 1242 1660` | 3:4 | Image-text sharing, knowledge posts |
+| WeChat Moments / IG | `0 0 1080 1080` | 1:1 | Square posters, brand showcases |
+| Story / TikTok | `0 0 1080 1920` | 9:16 | Vertical stories, short video covers |
+| WeChat Article Header | `0 0 900 383` | 2.35:1 | WeChat article cover images |
+| Landscape Banner | `0 0 1920 1080` | 16:9 | Web banners, digital screens |
+| Portrait Poster | `0 0 1080 1920` | 9:16 | Phone screens, elevator ads |
+| A4 Print | `0 0 1240 1754` | 1:sqrt(2) | Print posters, flyers |
+
+## Format Selection Decision Tree
+
+```
+Content purpose?
+├── Presentation
+│   ├── Modern devices → PPT 16:9 (1280x720)
+│   └── Traditional devices → PPT 4:3 (1024x768)
+├── Social sharing
+│   ├── Xiaohongshu (RED) → 1242x1660
+│   ├── WeChat Moments / IG → 1080x1080
+│   └── Story / TikTok → 1080x1920
+└── Marketing materials
+    ├── WeChat Article Header → 900x383
+    ├── Banner → 1920x1080
+    └── Print → 1240x1754
+```
+
+## Layout Principles
+
+### Landscape (16:9, 4:3, 2.35:1)
+- Visual flow: Z-pattern, left to right
+- Margins: 40-80px
+- Layouts: multi-column, left-right split, grid
+- Card dimensions (16:9): single-row 530-600px, double-row 265-295px
+
+### Portrait (3:4, 9:16)
+- Visual flow: top to bottom
+- Margins: 60-120px
+- Layouts: single-column, top-bottom split, card stacking
+- Card dimensions (3:4): height 400-600px, gap 40-60px
+
+### Square (1:1)
+- Visual flow: center-radiating
+- Margins: 60-100px
+- Core area: ~800x800px
+
+## Format-specific Design
+
+| Format | Title Area | Content Area | Special Notes |
+|--------|-----------|--------------|---------------|
+| PPT | 80-100px | Full width utilization | Page number bottom-right |
+| Xiaohongshu (RED) | 180-240px (bold) | Generous top/bottom whitespace | Brand area at bottom 120-160px |
+| WeChat Moments | 200-280px | Center 500-600px | QR code area at bottom 150-200px |
+| Story | — | Middle 1500px | Top safe zone 120px, bottom 180px |
+| WeChat Article Header | Center/left-aligned 48-72px | — | Image on right or as background |
+
+## ViewBox Examples
+
+```xml
+<svg width="1280" height="720" viewBox="0 0 1280 720">   <!-- PPT 16:9 -->
+<svg width="1242" height="1660" viewBox="0 0 1242 1660"> <!-- Xiaohongshu -->
+<svg width="1080" height="1080" viewBox="0 0 1080 1080"> <!-- WeChat Moments -->
+<svg width="1080" height="1920" viewBox="0 0 1080 1920"> <!-- Story -->
+<svg width="900" height="383" viewBox="0 0 900 383">     <!-- WeChat Article Header -->
+```