<!-- Generated from /contracts/readiness at build time. Do not edit by hand. -->
<!-- Source of truth: the rendered page. A hand edit here is overwritten on the next build. -->

# Designesy — /contracts/readiness

Canonical page: https://www.designesy.org/contracts/readiness

---

## AI Readiness

AI readiness is the 6th maturity axis (zeroheight 2026). A design system is AI-ready when it exposes machine-readable context that AI coding agents can consume — tokens, rules, discovery endpoints, and verification. This contract defines the checks that score it.

Version 0.1.0 · provisional · [machine export](https://www.designesy.org/contracts/readiness.json)

## Source authority

zeroheight 2026 Design System Maturity Model — AI Readiness axis

Whether your design system is the default context that AI tools build from, or whether AI is silently working around it

DLS Lead — "I made my design system LLM-readable. Here's exactly how."

## The six maturity axes

## AI-readiness signals

- Machine-readable token file (DTCG/JSON) exposed at a discoverable URL
- llms.txt brief present at /.well-known or /llms.txt
- agent.json discovery document at /.well-known/agent.json
- MCP endpoint exposing tools/list for AI agents
- DESIGN.md present (the @google/design.md standard)
- Token documentation — tokens carry $description for agent context
- Component contract — machine-readable component schema
- Sitemap.xml present for crawlability
- robots.txt permissive for agent crawlers
- Open Graph + Twitter meta for social/share context

## Verification

10 checks — 10 checks. PASS=1, WARN=0.5, FAIL=0. Score = (points/10) × 100. A≥90, B≥80, C≥70, D≥60, F<60.

Validation: Designesy readiness engine — HTTP probing of machine-readable artifacts. Method: HEAD/GET requests against the target origin for each known artifact path. Browser-only checks: None — all 10 checks are HTTP probes, no browser needed.

## Open questions

- r01 (token file) probes common paths (/tokens.json, /design-tokens.json) — custom paths may be missed
- r07 (component contract) is heuristic — no universal standard for machine-readable component schemas exists yet
- r04 (MCP endpoint) probes /api/mcp — custom MCP paths may be missed
- The score does not measure token quality — only presence. A badly structured token file still scores PASS on r01

## Run it

Score any URL for AI readiness:
