← Back

Design tokens and your brand: the values behind the look

A design token is a named brand value, a color, type size, or spacing unit, reused everywhere. Here is what design tokens are and where TrueKeep keeps them.

A design token is a named, reusable value that stores one brand decision: a hex color, a type size, a spacing unit. Instead of a designer picking "a blue that looks about right," the team uses brand-primary, and everyone gets the same blue. Design tokens exist because a brand guideline written in prose ("use our primary blue") still leaves room for someone to guess which blue. This post covers what a design token is, how it differs from a line in a style guide, and where TrueKeep keeps the ones your team actually uses: the components part of the portal, one of the four parts of the portal.

Key Takeaways

  • A design token is a named value (a color, a type size, a spacing unit) that stands in for a brand decision, so the decision gets reused instead of re-guessed.
  • TrueKeep shows tokens as the real thing: colors render as swatches, logos at presentation quality, typography in the actual typeface, not a hex code in a spreadsheet.
  • Design tokens live in the components part of the portal, alongside the brand's strategy, guide, and assets.
  • The design brief and the MCP connection carry a token's current value into Claude, ChatGPT, or Cursor, so an AI tool uses the real color, not a guess.
  • A token is only correct if someone updates it when the brand changes. TrueKeep's edit mode names who can make that change.

What is a design token?

A design token is a name attached to one value. brand-primary might point to #1A2B44. heading-size might point to 32px. space-sm might point to 8px. The name is what a person or a tool asks for; the value is the actual brand decision behind it.

The difference from a style guide entry is small but matters. A style guide says "our primary color is a dark navy." A design token says brand-primary: #1A2B44, the exact value, reusable by name, instead of described in words that a new hire or an AI tool has to interpret.

Where your design tokens actually live

A token is only useful if the whole team can find the current one. TrueKeep's portal holds four parts: strategy, guide, assets, and components, and the component part is where tokens show up as the colors, type, and spacing a real component is built from.

Tokens shown as a list of hex codes still ask the reader to imagine the color. TrueKeep renders them as the real thing: a color swatch you can look at, not a string of characters. The brand color palette guide walks through what a color token should include beyond the hex value, like which backgrounds it is approved against.

From token to component: showing the real value

A component is built from tokens. A primary button might reference the brand-primary color token, a space-sm padding token, and a radius-md corner token. Listed separately, those three values mean little. Shown on the actual button, in the portal, they are obviously right or obviously off.

Typography tokens work the same way. A heading-size value on its own is just a number. Set in the brand's real typeface, at that size, next to body text, it reads the way the reader will actually see it on the page. The typography guidelines post covers how type tokens (size, weight, line height) combine into the specs a designer follows.

Keeping design tokens current

Here is the tradeoff: a design token is a single source of truth only until the brand changes and nobody updates it. A color gets refreshed, a type scale gets adjusted, and the old token sits in the portal looking authoritative while it is quietly wrong.

TrueKeep's edit mode lets a curator change a token's value in the portal itself, so the update happens in one place instead of in a dozen files. That only works if someone is responsible for making the change. Name that person before you launch the token set, not after someone ships a deck with the old blue.

Design tokens and your AI tools

Most AI tools can match a logo you upload. Few know the token behind it, the exact color value, the approved type size, without being told. TrueKeep writes those values into a design brief and serves it through an MCP connection. Connect Claude, ChatGPT, or Cursor once, following the AI connection guide, and the AI reads the brief before it writes, pulling the real token value instead of guessing at one.

Nobody has to open the portal and copy a hex code into a prompt. The guidelines come to the work.

What TrueKeep doesn't do

TrueKeep is not a build pipeline. It does not sync tokens automatically into a Figma library, a Storybook instance, or a codebase, and no guide here documents that kind of connection. The components part of the portal is where a person or a connected AI tool checks the current value, not where a continuous integration job pulls it from. If your team needs tokens to flow straight into a design or development tool automatically, that is a different piece of infrastructure than a brand portal.

FAQ

What is a design token? A design token is a named, reusable value, typically a color, a type size, or a spacing unit, that stands in for one brand decision. The name (brand-primary) stays the same even if the value behind it changes later.

How is a design token different from a brand guideline? A brand guideline describes a decision in words ("use the primary blue"). A design token is the exact value behind that decision (#1A2B44), reusable by name instead of reinterpreted each time.

Who should own a company's design tokens? Whoever can change the value when the brand changes. TrueKeep's edit mode lets a named curator update a token in the portal directly, so the update happens in one place.

Can an AI tool read my design tokens? Yes, if the AI tool is connected to a system that serves them. TrueKeep's design brief, read through an MCP connection, gives Claude, ChatGPT, or Cursor the real token value before it writes.

Does TrueKeep sync design tokens with Figma or code? No. TrueKeep shows tokens as the real colors, type, and components in the portal and serves them to connected AI tools. It does not sync automatically into a Figma library, Storybook, or a codebase.

Conclusion

A design token turns a brand decision into one reusable value instead of a description someone has to interpret. TrueKeep keeps those design tokens in the components part of the portal, shown as the real color, type, and component rather than a code in a spreadsheet, and carries them into connected AI tools through the design brief. The part that still takes a person: naming who updates a token when the brand changes. Get started to put your team's tokens in one place.

Sources