Overview
How might we design prompt to ui so people can trust and act on AI output?
When to use
- Ideal for rapid prototyping tools, design-to-code platforms, and low-code development environments where speed from concept to implementation is critical.
When to skip
- Brand systems that forbid generative layout outside locked Figma libraries.
- Production engineering tools that need code ownership, not exploratory mock UI.
- Audience that only needs copy or images, not component structure.
Rules
Generated UI with no design-token or component-library grounding.
One-shot codegen with no visual select-and-edit loop.
Ignoring accessibility (labels, contrast, focus) in generated trees.
Overwriting hand-tuned layout on regenerate without a diff or lock.
Evidence
| Product | Implementation |
|---|---|
| v0 | Prompt → React UI with iterative refine and code export. |
| Framer AI | Generate and remix site sections inside the Framer canvas. |
| Builder.io | Prompt-assisted generation mapped to visual page building. |
| Relume | Sitemap and wireframe generation from prompts for Webflow/Figma flows. |