The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Link the new signup, verification, and welcome screens into a linear prototype so the growth team…
Execute — do the immediate task
+Link the new signup, verification, and welcome screens into a linear prototype so the growth team can run conversion tests. Ensure the email verification screen routes back to signup on error and to welcome on success, and include back navigation to the previous step. Confirm the hotspot areas are tappable on phone breakpoints.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I hand this to growth, make the prototype easy to evaluate: surface where links diverge on…
Improve — make it easier to accept
+Before I hand this to growth, make the prototype easy to evaluate: surface where links diverge on success versus error, make the back navigation consistent across steps, label hotspots with tap area sizes, and flag any screens that lack a clear target for the user’s next action.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I tested the flow and entering a valid code leaves me stuck on Verification. Growth and engineering…
Decide — diagnose the stuck moment
+The verification screen doesn’t go to Welcome after success.
I tested the flow and entering a valid code leaves me stuck on Verification. Growth and engineering expect a smooth handoff; I suspect the success hotspot wasn’t linked or the Success state is misnamed. I can’t tell whether the issue is a missing link, a misrouted state, or a breakpoint problem. What quick steps find and fix the routing so the funnel test can run?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We repeatedly ship prototypes where a single forgotten link breaks a conversion funnel, costing us…
Become — change the pattern
+Prototypes often have divergent links that break funnels late.
We repeatedly ship prototypes where a single forgotten link breaks a conversion funnel, costing us days when growth needs tests. I need a compact routine to prevent this: what checklist and link-naming convention will ensure every success and error path is explicitly linked before we hand off?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other interface design work people do in Figma.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.