The moments that lead here
If one of these is your afternoon, you are in the right place.
Developers repeatedly misunderstand my dashboard exports and I want to make annotations a standard that reduces back-and-forth.
1 ready prompt
Written for the moment this actually comes up.
Become — change the pattern
+Over the last ten dashboard handoffs, ambiguous screenshots cost two days each in clarification.…
Become — change the pattern
+Over the last ten dashboard handoffs, ambiguous screenshots cost two days each in clarification. Propose a repeatable annotation protocol: what metadata to include with each export, how to mark issues so developers can reproduce them, and a short checklist I follow before hitting send. Explain one change in my export process that will cut clarification cycles by half.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Who does this, and with what
The same task is different work inside a different job.
Business Intelligence AnalystAdobe Acrobat
Next to this one
Other record work people do in Adobe Acrobat.
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.