The moments that lead here
If one of these is your afternoon, you are in the right place.
I've been the team's de facto keeper of record rules; we still get tripped up by inconsistent filenames and duplicate files during audits.
1 ready prompt
Written for the moment this actually comes up.
Become — change the pattern
+Across the last [N=40] closed complaints, auditors lost time because there were three different…
Become — change the pattern
+Across the last [N=40] closed complaints, auditors lost time because there were three different 'final' versions in three places and no clear naming convention. Propose a retention and naming rule set that prevents duplicate authoritative records, keeps customer-facing and internal drafts distinct, and is simple enough for a ten-person CS team to adopt. Explain the trade-offs and the one enforcement check I should add to our weekly QA.
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.
Customer Service RepresentativeAdobe 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.