---
title: "The industry map, November 2026"
url: /notes/2026-11-16-industry-map
description: "Where design systems and AI agents stand in November 2026, with every figure sourced and every forecast marked as a judgment."
---

## §0 · map

# The industry map, November 2026

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

## §1 · facts

### What the sources show

- shadcn/ui is the default dialect of AI coding tools. shadcn/cli v4 shipped in March 2026; the shadcn MCP server (since August 2025) works with any registry that follows the shadcn registry specification [claim ind-shadcn-v4: shadcn/ui changelog and MCP documentation; source: https://ui.shadcn.com/docs/changelog ; https://ui.shadcn.com/docs/mcp; confirmed]
- 20 of 21 open-source design systems ship an MCP server, counting official and community servers [claim ind-mcp-share: Field study of 21 open-source design systems and 6 platforms, data gathered 26-28 July 2026, by Kaelig Deloumeau-Prigent; source: https://state-of-ai-in-design-systems.netlify.app/; confirmed]
- With the registry MCP alone an 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 [claim ind-supernova-rules: One test of the Supernova tool, published by its maker, round two: 9 runs (3 tasks × 3 runs) per set-up; rules file: 8 rules in a 12-line CLAUDE.md; source: https://www.supernova.io/blog/shadcn-mcp-design-system; confirmed]
- 68% of developers use AI to write code; 32% of designers and developers trust the output [claim ind-figma-trust: Figma's own AI report; sample size not stated on the page. Vendor: Figma; source: https://www.figma.com/blog/design-systems-ai-mcp/; confirmed]
- 59% report UI that bypasses the design system; documentation is the top AI use by satisfaction (63%); design generation has net satisfaction of -53 [claim ind-zeroheight-bypass: Vendor survey of 123 practitioners, 2026. Vendor: zeroheight; source: https://zeroheight.com/resources/state-of-ai-in-design-systems/; confirmed]
- DTCG 2025.10 is a Final Community Group Report of 28 October 2025; stable; not a W3C standard [claim ind-dtcg: Design Tokens Community Group; source: https://www.designtokens.org/tr/2025.10/; confirmed]

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.

## §2 · claude 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) [claim ind-claude-design-dates: Anthropic release notes, product page, help centre; source: https://www.anthropic.com/news/claude-design-anthropic-labs ; https://support.claude.com/en/articles/12138966-release-notes ; https://support.claude.com/en/articles/17440474-move-from-standalone-claude-design-to-claude; confirmed]

A design system in it is an artifact: a README as the brand book, tokens, 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 CI, a decision 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 [claim ind-supernova-colours: One test of the Supernova tool, published by its maker; Mozilla Protocol, three screens per set-up, tests 11-12 November 2026; source: https://www.supernova.io/blog/claude-design-design-system; confirmed] Even from code: 7 off-scale spacing values, 2 components not in the system [claim ind-supernova-drift: The same Supernova test; source: https://www.supernova.io/blog/claude-design-design-system; confirmed]

## §3 · heading

### 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 spec.
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.
