presentation

name	presentation
description	Use when the user wants Codex to create a self-contained HTML presentation, technical talk, keynote-style story, executive report, or visual explainer with the bundled presentation component kit.

presentation

Create polished, self-contained HTML presentations from a user topic, script, outline, or rough context.

When to Use

Use this skill when the user asks for:

• HTML presentation pages
• technical talks or case-study decks
• keynote-style narrative slides
• executive report presentations
• visual explainers that should be easy to open in a browser

Do not use this as a PowerPoint or Google Slides workflow. Use the dedicated presentation tooling when the user specifically needs .pptx, Google Slides, or editable office slides.

Assets

The reusable kit is bundled under assets/:

• assets/base: common CSS and JavaScript
• assets/components: reusable HTML sections
• assets/themes: theme-specific section guidance
• assets/templates: starter HTML templates

Read only the files needed for the requested presentation style. Keep the generated output self-contained unless the user explicitly asks for split files.

Workflow

1. Identify the presentation type: technical journey, tech showcase, keynote, executive report, or general talk.
2. Extract the core message, audience, story beats, metrics, code examples, comparisons, and closing insight.
3. Choose a small section set. Always include a strong opening and a clear closing. Add only sections that support the story.
4. Read the matching theme notes from assets/themes/<theme>/sections.md when available.
5. Reuse component patterns from assets/components instead of inventing new section structures.
6. Inline the needed CSS and JavaScript from assets/base and any selected theme CSS.
7. Generate one responsive HTML file with full-screen sections and stable layout.
8. Verify the file in a browser or with the available browser automation before claiming completion.

Component Selection

Map the user's material to components by intent:

• system overview: service-grid
• timeline or migration story: timeline-vertical
• metric-heavy opening: hero-metric
• before/after code: code-compare
• KPI or business report: executive-report/*
• keynote emphasis: keynote/*
• benchmark comparison: tech-showcase/*
• simple talk content: general-talk/*

Prefer fewer, stronger sections over many thin slides.

Output Rules

If the user gives an output path, write there. If not, ask once where to save the HTML file.

Use a readable slug filename, for example:

redis-cache-case-study.html
java-coroutine-talk.html
executive-api-report.html

Generated files should usually go under output/ in the current project or a user-provided destination. Do not place one-off generated presentations inside this skill directory.

Verification

Before reporting completion:

• open the HTML output in a browser
• check desktop and narrow viewport layout when practical
• confirm text is not clipped
• confirm sections fit without incoherent overlap
• confirm code blocks and charts are readable
• fix visual issues and re-check

If browser verification is not available, say that explicitly and provide the file path.