The workflow

The loop is short on purpose. You spend almost no time in the framework and almost all of it looking at pages.

Scaffold, once per project

npx --package=@beem-slide/cli beem init my-deck

You get slides/, a starter deck, the skills, a git repository with a first commit, and a dev server on port 5299. No theme is chosen for you and no house style is assumed — the first deck decides how it looks.

Draft

The agent does the first pass, because a first pass is mostly volume: a dozen pages of plausible structure that you can then argue with.

/create-slide scopes the deck with you before it writes — subject and aesthetic, roughly how many pages, how dense the text should be, whether it moves — then picks an id, plans the page order, and writes the files. Pages appear in the preview as they land rather than all at the end, so you can see a deck going wrong on page three instead of page twelve.

Before it writes anything it reads /slide-authoring, which is where the canvas rules, the type scale and the vertical budget live. That is why agent-written pages tend to fit and to look like each other.

Correct

This is where the time actually goes, and there are two routes into it because the two kinds of correction are different.

Some things are faster to just do. A heading that wants to be 88px, a word that should carry the accent colour, an image that needs a different crop — toggle Inspect, click, change it. Edits buffer until you hit Save, so twenty tweaks land as one write.

Some things are faster to describe. "This page is doing too much", "make the second column secondary to the first", "lose the icons" — those are edits you would have to think about to make by hand and can say in a sentence. Leave them as notes on the elements they apply to; they persist into the source as @slide-comment markers. When you have collected a few, run /apply-comments and the agent works through them and clears the markers.

draft → look → fix or flag → /apply-comments → look again

Then ship it

npx beem-slide build produces a static site, and npx beem-slide check type-checks every deck without building one — worth wiring into CI if the deck matters. If you would rather not manage either, beem push puts the deck in the cloud and beem publish gives it a link; see Connect.