pptx-com

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

PPTX COM

Use desktop Microsoft PowerPoint through Windows COM to work with native, editable

.pptx

presentations. This skill is intended for a Windows environment with PowerPoint installed. Do not require a PowerPoint MCP server when local shell execution can call COM directly.

通过Windows COM使用桌面版Microsoft PowerPoint，处理原生可编辑的

.pptx

演示文稿。本技能适用于已安装PowerPoint的Windows环境。当本地Shell执行可直接调用COM时，无需依赖PowerPoint MCP服务器。

Operating Boundary

操作边界

Before reading, summarizing, or reviewing an existing presentation, identify the input file and intended read-only action, and obtain explicit confirmation; keep the file unmodified.
Before creating a presentation, editing a deck, exporting a PDF, exporting slide previews, copying a template, or writing any output, show the intended input, output, save strategy, and actions; obtain explicit confirmation.
If the user asks to create a new deck from uploaded or specified documents, PDFs, reports, or synthesized source materials, require an approved detailed Markdown slide plan before creating any
```
.pptx
```
, whether or not a template is provided.
If the user already provides a plan, review it for sufficient slide-level detail and required production decisions, show any gaps or adjustments, and request approval to use it; do not generate a redundant replacement plan when the supplied plan is adequate.
Ask each time whether the PowerPoint window should remain visible during write operations.
Before producing or substantially revising slides, ask the user to choose a generation execution mode:
```
快速批量生成
```
or
```
PowerPoint 可见逐页生成
```
. Preserve the existing fast batch-generation path; use visible progressive generation only when the user selects it.
Default to saving a new file. Never overwrite an original deck or template unless the user explicitly approves the exact output path and overwrite action.
Do not delete slides, discard originals, or perform broad replacements without explicit approval.

在读取、总结或审阅现有演示文稿前，需明确输入文件和只读操作意图，并获得用户明确确认；保持文件未修改状态。
在创建演示文稿、编辑幻灯片、导出PDF、导出幻灯片预览、复制模板或执行任何写入操作前，需展示预期的输入、输出、保存策略及操作内容；获得用户明确确认。
如果用户要求根据上传或指定的文档、PDF、报告或合成素材创建新演示文稿，无论是否提供模板，在生成
```
.pptx
```
文件前都需获得一份已获批的详细Markdown幻灯片规划。
如果用户已提供规划，需检查其是否具备足够的幻灯片级细节和必要的制作决策信息，展示存在的漏洞或需调整的内容，并请求用户批准使用该规划；若用户提供的规划足够完善，无需生成冗余的替代规划。
每次执行写入操作前，需询问用户是否要保持PowerPoint窗口可见。
在生成或大幅修改幻灯片前，需让用户选择生成执行模式：
```
快速批量生成
```
或
```
PowerPoint 可见逐页生成
```
。保留现有的快速批量生成路径；仅当用户选择时才使用可见渐进式生成模式。
默认保存为新文件。除非用户明确批准具体的输出路径和覆盖操作，否则绝不能覆盖原始演示文稿或模板。
未经明确批准，不得删除幻灯片、丢弃原始内容或进行大范围替换。

Toolchain

工具链

Primary execution path:

text

PowerShell or task-specific script
-> Windows COM
-> PowerPoint.Application
-> native PowerPoint objects and files

Prefer native PowerPoint objects for text, shapes, connectors, tables, charts, notes, images, themes, and layouts. Do not use

PptxGenJS

, raw PPTX XML editing, or a PowerPoint MCP server as the default generation/editing backend.

Read

references/powerpoint-com-operations.md

before writing task-specific COM automation or when diagnosing COM behavior.

主要执行路径：

text

PowerShell or task-specific script
-> Windows COM
-> PowerPoint.Application
-> native PowerPoint objects and files

优先使用PowerPoint原生对象处理文本、形状、连接线、表格、图表、备注、图片、主题和版式。默认生成/编辑后端不使用

PptxGenJS

、原始PPTX XML编辑或PowerPoint MCP服务器。

在编写特定任务的COM自动化脚本或诊断COM行为前，请阅读

references/powerpoint-com-operations.md

。

Generation Execution Modes

生成执行模式

```
快速批量生成
```
: Use the existing COM production flow to create or update the approved deck efficiently, then perform the required validation and QA.
```
PowerPoint 可见逐页生成
```
: Keep PowerPoint visible and make progress observable in the open presentation. Build the deck slide by slide, navigate to the slide currently being constructed, add its principal elements in meaningful stages, and save at safe checkpoints so the user can watch progress and intervene if needed.
Both modes use the same approved plan, content constraints, template rules, native editable PowerPoint objects, save policy, and final QA requirements.
Progressive generation is an execution/display option only. Do not reduce validation, introduce unsupported claims, or alter agreed visual/content decisions because the user selected it.

