Guides

A guide is a body of authoring knowledge the agent asks for when it needs it, rather than a prompt you paste. There are five topics, and they are served by the MCP server's authoring_guide tool to a signed-in account — the same material regardless of which client is asking.

They are not in an npm package or in the scaffold; see Overview for why.

slide-authoring

The technical floor everything else stands on: the file contract, the 1920 × 1080 canvas and its vertical budget, the type scale, layout vocabulary, the self-review pass, and the list of things that look reasonable and break a page.

You rarely ask for this one by name. The other topics defer to it, and an agent about to write JSX should be reading it first — which is most of why agent-written pages come out fitting the canvas and looking like each other.

create-slide

Drafting a deck from a sentence. Scopes it with you first — subject and aesthetic, length, text density, whether it moves — then reads the theme if one was named, picks an id, plans the running order, and writes the pages one at a time so you can watch the shape emerge instead of waiting for all of it.

generate-deck

Drafting from source material rather than from a description: a document, a transcript, a pile of notes, a data export. The work it adds over create-slide is upstream of any page — pulling out what matters, deciding the order that makes an argument, and choosing what to leave out.

apply-comments

Turning the notes you left in the inspector into edits: find the @slide-comment markers, satisfy each one in the code it is anchored to, remove the marker. See Apply comments.

create-theme

Going the other direction — from a deck you like, a screenshot, or a brand, to a reusable theme. Writes the pair: the .md a future draft reads, and the .demo.tsx the themes gallery renders so the theme is something you can look at rather than only read.

Reach for it the second time you find yourself describing the same look.