Stoaken docs

Stoaken keeps your design tokens in one place and sends every change through review before it reaches code. These pages show how to set it up and use it from your tools.

QuickstartFrom sign-up to a reviewed release and an exported file.ConceptsBrands, token sets, themes, modes, releases and review.CLIConnect a project and keep token files up to date in CI.AI agents (MCP)Let Claude Code and other agents read tokens and propose changes.WebhooksSigned events when releases are submitted, published or rejected.REST APIKeys, limits, errors and every endpoint.Export formatsEvery file format, what it covers and its limits.

How it fits together

You keep tokens in Brands, as one or more token sets in the W3C design tokens format. A theme stacks some of those sets, optionally with modes such as light and dark. When something changes, someone proposes a release; a reviewer approves it in the Command Center; only then can code, the CLI, the API and agents use the new values.

Nothing reaches your code without a person approving it. Agents and the API can propose changes, but there is no way for them to publish one.