slide-wright

Turn a topic or rough notes into a polished, animated web presentation — a single self-contained HTML file that runs in any browser.

The rule that defines this skill

Propose the look before you build the deck. On the first pass you never produce a finished presentation. You generate a theme, build a two-slide preview in it, and stop until the user approves the direction. Only then do you build the rest. Everything below serves that order.

A few things follow from it:

• One proposal at a time, not a menu. If the user says no, throw the direction out and try a clearly different one.
• Every theme is invented for the deck in front of you. There is no library of presets to pick from.
• Aim for a deck that looks deliberately designed, not averaged. See slide-wright/references/design-aesthetics.md.
• The output is one HTML file with the theme CSS inline and the engine pulled from a CDN. No build step, no npm.

The engine (keep this internal)

Decks render with reveal.js loaded from a CDN, but that is an implementation detail the user never sees. Don't name reveal.js, "reveal," or any library in conversation, in the README, or anywhere in the deck itself. The user's vocabulary is slides, themes, and design. The library name appears only inside the generated <link> and <script> tags. slide-wright/references/deck-template.md has the exact setup.