AI-native design system platform
Any AI. One design system.
AI Ready Design System (AIRDS) brings designers, developers and AI agents into a shared domain schema — single source of truth for every tool and every AI.
Why it's built this way
Six decisions that hold the whole platform together
Every color is generated, never picked
One seed hex runs through Material's HCT color model — 6 tonal palettes, 13 canonical tone stops, 28 documented color roles resolved per mode. No primitive token can exist as a bare hex.
Three-tier tokens: ref → sys → comp
Material's own naming, adopted deliberately. Components alias system tokens through a component-tier token, so one component can be re-skinned without touching everything else that shares its role.
One source, many AI tools
A single canonical rules.json renders into AGENTS.md, CLAUDE.md, .cursor/rules/, and copilot-instructions.md — gated by which tools your team actually selected, not generated blind.
GitHub is the source of truth
Not a branch of any app repo. Designers sync from Figma, developers sync from code — both converge on ordinary, human-reviewed pull requests against one repo.
AI recommends. It never decides.
Detection, clustering, drift analysis, and pattern candidates are all AI-assisted. Promotion to system status, deletion, and publishing are permanently human-gated.
Idempotent by construction
Every generating action — bootstrap, sync, brand update — is safe to re-run. State updates in place; nothing silently duplicates.
Architecture
One source of truth, two front doors
There is no design branch versus dev branch. There is one design-system repo on GitHub, and two interfaces onto it — designers through the Figma plugin, developers through the CLI and whatever AI coding tool they already use.
GitHub — design-system repo
source of truth · main protected · schema, tokens, components, brand, context
Figma plugin
designers · design-sync/* PRs
CLI + Claude Code / Cursor
developers · dev-sync/* PRs
Published packages
@org/design-tokens · @org/design-assets
Product app repos
web, iOS, android, marketing — consume via package, never edit source
Governance
Every token, component, and pattern has a lifecycle
Nothing reaches system status without evidence — usage count, screen count, consistency, accessibility — and a human approval. AI proposes; it never promotes.