How it works

• Slide — one page of the talk. Its Content is the 16:9 stage (markdown; inline SVG welcome), the Notes hold the spoken script, and the Present area renders the chrome-free stage. The type is compiled live from Source.
• Deck — the presentation. Its Slides manifest is the ONE place the order lives: reorder, insert or drop a slide by editing that list — the slides themselves never change. The deck renders a collapsible side-nav plus a ▶ Present button.
• Publishing a deck — making a talk readable by the world, and handing out the thing it demos. The two grants a public surface needs, why a link inside a slide does not work, and why the demo goes out as a coupon rather than a public partition.

The skills

Two chat skills carry the whole authoring workflow — invoke them in any composer:

• /presentation — the end-to-end workflow: outline first, author each slide (stage sparse, lesson in the notes), order them in the deck's manifest, present. Hand it a brief and it builds the full deck.
• /slide — the per-slide authoring reference: stage layout, clamp() text sizing, one-big-visual composition, speaker notes.

For written documents that accompany a deck, use ordinary Markdown pages — the /markdown skill covers structure, embeds and live code cells.

Decks that ship with this pack

Own your estate — MeshWeaver in the customer's own cloud — twelve slides on running an instance in the infrastructure owner's own subscription: what each party owns, the estate as code, the three workload pools, the single instance token, pull-only delivery, the two update policies, and the rule that only pipelines change infrastructure while people approve. It is also a worked example of Publish/Deck + Publish/Slide.

Contents