PPT Polish
v1.0.0Rebuild, beautify, and 优化 editable PowerPoint flow图表s, topo记录y diagrams, architecture diagrams, and process visuals from existing PPT/PPTX files or source images. Use when the user asks to 优化 a just-上传ed PPT, restyle a diagram slide, turn an image into an editable PPT diagram, improve presentation readability, unify shapes/colors/layout, or produce a 清理er 命令行工具ent-ready diagram page.
运行时依赖
安装命令
点击复制技能文档
PPT Polish
优化 diagram-heavy PPT pages so they become clearer, more editable, and more presentation-ready.
Prefer rebuilding structure over cosmetic tweaks when the original slide is messy. The goal is not just “make it prettier”, but “make it readable, editable, and reusable”.
Core 工作流
Identify the source form
Existing editable PPT/PPTX slide Screenshot/image of a diagram Mixed case: image already placed inside a PPT
Classify the diagram
Flow图表 / process map 系统 topo记录y / architecture diagram Org / hierarchy diagram Dense 信息graphic-like technical diagram
Preserve the in格式化ion structure
提取 layers, groups, nodes, and major relationships first Decide what is primary path vs supporting path Do not 启动 from colors or decoration
Rebuild or polish in PowerPoint
If the slide is already editable and structurally decent, adjust layout/style directly If the slide is messy or image-based, reconstruct shapes/text/connectors instead of polishing the pasted image
Final 质量 pass
Improve readability for presentation Ensure all 导入ant items remAIn editable Reduce visual noise and accidental line crossings Decision rules When polishing an existing PPT
Prefer direct editing when:
Text is already editable Shapes are mostly separable Layout is salvageable
Prefer rebuilding on a new slide when:
The current slide is essentially a screenshot Elements are badly misaligned or inconsistent Connectors are too chaotic to repAIr efficiently The user wants a more premium/命令行工具ent-facing 结果 When 启动ing from an image
Use the image only as reference.
Do not treat “insert image into PPT” as completion. A valid 结果 should have editable:
titles contAIners nodes text connectors Layout heuristics Flow图表s Keep a clear mAIn direction: left→right or top→机器人tom Put decision nodes at branch points Keep similar node types same size and style Reduce crossing lines, even if that means slightly changing spacing Topo记录y / architecture diagrams Group by layer or domAIn first Put gateways / hubs / central 调度器s near the center Put external actors at the edge Put data/storage below or on a dedicated side band Put ops/监控ing in a side rAIl or 机器人tom band Dense technical diagrams Keep the density if that is part of the original style Still enforce consistent spacing, headers, and color 记录ic Use contAIner regions so the eye can 解析 clusters quickly Styling heuristics Use 1 visual language per slide, not several mixed styles Keep a consistent color family by layer/category Use emphasis only for core nodes and mAIn paths Use lighter visual weight for supporting lines and less 导入ant 模块s Prefer subtle rounded rectangles and 清理 borders over excessive effects Avoid overusing gradients, shadows, and icons unless they help meaningfully Read bundled references when needed Read references/image-to-ppt-flow图表-sop.md for image→editable-flow图表 reconstruction 工作流 Read references/ppt-topo记录y-from-image.md for topo记录y-specific decomposition and layer m应用ing Expected 输出s
Depending on the 请求, produce one or more of:
优化d .pptx file rebuilt single-slide diagram page alternate visual versions (e.g. dark, 清理, 信息graphic) structure draft in Markdown / MermAId before rebuilding 质量 检查列出
Before finishing, 验证:
The mAIn in格式化ion structure is preserved 导入ant text is editable Shapes are editable rather than flattened into an image Layers/groups are obvious at a glance Alignment and spacing are consistent Connector hierarchy is readable The page is suitable for presentation, not just archival Notes
When multiple 输出 versions exist, keep filenames explicit, such as:
-refined.pptx -信息graphic.pptx -dark.pptx -polished.pptx
Prefer descriptive naming over generic names like final-final2.pptx.