The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need the dashboard frames rebuilt with consistent auto-layout so components resize predictably.…
Execute — do the immediate task
+I need the dashboard frames rebuilt with consistent auto-layout so components resize predictably. Start with the main dashboard frame and convert its columns and cards to auto-layout, keep current padding and gaps, ensure nested buttons use horizontal auto-layout, and check that text fields don't collapse. Confirm visually in the 13” breakpoint and send back a single file named Dashboard-AutoFrame by Thursday noon.
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 engineers, make the layout easy to reuse and debug: surface the auto-layout…
Improve — make it easier to accept
+Before I hand this to engineers, make the layout easy to reuse and debug: surface the auto-layout direction and padding at the frame level, move fixed-width elements into separate non-auto frames, flag where nested auto-layouts will cause height jumps, and call out any text styles that will overflow. Produce a short list of three things that would make a reviewer hesitate to reuse these components.
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 switched the left column of the dashboard into auto-layout and several cards expanded vertically.…
Decide — diagnose the stuck moment
+I converted one column to auto-layout and now the card heights jumped unexpectedly
I switched the left column of the dashboard into auto-layout and several cards expanded vertically. Priya on front-end will have to reconcile this and we’re running into Friday’s demo. I’m not sure which nested component is forcing the stretch or whether I should revert just that column. What likely caused the height change, what should I inspect first, and what’s the fastest safe rollback to meet the demo?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the last three sprints I rebuild dashboard, settings, and reports frames from scratch instead…
Become — change the pattern
+I keep rebuilding similar frames rather than reusing a consistent auto-layout pattern
Over the last three sprints I rebuild dashboard, settings, and reports frames from scratch instead of reusing an auto-layout pattern. That wastes time and creates inconsistencies for engineering. What habit should I change so I stop duplicating work, and what practical steps make a single reusable auto-layout system that designers and engineers will actually adopt?
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.