How I work

Build the check, then break it.

I don't just make the file. I build the check that proves it's right, and I test the check by breaking it on purpose.

The ship report: four stations cleared, six inspections passed, three open items listed in plain sight.
The ship report: four stations cleared, six inspections passed, three open items listed in plain sight.
Mark and wordmark as a fixed pair: wordmark 1.25× the mark, gap = mark height ÷ 6.
Mark and wordmark as a fixed pair: wordmark 1.25× the mark, gap = mark height ÷ 6.
The plugin: paste HTML and CSS, get native, editable Figma layers. The bridge polls the relay for jobs.
The plugin: paste HTML and CSS, get native, editable Figma layers. The bridge polls the relay for jobs.
Newsletter Issue 01, the real send (2026-07-24), rebuilt from spec with QA 22/22.
Newsletter Issue 01, the real send (2026-07-24), rebuilt from spec with QA 22/22.

Three things stay in sync

Figma, the code, and the live site all win. None of them is the source of truth on its own. A change in one of them is a change in the others, in the same session. The design system names every value once. The bridge moves a page into Figma and back. The gates fail the file on purpose. The pipelines refuse to ship a quiet error.

Figma, code, and the live site, each connected to the other two in both directions. Figma Wide / Compact Code aux-tokens.css Live site The theme
Each line runs both ways.