Design system·2026·lilaquadrat
No Handoff
Figma describes a product. Code is the product. With one designer next to a team of developers, the two kept drifting apart. So Studio's design system, its rulebook and the shipped product are one artifact, written for three readers: designers, developers, and the agent that now builds UI from the same parts.
- Role
- Product designer, sole design owner
- Product
- Studio, B2B content platform
- Built with
- Vue, Less, Claude Code
- Status
- Shipped, in daily use
Problem
A description drifts from the thing it describes
Every mockup had to be translated into code by a developer, and every translation drifted a little: a spacing value nobody chose, a button variant that existed in one screen only.
Now an agent builds UI from the same parts too. Where a person makes a judgment call, an agent fills the gap with a confident guess.
Solution
Two sources, one loop
A style guide for people and a rulebook for the agent, both describing the code that ships. I design inside the product, and every change goes round the same loop before it reaches the team.
Renders the real shipped partialsDocumentation that can't go stale
Every pattern written as a checkThe same knowledge, as context
- DesignerDesign in the product
- Script + agent/design-check
- Agent/design-push
- Developers/design-review
↺Every lap ends where it started, so a mistake can't outlive one pass.
Style guide
What you see is what ships
Not a Storybook and not a hand-kept copy: a route inside the product that mounts the real partials, 45 specimens of them. It can't go stale, because it is the code.
Foundations first, then every form control in each of its states.
Style guide
Down to how each part behaves
Then navigation, panels and tiles, and the interaction patterns: how a destructive action arms, how a save closes, where the remove button sits.
The guide ends on the rulebook checklist, the same list /design-check audits against.
Rulebook
Judgment, written down
To a person, a vague rule is a judgment call. To an agent, it's an invitation to invent a variant. So every pattern says when it applies, which part to use, and what not to do, and ends in a Check: line a machine can verify. This is the one for deleting things.
4.4 Destructive action flow
Permanent deletions are confirmed inline, never in an overlay. The footer button arms a confirm inside the same panel, with an acknowledgment where the loss can't be undone, and only then does the danger button act. While armed, the danger button sits left and the safe “Keep …” button sits right.
Which button depends on where the remove sits:
- danger-secondary in a panel footer, standing alone on its own line
- danger-ghost inside a panel that already has outlines, so it doesn't add a third box
- danger-quiet next to a grey quiet button, so the pair share a shape
- danger for the confirm step only
Check: no window.confirm, no modal for deletions; armed footer = danger left, safe right.
25 patterns like this one, and every rule changes in the same commit as the code it describes.
Enforcement
A script for the fixed rules, the agent for judgment
/design-check first runs a script over the change: raw hex, grey primitives, rounded corners, raw spacing and type, each with the token that should replace it.
The agent then reads what a script can't: a deletion without its inline confirm, a hand-built control that duplicates a partial. Its first full sweep found rounded corners in a product whose first rule is sharp corners. Some became written exceptions, the rest went sharp. The agent found them. I made the call.
Handoff
The handoff is one command
/design-push carries branching, merging, conflicts, review packaging and cleanup, through three skills I wrote. I never touch git, and developers never reverse-engineer a mockup: they review real code with /design-review.
Result
Agents do the watching. I answer for it.
Screens can be generated now, but always from something: the tokens, the components, the rules. That part doesn't move, and it's the job. When something ships wrong, “the agent decided” isn't an answer.