Getting started

What Stoaken is for

Stoaken keeps a design system’s tokens in one place, and makes every change to them visible, reviewed and safe to ship.

The problem it solves

Design tokens are the named values a product is built from: its colours, spacing, type sizes, corner radii and so on. When they live in a spreadsheet, a Figma file and three code repositories, they drift apart, and nobody can say which value is right or who changed it.

Stoaken is the one place they live. Designers and engineers change them here, a reviewer approves each change before it goes out, and every app and tool reads the approved version.

How a change flows

  1. Someone with edit access changes tokens on the Tokens page and saves. Nothing is public yet.
  2. They propose a release: Stoaken compares the theme with what is live and lists exactly what changed.
  3. A reviewer opens it in the Command Center, sees the changes, what they reach and how components look, and approves or rejects it.
  4. Once approved, the release is published. Exports, the API, the CLI and AI agents now hand out the new values.

Tip: Only published releases ever leave Stoaken. Saving tokens is safe: it changes nothing for anyone else until a release is approved.

Where to go next

  • The words you’ll meet: Brands, token sets, themes, modes and releases, in plain terms.
  • Your first day: what to do first, depending on your role.
  • Each screen has its own article, and the (?) icons next to things open a short explanation with a link here.

Looking for the API, CLI or AI agents? They’re in the developer docs.