The short answer
A brand guide tells your team what your brand is. A Taste Profile tells your AI tools. Brand guides live as PDFs, Notion pages, or Figma cover files. They cannot be read by Claude Design, Cursor, ChatGPT, or Lovable. A Taste Profile is the same brand, encoded as Markdown and W3C tokens so machines can apply it consistently. Both can coexist. Most teams keep both.
Capability by capability
| Capability | PDF brand guide | Taste Profile |
|---|---|---|
| Read by Claude Design, Cursor, ChatGPT, Lovable | No | Yes (DESIGN.md, tokens.json) |
| Onboards new designers and marketers | Yes (intentional reading) | Partial (reference, not narrative) |
| Carries brand narrative, voice, and "nevers" | Yes (the prose itself) | Yes (DESIGN.md prose section) |
| Specifies tokens precisely (hex, type, spacing) | Partially (logo, palette, type only) | Yes (W3C DTCG tokens.json) |
| Specifies states: hover, focus, disabled | Rare | Yes |
| Versioned with diffable history | No (PDF revisions) | Yes (git, CHANGELOG.md) |
| Lives at a public URL | Sometimes (often gated) | Yes (yourbrand.tasteprofile.io) |
| Update cadence | Annually, if at all | Continuously (edit one file) |
| Format AI tools can consume | None | Markdown, JSON, Skills |
| Cost to maintain after launch | High (designer + freelance) | Edit a markdown file, or ask us |
Where a PDF brand guide still wins
Brand guides are not going anywhere, and a Taste Profile doesn’t pretend to replace them. Some things are still better as a document.
A brand guide reads cover-to-cover. It paces narrative, holds pull quotes, walks new hires through the brand from origin story to logo lockup to voice principles. It is the artifact your agency hands over at the end of a rebrand, the file your CMO points the new content lead at, the deck your founder shows on stage. Stakeholders trust documents. Boards approve documents. PDFs sit in folders next to the cap table. That is real and useful.
Brand guides also reach further than your product surface. They guide event signage, merchandise, sales decks, partnership co-marketing, packaging, regulatory submissions. None of that is what a Taste Profile is for. The Taste Profile lives in the toolchain. The brand guide lives in the boardroom and the onboarding folder. They serve different audiences.
Where a brand guide falls short for AI tools
Every AI tool that generates UI today reads structured text. Markdown, JSON, YAML, plain prose. They do not parse PDFs in any reliable way. They cannot extract tokens from your beautifully laid-out 60-page brand book. Even when they can read the words, they cannot tell which hex code is canonical and which one is just an example.
That has four practical consequences:
- Tokens get fuzzed. Most brand guides specify the primary color, the typeface, maybe a small palette. They almost never pin down hover tints, focus rings, disabled states, the eight-step neutral ramp, the exact corner radius for a card vs a chip. AI fills in the gaps. Different gaps every session.
- The narrative gets paraphrased. Brand guides say things like “our blue is confident, never corporate” or “we use generous whitespace to convey calm.” AI reads that and makes a judgement call about what blue, how generous, how calm. Your brand becomes the model’s interpretation of your brand.
- Updates do not propagate. Brand guides update annually if at all. The product evolves weekly. By month three, the AI is generating against a brand that no longer matches reality, and nobody updates the PDF because nobody reads PDFs.
- Every new chat starts blank. There is no plugin that loads a brand guide into Claude Design, Cursor, or ChatGPT at session start. So designers paste fragments, and the AI guesses the rest.
A Taste Profile fixes all four because it is the format AI tools actually consume. Markdown narrative, W3C DTCG tokens, Skills for Claude. The substance of your brand guide, restructured for machine parsing.
For the long-form essay version of this argument: Why not just paste your brand guide into Claude?
How they coexist
Most of our clients keep both. The split looks like this:
- Brand guide stays the strategic, narrative document for humans. New hires read it. Boards review it. Agencies reference it. Sales decks pull from it.
- Taste Profile is the operational, machine-readable spec for daily tool use. Designers point Cursor at it. Engineers consume tokens.json from the repo. Marketers ask Claude Design for a landing page and get something on-brand.
The Taste Profile is built from your brand guide as part of brand capture. We read what you have (PDF, Notion, Figma cover page, sometimes just a website), pull the narrative into DESIGN.md, pin the tokens into tokens.json, fill in the gaps your guide leaves silent (hover states, focus rings, the spacing scale), and ship it as a hosted viewer.
Your brand guide does not need to change. Your tools just gain a source they can actually read.
Pricing
$999 intro, done-for-you.
Brand capture from your existing assets, tokens, DESIGN.md, SKILL.md, themed components, hosted viewer, and platform-specific install instructions. Ships in days. Add a Brand Discovery Workshop, Extended Components, or Month of Guidance if you need them.
FAQ
Questions about brand guides + Taste Profile
No, and we would push back if you tried. A brand guide is the strategic, narrative document for humans (board members, agencies, new hires, stakeholders). A Taste Profile is the operational, machine-readable spec for the tools your team uses every day. Most of our clients keep both. The brand guide for the boardroom, the Taste Profile for the toolchain.
Yes. As part of brand capture you send us your brand guide (PDF, Notion, Figma cover page, whatever you have) along with your website, Figma library, or any other reference you want us to use. We compress it into DESIGN.md, tokens.json, SKILL.md, and themed components. The narrative survives. The tokens get pinned down. The detail gaps get filled in.
Common, and expected. Most brand guides specify the headline pieces (logo, palette, type, voice) and leave the day-to-day details (hover tints, focus rings, disabled states, spacing scale, icon stroke widths) implicit. We surface those gaps during delivery, propose tokens that fit your brand, and document the decisions so you can adjust. The Taste Profile is where the implicit becomes explicit.
Yes, and many of them now also deliver Taste Profiles, or partner with us to add one as a downstream artifact. The brand guide remains the document the agency hands over at project end. The Taste Profile is what your team and your AI tools actually run on day-to-day. They serve different stages of the brand lifecycle.
Build your DESIGN.md
Ready to get AI tools to follow your taste?
Stop getting generic design. Start getting work that actually feels like you without having to tell it each time.