Chronicle

Brand kits - decks that come out already on brand

Store a brand once - colours, typography, logos and how it talks - and every deck generated after that is on brand before anyone opens the editor.

One kit, read every time a deck is generated

BrandDesign systemsAIAgentsTypeScript

What the kit stores

Four things, all read while the slides are written.

  • Colours - the palette, and what each colour is for.
  • Typography - which font to use where.
  • Logos - every mark, and when to use it.
  • Voice - how the brand talks.
Setting up the kit, once.

The deck above

The slides at the top are a launch deck for Duolingo Music - a course that teaches you to read music and play by ear in five-minute lessons. Create with one prompt.

It is a good test because all four have to hold at once - the green, the type, the mark, and a voice that could not belong to anyone else.

The palette and slide themes go into the renderer; about, personality and slide preferences go into the generator’s system prompt. So the first draft is on brand in its words as well as its colours - no design pass afterwards.

My role

I built the kit’s data model - how a colour, a font tier and a slide theme are stored and resolved - and the path that carries all of it into generation: the colour tokens the agent draws from, and the written guidelines in the system prompt.

I also sat with the product team to work out where this goes next. The kit is deliberately a store of brand rules rather than a slide template, because the same shape holds a lot more than we ship today: a design-system.md imported straight from a company’s repo, spacing and component rules, the tone guide their writers already maintain.