The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Add Maya Thompson to my account as a team member with the role of Billing Assistant. Use her work…
Execute — do the immediate task
+Add Maya Thompson to my account as a team member with the role of Billing Assistant. Use her work email maya@studioforge.com and have her start on Monday, July 21. Notify her by email and give me a summary of the invitation status when done.
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 invite Maya Thompson as Billing Assistant, make the onboarding decision easy: show me…
Improve — make it easier to accept
+Before I invite Maya Thompson as Billing Assistant, make the onboarding decision easy: show me which existing role most closely matches Billing Assistant, list the permissions that role grants, indicate any gaps she’ll need for her day-to-day, and warn if the chosen permissions let her view or move money so I can restrict them if needed.
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 want to add Maya Thompson as Billing Assistant starting July 21 but she gave me two emails — a…
Decide — diagnose the stuck moment
+I need to add a team member but I’m unsure which email they’ll use
I want to add Maya Thompson as Billing Assistant starting July 21 but she gave me two emails — a personal Gmail and maya@studioforge.com. I’m worried an invite to the wrong account will block her access or expose finances. Which account should I invite now, what should I ask Maya before sending the invite, and how do I prevent duplicates and confusion?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the last quarter I’ve invited three contractors with wrong emails or wrong roles, which…
Become — change the pattern
+I keep creating excess user invites and dropping onboarding tasks
Over the last quarter I’ve invited three contractors with wrong emails or wrong roles, which created access holes and follow-up work. What standard checklist or single habit should I apply before sending any team invitation to avoid rework and security gaps?
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 payments work people do in PayPal.
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.