Figma describes a product. Code is the product. A description drifts from the thing it describes unless something forces them back together, and on a team of one nothing does. So the design system, the rulebook and the shipped product are one artifact. Nothing to translate, nothing to drift.
Not a Storybook of isolated stories, not a hand-maintained copy. A route inside the product that mounts the real partials. Because it runs, it holds what a frame cannot: a row that opens its edit form inline, and the same component answering at phone width in the window beside it.
Every pattern carries a Check: line, the rule restated so a machine can verify it. That single constraint is what turns a reference into something enforceable.
This is what /design-check actually returns: every file in the change, audited against the rulebook, each violation handed back with the line and the rule it broke. I run it, developers run it, and the rulebook does not care whose code it is. Not an opinion about the work. A finding.
Branching, merging, conflict resolution, review packaging, cleanup, all of it carried by three skills I wrote. I never touch git; developers never reverse-engineer a mockup.
Three months inside the product the system describes. Every number below is something the loop keeps true without anyone remembering to check.