Before I switch windows
Four things to watch for
01
The prompt is plain English. I don’t type any CSS.
02
The agent reads the design system first, before it writes anything.
03
The linter fires on the edit and the agent fixes its own mistake.
04
I reload the browser. That’s the deploy.
No export. No conversion. No “save as”.
If you only remember one of these, make it number three. Everything else here is
convenience; a check the agent cannot talk its way past is the part that makes
this trustworthy enough to put on a projector.
Live · building a slide
Switching to the repo
the prompt, verbatim — copy it out of the recording
Add a slide to the death-by-powerpoint deck:
a two-column comparison of what we gain and
what we give up. Match the deck’s design system.
This slide is deliberately a holding card. If the demo goes wrong, the honest move is to
come back here, say so, and go straight to the next slide — which explains the whole
loop without needing the demo to have worked. Nobody has ever enjoyed watching
someone debug live.
The loop
What just happened
ASK
One sentence of English
READ THE RULES
SKILL.md, design system, sizing rules
WRITE
HTML into a real file in a real repo
LINT
Hook runs automatically on the edit
lint fails → the agent reads the error → fixes it → retries
Nothing in that loop was specific to slides. It is an agent, a written standard, and
a check that fails loudly — and you can point it at anything your team
produces repeatedly. The slide is now a file in git. It has a diff. Someone can review it.