The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Rename the file used by the inventory API: change src/api/oldInventory.js to src/api/inventory.js,…
Execute — do the immediate task
+Rename the file used by the inventory API: change src/api/oldInventory.js to src/api/inventory.js, update any imports in src and tests so they still resolve, and run the unit tests before I push to the feature branch by Monday.
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 rename this module, make the change low-friction for reviewers: rename…
Improve — make it easier to accept
+Before I rename this module, make the change low-friction for reviewers: rename src/api/oldInventory.js to src/api/inventory.js, update all project imports, add a short note in the git commit message explaining why, and run tests to show nothing broke so the reviewer can focus on logic changes not refactoring noise.
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 renamed src/api/oldInventory.js to src/api/inventory.js and now multiple imports fail. The…
Decide — diagnose the stuck moment
+I renamed a file and imports started failing across the repo.
I renamed src/api/oldInventory.js to src/api/inventory.js and now multiple imports fail. The release manager needs a green build; I don't know whether some imports reference the old path, if case-sensitivity on the build server is causing it, or if I missed updating index exports. What's the most likely cause and the quickest fix to restore a green build?
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 renaming files by hand and then spend time hunting broken imports and CI failures. What…
Become — change the pattern
+I rename files manually and break imports repeatedly.
I keep renaming files by hand and then spend time hunting broken imports and CI failures. What single change to how I rename files or one habit to adopt will prevent these regressions across projects?
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 code editor work people do in Visual Studio Code.
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.