Evidence
System surface
No public screenshot on file, generative preview stands in for the visual layer.
Story arc
How this shipped
Building the tools that build the toolsThree beats: what pressed against the work, how the stack answered, and what changed once it was live.
I · Constraint
The brief
AI screenshot-to-code tools invent generic markup that ignores your design system, and they hide how they got there. Developers get garbage JSX with no way to trust or steer it.
II · Build
The craft
Grounded generation in a real component catalog via an in-prompt whitelist (no vector DB, no credentials). Added "what the AI sees" inspector with per-element confidence and grounded/inferred/guessed tags, a Sandpack live-editable preview, a compile-check self-repair loop, and an axe-core accessibility score with one-click fixes.
III · Proof
What moved after launch
Won the DEV.to GitHub Finish-Up-A-Thon. 38 tests. Reuses real components instead of inventing markup, renders live and editable, and self-repairs both compile errors and accessibility violations on one click.
Signals
Signals & scale
Engine room
At a glance
Inventory