kiselas/every-slide-is-code

deck-kit

Presentation decks as code — pitch decks, product launches, idea pitches, board and quarterly reviews, tech talks.

How to use

Copy the installation command and review the source package before installing it in your own agent environment.
Check the source document for required tools, credentials and supported hosts.
Describe your input and desired deliverable; review the output against the source material.

npx skills add https://github.com/kiselas/every-slide-is-code --skill deck-kit

Installation does not include a model subscription, API allowance or permission to access your files.
Repository stars and installation counts describe activity, not an independent quality or security test.

Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

any deck: 01-runtime.md, 03-story.md, 04-slide-design.md, 12-export-qa.md;
the brief is vague or you are writing a prompt: 02-prompting.md;
animation and builds: 05-motion.md;
transitions between slides: 06-transitions.md;
numbers and charts: 07-charts.md;
flows, architecture, timelines, matrices: 08-diagrams.md;
titles, big numbers, text treatment: 09-typography.md;
a background world that lives behind all slides: 10-stage.md;
rehearsal, presenter view, the room: 11-presenting.md;
smoothness, battery, heavy slides: 13-performance.md.

Start every deck from template/deck.html (node scripts/sync-runtime.mjs --new my-deck.html), or copy the template and paste runtime/deck.css and runtime/deck.js into its two marked slots.
Show the plan as data first: the storyline (one sentence per slide), the style, and which slides carry a chart, a diagram or a transition with a meaning. Then write code.
After every version run node export/deck.mjs check and node export/deck.mjs sheet, look at the sheet yourself and fix by slide and step number (4.1, not "the chart slide"). Before handing over, also run check --timeline, check --no-webfonts and perf.