June 15, 2026 · Available on all plans.
What Shipped
Brew learns your brand by extracting it from your domain in about 30 seconds. But most teams already have a brand guide: a PDF, abrand.md in Notion, a
folder of logos, a few emails they’re proud of. Until now that material had
nowhere to go. Today, you can hand it all to Brew, and it wins over anything
inferred from your site.
Drop in What You Already Have
On brand setup, add your domain and attach your files together: brand guidelines, PDFs, existing markdown, logos, product shots, past emails. Brew reads your live site for how you show up in the world, and your files for the rules you’ve already written down.Your Files Win on Conflict
When the domain and your uploads disagree, your uploads win. If your guide says the accent is#FF5A1F and the marketing site drifted to a different
orange, the guide is the source of truth and the site is a hint. The domain
only fills the gaps your uploads leave.
Brew also flags tensions instead of silently overwriting. If your imagery
reads bright and near-white but your email surfaces are dark, it calls that
out and reconciles the two, so the palette language matches the emails you
actually send.
Brew Writes an email-design.md
From all of that, Brew’s extraction agent writes a document, not a schema.
It’s called email-design.md: a markdown brand spec that captures your color
system, typography, voice, and signature moves in prose, written in the
grammar of email (light and dark palettes, email-safe font fallbacks, the
600px container, table-based layouts).

image-style.md (the Design profile JSON on your
Assets page). Where email-design.md governs how an email is built,
image-style.md art-directs what Brew generates: palette, subjects,
composition, lighting, render mode, and a hard list of what to avoid.

email-design.md keeps your emails on-brand,
image-style.md keeps your generated images on-brand.