```
快速批量生成
```
：使用现有的COM生产流程高效创建或更新已获批的演示文稿，然后执行所需的验证和质量检查。
```
PowerPoint 可见逐页生成
```
：保持PowerPoint窗口可见，让用户可在打开的演示文稿中观察进度。逐页构建演示文稿，导航到当前正在制作的幻灯片，分阶段添加主要元素，并在安全检查点保存，以便用户监控进度并在需要时干预。
两种模式均使用相同的已获批规划、内容约束、模板规则、原生可编辑PowerPoint对象、保存策略和最终质量检查要求。
渐进式生成仅为执行/显示选项。不得因用户选择该模式而减少验证步骤、引入未支持的功能或改变已达成一致的视觉/内容决策。

Supported Work

支持的工作内容

Read slide titles, body text, notes, shape inventory, slide count, and basic layout information.
Summarize an existing deck or review it for structure, density, visual clarity, consistency, and likely presentation issues.
Create a presentation from a user outline, report, document, images, or content synthesized from supplied materials.
Copy and populate a template or revise an existing presentation.
Insert user-provided images and, when allowed, images generated by the currently available image generation tool.
Draw simple process diagrams, timelines, comparisons, and callout layouts as editable PowerPoint objects.
Create slides containing mathematical definitions, derivations, loss functions, metrics, quantization expressions, and other complex formulas with formula-specific verification.
Export PDF only when requested and confirmed.

读取幻灯片标题、正文文本、备注、形状清单、幻灯片数量和基本版式信息。
总结现有演示文稿，或审阅其结构、内容密度、视觉清晰度、一致性及潜在的演示问题。
根据用户大纲、报告、文档、图片或从提供素材中合成的内容创建演示文稿。
复制并填充模板，或修改现有演示文稿。
插入用户提供的图片，在允许的情况下，也可插入当前可用图像生成工具生成的图片。
将简单的流程图、时间线、对比图和标注布局绘制为可编辑的PowerPoint对象。
创建包含数学定义、推导、损失函数、指标、量化表达式及其他复杂公式的幻灯片，并进行公式专项验证。
仅在用户请求并确认后导出PDF。

Input and Content Planning

输入与内容规划

For creation tasks, establish:

Purpose, audience, speaking context, target duration, and expected slide count.
Input sources and whether claims, figures, or numbers must be reproduced exactly.
Whether a template or reference presentation exists.
Language, terminology constraints, font overrides, and output deliverables.
Whether the requested result is a quick draft or a formal deliverable.

When building from summarized content, convert material into a slide-level narrative before opening PowerPoint for production. Each slide should have one primary communication job. Do not invent missing claims, figures, citations, or data.

对于创建任务，需明确以下事项：

演示目的、受众、演讲场景、目标时长和预期幻灯片数量。
输入来源，以及是否需要精确重现声明、图表或数据。
是否存在模板或参考演示文稿。
语言、术语约束、字体覆盖规则和输出交付物。
请求的结果是快速草稿还是正式交付物。

基于总结内容创建演示文稿时，需先将素材转换为幻灯片级叙事内容，再打开PowerPoint进行制作。每张幻灯片应承担一个核心传达任务。不得编造缺失的声明、图表、引用或数据。

Source-Based Creation Planning Gate

基于素材创建的规划审核关卡

If the user supplies or identifies documents, PDFs, reports, or synthesized content and requests a new presentation, regardless of whether a

.pptx

.potx

template is provided:

Analyze the document before creating any presentation file.
If no plan is supplied, produce a detailed Markdown planning document and request approval.
If the user supplies a plan, review it rather than duplicating it: verify page count, per-slide content, source/evidence mapping, template usage if any, design requirements, and unresolved production decisions. Request approval after documenting necessary corrections or confirming it is adequate.
Name a newly generated plan
```
<topic>_ppt_plan.md
```
in the specified output directory, or in the current workspace if no output directory has yet been specified.
Include in a newly generated plan the source analysis, proposed page count, speaking duration when inferable or supplied, template mapping when a template exists, visual direction, color/font proposal, image-generation suggestion, and a detailed per-slide plan.
If reference images are also supplied for recreating PPT diagrams or layouts, include a content-to-visual mapping: source document facts first, reference image visual structure second, and the proposed mapping between document content and image-inspired PPT objects.
Make every accepted plan auditable: identify slide objective, core takeaway, intended on-slide content, data/evidence, visual presentation, source location, and unresolved questions or risks.
Even if the user requests a quick PPT draft, require an approved abbreviated but still reviewable plan before generating
```
.pptx
```
.
After plan approval, confirm the output/save/display/image/PDF options before performing COM write operations.

