§0talk

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

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.

§1start

Four steps to start this week

For you, if you run a design system and want coding agentsAn AI program that writes and changes code, for example Claude Code or Cursor. On this site, "agent" means a coding agent. 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, 42 sections and 238 items.
  2. Write a short rules file that names what the agent gets wrong, with the correct replacement.
  3. Number your decisionsA written choice of the team, with an id, a reason and the check that enforces it. On this site, a row of the register. and add an "Enforced byThe field of a decision that names the check that proves it, or says "not enforced (gap)"." column. Leave it honestly empty where nothing checks the rule.
  4. Add one check that runs in CIContinuous integration: the checks that run on each change of the code. for the rule that hurts most.

Find your level

§2abstract

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 tokensA named design value, for example a color or a spacing step, kept as data. DTCG 2025.10 gives the file format.. The second is connecting the design system to AI agents through MCPModel Context Protocol. The open protocol that agents use to read tools and data. (Model Context Protocol). I show what this means in practice and why it concerns small teams too, not only the enterprise.

  • Why shadcn/uiA set of open-source components that you copy into your code. Agents know it well. 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 registryA list of the components of a system that a tool or an agent can read. and generates code that fits the existing tokens and Tailwind theme, practically without driftA difference between the design system and what was built. 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.
  • No LangChain layer runs today. What runs is skillsA file that tells an agent how to do one task. In my method, a skill applies a rule. It does not make one., hooks, sub-agents and deterministicGives the same result each time, with no language model. scripts. The next step is an open framework for design-system rules, and I want to build it with others. Read the white paper 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.
§3sources

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 Supernova, 21 October 2026 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 Figma MCP server Vendor
9 Supernova Editor MCP gives agents write access to a design system: documentation, tokens, components, files, skills, contexts and pipelines Supernova, 1 September 2026 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 shadcn/ui changelog, MCP docs, Basecoat
11 20 of 21 open-source design systems ship an MCP server, counting official and community servers State of AI in Design Systems 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) Anthropic, release notes, move article
14 Colours outside the system across three screens: 10 from screenshots, 0 from code and tokens Supernova, 13 November 2026 Published by the tool's maker
15 Even from code: 7 off-scale spacing values, 2 components not in the system same Published by the tool's maker
16 68% of developers use AI to write code; 32% of designers and developers trust the output Figma 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 zeroheight Vendor
17 figlens, the JSON-export tool I use npm Open source
19 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 designtokens.org
28 Design System Checklist: 42 sections, 238 items in 4 categories Design System Checklist Counted from its data files
29 Voice & Tone plugin Voice & Tone My own, open source
30 Rock8Cloud, where this site runs 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 with its base.

§4open 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 · How this site uses it