Medium · Workflow

Spec’d AI prototype

Detailed brief plus artifacts beat vague prompts — then critique like a design review.

Purpose

NN/g’s prototyping evaluation showed specific prompts and attached artifacts (sketch, mock, Figma frame) pull tools toward human-quality structure; broad prompts scatter. Medium practice upgrades beginner `prompt-to-wire-mock` with a real brief, DS constraints, and a heuristic review — still not a silent ship.

Steps

1. **Assemble the packet** — goals, users, components list, brand constraints, states (empty/error/loading). 2. **Attach artifacts** — sketch photo, existing mock, or Figma frame URL — not text alone. 3. **Generate once from the packet** — prefer Make/Stitch/code prototype tools; save the prompt with the file. 4. **Heuristic review** — compare to the human reference or NN/g-style checklist; list gaps, do not “vibes approve.” 5. **Decide** — accept as exploration prototype, schedule human redesign, or escalate to profi handoff with Code Connect/MCP.

When to use / Skip

Use when discovery mocks are not enough and stakeholders need interactive fidelity. Skip when you only need mood (`concept-visual-explore`) or when production code is the goal without a decide gate — that is `mcp-design-to-code` after `brief-decide-handoff`.