Read

references/document-to-deck-planning.md

whenever this workflow applies.

如果用户提供或指定了文档、PDF、报告或合成内容，并请求创建新演示文稿，无论是否提供

.pptx

或

.potx

模板：

在创建任何演示文稿文件前，先分析文档内容。
如果用户未提供规划，需生成一份详细的Markdown规划文档并请求用户批准。
如果用户提供了规划，需进行审核而非重复生成：验证页数、每页内容、来源/证据映射（若有）、模板使用情况（若有）、设计要求及未解决的制作决策。在记录必要的修正或确认规划足够完善后，请求用户批准。
将新生成的规划命名为
```
<topic>_ppt_plan.md
```
，保存到指定的输出目录；若未指定输出目录，则保存到当前工作区。
新生成的规划需包含素材分析、建议页数、可推断或用户提供的演讲时长（若有）、模板映射（若有模板）、视觉方向、颜色/字体建议、图片生成建议及详细的逐页幻灯片规划。
如果还提供了参考图片用于重现PPT图表或版式，需包含内容与视觉的映射关系：优先遵循源文档事实，其次参考图片的视觉结构，最后展示文档内容与图片启发的PPT对象之间的拟议映射。
确保每份获批的规划可审计：明确幻灯片目标、核心要点、预期幻灯片内容、数据/证据、视觉呈现、来源位置及未解决的问题或风险。
即使用户要求快速生成PPT草稿，在生成
```
.pptx
```
前也需获得一份已获批的、简短但仍可审阅的规划。
规划获批后，在执行COM写入操作前，需确认输出/保存/显示/图片/PDF选项。

当适用此工作流时，请阅读

references/document-to-deck-planning.md

。

Academic Presentation Coordination

学术演示协同

Only mention
```
nature-paper2ppt
```
when the input clearly concerns a paper, preprint, literature review, journal club, paper-sharing presentation, thesis/academic defense material, or comparable academic evidence-driven presentation.
For ordinary business, project, course, training, or general document-to-slide tasks, do not proactively mention
```
nature-paper2ppt
```
.
For a clear academic presentation task, check whether
```
nature-paper2ppt
```
is available. If installed, offer optional joint use and wait for the user's decision. If it is unavailable, explain its optional role and ask whether the user wants help installing it.
When jointly used,
```
nature-paper2ppt
```
supplies academic argument planning, evidence/figure selection, and slide narrative; this skill remains responsible for approved PowerPoint COM production, native-object refinement, and validation.
Do not automatically enable the joint workflow or install another skill without user confirmation.

仅当输入内容明确涉及论文、预印本、文献综述、期刊俱乐部、论文分享演示、论文/学术答辩材料或类似的学术证据驱动型演示时，才提及
```
nature-paper2ppt
```
。
对于普通商务、项目、课程、培训或通用文档转幻灯片任务，不得主动提及
```
nature-paper2ppt
```
。
对于明确的学术演示任务，需检查
```
nature-paper2ppt
```
是否可用。若已安装，可提供联合使用的可选方案并等待用户决策。若未安装，需说明其可选作用，并询问用户是否需要协助安装。
联合使用时，
```
nature-paper2ppt
```
负责学术论证规划、证据/图表选择和幻灯片叙事；本技能负责已获批的PowerPoint COM制作、原生对象优化和验证。
未经用户确认，不得自动启用联合工作流或安装其他技能。

Template Workflow

模板工作流

If the user provides a template or existing deck, strictly prefer its established system:

Master/layout choices, theme colors, font family, header/footer treatment, spacing, and recurring visual patterns take precedence over default styling.
First inspect the deck structure and reusable layouts; then map the requested content to suitable pages or layouts.
Work on a confirmed output copy unless the user explicitly approves direct modification.
Preserve editable native objects wherever practical.

Read

references/template-workflow.md

when a template, branded deck, existing presentation, or visual reference is provided.

如果用户提供了模板或现有演示文稿，需严格遵循其既定规范：

母版/版式选择、主题颜色、字体族、页眉/页脚处理、间距和重复视觉模式优先于默认样式。
首先检查演示文稿结构和可复用版式；然后将请求的内容映射到合适的页面或版式。
除非用户明确批准直接修改，否则需在已确认的输出副本上进行操作。
尽可能保留可编辑的原生对象。

