Prototyping
Having the agent build a quick, rough version when conversation is too low-fidelity and you need a real artefact to talk about.
Prototyping is having the agent build a quick, rough version when talking is not precise enough. A sketch of an interface, a stub of the flow, a faked data shape: something you can point at, which is a different thing from something you can describe.
The reason it works is that the artefact answers questions the conversation could not. You can say what you want for ten minutes, or you can look at a rough version and say that is wrong in a way that is specific and actionable. The second one is much more productive.
It also has to stay cheap, which means it has to be explicitly disposable. A prototype that is good enough to keep becomes production code by accident, carrying its shortcuts and its fake data into the real system. The value comes from throwing it away.
Related terms
Design Concept
The shared understanding of what is being built, held in common between user and agent but separate from any asset.
Grilling
A technique for developing a design concept: the agent interviews the user one decision at a time.
Vibe Coding
Writing software by describing what you want and accepting the result without reading it closely.
Spec
A written description of what to build, written before building it.
Testing
The cheapest way to know a change is safe: a check that runs without a human reading anything.
Want this working inside your team?
It starts with one conversation about your workflow.