Field study · data gathered July 2026

How design systems talk to machines

A field survey of 19 actively maintained open-source design systems and component libraries, plus the five platforms around them. For each one: what it ships so coding agents can build with it (MCP servers, agent skills, llms.txt, editor rules, registries) and the tricks that keep a model using real components and tokens instead of making up its own. Every snippet links to its source.

By Kaelig Deloumeau-Prigent · data gathered 26–27 July 2026

---

• 19
  design systems studied
  + 5 platforms · 168 affordances
• 16
  ship an official MCP server
  of 19 systems
• 17
  ship official agent skills
  npx skills add …
• 14
  publish llms.txt
  curated context files
• 148
  coercion techniques catalogued
  11 categories

The maturity spectrum

Every system placed on one ordinal scale. Placement is editorial, based on the affordances catalogued. Click through for the receipts.

Findings

1. The machine interface is table stakes: 16 of 19 ship an official MCP server

   Only Cloudscape, Nord and USWDS lack one, and Cloudscape makes up for it with the most engineered docs pipeline in the study. Nobody is still arguing about whether to ship a machine interface. The arguments now are about how the context gets sliced, how generation gets gated, and how the whole thing is kept from rotting.

2. 2026 is the year of the agent skill

   Seventeen of nineteen ship official agent skills (Cloudscape has none; USWDS has an open issue). Distribution has settled on npx skills add, and Nord, React Spectrum, Nuxt UI and Atlassian serve skills from well-known discovery endpoints, a pattern that didn’t exist a year ago. PatternFly ships 32 consumer skills across 8 plugins. daisyUI sells paid Dashboard and Charts skills next to its free one.

3. The frontier: portable design context and published evals

   Atlassian ships DESIGN.md, an 80KB token-first manifest (RFC 2119 rules over roughly a thousand lines of YAML tokens) for generating on-brand UI anywhere, and routes production work to the MCP server instead. It also published head-to-head evals of its own affordances: MCP vs skill vs DESIGN.md vs no context, with token, time and turn counts. shadcn regression-tests its skill’s rules with an evals.json. Agent-facing artifacts are becoming measured, versioned software.

4. Tool-gating beats prohibition

   The strongest systems restructure the task so hallucination can’t happen, rather than asking nicely. Shopify’s Polaris skill tells the model “you cannot trust your trained knowledge” and gates every answer behind a docs search plus a validator run. Primer writes “CRITICAL: CALL THIS FIRST” into its MCP tool descriptions, and “you cannot complete a task involving CSS without a successful run of this tool”. shadcn’s skill bans fetching raw files outright: “NEVER fetch raw files from GitHub manually — always use the CLI.”

5. The best context files are compiled, not written

   Mantine regenerates llms.txt, a 4.2MB llms-full.txt and mcp/index.json from the same MDX and docgen data as the human docs, on every release. Cloudscape mirrors every docs page as markdown, exposes typed JSON API definitions per component and regenerates llms.txt daily. HeroUI refreshes its MCP server from docs deploys via repository_dispatch. Hand-written agent docs rot. These can’t.

6. Consumer-side and builder-side investment barely track each other

   Fluent UI has the deepest builder-side agent stack in the study (nine executable skills, never-violate rules, lint auto-fix loops, visual verification) and almost nothing for consumers. React Spectrum, shadcn, Polaris and SLDS are the mirror image: heavy consumer investment, no public agent files for contributors. Carbon, HeroUI, Ant Design and Chakra are the few investing seriously on both sides.

7. A walled-garden pattern is emerging alongside the open one

   Polaris blocks GPTBot, ClaudeBot and friends in robots.txt and puts noai meta tags on every docs page, while funneling all AI consumption through Shopify’s own tightly gated toolkit. Nuxt UI bets the other way: RFC 9727 api-catalog, Link headers, markdown content negotiation, maximum discoverability for any agent. Both are deliberate. They can’t both be the future.

8. Validation loops turn guidelines into gates

   SLDS ships a dedicated validate skill plus slds-linter. Fluent’s skills wrap lint auto-fix loops with Storybook and Playwright visual checks. shadcn exposes an audit checklist as an MCP tool. Polaris bundles a validate.mjs the agent must run. None of them trust generation. They check it mechanically and make the agent fix what fails.

9. The public sector is sitting this out, so far

   USWDS ships zero consumer-facing AI affordances: no llms.txt, no MCP, no AI docs. Three weeks before this study it merged a single deliberately vendor-neutral AGENTS.md for contributors, on 2026-07-06. That is the entire federal contribution to date. The AI-affordance race is a private-sector phenomenon for now.