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 a library of reusable symbols for Lark & Finch: header, footer, CTA button states, input…
Execute — do the immediate task
+Create a library of reusable symbols for Lark & Finch: header, footer, CTA button states, input field, and card component as artboard-based symbols with named overrides for text and icons. Ensure instances retain constraints and exportability. Publish the library and include a changelog PDF showing token mappings. Deliver before Monday morning so product can prototype.
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 symbol library, make it easy for product designers to adopt: surface which…
Improve — make it easier to accept
+Before I publish the symbol library, make it easy for product designers to adopt: surface which overrides are safe to change, list which properties are tied to global tokens, add a ‘do not edit’ note on master components, and flag any dependencies that will break when the library is updated.
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
+A junior just edited the master CTA symbol and it cascaded changes across dozens of pages; I’m…
Decide — diagnose the stuck moment
+A junior designer edited a master symbol and broke multiple pages.
A junior just edited the master CTA symbol and it cascaded changes across dozens of pages; I’m worried about accidental edits and I can’t revert without losing recent requested tweaks. What’s the likely cause, what immediate rollback or containment steps do I take, and how do I communicate the fix to the team to avoid blame?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We repeatedly lose time to people editing masters instead of using instances, causing regressions.…
Become — change the pattern
+Team members keep modifying masters instead of using instances.
We repeatedly lose time to people editing masters instead of using instances, causing regressions. Which policy, tooling convention, or onboarding habit prevents accidental master edits, and what small changes to the library structure would make correct usage the path of least resistance?
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.
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.