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 a new feature folder inside the frontend app. Create a folder named feature-cart under…
Execute — do the immediate task
+I need a new feature folder inside the frontend app. Create a folder named feature-cart under src/components of the current workspace, and confirm the folder appears in the explorer with a README.md inside so I can document the component purpose before I add files.
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 add components, make creating a new folder less error-prone: offer to place it under the…
Improve — make it easier to accept
+Before I add components, make creating a new folder less error-prone: offer to place it under the nearest package.json or src directory, prefill a README.md and index.js, and show the relative path where it will be created so I don’t accidentally nest it under the wrong module.
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 attempted to create feature-cart but it ended up inside a nested test folder. I’m on a tight…
Decide — diagnose the stuck moment
+I tried to add a folder but it appeared in the wrong place
I attempted to create feature-cart but it ended up inside a nested test folder. I’m on a tight deadline and afraid I’ll scatter files across the repo. I don’t know whether I clicked the wrong tree node or the workspace has multiple roots. Tell me how to verify which workspace folder is active and how to create the folder explicitly under src/components so I don’t repeat this mistake.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across projects I waste time moving folders because I habitually create them from the wrong tree…
Become — change the pattern
+I repeatedly create folders in inconsistent locations
Across projects I waste time moving folders because I habitually create them from the wrong tree node. I want one simple habit change to stop that. Suggest an action I can make mandatory when creating a folder—what to look at or a quick check—to ensure I always create new folders in the intended package or src root.
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.