Agree on what you’re building before anyone polishes it. The spec becomes a schema you can see and change, and the first screens follow.
Context
Most of the time goes into rework, not design.
Every tool is getting better in its own lane. Figma and Paper on the canvas, Cursor and Claude in the editor, and nothing between them. So a designer spends a day in Figma, then a day fighting a model to make it build and look right. Then it goes in front of product and leadership, and the real problems show up: the wrong thing, the right thing the wrong way, or a PRD two people read differently. One ambiguous line in a ticket, and it’s back to the drawing board.
Almost all of that is rework. Polish and design-system decisions spent on something nobody had agreed on yet, because the gaps don’t show until someone makes it concrete. I wanted the concrete thing to exist earlier and cost almost nothing. Not words in a Jira ticket, but a living artifact made from those words that everyone can point at and change.
Outputs & Outcomes
Paste the spec. Get a blueprint you can see, change, and build from.
Start with a few sentences, a spec, or a whole PRD. A model pulls out what the product is made of: the objects, what people can do with them, and how they relate. That becomes a relational schema you can see on a canvas and move around, and the first screens come from the same structure. Where the nav goes, whether a button opens a drawer or a modal, what a list shows. Most of an interface is a few primitives, a string, a selector, an input, and lists you can create, read, update, and delete. Semantic builds up from those.
The schema is what the team reviews. If a PM reads the spec one way and I read it another, it shows up as a wrong relationship on the canvas and gets fixed in a minute, not in a prototype a week later. Polish, interaction, and the design system start once the structure is agreed on, which is where the judgment actually matters.
Loading studio
Ambiguity surfaces before the prototype. A misread spec shows up as a wrong object or relationship on the canvas, fixed in a minute instead of a week.
A living blueprint instead of a ticket. The spec becomes a schema everyone can see and change, and the screens stay tied to it.
Polish happens once. Interaction, UI, and design-system work start after the structure is agreed on, so they don’t get redone.