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 final PNG and SVG assets for the mobile app screens and icon set ready for…
Execute — do the immediate task
+I need the final PNG and SVG assets for the mobile app screens and icon set ready for implementation. Export every screen at 1x and 2x, name files exactly like the component IDs the engineering team uses, and put them in the shared build folder by Friday 5pm. Before exporting, check that every symbol is detached where developers expect vector assets and that text layers are outlined for the icons.
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 export, make it easy for engineers to pick up the assets: surface the pixel sizes and…
Improve — make it easier to accept
+Before I export, make it easy for engineers to pick up the assets: surface the pixel sizes and intended scale factor next to each artboard, make exported file names follow our repo convention, and flag any layers that are still using effects or masks that would break in code.
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 tried to export the icons for Android and several came out flattened instead of SVG.…
Decide — diagnose the stuck moment
+I clicked export and some icons came out rasterized.
I just tried to export the icons for Android and several came out flattened instead of SVG. Developers on the Android team will break if they get raster icons for different densities. I do not know whether those layers were converted to bitmaps or if an effect forced rasterization. Do you think the source components have non-vector effects or were they accidentally flattened when grouped? What is the fastest check and fix so I can re-export by the end of the day?
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 release I lose time re-exporting assets because file names, export settings, or vector…
Become — change the pattern
+I keep re-exporting after engineers report missing or wrongly named assets.
Every release I lose time re-exporting assets because file names, export settings, or vector treatments are wrong. I want a habit that prevents these last-minute fixes and avoids back-and-forth with Marco in Android. Which naming, layer-check, and pre-export review routine should I adopt so exports are right first time and take under 30 minutes?
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.