当提供模板、品牌演示文稿、现有演示文稿或视觉参考时，请阅读

references/template-workflow.md

。

Language and Typography

语言与排版

Detect the language from the task. Chinese tasks default to Simplified Chinese.
Preserve English technical terminology, abbreviations, model names, dataset names, formulas, and code where meaningful.
Typography precedence: user-specified fonts > template font system > defaults below.

Default fonts when no template or override applies:

Content	Font
Chinese title	Microsoft YaHei Bold
Chinese body, captions, sources	Microsoft YaHei
English title/body and numerals	Times New Roman
Code	Consolas

Default minimum sizing guidance:

Element	Size
Cover title	30-44 pt
Slide title	26-36 pt
Section heading	20-24 pt
Body	16 pt minimum
Caption/source	10-11 pt minimum
Key metric	40-64 pt

Read

references/typography-and-layout-zh.md

before designing a deck without a complete template, or when fixing typography/layout problems.

从任务中检测语言。中文任务默认使用简体中文。
保留有意义的英文技术术语、缩写、模型名称、数据集名称、公式和代码。
排版优先级：用户指定字体 > 模板字体系统 > 以下默认设置。

无模板或覆盖规则时的默认字体：

内容	字体
中文标题	微软雅黑粗体
中文正文、说明文字、来源	微软雅黑
英文标题/正文及数字	Times New Roman
代码	Consolas

默认最小字号参考：

元素	字号
封面标题	30-44 pt
幻灯片标题	26-36 pt
章节标题	20-24 pt
正文	最小16 pt
说明文字/来源	最小10-11 pt
关键指标	40-64 pt

在无完整模板的情况下设计演示文稿，或修复排版/布局问题前，请阅读

references/typography-and-layout-zh.md

。

Complex Formulas and Mathematical Accuracy

复杂公式与数学准确性

Before writing complex formulas, establish a formula baseline from the user-provided expression, source material, or an explicitly approved correction. Record unresolved operator, index, delimiter, and symbol ambiguities before production.
Prefer editable native Office Math equations in PowerPoint for fractions, sums, integrals, matrices, subscripts/superscripts, hats, absolute values, conditional probability, aligned expressions, and multi-step derivations.
Do not typeset complex formulas as ordinary text boxes merely because plain text is easier to automate. If native equation creation cannot be completed reliably, stop and request approval for a clearly labeled vector-formula fallback.
Treat formula correctness as content integrity: do not silently rewrite mathematical definitions, change normalization factors, replace operators such as
```
round
```
,
```
floor
```
, or
```
clip
```
, or infer missing bounds without confirmation.
For formal presentations containing formulas, perform formula-specific QA after preview rendering: compare each rendered equation against the approved baseline and verify fractions, exponents, indices, summation limits, hats, absolute values, conditional bars, brackets, operators, minus signs, and surrounding interpretation text.
If a formula uses data values, constants, or reported results, verify those values against the approved source in addition to checking rendering.

Read

references/formula-workflow.md

whenever a slide contains complex formulas or formula-derived explanation.

在编写复杂公式前，需从用户提供的表达式、素材或明确批准的修正内容中建立公式基准。在制作前记录未解决的运算符、索引、分隔符和符号歧义。
对于分数、求和、积分、矩阵、下标/上标、符号帽、绝对值、条件概率、对齐表达式和多步推导，优先使用PowerPoint中可编辑的原生Office Math公式。
不得仅因纯文本更易于自动化，就将复杂公式排版为普通文本框。若无法可靠完成原生公式创建，需停止操作并请求用户批准使用明确标记的矢量公式替代方案。
将公式正确性视为内容完整性的一部分：不得擅自重写数学定义、更改归一化因子、替换
```
round
```
、
```
floor
```
或
```
clip
```
等运算符，或在未确认的情况下推断缺失的边界。
对于包含公式的正式演示文稿，在预览渲染后需进行公式专项质量检查：将每个渲染后的公式与已批准的基准进行对比，验证分数、指数、索引、求和极限、符号帽、绝对值、条件栏、括号、运算符、减号及周边解释文本。
如果公式使用了数据值、常量或报告结果，除检查渲染效果外，还需验证这些值与已批准的来源是否一致。

当幻灯片包含复杂公式或基于公式的解释时，请阅读

references/formula-workflow.md

。

Visual and Layout Principles

视觉与布局原则

