The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Resolve the unblockers on the checkout redesign: accept the legal copy changes that don’t affect…
Execute — do the immediate task
+Resolve the unblockers on the checkout redesign: accept the legal copy changes that don’t affect layout, push the promo code edge case to a follow-up ticket, confirm the success state with payments, and tell Priya in product and Daniel in payments the final decision and next ticket owners.
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 close feedback on the checkout, make the resolution easy to approve: summarize each open…
Improve — make it easier to accept
+Before I close feedback on the checkout, make the resolution easy to approve: summarize each open issue with our position, mark which require design changes vs engineering work, show the trade-off for each choice, and recommend the minimal changes to ship on Monday.
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
+Legal handed a rewrite this morning that would push our launch past the committed date. I am the…
Decide — diagnose the stuck moment
+Legal demanded a rewrite that would delay launch
Legal handed a rewrite this morning that would push our launch past the committed date. I am the designer, legal lead is Omar, and the product manager pledged the current launch. I don’t know whether Omar will accept a narrower scope or insist on full rewrite. What’s the likeliest posture and the best next move to keep the launch date?
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 delay launches because small unresolved feedback accumulates into big scope changes.…
Become — change the pattern
+Small feedback threads keep delaying launches
We repeatedly delay launches because small unresolved feedback accumulates into big scope changes. I coordinate launches across product, legal, and payments. Which habit should I change to stop tiny comments from derailing release dates and how do I enforce it?
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.