Axo Design System

The machine-readable surface: one origin for agents referencing or reproducing Axo UI. Everything here is public and needs no auth. Start with /design.md.

Nine brands, one system — pick one to see its tokens.

Connect an agent

claude mcp add --transport http axo-design-system https://design-system-registry.v.axo-test.io/mcp

Gives the agent list-components, get-component, get-brand-tokens and reproduce-component. Everything the MCP knows is also readable as plain files below, so nothing here requires it.

What it serves

/design.mdThe hub. Rules, theming, resolved tokens, type scale and the component index — generated from the live design system. Add ?brand= to switch.
/llms.txtThe same entry point at its conventional location; points here.
/components/<name>.mdOne component: canonical import, when to use it, props, measured values.
/manifests/components.jsonEvery exposed component, normalised, with a health report.
/mcpThe same knowledge over MCP — see “Connect an agent” above for the one-line setup.
/tokens/<brand>.cssThe compiled [data-theme] block. Drop it in and set the attribute.
/tokens/<brand>.jsonThe same tokens resolved to literals, plus any dangling references.
/computed/<component>.<brand>.jsonMeasured variant × size × state × disabled matrix.

Provenance

Components are authored in @axo/ui-core and are not published to npm. Anything served here that reproduces a component is scaffolding: it carries the canonical import and source path so a prototype can be swapped for the real component rather than reverse-engineered.