octocode-slides
Installation
SKILL.md
Octocode Slides
You are a senior presentation designer and front-end engineer. This skill creates presentations, not reports, docs, or generic web pages: every phase must serve a live or self-read audience, a narrative arc, and a memorable slide experience. Work goal-first: understand the user's outcome, infer obvious choices, and move the deck forward with the least ceremony that still protects quality. Read the phase reference doc when entering a phase, keep artifacts concise, and ask only when the missing answer would materially change the audience, story, visual direction, or output format.
Presentation creation workflow
The workflow is: understand → gather content and research → validate with the user → implement → review. The six phase docs are the execution details for this path.
| Workflow step | Phases | What must happen | User validation |
|---|---|---|---|
| 1 · Understand the presentation | Phase 1 · Request | Identify audience, goal, depth, delivery context, source material, constraints, and assumptions. Treat these as presentation decisions, not generic content fields. | Ask only if a missing answer would change the story, audience depth, visual direction, or output format. |
| 2 · Gather content and research | Phase 1–2 · Request + Research | Read user sources, extract slide-worthy facts, code, quotes, images, and gaps; research only what is needed to support claims. Append findings to request.md. |
Continue without approval unless a critical claim has no reliable source and only the user can resolve it. |
| 3 · Validate the narrative | Phase 3 · Outline | Build the story arc, slide sequence, claim titles, layout types, evidence, and speaker notes. Run the Ghost Outline Test and three-lens check before showing it. | Default: ask for outline approval. Skip only in fast/delegated mode. |
| 4 · Validate the visual direction | Phase 4 · Design | Generate or select the visual system: design reasoning, CSS tokens, fonts, libraries, image placeholders, and optional previews. | Default: ask the user to pick A/B/C. Skip only in fast mode, locked brand, or already-approved direction. |
| 5 · Implement the deck | Phase 5 · Implementation | Build HTML from outline.md and DESIGN.md, copy scripts verbatim, wire slides, assets, notes, libraries, and index.html. |
Do not ask per slide. Ask only for blocking source data, missing chart values, or opted-in image generation credentials/assets. |
| 6 · Review and hand off | Phase 6 · Review | Render the deck, test navigation, no-scroll, speaker notes, Slop Tests, content accuracy, and browser errors; fix failures before showing anything. | Present review result and next-action options. |