The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Build a 24-icon system for Lark & Finch product UI: filled and outline versions at 24px and 16px…
Execute — do the immediate task
+Build a 24-icon system for Lark & Finch product UI: filled and outline versions at 24px and 16px grids, consistent stroke weight, and matching corner radii. Deliver SVGs with consistent viewBox and a single 12px padding rule. Include a sprite sheet and a PDF sheets previewing all icons on dark and light backgrounds. Complete by Wednesday noon for the front-end sprint.
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 give these to the front-end engineer, make the icons easy to implement: surface the stroke…
Improve — make it easier to accept
+Before I give these to the front-end engineer, make the icons easy to implement: surface the stroke weight and grid size on the title artboard, label which are semantic (success, warning, info), make the export names match the component tokens, and flag any icons that will be ambiguous at 16px.
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
+Dev reported that three icons collapse into the same shape at 16px; I’m worried the UI will confuse…
Decide — diagnose the stuck moment
+Dev says several icons look like others at 16px.
Dev reported that three icons collapse into the same shape at 16px; I’m worried the UI will confuse users and I can’t change the timeline. Which icons are likely the problem, what minimal edits keep visual language consistent, and what do I send dev as a quick swap set to avoid broken behaviour in tomorrow’s build?
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 projects we repeatedly tweak icons after dev has wired them, costing sprints. Where in our…
Become — change the pattern
+We redo icons late in development when they’re already coded.
Across projects we repeatedly tweak icons after dev has wired them, costing sprints. Where in our process are decisions leaking, what rule would prevent late visual changes, and which compact review ritual or deliverable would stop rework while keeping designers trustworthy?
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 vector design work people do in Adobe Illustrator.
Adjust character and paragraph stylesAlign and distribute objectsApply and edit strokes and fillsApply effects and appearance attributesAutomate repetitive tasks with actionsCollaborate via shared librariesCompare and revert to earlier versionsConvert sketches to vector artConvert text to outlinesCreate a new vector illustration
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.