Beginner · Workflow

Prompt → wire / mock

Bounded text or sketch → wire/mock for exploration — then a human picks the direction.

Purpose

Cases like Ingenico (Uizard) show prompt-to-mock collapses early alignment meetings. NN/g’s prototyping eval shows vague prompts scatter quality. Beginner practice: one job, one audience, a specific first prompt, a time-box, then stop — do not polish AI chrome as if it were the DS.

Steps

1. **Write the job** — what screen, who for, success check. Attach a rough sketch if you have one. 2. **First prompt front-loads five things** — product type, structure/sections, visual style, content tone, interaction expectations (Mantlr-style discipline; works across Stitch/Uizard). 3. **Generate ≤3 variants** — same brief; label each A/B/C with a one-line bet. 4. **Heuristic glance** — hierarchy, primary action, empty states. Do not pixel-fight. 5. **Decide or escalate** — pick a direction for a human redesign, or escalate to `spec-ai-prototype` with a longer brief and artifacts. Archive losers.

When to use / Skip

Use in discovery or stakeholder alignment when you need structure fast. Skip when the DS and flows are already locked — then use `narrow-canvas-assist` or profi handoff. Falsifier: if you are editing the AI mock for more than one focused hour, you left beginner track; move to medium `spec-ai-prototype` or redraw by hand.