The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+We need a payment link for a one-time consulting fee of $600 payable by end of month. Create a…
Execute — do the immediate task
+We need a payment link for a one-time consulting fee of $600 payable by end of month. Create a payment link that collects customer name, email, and company, shows the $600 total with tax included, includes our refund policy on the link page, and expires in seven days. Share the link with the founder and head of sales for approval before publishing.
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 a payment link for our $600 consulting fee, make it easy for clients to approve…
Improve — make it easier to accept
+Before I publish a payment link for our $600 consulting fee, make it easy for clients to approve and pay: show the total and tax up front, add a brief line explaining what happens after payment, make the required fields obvious, and call out anything that might make legal or procurement hesitate. Suggest two microcopy edits that reduce abandonment.
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
+Sales just asked for a payment link for a $250 pilot and want it live this afternoon. I don’t know…
Decide — diagnose the stuck moment
+Sales asked for a quick payment link for a pilot.
Sales just asked for a payment link for a $250 pilot and want it live this afternoon. I don’t know whether procurement will need an invoice number or company field. The sales lead, Kevin, wants speed; finance wants trackability. What is the likely trade-off and what single field should I add now to prevent reconciliation headaches?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every time sales asks for a pilot we build a unique payment link and later struggle to reconcile…
Become — change the pattern
+We repeatedly rebuild ad-hoc payment links.
Every time sales asks for a pilot we build a unique payment link and later struggle to reconcile and report. This wastes developer time and confuses finance. What standard template and naming habit should we adopt so payment links are uniform, searchable, and reconciliable across the team?
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 Stripe.
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.