The design kit — brand bible and design tokens as structured data — step 1 of 10

Your brand bible, as data a script can read

Every brand you've ever worked on has a bible: the 40-page PDF with the logo clear-space diagrams, the Pantone chips, the typographic scale, the moodboard of what the brand is and — usually on one passive-aggressive page near the back — what it is not. You fought for every page of it.

An image model has read none of it. It can't. The PDF sits in a shared drive; the model sits in an API. Every time you type a prompt from memory, you are re-deriving the brand bible by hand, and on the fourteenth asset of a long Thursday you will forget the "no neon" rule. The client will not.

The fix is the design kit: the promptable core of the brand bible, restructured as data. Run the editor — that's a real one:

• palette — named colors with hex values and roles. Names go into prompts ("terracotta and deep teal"); hex values feed the QA checks in lesson 3, where a script measures whether the renders actually stayed in gamut.
• type — the typographic voice, phrased as instructions. You'll mostly set real type yourself, but when a render includes lettering, this keeps it from coming back faux-handwritten.
• motifs — the recurring visual furniture that makes an asset recognizably this brand: the halfmoon mark, the steam lines. Motifs are what let asset #37 sit next to asset #2 in a feed and read as siblings.
• banned — the "never" page, promoted from passive-aggressive PDF appendix to first-class data. Next step is all about it.

Why structured beats prose

You could paste brand notes as a paragraph into every prompt. Structured wins for the same reason specs beat vibes in the studio:

1. It compiles. ", ".join(c["name"] for c in kit["palette"]) drops the palette into any prompt, in any tool dialect, spelled identically every time.
2. It validates. A script can check that every hex parses, that banned isn't empty, that a text color actually clears contrast on the background — before a single credit is spent.
3. It versions. halfmoon-kit-v3.json in the client folder, dated, diffable. When the client rebrands from teal to sage, you change one field and every future prompt follows. The PDF requires a human to remember; the kit doesn't.

One kit per client, built once, feeding every prompt on the retainer. And the brand doesn't stop at images — later this lesson the same move covers the screens in the brief: design tokens, the kit's interface wing, with color roles and type and spacing scales a script can audit the same way. That's the whole trick of this lesson.