---
title: Design system leads
description: Tokens live in a plain-text file agents read, so agent output arrives on your system. Modes, brands, libraries and a linter included.
section: solutions
order: 4
featured: false
related: design-system/overview, solutions/brand-changes, editor/components
---

# Brilliant for design system leads

How do I keep agents on the system? Make the system the shortest path. In Brilliant, the system is a plain text file in the project, and every agent on the canvas gets the token catalog in context. Agents paint with roles, not hex.

<DocFigure src="/docs/images/solutions/design-system-leads-scene.webp" srcMobile="/docs/images/solutions/design-system-leads-scene-390.webp" stage="panel" alt="A system check listing a fill that is not a token" caption="The check names what left the system." />

## Where does the system live?

In Styles/default.ds, in your project. Brilliant writes a fully populated one when you open a fresh project, and regenerates a resolved file on every save for Style Dictionary, Tokens Studio plugins and build scripts.

```text title="Project layout"
my-project/
  Styles/
    default.ds            you edit this
    .gen/default.gen.yaml generated on save
  Canvas.bl
```

## How do tokens work?

Primitives hold one fixed value. Semantics hold one value per mode. Generators do the expansion, so one seed color gives you a full OKLCH ramp and mode-aware roles like primary.mid and spacing.md. See [Tokens](/docs/design-system/tokens).

## How are agents held to it?

With a system active, each color, size and font slot an agent writes is a token resolved through the current brand and mode. Ask it to bind a stray fill to the closest token, and it will. The [Quality linter](/docs/developers/quality-linter) flags what got away.

<DocFigure src="/docs/images/solutions/design-system-leads-lint.webp" srcMobile="/docs/images/solutions/design-system-leads-lint-390.webp" stage="panel" alt="The quality linter reporting a problem with a suggested fix" caption="Every write is checked against what landed." />

## How do modes and brands work?

Modes are named axes: theme, density, accessibility and any others you declare. A brand is a sparse sibling file with only its deltas, and the rest cascades from the base, down the folder tree like .editorconfig. See [Modes and brands](/docs/design-system/modes-and-brands).

<DocFigure src="/docs/images/solutions/design-system-leads-system.webp" srcMobile="/docs/images/solutions/design-system-leads-system-390.webp" stage="panel" alt="The design system editor beside a design that follows it" caption="One system, every bound layer." />

## Can I share components across projects?

Yes. Use a project as a library and release new versions to the projects that use it. See [Components](/docs/editor/components).

## Common questions

### What about a raw hex on an element?

It stays a raw hex until someone binds it. Select it and tell the agent to bind it to the closest token.

### Can I import an existing system from Figma?

Yes. The plugin brings variables and styles across as tokens, with layers still bound. See [Import from Figma](/docs/import/from-figma).

## Where next?

- Start here: [Design system overview](/docs/design-system/overview).
- Every token type: [Tokens](/docs/design-system/tokens).
- Theming and multi-brand: [Modes and brands](/docs/design-system/modes-and-brands).
- Run a rebrand: [Apply a brand change](/docs/solutions/brand-changes).
- The reuse layer above tokens: [Components](/docs/editor/components).
