Wrap inline text in [ … ] and add one or more dot-classes. They set color, size, or a gradient fill. You never leave Markdown. Classes chain.
The deck your AI [actually]{.orange} gets right.
[Plain text in.]{.grad}
[40-80%]{.grad-purple .huge} less hand-fixing
[300+]{.green .lg} decks a week
[caption text]{.sm .muted}
Classes resolve against the master. So .blue or .accent mean whatever the theme says they mean.
Class vocabulary
| Class | Effect |
|---|---|
.<color> |
text color. Any palette key or roles name, like .blue, .accent, .muted |
.grad |
fill the text with the master’s brand gradient |
.grad-<name> |
fill the text with a named gradient, like .grad-purple |
.xs .sm .md .lg .xl .xxl .huge |
font size, mapped to type-scale steps |
.bold |
weight 800 |
.muted |
the muted color |
A raw hex or CSS color also works as an escape hatch, like [x]{.#3366ff} or [x]{.tomato}. Prefer palette and role names. They keep the deck on theme.
An unknown class does not fail quietly. It warns (unknown-class or unknown-gradient), so a typo never renders as invisible text.
Use roles like
.accentover raw palette names like.bluewhere you can. Then a deck survives a theme change. The size classes map onto the theme’s type scale, not fixed pixels.