Figma Prototype Interaction and Flow Logic Review
Check that clickable flows match intended behaviour.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Review a Figma prototype. Flows and screens with the interactions defined (triggers, actions, transitions): [PROTOTYPE_DESCRIPTION]. Intended user journeys: [JOURNEYS]. Walk each journey as numbered steps with the screen, the action, the result in the prototype and the intended result, and mark mismatches. Look for dead ends, missing back paths, inconsistent transitions, uncovered states (error, empty, offline), unrealistic data, hover-only behaviour that fails on touch, and long animations (over about 400 milliseconds as a rule of thumb to test). Check the places that often fail: back navigation, closing overlays, form validation messages, doing nothing, and a long list. Rate each issue as blocking, confusing or cosmetic, count them, and show how many block a journey. Separate prototype limitations from design flaws. Return a table with Journey, Step, Problem and Fix, fixes in order, and the tasks to give testers so these issues are exercised. Mark feature names [VERIFY]. Say what you could not judge from my description, such as animation timing, and which screens you would want to see before giving a final view. Keep the findings in the order a tester would meet them.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.