𝗜 𝗳𝗼𝘂𝗻𝗱 𝗮 𝗱𝗲𝗮𝗱-𝘀𝗶𝗺𝗽𝗹𝗲 𝘄𝗮𝘆 𝘁𝗼 𝗰𝘂𝘁 𝗨𝗜 𝗰𝗹𝘂𝘁𝘁𝗲𝗿 𝘄𝗵𝗲𝗻 𝘃𝗶𝗯𝗲-𝗰𝗼𝗱𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁𝘀.

While building a visual forensic UX research tool using Google AI Studio, I found a trick to fix UI/UX issues when vibe-coding: instead of treating the AI as one assistant who "fixes" your interface, I started running it as multiple simulated users each with their own goals, frustrations, and blind spots.

𝗧𝗵𝗲 𝗽𝗿𝗼𝗺𝗽𝘁:
"𝘈𝘤𝘵 𝘭𝘪𝘬𝘦 𝘢 𝘜𝘟 𝘳𝘦𝘴𝘦𝘢𝘳𝘤𝘩𝘦𝘳. 𝘚𝘪𝘮𝘶𝘭𝘢𝘵𝘦 𝘩𝘰𝘸 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘵 𝘶𝘴𝘦𝘳𝘴 𝘸𝘰𝘶𝘭𝘥 𝘦𝘹𝘱𝘦𝘳𝘪𝘦𝘯𝘤𝘦 𝘵𝘩𝘪𝘴 𝘪𝘯𝘵𝘦𝘳𝘧𝘢𝘤𝘦: 𝘢 𝘳𝘶𝘴𝘩𝘦𝘥 𝘤𝘰𝘮𝘮𝘶𝘵𝘦𝘳 𝘤𝘩𝘦𝘤𝘬𝘪𝘯𝘨 𝘪𝘵 𝘰𝘯 𝘮𝘰𝘣𝘪𝘭𝘦, 𝘢 𝘴𝘬𝘦𝘱𝘵𝘪𝘤𝘢𝘭 𝘦𝘯𝘵𝘦𝘳𝘱𝘳𝘪𝘴𝘦 𝘣𝘶𝘺𝘦𝘳 𝘦𝘷𝘢𝘭𝘶𝘢𝘵𝘪𝘯𝘨 𝘴𝘦𝘤𝘶𝘳𝘪𝘵𝘺, 𝘴𝘰𝘮𝘦𝘰𝘯𝘦 𝘸𝘩𝘰 𝘴𝘬𝘪𝘱𝘱𝘦𝘥 𝘵𝘩𝘦 𝘰𝘯𝘣𝘰𝘢𝘳𝘥𝘪𝘯𝘨. 𝘞𝘩𝘦𝘳𝘦 𝘥𝘰 𝘵𝘩𝘦𝘺 𝘨𝘦𝘵 𝘴𝘵𝘶𝘤𝘬? 𝘞𝘩𝘢𝘵 𝘥𝘰 𝘵𝘩𝘦𝘺 𝘮𝘪𝘴𝘶𝘯𝘥𝘦𝘳𝘴𝘵𝘢𝘯𝘥? 𝘍𝘰𝘳𝘮𝘢𝘭𝘪𝘻𝘦 𝘢 𝘤𝘰𝘯𝘤𝘪𝘴𝘦 𝘳𝘦𝘱𝘰𝘳𝘵 𝘪𝘯 𝘶𝘹_𝘳𝘦𝘴𝘦𝘢𝘳𝘤𝘩.𝘮𝘥 𝘧𝘪𝘭𝘦 𝘢𝘯𝘥 𝘴𝘶𝘨𝘨𝘦𝘴𝘵 𝘤𝘩𝘢𝘯𝘨𝘪𝘯𝘨𝘴."

𝗪𝗵𝘆 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀: The AI generates structured, persona-based feedback instead of generic suggestions. You get specific friction points, not fluff.

𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁: Faster iteration, less bloat, and UI decisions backed by simulated multi-perspective research without the research timeline.

No frameworks. No buzzwords. Just a prompt that forces the AI to argue with itself before it gives you advice. And finally, you can implement without getting headache when you ask AI for changings and it removes functionalities in app.

Building with Cursor, Antigravity, or AI Studio? Try it on your next screen.