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 POST JSON to https://api.example.com/v1/orders to create order 9045. Include…
Execute — do the immediate task
+I need to POST JSON to https://api.example.com/v1/orders to create order 9045. Include Authorization Bearer token stored in auth.token, send Content-Type application/json, and retry once on network failure. Return the parsed JSON response so I can update the UI immediately.
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 send this request to the payments API, make it easy for a reviewer to approve: surface the…
Improve — make it easier to accept
+Before I send this request to the payments API, make it easy for a reviewer to approve: surface the exact headers and body up front, highlight any sensitive fields being sent, show the retry logic and timeout value, and flag anything that would make a procurement reviewer hesitate such as using a non-HTTPS URL or long timeouts.
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 posted to the orders endpoint for order 9045 and the call timed out three times. The payment team…
Decide — diagnose the stuck moment
+The request to create an order timed out repeatedly.
I posted to the orders endpoint for order 9045 and the call timed out three times. The payment team says their endpoint is healthy. I’m worried my timeout is too short, or my request body is malformed causing the server to hang. I can’t tell whether the failure is client-side networking, my headers, or a server-side problem. What checks should I perform in order to diagnose and the best immediate next action to get the order created safely?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+I keep losing time chasing intermittent HTTP failures: requests that succeed locally but fail in CI…
Become — change the pattern
+Repeated intermittent network failures
I keep losing time chasing intermittent HTTP failures: requests that succeed locally but fail in CI or on staging, and I often blame timeouts or retries without proof. Where am I wasting time in my current request patterns, and what changes to error handling, timeouts, or local tooling will reduce firefights and make failures actionable?
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.