The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Restore the version from last Thursday at 4pm and make it the current working file. Before…
Execute — do the immediate task
+Restore the version from last Thursday at 4pm and make it the current working file. Before replacing anything, export a PDF of the most recent changes and save a copy of the latest branch named 'post‑review' for legal. Notify Priya in product and Sam in QA that the file has been restored and ask them to recheck the updated flows by Friday end of day.
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 pick a version to restore, make it easy to compare candidates. Show the last five major…
Improve — make it easier to accept
+Before I pick a version to restore, make it easy to compare candidates. Show the last five major saves with who made them, the top three artboards changed in each, and a one‑line summary of why they were changed. Highlight any commits that removed assets or modified tokens so I can avoid restoring a bad state.
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 accidentally pushed an iteration that removed the new button states and three assets. Product…
Decide — diagnose the stuck moment
+Accidentally published a bad iteration
I accidentally pushed an iteration that removed the new button states and three assets. Product flagged it and the team wants the previous version, but I’m not sure which save includes the exact fixes from yesterday’s review. Restoring the wrong version will reintroduce bugs. What’s the quickest way to identify the correct prior version and safely restore it without losing today’s unrelated edits?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every time we try to roll back changes, we spend hours reconstructing which save had the right mix…
Become — change the pattern
+Version rollbacks disrupt progress every release
Every time we try to roll back changes, we spend hours reconstructing which save had the right mix of fixes and new work. That creates friction with engineering and makes me babysit versions instead of designing. What process and naming habits should I adopt so version history is reliable and rollbacks take minutes, not days?
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.