oil-ppt

oil-ppt

Make the presentation as a set of independent HTML pages. First determine what each page should show, then create the visuals; pages have few words, the main visual is clear, and it can be seen clearly during projection. Use the scripts/oil-ppt command under this Skill's relative path. When modifying audience-visible copy, also use oil-tone。

Outline: only write what each page does

outline.md is a page-by-page checklist for the user. For each page, write a title and a one-sentence visual description; only add a sentence if there are facts or material requirements that truly affect that page. Do not write audience analysis, viewing scenarios, creative rationale, narrative suggestions, verification checklists, or instructions for the model, and do not add a summary page just to appear complete. During actual production, the number and order of pages can be adjusted.

The outline content should directly answer: "What does page X talk about, and what does the audience mainly see?" For example:

1. 旧版分工：用一张图展示四种角色及原来的模型。
2. 新版分工：四种角色分别负责什么、使用什么模型。
3. 一个任务怎样选角色：画出按任务选择的分支。

Page: visuals first, text second

• Each page covers only one judgment or relationship. First choose screenshots, charts, flows, comparisons, or conceptual visuals, then decide which words are needed. For specific drawing methods and components, see references/components.md。
• By default, there is only a short title and the main visual. Eyebrow text, subtitles, captions, sources, and footnotes are all optional: delete text that would not be misunderstood if removed, do not write production notes or spoken narration arrangements into the page, and do not replace them with small pill-shaped text.
• When it is hard to see clearly, first delete repeated explanations, enlarge the main visual, or split the page; do not cram content in by shrinking the font size, and do not delete necessary facts, causes, impacts, or steps from the material just to be short. Handle the retained text according to references/components.md 's font size specifications.
• Keep real screenshots, data, and quotations faithful; conceptual diagrams must not pretend to be real interfaces or measured results. Do not fabricate facts that are not in the material.
• Choose materials according to the visual's responsibility: use official logos to identify real products, use consistent function icons to explain operations, use real screenshots to present facts, use HTML/CSS/SVG for accurate relationships, and use oil-visualfor abstract actions and object metaphors. These materials can together form one page; for selection details, see references/media.md。
• Do not first lay out a row of equal-weight cards and then fill in text. When the visual needs to express order, comparison, or causality, directly use tracks, columns, connecting lines, or primary-secondary relationships.

Start and continue

New project:

scripts/oil-ppt init <项目>
scripts/oil-ppt status <项目> --json

For an existing project, first run scripts/oil-ppt status <项目> --json; when the user names a specific page to modify, add --intent edit --slide <页码或ID>. When you need to find multiple projects, use scripts/oil-ppt batch <项目或父目录> [更多项目或父目录]。

status、slide check and batch only read the project; only for formal preview or when modifying pages or themes via commands do you synchronize the runtime files bundled with the Skill.

According to the returned next , do one thing, then after completion execute the command it provides and re-read the status. Once the outline is written, you can continue production. Do not modify the generated 预览.html or 演示文稿.html; page content is in slides/<id>.html, and order is in deck.json. Formal preview is confirmed by the user.

• edit_outline: only edit next.path, write the page-by-page checklist, and after completion execute next.rerun。
• author_slides: based on next.brief , make one real page at a time, and after completion rerun status; once the pages are complete, then execute next.command_when_ready。
• edit_slide: only edit next.path, fix next.issues, then execute next.rerun。
• fix_media: only handle next.path the referenced page and related assets, fix next.issues, then run next.rerun。
• run_command: run next.command。
• ask_user_to_confirm_preview: display next.artifact; after user confirmation, run next.command_on_confirm, and if there is page feedback, revise the corresponding page.
• complete: the demo is complete.

make one page

When making a page for the first time, read references/components.md, and afterwards consult the relevant sections as needed. First look at the starter directory and choose the one closest to this page's visuals; the starter is only a starting point, and sample text, numbers, images, and extra decorations must all be replaced or deleted.

scripts/oil-ppt starter list --json
scripts/oil-ppt starter show <名称>
scripts/oil-ppt slide add <项目> <页面ID> --title "<标题>" [--starter <名称>] [--after <页面ID>]

Edit only the returned slides/<id>.htmlfor one page. Check the original size and the presentation scaling effect: the main visual is large enough, the text is readable, images are not mistakenly cropped, and there is no useless small text or sample content. Then run status to fix the actual problems it reports. Page order can be adjusted with slide move, and pages can be deleted with slide remove。

First determine this page's judgment, the role of the assets, and the layout positions, then obtain or generate the assets; after placing them back on the page, check the actual size of the main subject and the alignment of labels, and finally add a small amount of decoration for service level and rhythm. Do not first generate images in bulk and then look for placement positions.

When external assets, official logos, or function icons are needed, read references/media.md; for conceptual illustrations, read references/illustration.md and use oil-visual; for HTML/CSS/SVG explanatory diagrams, read references/programmatic-visuals.md. If you encounter build or export failures, then read references/troubleshooting.md。

Check and deliver

Before presenting, look at the full set of thumbnails and confirm that each page's visuals are distinguishable, the necessary content is covered, and there is no sample copy, placeholder visuals, fake sources, or information drowned out by cards and small text. The program's checks for structure, resource paths, overflow, and minimum font size are technical checks;style_advice is for reference only, do not treat it as a gate to check off item by item, and do not add decoration or pages to satisfy suggestions.

The full set of thumbnails is used to check whether the visual rhythm, color scheme, and icons are consistent; for pages that have been rearranged or newly illustrated, look again at the original size to check transparent edges, subject size, cropping, and text alignment. When you find a problem, first determine whether it is caused by the layout, asset whitespace, or generated content, then fix the corresponding part; only re-verify the changed page and its effects, and do not repeatedly generate because of transparent blank edges inherent to the assets.

After the formal preview is confirmed, continue building according to the status. Run scripts/oil-ppt export-pptx <项目>only when the user explicitly needs PowerPoint. The final HTML is 演示文稿.htmlin the project root directory; the PPTX is a hybrid editable deliverable.