The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need to send an invoice to a client. Convert the invoice object with id 2026-0817, amount 425.5,…
Execute — do the immediate task
+I need to send an invoice to a client. Convert the invoice object with id 2026-0817, amount 425.5, currency USD, lineItems as an array into a JSON string and include it in the HTTP POST body to billing.example.com/invoices, then log the request body and the server response.
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 include this payload in the billing request, make the stringified JSON more reviewable:…
Improve — make it easier to accept
+Before I include this payload in the billing request, make the stringified JSON more reviewable: ensure numeric amounts keep two decimals, move metadata to a top-level metadata object, and show the final string with keys sorted so a reviewer can spot price or currency mistakes quickly.
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 tried POSTing a new invoice and the API returned 415 Unsupported Media Type; the code uses…
Decide — diagnose the stuck moment
+Server rejects invoice with unexpected body format
I tried POSTing a new invoice and the API returned 415 Unsupported Media Type; the code uses JSON.stringify but the server still complains. I’m not sure if I missed headers, included circular refs, or accidentally sent an object wrapper. What’s the most likely oversight and the minimal fix to get a valid request out now?
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 keep getting billing errors because different clients send semantically similar invoice objects…
Become — change the pattern
+Inconsistent client payloads causing billing errors
We keep getting billing errors because different clients send semantically similar invoice objects in different shapes. Each time I patch one client’s serializer. Which serialization habit should I standardize across the codebase to reduce these incidents, and what small validation or lint rule would stop the most common mistakes before they reach billing?
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 programming language work people do in JavaScript.
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.