kaisersong/slide-creator

> You have great content — but great content deserves a great presentation. AI can generate slides, but the results are inconsistent and re-rolling gets old fast. Slide-Creator separates content planning from consistent rendering: pick a style that fits your audience, then review important facts and decision conditions before presenting.
>
> **See the guide as a report →** — this document was generated by slide-creator itself.
A skill for Claude Code and OpenClaw that generates stunning, zero-dependency HTML presentations.
English | 简体中文
---
Download v2.34.2
Compact Skill runtime ZIP · Release and SHA-256 · Optimization methodology v1.0.1 ZIP
Read the cross-Skill optimization guide, including plan, evaluation and bug templates. The methodology is packaged separately to keep research documents out of the normal generation context.
---
Live Demo
See what slide-creator produces — open directly in your browser:
- slide-creator intro (English)
- slide-creator 介绍（中文）
Click any screenshot below to open the live demo (same content, different styles):
Fantasy Rainbow · 奇幻彩虹 — custom theme
Blue Sky
Bold Signal
Electric Studio
Creative Voltage
Dark Botanical
Notebook Tabs
Pastel Geometry
Split Pastel
Vintage Editorial
Neon Cyber
Terminal Green
Swiss Modern
Paper & Ink
Aurora Mesh
Enterprise Dark
Glassmorphism
Neo-Brutalism
Chinese Chan
Data Story
Modern Newspaper
Neo-Retro Dev Deck
Strategy Consulting
---
Design Philosophy: Models Plan Content, Programs Enforce Delivery
slide-creator serves the last step of a content workflow: turning an existing argument into a usable presentation. That step often arrives after a long conversation. The architecture preserves the original material and explicit choices, gives the model a compact content contract, and delegates repeated implementation to a renderer.
Review and evaluation run according to the requested workflow; ordinary generation does not automatically invoke an independent model judge. Each layer has a distinct responsibility.
1. Separate content judgment from repeated implementation
The model organizes claims, evidence, narrative, exhibit intent, local facts, the closing request and speaker notes. The program loads the complete selected style and runtime, chooses concrete layouts, implements CSS and JavaScript, assembles export DOM, and validates the output before writing.
This split reduces repeated source reads and implementation retries. A renderer defect belongs in the renderer; asking every new content task to inspect and patch runtime code would hide that defect and consume context. The generator follows render_from_brief() for native core presets, unified profile presets and supported custom themes.
Auto and Polish retain the same execution path. Auto produces a first draft; Polish adds deeper content and design review. Polish is an additional review workflow, not a guarantee of perfect source fidelity.
2. Treat BRIEF as a derived plan, not verified truth
Original material defines the facts. Explicit user choices define the requested output. BRIEF.json is the model's structured interpretation of both, so it can still contain a mistake. A valid schema does not make its claims true.
The plan keeps each page's claim, explanation, supporting_facts, numeric evidence and visual intent together. numeric_facts is an auxiliary index for binding values, not an extra set of table rows. speaker_note carries speaking guidance separately from audience-visible copy, and desired_action preserves the scope and timing of the closing request. Old BRIEF files retain documented fallbacks.
--plan creates this executable plan. PLANNING.md remains an optional human-readable view. The same rule applies to direct prompt generation: materialize BRIEF first and use the renderer instead of hand-authoring final HTML.
3. Compile a small model contract from complete implementation owners
SKILL.md routes the task. The generation contract comes from the existing schema, style compiler, title profiles and capability registry, so the model receives field shapes, supported layouts, tokens and content rules without repeatedly reading implementation source.
The complete capability stays in the program. Context reduction must preserve evidence, conditions and necessary design choices; an arbitrary reference-read limit is not a substitute for a useful contract.
4. Make explicit style choices independently enforceable
When the user has not selected a style, offer suitable previews and recommendations. When a style is already explicit, preserve it instead of reopening the choice.