Token reference

Kimen’s token tables are generated from the token sources, never hand-written — a constitutional rule (Art. I) that exists because hand-copied token lists drift the moment the next token lands. This page tells you where the generated surfaces live; the numbers below are computed from the built stylesheet at every site build:

The built onmars stylesheet currently defines 1946 unique --ki-* custom properties, of them component-layer tokens.

Where to look

• Per-component styling contract — every component page renders its CSS custom properties table from the generated Custom Elements Manifest: exactly the tokens that component consumes, with their purpose.

• The full generated reference — the Tokens reference page in Storybook is regenerated from the DTCG token sources and lists every token with its resolved value in both schemes.

• The stylesheets themselves — @kimen/tokens ships plain CSS custom properties, so the built files are their own reference:

  Export	Contents
  @kimen/tokens/css	The default onmars theme, light and dark
  @kimen/tokens/css/material3	The material3 reference theme, opt-in via data-ki-theme
  @kimen/tokens/css/base	The page contract: color-scheme + page colors

• Machine consumers — the same token names appear in the Custom Elements Manifest per component, so agents and design tooling read the styling contract without scraping docs.

Reading a token name

Token names encode their layer and scope:

• --ki-color-brand-500, --ki-space-md — primitive ramps; never consumed by components directly.
• --ki-surface-s0…s5, --ki-text-high-em, --ki-elevation-e1…e6, --ki-motion-duration-fast — semantic: meaning a theme reassigns.
• --ki-button-primary-neutral-rest-bg, --ki-dialog-backdrop-blur — component: the element, then its variant/tone/state path, then the property.

The Design tokens guide explains the model and how to customize safely.