Give every slide a clear focal point; avoid dense text dumps.
Avoid a monotonous sequence of identical title-plus-bullets slides.
Left-align body text and lists by default; align titles according to the template or intended composition.
Maintain consistent margins, spacing, grid alignment, and visual hierarchy.
Keep text and icon contrast high enough for projection and ordinary displays.
Use images, diagrams, data displays, or purposeful shapes only when they strengthen the message.
Avoid generic decoration such as repeated ornamental title underlines unless the supplied template requires it.

每张幻灯片需有明确的焦点；避免密集的文本堆砌。
避免单调的“标题+项目符号”幻灯片序列。
默认左对齐正文文本和列表；标题对齐方式遵循模板或预期布局。
保持一致的边距、间距、网格对齐和视觉层次。
确保文本和图标具有足够的对比度，适用于投影和普通显示屏。
仅当图片、图表、数据展示或特定形状能强化信息传达时才使用它们。
避免通用装饰，如重复的装饰性标题下划线，除非提供的模板要求。

Images, Figures, and Diagrams

图片、图表与图形

Read

references/reference-image-diagram-recreation.md

when the task involves imitating, recreating, redrawing, or making a PPT version of a reference image, paper figure, architecture diagram, relation map, screenshot, or visual draft.

User image folders:

Read image assets only from directories or files the user identifies for the task.
Do not silently substitute or alter evidence figures.

Image-reference recreation:

When the user asks to imitate, recreate, redraw, or make a PPT version of a diagram, chart, layout, screenshot, draft, or visual reference image, first produce a short interpretation plan and obtain confirmation before creating or editing slides.
The interpretation plan must identify the reference image, intended slide/page target, visible text to reproduce, diagram structure, key shapes, colors, approximate layout, editable-object goal, and any illegible or ambiguous content.
If the user supplies documents, PDFs, reports, or notes together with reference images, treat the documents as the content authority and the images as visual/layout references unless the user explicitly says otherwise.
In that combined case, analyze the documents first, extract the facts/terms/relationships to be shown, then interpret the reference image, then present a source-to-visual mapping for approval before production.
Ask whether the goal is faithful visual recreation, editable conceptual recreation, or stylistic inspiration. Do not assume exact copying is desired when the user only provides an image.
Do not invent missing labels, data values, axis text, legends, formulas, or relationships from the image. Mark uncertain content and request user confirmation or source material.
Default to PowerPoint COM native editable objects only for simple diagrams and ordinary flowcharts where the object count, arrows, and layout are easy to control.
For slightly complex diagrams, module diagrams, relation maps, architecture sketches, or diagrams with non-trivial arrows/groups, prefer the installed draw.io capability when available. Do not modify draw.io skill/tool rules; use it as the diagram authoring backend.
Draw.io workflow: use the draw.io skill/capability to create the source diagram, use the local draw.io application to export both SVG and PNG, inspect the PNG for layout/visual QA, and inspect the SVG text/rendering for mojibake, missing labels, and PowerPoint compatibility before importing into PowerPoint.
A draw.io-exported SVG is PPT-compatible only if it has no visible mojibake/missing labels and does not contain unsupported HTML text fallbacks such as
```
foreignObject
```
, embedded
```
data:image
```
label fallbacks, or the draw.io warning text
```
Text is not SVG - cannot display
```
. If any of these appear, treat the SVG as not suitable for PPT insertion.
Import the draw.io-exported SVG into PowerPoint through COM only after the SVG passes the no-mojibake/no-missing-label and PPT-compatibility checks. Keep the PNG as a preview/reference artifact for QA.
If the SVG is invalid, visually broken in PowerPoint, has mojibake, drops labels, contains unsupported HTML/foreignObject text, or otherwise fails the SVG check, use the draw.io-exported PNG as the PPT fallback after telling the user that the inserted diagram will be a raster image and not conveniently editable inside PowerPoint.
If draw.io software or the draw.io skill/capability is not installed or unavailable, tell the user and ask whether to install/enable it or fall back to PowerPoint COM native drawing/SVG generation.
For dense paper figures, relation maps, multi-branch taxonomy diagrams, or diagrams with many small labels/edges, use a diagram-first workflow: produce a diagram specification, render it as SVG/draw.io/vector artwork when high visual fidelity matters, then insert it into PowerPoint through COM.
Before producing a complex recreated diagram, ask the user to confirm one production mode:
```
高保真视觉复刻
```
(SVG/vector inserted, limited PPT editability),
```
PPT 原生可编辑简化版
```
(editable but less faithful), or
```
混合版
```
(vector base plus editable labels/callouts where practical). If a non-native/vector/image path is chosen, explicitly state which parts will not be conveniently editable in PowerPoint.
The diagram specification must list nodes, visible text, hierarchy/regions, connector directions, colors, approximate layout, source-to-visual mapping, and any uncertain labels. Obtain approval for this specification before rendering.
For COM-native recreated diagrams, the specification must also include connector routing, object layering, drawing order, and special-symbol handling before writing the automation script.
If the user wants a new diagram inspired by a reference image and based on documents, the documents define content and relationships; the reference image defines only visual grammar unless the user explicitly says to copy its content.
For formal outputs based on a reference image, include reference-image comparison in QA: check text, labels, hierarchy, directionality, relative placement, color intent, aspect ratio, alignment, and whether any approved ambiguities remain unresolved.

