The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Bring the header logos, hero images, and SVG charts from the legacy design files into the current…
Execute — do the immediate task
+Bring the header logos, hero images, and SVG charts from the legacy design files into the current project and place them into the assets page. Make sure raster images remain at original resolution, SVGs are cleaned of inline styles, and rename files to match our tokens: brand-logo-primary, hero-2026-q3, chart-sales-svg. Confirm export settings so engineering can pull PNGs and optimized SVGs.
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 import everything, make the asset import easy for reviewers: highlight any images that…
Improve — make it easier to accept
+Before I import everything, make the asset import easy for reviewers: highlight any images that will scale poorly, flag vector assets with inline fills or fonts, list files whose names don't match our tokens, and group assets by use case so a developer can pick the right one without opening the design file.
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 imported the SVG charts from the old files and now their colors render differently in this file.…
Decide — diagnose the stuck moment
+Imported SVGs display with wrong colors
I imported the SVG charts from the old files and now their colors render differently in this file. The engineer assumes brand tokens will be used and the PM will think I broke them. I don't know whether the color shift came from embedded styles, color profiles, or mismatched fill tokens. What's the likely cause and the quickest way to normalize these SVGs to our current token set?
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 migrate work from legacy files, the team spends days cleaning SVGs and renaming…
Become — change the pattern
+We repeatedly re-clean assets after migration
Every time we migrate work from legacy files, the team spends days cleaning SVGs and renaming assets instead of moving forward. I'm the person asked to fix it. Which three habits or checks around naming, token mapping, and a one-page import checklist will stop this recurring drain on time?
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.