---
title: "AI-augmented Design System: from tokens to autonomous agents"
url: /talk/techmeetup-2026
description: "Slides, sources and four steps to start from Pavol Hudran's talk at TechMeetup Conference, Ostrava, 20 November 2026."
---

## §0 · talk

# AI-augmented Design System: from tokens to autonomous agents

TechMeetup Conference 2026 · Nová Aula VŠB-TUO, Ostrava · 20 November 2026 · 30 minutes

[Open the slides](/talk/techmeetup-2026/slides)

One HTML and CSS file that works offline. Use the switches at the top right of the deck, or the keys: **L** for language (English or Czech), **B** for brand (Index or Kiln), **D** for dark mode. Space and the arrow keys move one slide.

## §1 · start

### Four steps to start this week

For you, if you run a design system and want coding agents to follow it. These are changes to your own repository, not prompts.

1. Spend one hour counting what your system has against the [Design System Checklist](https://www.designsystemchecklist.com/), 42 sections and 238 items [claim ind-checklist: Counted from its data files on 2026-11-16 (repo commit 28f06a2): design language 2/10, foundations 6/24, components 29/176, maintenance 5/28. Coverage, not quality; source: https://github.com/ardakaracizmeli/design-system-checklist; confirmed].
2. Write a short rules file that names what the agent gets wrong, with the correct replacement.
3. Number your decisions and add an "Enforced by" column. Leave it honestly empty where nothing checks the rule.
4. Add one check that runs in CI for the rule that hurts most.

[Find your level](/ladder)

## §2 · abstract

### The abstract

My English translation of the abstract I submitted in Czech.

Design systems in 2026 are going through a second wave of automation. The first was the introduction of design tokens. The second is connecting the design system to AI agents through MCP (Model Context Protocol). I show what this means in practice and why it concerns small teams too, not only the enterprise.

- Why shadcn/ui became the default "unofficial" design system for AI coding agents (Claude, Cursor, v0, Lovable), and what it means for designers who never knew.
- How the shadcn MCP plus Figma MCP workflow works: the agent reads a Figma frame, finds the components in the registry and generates code that fits the existing tokens and Tailwind theme, practically without drift between design and code.
- Where Figma and its competitors are going: Figma Make against tools such as Lovable, v0 or Google Stitch, and why this is not only about "vibe coding" but about who will own the design-system layer.
- How I build an agent layer on top (LangChain): orchestration where the agent does not only generate UI but also watches governance, token consistency and documentation.
- What can really be used today, and what is still a demo.

### Where the talk differs from the abstract

Two lines of the abstract did not hold, and one topic grew.

- **"Practically without drift" did not hold.** In one test of the Supernova tool, published by its maker, even built from code and tokens, the tool produced 7 off-scale spacing values and 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].
- **No LangChain layer runs today.** What runs is skills, hooks, sub-agents and deterministic scripts. The next step is an open framework for design-system rules, and I want to build it with others. [Read the white paper](/living-design-system) and join the effort. Tracing (LangSmith, or Langfuse self-hosted) and orchestration (LangGraph) come later, for tuning. Langfuse is not a LangChain product.
- **Claude Design got its own part.** It is moving into Claude, and its own working rule is the point of the talk: code is the truth, screenshots are lossy.

## §3 · sources

### Every source from the slides

| Slide | Figure | Source | Note |
|---|---|---|---|
| 3 | 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] | [Supernova, 21 October 2026](https://www.supernova.io/blog/shadcn-mcp-design-system) | Published by the tool's maker |
| 9 | Agents can write to the Figma canvas through Figma's MCP server, using the team's components and variables [claim ind-figma-write: Figma developer documentation. Remote server only; in beta and free during the beta; source: https://developers.figma.com/docs/figma-mcp-server/write-to-canvas; confirmed] | [Figma MCP server](https://developers.figma.com/docs/figma-mcp-server/write-to-canvas) | Vendor |
| 9 | Supernova Editor MCP gives agents write access to a design system: documentation, tokens, components, files, skills, contexts and pipelines [claim ind-supernova-editor: Supernova blog post introducing Editor MCP, 1 September 2026; public beta, free during the beta; source: https://www.supernova.io/blog/introducing-supernova-editor-mcp; confirmed] | [Supernova, 1 September 2026](https://www.supernova.io/blog/introducing-supernova-editor-mcp) | Vendor |
| 10 | 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] | [shadcn/ui changelog](https://ui.shadcn.com/docs/changelog), [MCP docs](https://ui.shadcn.com/docs/mcp), [Basecoat](https://basecoatui.com/) | |
| 11 | 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] | [State of AI in Design Systems](https://state-of-ai-in-design-systems.netlify.app/) | Independent field study |
| 13 | 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] | [Anthropic](https://www.anthropic.com/news/claude-design-anthropic-labs), [release notes](https://support.claude.com/en/articles/12138966-release-notes), [move article](https://support.claude.com/en/articles/17440474-move-from-standalone-claude-design-to-claude) | |
| 14 | 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] | [Supernova, 13 November 2026](https://www.supernova.io/blog/claude-design-design-system) | Published by the tool's maker |
| 15 | 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] | same | Published by the tool's maker |
| 16 | 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] | [Figma](https://www.figma.com/blog/design-systems-ai-mcp/) | Vendor |
| 16 | 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] | [zeroheight](https://zeroheight.com/resources/state-of-ai-in-design-systems/) | Vendor |
| 17 | figlens, the JSON-export tool I use | [npm](https://www.npmjs.com/package/@krisztiaan/figlens) | Open source |
| 19 | 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] | [designtokens.org](https://www.designtokens.org/tr/2025.10/) | |
| 28 | Design System Checklist: 42 sections, 238 items in 4 categories [claim ind-checklist: Counted from its data files on 2026-11-16 (repo commit 28f06a2): design language 2/10, foundations 6/24, components 29/176, maintenance 5/28. Coverage, not quality; source: https://github.com/ardakaracizmeli/design-system-checklist; confirmed] | [Design System Checklist](https://github.com/ardakaracizmeli/design-system-checklist) | Counted from its data files |
| 29 | Voice & Tone plugin | [Voice & Tone](https://pavolhudran.github.io/ai-voice-and-tone/) | My own, open source |
| 30 | Rock8Cloud, where this site runs | [rock8.cloud](https://rock8.cloud/) | Made by ProRocketeers, where I work |

Figures from my own projects (slides 17, 20 to 22 and 25) have no public source. Each one is in the [claims registry](/claims.json) with its base.

## §4 · open source

### Install tonight

Voice & Tone is a Claude plugin built for marketing teams who write at scale. It applies the same method to words:

- It reads what you have already written and turns it into rules.
- Every rule shows who decided it and on what evidence.
- You pick between two rewrites of your own copy, not a score from 1 to 5.
- The tone follows the reader: no jokes for a frustrated customer.
- Plain Markdown in your repository: no database, no account.

Install it with `/plugin install voice-and-tone`. [The plugin's page](https://pavolhudran.github.io/ai-voice-and-tone/) · [How this site uses it](/voice-and-tone)