Generated images:

Use the currently available image generation capability only after the user permits generated imagery for the deck.
Suitable uses: cover visual, background, section divider, conceptual illustration, non-factual decoration.
Never use generated visuals as experimental results, paper evidence, product screenshots, real-world measurements, statistical plots, or text-heavy factual diagrams.
Keep slide text as native PowerPoint text, not baked into generated imagery.

Diagram defaults:

Diagram	Production path
Very simple diagram or ordinary flowchart	Editable native PowerPoint shapes/connectors through COM
Slightly complex module diagram, relation map, architecture sketch, or grouped arrow diagram	Prefer draw.io skill/source; export SVG and PNG with draw.io software, verify PNG layout and SVG text, import SVG if valid, otherwise insert PNG fallback with editability warning
Complex architecture, dense relation map, or paper taxonomy figure	Use draw.io/SVG/vector workflow, then insert into PowerPoint after confirming editability tradeoff
Fully editable complex diagram explicitly requested	Use native objects as far as practical and explain tradeoffs

当任务涉及模仿、重现、重绘参考图片、论文图表、架构图、关系图、截图或视觉草稿的PPT版本时，请阅读

references/reference-image-diagram-recreation.md

。

用户图片文件夹：

仅从用户为任务指定的目录或文件中读取图片资源。
不得擅自替换或修改证据图表。

参考图片重现：

当用户要求模仿、重现、重绘图表、布局、截图、草稿或视觉参考图片的PPT版本时，需先生成一份简短的解读规划并获得确认，再创建或编辑幻灯片。
解读规划需明确参考图片、预期幻灯片/页面目标、需重现的可见文本、图表结构、关键形状、颜色、大致布局、可编辑对象目标及任何难以辨认或模糊的内容。
如果用户同时提供了文档、PDF、报告或笔记与参考图片，除非用户明确说明，否则将文档视为内容权威，图片视为视觉/布局参考。
在这种组合情况下，需先分析文档，提取要展示的事实/术语/关系，然后解读参考图片，最后提交一份来源与视觉的映射方案供批准后再进行制作。
需询问用户目标是高保真视觉复刻、可编辑的概念性重现还是风格灵感参考。当用户仅提供图片时，不得假设需要精确复制。
不得从图片中编造缺失的标签、数据值、轴文本、图例、公式或关系。标记不确定的内容并请求用户确认或提供素材。
对于简单图表和普通流程图，默认仅使用PowerPoint COM原生可编辑对象，因为其对象数量、箭头和布局易于控制。
对于稍复杂的图表、模块图、关系图、架构草图或包含大量箭头/分组的图表，若可用则优先使用已安装的draw.io功能。不得修改draw.io技能/工具规则；将其作为图表创作后端使用。
draw.io工作流：使用draw.io技能/功能创建源图表，使用本地draw.io应用导出SVG和PNG，检查PNG的布局/视觉质量，检查SVG的文本/渲染是否存在乱码、缺失标签及PowerPoint兼容性，然后再导入PowerPoint。
只有当draw.io导出的SVG无可见乱码/缺失标签，且不包含不支持的HTML文本替代方案（如
```
foreignObject
```
、嵌入的
```
data:image
```
标签替代方案或draw.io警告文本
```
Text is not SVG - cannot display
```
）时，才视为与PPT兼容。若存在上述情况，则该SVG不适合插入PPT。
仅在SVG通过无乱码/无缺失标签和PPT兼容性检查后，才通过COM将其导入PowerPoint。将PNG保留为预览/参考工件用于质量检查。
如果SVG无效、在PowerPoint中视觉损坏、存在乱码、丢失标签、包含不支持的HTML/foreignObject文本或未通过SVG检查，则使用draw.io导出的PNG作为PPT替代方案，并告知用户插入的图表将是光栅图像，无法在PowerPoint中方便地编辑。
如果draw.io软件或draw.io技能/功能未安装或不可用，需告知用户并询问是否要安装/启用它，或退回到PowerPoint COM原生绘图/SVG生成。
对于密集的论文图表、关系图、多分支分类图或包含许多小标签/边的图表，需使用图表优先工作流：生成图表规范，当需要高视觉保真度时将其渲染为SVG/draw.io/矢量图，然后通过COM插入PowerPoint。
在制作复杂的复刻图表前，需让用户确认一种制作模式：
```
高保真视觉复刻
```
（插入SVG/矢量图，PPT可编辑性有限）、
```
PPT 原生可编辑简化版
```
（可编辑但保真度较低）或
```
混合版
```
（矢量基础加上可编辑的标签/标注，在可行的情况下）。若选择非原生/矢量/图像路径，需明确说明哪些部分无法在PowerPoint中方便地编辑。
图表规范需列出节点、可见文本、层次/区域、连接线方向、颜色、大致布局、来源与视觉的映射关系及任何不确定的标签。在渲染前需获得批准。
对于COM原生复刻图表，规范还需包含连接线路由、对象分层、绘制顺序和特殊符号处理，然后才能编写自动化脚本。
如果用户想要基于文档并受参考图片启发的新图表，文档定义内容和关系；参考图片仅定义视觉语法，除非用户明确说明要复制其内容。
对于基于参考图片的正式输出，质量检查需包含参考图片对比：检查文本、标签、层次、方向性、相对位置、颜色意图、宽高比、对齐方式及是否存在未解决的已批准歧义。

