§0map
← All field notes

The industry map, November 2026

Written on 2026-11-16. Several sources are vendors; each is marked.

§1facts

What the sources show

  • shadcn/uiA set of open-source components that you copy into your code. Agents know it well. is the default dialect of AI coding tools. shadcn/cli v4 shipped in March 2026; the shadcn MCPModel Context Protocol. The open protocol that agents use to read tools and data. server (since August 2025) works with any registryA list of the components of a system that a tool or an agent can read. that follows the shadcn registry specification
  • 20 of 21 open-source design systems ship an MCP server, counting official and community servers
  • With the registry MCP alone an agentAn AI program that writes and changes code, for example Claude Code or Cursor. On this site, "agent" means a coding agent. broke 20 team rules across 9 runs and rebuilt its own dialog 3 of 3 times; a 12-line rules file removed every break
  • 68% of developers use AI to write code; 32% of designers and developers trust the output
  • 59% report UI that bypasses the design system; documentation is the top AI use by satisfaction (63%); design generation has net satisfaction of -53
  • DTCGThe Design Tokens Community Group and its file format for design tokens, version 2025.10. A Final Community Group Report, not a W3C standard. 2025.10 is a Final Community Group Report of 28 October 2025; stable; not a W3C standard

Connecting a design system to agents through MCP is close to standard. The open problem is one layer up. MCP tells an agent what exists. It does not say how the team uses it, which rule wins a conflict, or whether the result is correct.

§2claude design

One vendor up close: Claude Design

Claude Design: research preview 17 April 2026; inside every Claude conversation from 16 September 2026; standalone site closes 14 December 2026 (moving into Claude)

A design system in it is an artifact: a README as the brand book, tokensA named design value, for example a color or a spacing step, kept as data. DTCG 2025.10 gives the file format., components with live previews and guidelines, assets. It can be built from code with /design-sync in Claude Code (an upload from code to the tool, for React component systems), from a design tool through a connector or from a conversation with uploads.

Its own working rules match this site's patterns: code is treated as the truth and screenshots as lossy; a system synced from code is read-only in the tool; values are not invented, and what could not be placed is listed.

What it lacks: rule ids with a severity and an enforcement link, a check a team can run in CIContinuous integration: the checks that run on each change of the code., a decisionA written choice of the team, with an id, a reason and the check that enforces it. On this site, a row of the register. register, a proposal path. It checks itself, and nobody else can run that check.

Colours outside the system across three screens: 10 from screenshots, 0 from code and tokens Even from code: 7 off-scale spacing values, 2 components not in the system

§3heading

Where this is heading

Each line is a judgment, not a fact.

  1. Judgment: the source of truth moves from the design file to code and data. The design tool becomes one view.
  2. Judgment: the rules layer becomes the design system's main product. Components become a commodity.
  3. Judgment: correct-by-construction replaces review of generated code. The agent fills a typed specA structured description of a page that a script turns into HTML. The agent fills the spec. It does not write the HTML..
  4. Judgment: design systems get evals, as code got tests.
  5. Judgment: governance gets cheap enough for a team of two.
  6. Judgment: validators report and route. They do not block agents.
  7. Judgment: UI that bypasses the system becomes the main governance problem.
  8. Open question: does the designer's work shift toward curating rules, reference pages and taste?
  9. A bet: design work moves into the browser. A screen is composed from the design system in HTML and CSS and reviewed there. The limits: one system is built this way, one has a plan, and no designer has signed the plan off. The hand-off changes its kind. Tokens are connected today, pages are next.
§ sources