How to use AI to build a prototype - Summer Sessions

Turn one idea into a prototype this week
Pick a real feature you’re considering (not a fake example) and commit to building an interactive prototype for it instead of writing a long PRD.

Rebuild your product shell once, then reuse it
Take 3–5 key screens from your app (or Figma) and ask your AI prototyping tool:
“Recreate this product shell with matching layout, navigation, and styling so I can reuse it as a baseline for future prototypes.”

Use prompts to tune visual details, not just copy
After the shell looks “close enough”, prompt for specific tweaks:
“Tighten spacing, soften borders, and match the primary button style in these screenshots while keeping everything responsive.”

Prototype multiple solutions before choosing one
For your chosen feature, ask:
“Generate 3 different UX approaches for this feature (e.g. sidebar, modal, inline section) using my existing shell. List pros/cons for each.”

Test real flows with realistic sample data
Paste real transcripts, documents, or example user data into the tool and ask it to wire mock APIs or LLM calls so you can click through realistic states instead of lorem ipsum.

Compare model and UX trade‑offs inside the prototype
Once flows work, prompt:
“Show this prototype using a ‘fast’ model vs a ‘quality’ model and explain how latency and answer quality change the UX.”

Share prototypes early with your team and users
Send the link to designers, engineers, and 3–5 target users and ask them to record a short loom or notes on: “What felt confusing?” and “What felt surprisingly good?”.

Let prototypes shape your roadmap, not slides
After feedback, summarise in one page:
“What we learned from the prototype, what we’re changing, and whether this feature moves onto the roadmap or gets parked.” Keep that as your new default way of making product decisions.

Treat prototypes as disposable experiments, not mini‑products
Time‑box each one (e.g. a day or two), keep scope narrow, and be willing to throw it away.
If it works, you can always recreate a cleaner version using the same prompts and baseline shell.

Make “prototype first” a habit in your team rituals
Add a weekly or bi‑weekly “prototype hour” where PMs and designers bring one idea, build or tweak a prototype together, and walk the team through what they learned instead of just showing slides.