Web ppt

Web PPT Skill

Create a single-file HTML deck using the vendored upstream runtime. Knot owns only this entry adapter: skill name, trigger semantics, delivery boundary, and verification routing. Keep assets/, references/, scripts/, and LICENSE synchronized with the upstream source commit recorded in UPSTREAMS.md.

Routing

Use this skill for browser-based presentation deliverables:

• web PPT or HTML slides
• magazine-style or Swiss-style decks
• horizontal swipe decks
• shareable presentations that should open directly in a browser

Use office-pptx instead when the requested final artifact is a native PowerPoint .pptx file. Do not use this skill for document extraction, knowledge ingestion, or Office XML-level editing.

Templates

• Style A: editorial magazine / e-ink feel, serif display type, warm visual tone.
• Style B: Swiss international style, dense grid, strong functional accent color.

Workflow

1. Resolve the target style. If the user does not specify, choose Style A for narrative/editorial topics and Style B for technical, product, roadmap, or data-heavy topics.
2. Clarify only blocking inputs: audience, duration/page count, source material, images or screenshots, theme color, and hard constraints.
3. Copy the matching template into the work area:
   • Style A: assets/template.html
   • Style B: assets/template-swiss.html
4. Plan the slide outline before editing HTML. Keep one idea per slide.
5. Use upstream reference files for detailed workflow and style rules:
   • Style A layouts: references/layouts.md
   • Style B locked layouts: references/swiss-layout-lock.md
   • Style B examples and rules: references/layouts-swiss.md
   • Components: references/components.md
   • Themes: references/themes.md or references/themes-swiss.md
   • Image prompt guidance: references/image-prompts.md
   • Screenshot framing: references/screenshot-framing.md
   • Final QA: references/checklist.md
6. Write final deliverables under the current direct-user workspace deliverables/ directory, or under the current authorized group workspace deliverables/ directory in group scope. Use the Knot delivery helper expected by the workspace.
7. Open the generated index.html in a browser and visually inspect every slide before delivery.

Style Rules

• Do not mix Style A and Style B CSS/components in the same deck.
• For Style B, follow the upstream conservative Swiss defaults in the bundled validator and references. Do not relax those defaults locally.
• Use real content, data, images, or generated assets. Do not leave placeholder blocks, lorem ipsum, unused sample slides, or broken image paths.
• Avoid emoji as interface decoration; use icons or typography from the template.
• Keep browser delivery simple: the generated deck should open directly as a local HTML file unless the user asks for hosting.

Verification

Before claiming completion:

node scripts/validate-swiss-deck.mjs path/to/index.html  # Style B only

Then inspect the deck in a browser. Fix visible overlap, clipped text, misaligned images, missing assets, blank slides, or navigation problems before handoff.