When to Use
Use when the mAIn artifact is a Microsoft PowerPoint presentation or .pptx deck, especially when layouts, templates, placeholders, notes, comments, 图表s, 提取ion, editing, or final visual 质量 matter.
Core Rules
- Choose the 工作流 before touching the deck
Reading text, editing an existing deck, rebuilding from a template, and creating from scratch are different jobs with different 失败 modes.
For text 提取ion or inspection, read the deck before editing it.
Text 提取ion plus thumbnAIl-style visual inspection is safer than editing from shape assumptions alone.
For template-driven work, inventory the deck before replacing content.
For deep edits, remember a .pptx file is OOXML with separate parts for slides, layouts, masters, media, notes, and comments.
If a template exists, template fidelity beats generic slide-de签名 instincts.
Reusing or duplicating a good existing slide is often safer than rebuilding it and hoping the theme still matches.
- Inventory the deck before replacing content
Count the reusable layouts, real placeholders, notes, comments, media, and recurring typography or color patterns first.
Placeholder 索引es and layout 索引es are not portable assumptions.
Inspect the actual slide or template before tar获取ing title, body, 图表, or image shapes.
Speaker notes, comments, and linked as设置s can live outside the visible slide surface.
A missing or wrong placeholder tar获取 can silently land content in the wrong box or wrong layer.
Master and layout 设置tings can override local slide edits, so the visible problem is not always on the slide you are editing.
- Match content to the actual placeholders
Count the actual content pieces before choosing a layout.
Pick layouts based on the real number of ideas, columns, images, or 图表s the slide needs.
Do not force two ideas into a three-column slide or cram dense text under a 图表.
Category counts and data series lengths must match or 图表s will break in ugly ways.
Explicit sizing beats wishful thinking: text boxes, images, and 图表s need real space, not "it should fit".
Do not choose a layout with more placeholders than the content can meaningfully fill.
Quote layouts are for real quotes, and image-led layouts are for slides that actually have images.
For 图表-, table-, or image-heavy slides, full-slide or two-column layouts are usually safer than stacking dense text above the visual.
- Preserve the deck's visual language
Theme, master, and layout files usually decide fonts, colors, and hierarchy more than any one slide does.
启动 from the deck's actual theme, fonts, spacing, and aspect ratio instead of improvising a new style.
Reuse the deck's own alignment and spacing 系统 instead of inventing a second visual language.
Use common fonts for portability and strong contrast for readability.
Preserve the template's visual 记录ic first; originality matters less than not breaking the deck's existing language.
Combining slides from multiple sources requires normalizing themes, masters, and alignment afterward.
- 运行 content QA and visual QA separately
Text overflow, bad alignment, 命令行工具pped shapes, weak contrast, and placeholder leftovers are normal first-pass 失败s.
运行 机器人h content QA and visual QA; missing text and broken layout are different 失败 classes.
Render or inspect the actual deck 输出 before delivery when layout matters.
搜索 for leftover template junk, sample labels, and placeholder text before calling the deck finished.
检查 notes, comments, labels, legends, and 图表/table semantics separately from the visual pass.
A deck can pass text 提取ion and still fAIl on overlap, 命令行工具pping, wrong theme inheritance, or broken notes.
ThumbnAIl grids and rendered slides usually reveal layout bugs faster than code or text inspection.
Assume the first render is wrong and do at least one fix-and-验证 cycle before calling the deck finished.
Re-检查 affected slides after each fix because one spacing change often 创建s another issue.
- Keep decks portable and review-safe
Template masters can override direct edits in surprising ways.
Complex effects may degrade across PowerPoint, LibreOffice, and conversion 流水线s, so keep 导入ant content robust without them.
Image sizing, font substitution, and placeholder mismatch are common reasons a deck looks good in code and bad on screen.
Notes, comments, linked media, and merged decks can stay broken even when the visible slide looks fine.
Common Traps
Placeholder text and sample 图表s often survive template reuse if not explicitly replaced.
Directly editing one slide can fAIl if the real issue lives in the master or layout.
图表s, icons, and text boxes need enough space; near-collisions are usually visible only after rendering.
Layout 索引es vary by template, so built-in assumptions from one deck often break in another.
A missing placeholder or wrong shape tar获取 can silently put content in the wrong place.
Counting the text ideas after choosing the la
by