生成的图片：

仅在用户允许为演示文稿使用生成图像后，才可使用当前可用的图像生成功能。
适用场景：封面视觉、背景、章节分隔符、概念插图、非事实性装饰。
绝不能将生成的视觉内容用作实验结果、论文证据、产品截图、实际测量数据、统计图表或包含大量文本的事实性图表。
幻灯片文本需保留为PowerPoint原生文本，不得嵌入到生成的图像中。

图表默认制作路径：

图表类型	制作路径
极简单图表或普通流程图	通过COM使用可编辑的PowerPoint原生形状/连接线
稍复杂的模块图、关系图、架构草图或分组箭头图	优先使用draw.io技能/源；使用draw.io软件导出SVG和PNG，验证PNG布局和SVG文本，若SVG有效则导入，否则插入PNG替代方案并告知可编辑性限制
复杂架构图、密集关系图或论文分类图	使用draw.io/SVG/矢量工作流，确认可编辑性权衡后插入PowerPoint
明确要求完全可编辑的复杂图表	尽可能使用原生对象并说明权衡点

Required Confirmation Before Writes

写入前的必要确认

Before any creation, edit, copy, export, or preview-render operation, present and confirm:

Input deck/template/materials.
Proposed output path and file name.
Whether work is performed on a copy.
Whether any existing file will be overwritten; recommend no overwrite.
Whether PowerPoint should remain visible during execution.
Whether PDF export is needed.
Whether generated images or a specified image directory may be used.
For image-reference recreation, whether the image interpretation plan and uncertain text/data have been approved.
For document-plus-reference-image recreation, whether the source-to-visual mapping has been approved and any conflict between source content and image appearance has been resolved.
Whether the output is a quick draft or formal presentation.

Generation execution mode:

快速批量生成

PowerPoint 可见逐页生成

For source-based creation of a new deck, whether a detailed Markdown plan has been approved, either newly generated or user-supplied and reviewed.

在执行任何创建、编辑、复制、导出或预览渲染操作前，需展示并确认以下内容：

输入演示文稿/模板/素材。
拟议的输出路径和文件名。
是否在副本上进行操作。
是否会覆盖现有文件；建议不要覆盖。
执行过程中是否保持PowerPoint窗口可见。
是否需要导出PDF。
是否可使用生成的图片或指定的图片目录。
对于参考图片重现任务，图片解读规划和不确定的文本/数据是否已获批。
对于文档加参考图片的重现任务，来源与视觉的映射是否已获批，且源内容与图片外观之间的任何冲突是否已解决。
输出是快速草稿还是正式演示文稿。

生成执行模式：

快速批量生成

或

PowerPoint 可见逐页生成

。

对于基于素材创建新演示文稿的任务，详细的Markdown规划是否已获批（无论是新生成的还是用户提供并审核后的）。

Validation and QA

验证与质量检查

Read

references/visual-qa.md

for checks and execution details.

Quick draft:

Save successfully.
Reopen or open with PowerPoint to confirm the presentation is readable.
Confirm expected slide count and principal content were produced.
Do not require full-slide preview inspection unless a visible problem is found.

Formal presentation:

