3 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+Enable word wrap for long lines in the editor for the documentation team. Update the workspace…
Execute — do the immediate task
+Enable word wrap for long lines in the editor for the documentation team. Update the workspace settings to set "editor.wordWrap": "on" and verify README.md and CONTRIBUTING.md display wrapped lines at the current window width without changing file contents.
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 enabled word wrap in the workspace and Jamie in docs opened a PR complaining that my change…
Decide — diagnose the stuck moment
+I turned on word wrap and a reviewer thought I changed file formatting.
I enabled word wrap in the workspace and Jamie in docs opened a PR complaining that my change reformatted their file, though I did not modify the file bytes. I don't know whether their diff tool is set to ignore display-only changes. Should I add a note in the PR, revert the workspace setting, or change the team's diff settings? Recommend the most effective immediate message to Jamie and the minimal technical step to prevent future confusion.
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 wasting review cycles because editor display settings like word wrap are mistaken for…
Become — change the pattern
+Docs and code teams keep confusing display settings with file edits.
We keep wasting review cycles because editor display settings like word wrap are mistaken for actual file edits. Reviewers block PRs expecting reflowed text to be committed. What single team habit will stop these false alarms and a one-sentence PR guideline to make it stick?
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.