The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+We need a coherent icon set for the product release: 48 icons covering navigation, actions, and…
Execute — do the immediate task
+We need a coherent icon set for the product release: 48 icons covering navigation, actions, and status. Produce filled and outline styles, 24px grid, consistent stroke weight and corner radii, and export-ready slices for SVG and PDF. Include naming that matches the app taxonomy like Home, Search, Save, Error, and Active and put them in a single icon page for handoff.
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 publish the icon set, make it approval-friendly: surface any icons that deviate in stroke,…
Improve — make it easier to accept
+Before I publish the icon set, make it approval-friendly: surface any icons that deviate in stroke, list icons that duplicate metaphors, flag ambiguous symbols, and reorder so the most used app actions appear first. Also add a short usage note about when to use filled versus outline.
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 just handed the icon set to engineering and they flagged inconsistent stroke weights and…
Decide — diagnose the stuck moment
+Design criticized for inconsistent stroke weights during handoff
I just handed the icon set to engineering and they flagged inconsistent stroke weights and mismatched optical centers. The product manager expects a single source of truth and the release is two weeks away. I don't know if the problem is in vector boolean operations, exported SVG precision, or my grid alignment. Which issue is likely and what step-by-step fix makes the set ship-ready today?
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 project forks the core icons—some teams add icons, others tweak strokes—and we lose…
Become — change the pattern
+Each project ends up with slightly different icons
Every project forks the core icons—some teams add icons, others tweak strokes—and we lose consistency and time reconciling them during QA. I'm the design lead and need a daily habit to stop this drift. What governance, naming conventions, and lightweight checks should I enforce so the icon set stays unified across teams?
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.