Confirm it opens successfully.
Produce a preview of the deck for visual inspection.
Perform one full-deck visual review.
When slides recreate a reference image, compare the preview against the approved interpretation plan and reference image.
When formulas are present, perform formula-specific comparison against the approved formula baseline.
Fix discovered issues.
Recheck affected slides after fixes before delivery; a repair is not complete until a new preview or equivalent visual check confirms the repaired slide.
Limit formal visual QA to at most two preview/check cycles unless the user explicitly asks to continue. If the second QA pass still shows that the slide or diagram has not reached the approved target, stop, explain the remaining mismatch, and recommend the next production mode or required source material instead of continuing blind patching.
For draw.io-based diagrams, QA must include both the exported PNG preview and the SVG text/rendering check before importing or delivering the PPT. If SVG import is rejected and PNG fallback is used, the final PPT preview must be checked again with the inserted PNG.
For complex recreated diagrams, if repeated repair cycles still fail to match the approved specification closely enough within the two-QA limit, stop and report the remaining mismatch and the recommended next production mode.

有关检查和执行细节，请阅读

references/visual-qa.md

。

快速草稿：

保存成功。
重新打开或用PowerPoint打开，确认演示文稿可读。
确认生成了预期的幻灯片数量和主要内容。
除非发现可见问题，否则无需进行全幻灯片预览检查。

正式演示文稿：

确认可成功打开。
生成演示文稿预览供视觉检查。
执行一次全演示文稿视觉审阅。
当幻灯片重现参考图片时，将预览与已批准的解读规划和参考图片进行对比。
当包含公式时，将其与已批准的公式基准进行专项对比。
修复发现的问题。
修复后重新检查受影响的幻灯片；只有通过新的预览或等效的视觉检查确认修复后的幻灯片符合要求，修复才算完成。
正式视觉质量检查最多进行两次预览/检查循环，除非用户明确要求继续。如果第二次质量检查仍显示幻灯片或图表未达到已批准的目标，需停止操作，说明剩余的不匹配情况，并建议下一种制作模式或所需素材，而非继续盲目修补。
对于基于draw.io的图表，质量检查必须包括导出的PNG预览和SVG文本/渲染检查，然后才能导入或交付PPT。如果SVG导入被拒绝而使用PNG替代方案，最终的PPT预览需再次检查插入的PNG。
对于复杂的复刻图表，如果重复修复循环仍无法在两次质量检查限制内足够接近已批准的规范，需停止操作并报告剩余的不匹配情况及建议的下一种制作模式。

Bundled Scripts

捆绑脚本

```
scripts/test_powerpoint_com.ps1
```
: verify that PowerPoint COM is available without saving a file.
```
scripts/inspect_presentation.ps1
```
: read-only slide/text/shape inventory for an explicitly identified deck.
```
scripts/copy_template.ps1
```
: make a safe working copy after write approval.
```
scripts/export_preview.ps1
```
: export slide PNG previews after write/export approval.

For substantive generation and edits, write a task-specific PowerShell script in the user workspace after confirmation, using the references and the requested presentation structure. Keep reusable scripts safe and narrowly scoped rather than attempting to encode every possible design operation.

```
scripts/test_powerpoint_com.ps1
```
：验证PowerPoint COM是否可用，无需保存文件。
```
scripts/inspect_presentation.ps1
```
：对明确指定的演示文稿进行只读的幻灯片/文本/形状清单检查。
```
scripts/copy_template.ps1
```
：获得写入批准后创建一个安全的工作副本。
```
scripts/export_preview.ps1
```
：获得写入/导出批准后导出幻灯片PNG预览。

对于实质性的生成和编辑操作，在获得确认后，需根据参考文档和请求的演示文稿结构，在用户工作区编写特定任务的PowerShell脚本。保持可复用脚本安全且范围狭窄，而非试图编码所有可能的设计操作。

Delivery

交付

Primary output is
```
.pptx
```
.
Export
```
.pdf
```
only when requested and confirmed.
Report output paths, whether the original file remained untouched, the validation level performed, and any unresolved visual or content risks.
If the work created task-specific PowerShell scripts (
```
.ps1
```
) or preview artifacts that are not required final deliverables, tell the user they are intermediate files and ask whether to keep or delete them; never delete them without explicit confirmation.

主要输出为
```
.pptx
```
文件。
仅在用户请求并确认后导出
```
.pdf
```
文件。
报告输出路径、原始文件是否未被修改、执行的验证级别及任何未解决的视觉或内容风险。
如果工作创建了特定任务的PowerShell脚本（
```
.ps1
```
）或非必需最终交付物的预览工件，需告知用户这些是中间文件，并询问是否保留或删除；未经明确确认不得删除。