Decklume vs frontend-slides
Both are free, MIT-licensed Claude Code skills that output a single HTML presentation. This is where they differ.
| frontend-slides | Decklume | |
|---|---|---|
| How design is controlled | Prose guidance and style recipes the model translates by hand | Design tokens, 30 tested layouts and themes written as code |
| Story | Asks for your content | You approve an outline with an assertion headline per slide |
| Style previews | Three separate files, title slide only | Your title and content slides in three themes, on one page |
| Themes | 12 presets and 34 bold style recipes | 13 complete themes, every layout designed and tested |
| Motion | Entrance animations | Entrances, step-by-step builds and Magic Move transitions |
| Charts | Not included | Bar, horizontal bar, line and donut charts in SVG |
| Verification | Advice to review screenshots | Automated QA gate with contact sheet, tested in CI |
| Presenting | Speaker notes passed to a host | Presenter window with notes, timer and next slide |
| PDF export | Screenshot images; about 20 MB for 18 slides (per its docs) | Vector with selectable text; 1.1 MB for 33 slides |
| PowerPoint import | Python script: text, images and notes | Pure Node: adds bullet levels, tables, grouped shapes and native chart data |
| Output | One self-contained HTML file | One self-contained HTML file |
| License | MIT | MIT |
When frontend-slides may suit you better
If you want the widest range of bold, one-off visual styles, its 34-recipe template pack is a great source of ideas, and it needs no Node scripts at all.
When Decklume may suit you better
If you want every slide type designed consistently, a story you approve first, and a deck that has been checked in a browser before you present it, Decklume is built for that.