02 / Design tooling
Stitchwand
Fieldhaus
The problem
Google Stitch turns a prompt into screens. What it needs around it is a design system to follow, prompts that steer it somewhere new, and a way to check what comes back. Stitchwand is that workspace.
Design tokens live in many formats: Style Dictionary, Tokens Studio, Tailwind, plain CSS variables. DESIGN.md gives a design system one readable file for people and for AI tools. Getting tokens into that file, checking a page against it and seeing what changed between two versions were all jobs done by hand.
AI design tools add a problem of their own. Left alone they drift to the same look: purple gradients, Inter everywhere, sparkle icons, bento grids. Something has to tell them what not to do.
How it works
The design question was what a design system should be able to say no to. Seven validation rules cover what a reviewer checks by eye, from color and contrast to heading order and touch targets, and a list of more than 80 named anti-patterns covers the look AI tools drift to on their own.
- 01
A web address becomes a design system
Paste a web address and Stitchwand reads the page and its stylesheets and writes a DESIGN.md. Pointed at gov.uk it found 40 colours, 16 type values and 12 spacing values in two stylesheets and turned them into a 79-token system card.
A web address becomes a design system. - 02
Start from a real design system
The library holds 116 design systems to start from, from Google Material and Primer to GOV.UK. Each opens as a designer reads it: palette, type scale, spacing and sample components, with an editor and a merge beside it. One active DESIGN.md then follows you from tool to tool.
A library of 116 design systems. - 03
Starter Kits
Five steps, describe, colours, typeface, style and name, produce a DESIGN.md, a rendered preview and a prompt ready for Stitch. Forty quick themes, or the colours of any system in the library.
Starter Kits, from a description to a DESIGN.md and a Stitch prompt. - 04
The tool that knows what not to do
Eighty-two named clichés sit in eight groups as chips, from Purple Gradients Everywhere on. Tick one and the prompt gains a Patterns to minimize block as you watch. They are soft constraints: what you ask for outright still wins.
Anti-patterns as chips; the prompt gains a soft-constraints block. - 05
Prompts with their reasons
The Prompt Library holds 164 prompts in 13 categories, each with an anti-pattern note and the reasons it works, beside templates with variables and a seven-step Prompt Builder whose preview grows as each step is answered.
Prompts with their tips and anti-patterns. - 06
Design by multiplication
Design Swarm shows its arithmetic before you generate: 4 components times 3 layouts times 3 visual styles is 36 variant prompts. It writes the prompts; Stitch does the drawing.
Design Swarm: components times layouts times styles. - 07
Tokens in, DESIGN.md out
Token Studio turns Style Dictionary, Tokens Studio, Tailwind or CSS variables into a DESIGN.md with a readable preview, and exports to twelve formats.
Token formats in, DESIGN.md out. - 08
Seeing tokens
Five ways to look at a token set: a tree, a relationship graph, a usage heatmap, a matrix and a sunburst. They draw a built-in sample token set, not the selected system.
Five visualisers in turn. They draw a built-in sample token set. - 09
Findings that open
Validation sets the page Stitch made against the active DESIGN.md. Each finding is a row that opens to its rule, the element, the detail and a fix, with a Copy Prompt button to hand the fix to an assistant.
Sample HTML validated against the active DESIGN.md. - 10
From D to A
The accessibility lint cites WCAG for every issue. Fix the HTML and run it again: the same sample card goes from 64.5 with 11 violations to 100.
Accessibility lint on a sample card, then the fix. - 11
One block of HTML, many frameworks
Paste HTML and get React, Vue, Svelte, Angular, plain HTML, CSS and JS, or Markdown docs, with the component tree, the props and a prompt to refine it.
One block of HTML, shown in React, Vue, Svelte and Angular. - 12
Documents
Twelve document types, from product requirements on. Each gives a prompt to run in Stitch, then takes the reply back and formats it.
Twelve kinds of document. - 13
Dark, with a light theme
Dark by default with a full light theme: near-black surfaces, an indigo accent, Inter for text and JetBrains Mono for code, and slow drifting colour behind the app.
The light theme. - 14
Small screens
At phone width the sidebar becomes a rail of icons.
At phone width, the sidebar becomes a rail of icons.
The solution
Stitchwand is one core library with three surfaces. Developers run the CLI in a terminal, AI assistants call six tools through the MCP server, and everyone else opens the web app at stitchwand.com with no sign-in.
The three packages are on npm under MIT. Accounts, a database and paid plans are planned and not built; what a user saves stays in the browser.
Decisions along the way
Core first
Every engine lives in one library with no interface attached. The command line, the MCP server and the web app are thin, so a fix lands in all three at once.
Soft constraints
The anti-pattern list steers, it does not forbid. Ask outright for a purple gradient hero and you get one. You just never get one by accident.
Rule IDs and locations
A validation result names the rule it broke and where, so a person or an assistant can fix the exact line instead of guessing.
Free of accounts for now
Settings, systems and templates persist in the browser. Sign-in, a database and paid plans are planned and deliberately not built yet.
What I delivered
- The core library: convert, validate, diff, lint, components, Figma export, test generation and parity scoring
- A CLI with five commands
- An MCP server with six tools, listed in the official MCP Registry
- A Next.js web app with a library of 116 design systems
- A list of 82 named anti-patterns in eight groups
- 614 tests across 48 files
Value added
For designers
A page can be checked against its design system before the review, and every problem comes back with the rule it broke and where.
For design system teams
Tokens move from Style Dictionary, Tokens Studio, Tailwind or CSS variables into DESIGN.md in one step, and two versions of a system can be compared side by side.
By the numbers
Commits per week, spring 2026
164 of the 165 commits fall between 29 March and 30 April; one more came on 21 November.
View as table
| Period | Value |
|---|---|
| 23 Mar | 11 |
| 30 Mar | 25 |
| 6 Apr | 97 |
| 13 Apr | 28 |
| 20 Apr | 0 |
| 27 Apr | 3 |
Source: git history of the Stitchwand repo
The result
The web app runs at stitchwand.com with no sign-in. The core library, the CLI and the MCP server are on npm under MIT, published in April 2026, and the MCP server is listed in the official MCP Registry. All 614 tests pass across 48 files. Accounts, a database and paid plans are planned and not built. I presented it at Google Cloud Next 2026 in Las Vegas.
Results
- 614tests passing across 48 files
- 116design systems to start from
- 82named anti-patterns, as soft constraints
What I took from it
The most useful file in the repo is a list of things not to do: purple gradients, Inter everywhere, sparkle icons, bento grids. Naming the clichés made them easy to avoid. Keeping them as soft constraints mattered just as much: a designer who asks for a purple gradient still gets one. It just never arrives by accident.
Background
Stitchwand sits between a few open pieces. Stitch is Google's tool for generating interface designs. The Model Context Protocol is an open protocol that lets AI assistants call outside tools, which is how an assistant reaches Stitchwand's six. Style Dictionary is one of the token formats it converts from, the Design Tokens Community Group publishes the format the field is converging on, and WCAG sets the contrast floors the linter checks.