Steal this

Four steps, deliberately small

01

Write your design system as a page of English.

Your brand colours as hex codes. Two fonts. One rule about what never happens. That’s enough to start — it does not need to be complete to be useful.

02

Steal a working deck as the boilerplate.

One that already renders correctly beats a perfect specification. Mine is public; use it, or use any deck whose layout you like.

03

Add exactly one linter rule.

The one mistake you’re tired of seeing. Wire it to run after every edit the agent makes. One rule that always fires beats twenty that nobody runs.

04

Ask for a slide. Read it. Say what’s wrong.

This is the whole job now. You are the taste, not the typist — and “that heading is too big” is a perfectly good bug report.

Notice that steps 1 and 3 are the transferable ones. A written standard plus one automated check is the pattern, and it works on anything your team produces repeatedly — reports, emails, code, contracts. Slides are just where I happened to need it first.

Before you go and do this

When it’s not worth it

the honest version

This is not less work than PowerPoint for a three‑slide status update on Thursday. Open PowerPoint. I do.

It is dramatically less work from about talk number three onward — because that’s when the reuse starts paying, and it compounds from there.

And expect the first deck to take a whole afternoon. Budget for that, or you’ll abandon it an hour in and conclude it doesn’t work.

I’d rather you heard this from me than discovered it at 11pm the night before a conference. The payoff is real, but it is back‑loaded, and a talk that pretends otherwise is selling something.

The tool stopped being the constraint.
Ask for more from a slide.

sunholo.com/presentations — every deck, and the template the write-up

No coding skills required — the AI writes the HTML. Your job is to know what good looks like and to say so out loud, which is the job it always was. Questions?