What a brand kit actually is
Most teams think a brand kit is a Notion doc with hex codes. The useful version is something machines can read.
Ask ten people what a brand kit is and you'll get ten Notion docs. Logo files, hex codes, maybe a font name, possibly a voice paragraph that says "warm but professional." That document is fine for human designers, but it's useless for a machine, and that's a problem now that machines are doing more of the work.
The legacy brand kit
The legacy version is a deliverable for a human creative team. It assumes context: the team has met the founder, sat through brand strategy, read the deck. The kit is a reference, not a spec. A designer reads "warm but professional" and infers the right typeface; an intern reads it and picks Comic Sans.
The legacy kit is also static. It doesn't know which page on your site is the homepage versus the careers page. It doesn't know which font is for headlines versus body. It doesn't know which images are products versus partners.
The machine-readable brand kit
A useful brand kit for an AI pipeline is closer to a database row. It has structure:
- Palette: 5 named colors with roles (primary, accent, background, secondary, highlight), not just a list.
- Typography: roles attached, heading vs body, weight ranges, source (Google Fonts, hosted, system).
- Voice: tone descriptor, vocabulary chips, words to never use.
- Audience: who you're posting to, separate from who you are.
- Pillars: 4-6 topic categories that drive content mix.
- Visual personality: an aesthetic mode (editorial, photographic, illustration, infographic) that constrains image generation.
- Don'ts: a banned-claim list. Anything the brand legally or culturally can't say.
When a generation pipeline reads that structure, the output stops feeling like AI slop. It starts feeling like the brand wrote it.
How we extract it
The interesting part: most of this is already on your website. The brand kit isn't something a designer invented; it's something the designer captured. A scraper reading your homepage finds the colors. Your CSS tells you the fonts. Your H1 tells you the tagline. Your about page tells you the voice.
The job of the brand-kit pipeline isn't to generate identity, it's to extract it. The brand already exists. We just need to put it in a row.
Why this matters
Once the brand kit is structured, every downstream generation is bounded. Carousels look right because the palette is locked. Captions sound right because the voice chips are pinned. Hashtags fit because the pillars are explicit. You don't get drift, because drift requires room, and a well-structured kit doesn't leave any.
The brand kit is the moat. The model is a commodity.
Keep reading