3 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+A file needs to live under utils now. Move userHelpers.js from src/services to src/utils, preserve…
Execute — do the immediate task
+A file needs to live under utils now. Move userHelpers.js from src/services to src/utils, preserve its import paths, and update any imports across the workspace so nothing breaks. Check for failing references and report any files that need manual fixes before I push.
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 just moved userHelpers.js to src/utils and now several modules fail to import it. I’m afraid I…
Decide — diagnose the stuck moment
+I dragged a file and imports are failing
I just moved userHelpers.js to src/utils and now several modules fail to import it. I’m afraid I broke the build for everyone. I don’t know if the editor updated relative paths or if I broke default versus named exports. Help me diagnose why imports are failing, how to revert or fix the paths quickly, and give the exact steps to update imports across the workspace 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
+Every refactor costs me time because I move files and forget to update imports, leading to CI…
Become — change the pattern
+I keep breaking imports when reorganizing files
Every refactor costs me time because I move files and forget to update imports, leading to CI failures. I want a habit or simple pre-move checklist to avoid this. Recommend one change to my workflow—what to check or run before moving files—and a quick post-move verification that prevents import breakage.
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.