The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+The extension is causing my linting to flag every third line in the repo. Disable the ESLint…
Execute — do the immediate task
+The extension is causing my linting to flag every third line in the repo. Disable the ESLint extension for this workspace and leave it enabled globally so my colleagues' environments are unaffected. Do the disable now and confirm the extension is inactive for this project by running a quick file save to show no new lint errors.
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 disable the extension across the team, make it safe to toggle: show which settings the…
Improve — make it easier to accept
+Before I disable the extension across the team, make it safe to toggle: show which settings the extension has overridden in this workspace, list any workspace-specific config files it touches, and surface any alternative extensions or built-in features that will cover critical checks. Flag any tests or CI steps that will fail if it goes off.
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 disabled the ESLint extension for this workspace and most lint errors went away, but three rules…
Decide — diagnose the stuck moment
+I just toggled disable and errors disappeared but I’m not sure why some checks still run
I disabled the ESLint extension for this workspace and most lint errors went away, but three rules still run on save. I fear there is a workspace config or a project-level precommit hook I cannot see. Tell me the likely places those remaining checks live, what command to run to reveal them, and the safest next step to stop them without breaking CI.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the past month I’ve repeatedly disabled different lint and formatter extensions to stop noise…
Become — change the pattern
+I keep disabling extensions to stop noisy diagnostics
Over the past month I’ve repeatedly disabled different lint and formatter extensions to stop noise in projects. Each time I lose time re-enabling and reconfiguring per-repo. Recommend a habit or small conventions for the team to reduce this cycling — what to document in repos, what to lock in global settings, and a quick checklist to run before disabling any extension.
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.