Single-file HTML presentations with a built-in browser editor. This deck was generated directly from the skill README and then verified in the browser.
GeneratePick a preset or preview path.
EditMove, resize, format, reorder.
DeliverSave locally or export clean HTML.
01 / What it does
What the skill actually ships
The README positions the skill as a zero-dependency presentation generator with a persistent browser editor. The deck it creates is meant to stay useful after generation, not freeze into a one-off artifact.
GenerateSingle fileInline CSS and JS, style previews, and no build step.
EditLayout runtimeDrag objects, resize text blocks, multi-select, and keep undo/redo inside the file.
DeliverPersist or exportSave the full deck structure to localStorage during iteration, then export a sanitized standalone HTML when the layout is ready to ship.
02 / Why the fork exists
The trade-off is deliberate
The editable fork keeps the original deck-generation path, but adds weight on purpose: a Pages sidebar, object editing, history, persistence, and export. The goal is not the smallest file. The goal is iterative control.
Parent skillRead-only firstUse it when the deck is close to final and file weight matters more than in-browser iteration.
Editable forkDraft to reviewUse it when layouts keep moving and the browser file itself needs to stay editable after generation.
Better for review cyclesHeavier, but more forgiving
03 / Style-first workflow
Ask about the look before the polish
The current README and skill now bias toward style discovery early: collect visual preference, recommend matching presets, then let the user either pick directly or preview within that neighborhood.
01Purpose + lengthStart with context and slide count.
02Style preferenceAsk for clean, bold, editorial, technical, or “recommend for me”.
03Preset shortlistRecommend two to four styles that fit the audience and energy level.
04Pick or previewLet the user choose from recommendations or preview nearby variants.
05Generate, edit, exportBuild the full deck with the editable runtime, then keep refining it inside the browser without leaving the file.
04 / Editing runtime
The browser file keeps doing work
Editable mode is more than text editing. The runtime is responsible for object manipulation, focus routing, history, Pages filmstrip behavior, and storage of the whole deck structure.
ObjectsMove + resizeDrag the handle, resize with the corner, and let text reflow with the width.
TextFormat in placeFocus a text object and the toolbar exposes bold, italic, font, and size controls.
PagesFilmstrip sidebarPreview every slide, reorder them, delete them, and keep the list scoped to the real deck root.
E enters edit modeCtrl+S saves structureExport strips edit-state chrome
05 / Documentation map
Four files do most of the heavy lifting
The README explains positioning and usage, while the skill and runtime notes define the contract an agent has to satisfy. The reference HTML is where all of those rules finally meet working code.
READMEPositioningWhat the skill is for, when to use it, and how it differs from the parent skill.
SKILL.mdWorkflowWhich questions come first, how style recommendations work, and when to branch into previews.
editor-runtimeDOM contractUnique `data-oid`, edit layer rules, snap behavior, and history expectations.
Reference HTMLWorking runtimeThe canonical CSS and JS for sidebar, object editor, persistence, and export.
06 / Contracts worth protecting
The runtime only feels stable when the boring rules hold
The editable skill is sensitive to a few structural guarantees. Miss any one of them and navigation, filmstrip behavior, persistence, or editing affordances start drifting out of sync.
SlidesStable ids`section.slide#slide-N` is the persistence anchor. Reordering depends on it.
ObjectsUnique `data-oid`Selections, patches, deletes, and saves all assume object ids are unique across the whole deck.
QueriesRoot-scoped listsFilmstrip clones look like slides, so slide enumeration must stay scoped to `.slides-offset`.
StylingViewport + chrome tokensThe slide theme and edit chrome must both stay readable while every slide still fits the viewport.
07 / When to use it
Generate fast. Keep editing.
Choose the editable fork when the first generated draft is only the start of the conversation. Keep the deck alive, test the runtime, and only export when the browser version feels settled.
Choose editableIf feedback is still movingBest when layout changes, content reflow, and review comments still arrive after generation.
Choose parentIf the file must stay leanBest when the deck is close to final and you prefer the smallest read-only output possible.
Try it now: press E to edit, hover the top-left controls, use Ctrl+S to save, and export a clean HTML when the structure is ready.