02 / Design system workbench
UI Wand
Fieldhaus
The problem
A component kit usually shows one design language, so it is hard to tell which decisions belong to the system and which belong to the style.
UI Wand holds the components still and changes only the language, so the difference a style makes can be seen, handled and heard.
How it was built
No framework runtime and no bundle: plain HTML, CSS and classic scripts, with custom properties carrying the system and one self-contained document per style for the physics.
- 01
Tokens in three layers
Primitives, then semantic tokens, then one block per style that overrides semantic tokens only. The token file defines 132 custom properties, and 116 motion tokens sit beside them. All seven skins are loaded at once and scoped by html[data-theme], so the page restyles with one attribute change while the workbench frame swaps to that style's document.
All seven styles from the Style menu, one after another. - 02
Modern
Modern shares one document with Classic iPhone. Its 59 pieces are DOM elements in an iframe that can be dragged, thrown and knocked into each other, with an 8px radius and 40px controls set by its token block.
Modern: throw, Scatter, Go crazy, Align. - 03
Extrude
Extrude is DOM pieces with no rigid-body engine. Depth is two shadows, a light offset and a dark one, and press states are weighted; its token block sets 16px corners and 44px pill controls.
Extrude: throw, Scatter, Go crazy, Align. - 04
Primitives
Primitives has a document and an engine of its own, light physics over 56 pieces. Its source also carries the note on the hardest bug: a ready and keep-out message loop that rebuilt the physics world about 400 times a second, since fixed.
Primitives: throw, Scatter, Go crazy, Align. - 05
Gel
Gel is matter-js rectangles with a spring on each body's scale and a canvas ghost layer drawn through a goo filter, so the pieces squash and merge. Align stacks them into merged columns.
Gel: throw, Scatter, Go crazy, Align. - 06
Frost
Frost is drawn on a canvas: 55 pieces of 54 types, glass panes with a 22px blur and a white rim.
Frost: throw, Scatter, Go crazy, Align. - 07
Classic iPhone
Two skins, one DOM. Every piece in the shared document holds both the Modern and the Classic iPhone markup, and the page posts one message to swap them, so this switch needs no reload.
Classic iPhone: throw, Scatter, Go crazy, Align. - 08
Retro
Retro is a canvas platformer at 720 by 418, scaled two times, with 91 pieces of 51 types; Scatter drops them to the floor like a platform game. Its motion tokens are 360 ms with a 4px pixel step and no press scale, and its pixel font is self-hosted.
Retro: throw, Scatter, Go crazy, Align. - 09
The page and the frame talk
The page sends keep-out rectangles for the nav, the bar and the spec link, plus mute and bar actions. The frame answers ready, done and gesture. If no ready arrives in 4 seconds, a failsafe shows the frame anyway.
Using the Modern workbench, then Shake, Scatter and Align. - 10
Quality from frame time
A shared degradation ladder picks the quality level from measured frame time, never from screen width. With reduced motion the frame gets a reduced flag, the style switch is instant and the cursor dust is off.
The workbench as it settles, in all seven styles. - 11
Sound as data
Each style's sound pack is JSON over an .ogg sprite: 65 control types, 22 events and 492 samples per pack (519 in Retro), with written rate limits such as one hover sound per element every 250 ms.
The Sound page, sound turned on. The clip itself is silent. - 12
Specs as build artefacts
Each style's DESIGN.md has YAML front matter for colors, typography, radii, spacing and components, fourteen sections of rules, and a provenance section that cites CSS files and line numbers. tokens.json follows the design tokens format; theme.css is a Tailwind @theme block.
The DESIGN.md page, in Modern and in Retro. - 13
Every state, every style
The component sheet renders 18 rows and 120 cells, with is-hover, is-focus, is-active, is-disabled and is-loading classes that mirror the real pseudo-states, in every style.
One primary button, every state, in all seven styles. - 14
Private studies without a server
The private case studies are encrypted for the browser with AES-GCM, using a key derived with PBKDF2-SHA256 over 250,000 iterations and a salt per file. Decryption happens on the visitor's machine, and the comments set out the contract a real backend would keep.
The solution
A single non-scrolling workbench of about sixty pieces, a six-control bar and seven styles, with a component sheet, a sound page and a design page behind it.
Per style, a DESIGN.md, a tokens.json in the design tokens format and a Tailwind theme.css, ready to download.
Decisions along the way
No framework
Hand-written HTML, CSS and classic scripts with no build step, and each style's engine in one self-contained document.
Same DOM, two skins
Keeping both markups on every piece let the two closest styles swap with one message instead of a reload.
Frame time, not screen width
Quality steps down when frames run long, whatever the size of the screen.
Re-parent the menu
A backdrop-filter on the bar made the fixed style menu clip and stop taking clicks. While it is open, the menu now moves to the body.
What I delivered
- The workbench home page, in seven styles
- A bar with six controls: style, sound, shake, align, scatter and go crazy
- A component sheet: 18 rows, every state, every style
- A sound page with a pack per style
- A DESIGN.md, tokens.json and theme.css per style
- Private case studies behind a password, decrypted in the browser
Value added
For engineers
Seven very different engines behind one small message protocol, on a static site with no framework.
For AI tools
Each style is three readable files: a markdown spec with provenance, DTCG tokens and a Tailwind theme.
By the numbers
The result
Live at uiwand.com: the workbench, a component sheet, a sound page and a downloadable spec for each of the seven styles. The case studies on the site are private.
Results
- 7design languages over one component kit
- 6controls on the workbench bar
- 3files per style for AI tools: DESIGN.md, tokens.json, theme.css
What I took from it
Putting each style in its own document let the styles differ in physics, not only in CSS. The protocol between the page and the frame is what keeps that safe, and it is also where the hardest bug lived: a ready and keep-out message loop that rebuilt the physics world about 400 times a second until it was fixed.
Background
Two open formats sit behind the downloads. The Design Tokens Community Group publishes the format tokens.json follows, and Tailwind CSS reads a theme from an @theme block. The rigid and soft bodies on the workbench come from matter-js, an open-source 2D physics engine, and the private case studies use the browser's own Web Crypto API.