The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Create and refine the primary app icon as a vector shape set that scales cleanly. Start from the…
Execute — do the immediate task
+Create and refine the primary app icon as a vector shape set that scales cleanly. Start from the rough sketch on page three, convert it to boolean shapes with clean corner radii, ensure strokes are outlined so scaling doesn’t change weight, create 24px, 48px, and 96px export frames, and save as AppIcon-Vectors for the iOS build by Friday evening.
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 finalize these vectors for engineering and marketing, make them production-ready: simplify…
Improve — make it easier to accept
+Before I finalize these vectors for engineering and marketing, make them production-ready: simplify overlapping paths, remove unnecessary nodes, check corner radius consistency, and flatten compound shapes that might render differently in the build. Point out any shapes that will rasterize poorly at small sizes and recommend an alternate simplified form for 24px.
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 outlined strokes to keep weight consistent but at 24px the icon looks blurry in the simulator.…
Decide — diagnose the stuck moment
+I converted strokes to outlines and now the small-size icon blurs
I outlined strokes to keep weight consistent but at 24px the icon looks blurry in the simulator. I’m not sure whether I should simplify details, snap to pixel grid, or keep a stroke at small sizes. What’s the usual cause of this blur, what quick experiments should I run to confirm the fix, and which result should I hand to the iOS engineer to avoid extra rework?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across multiple launches our icons look great at 96px but fail at 16–24px, causing extra…
Become — change the pattern
+I repeatedly over-detail icons and they fail at small sizes
Across multiple launches our icons look great at 96px but fail at 16–24px, causing extra design-engineering iterations. What habit should I adopt when creating icons so they work across scales, and what concrete process (like a mandatory small-size pass or a two-variant rule) will stop us from shipping illegible icons?
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.