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 CI build failed and the lint job lists 87 errors across utils/date.js and…
Execute — do the immediate task
+The CI build failed and the lint job lists 87 errors across utils/date.js and components/Header.jsx. Fix the lint errors so the build passes by Friday; run the linting locally, correct only genuine style or syntax issues (no feature changes), and push a single commit with 'fix: lint errors' so QA can re-run the pipeline.
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 push fixes for the lint failures, make the changes easy to review: surface the files…
Improve — make it easier to accept
+Before I push fixes for the lint failures, make the changes easy to review: surface the files changed and number of errors up front, group fixes by type (semicolons, unused vars, arrow-body style), and mark any locations where a deeper logic change might be tempting so a reviewer can ignore or approve style-only edits.
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
+The CI lint stage failed on utils/date.js and components/Header.jsx. I am the only engineer on the…
Decide — diagnose the stuck moment
+CI lint stage failed and shows many errors.
The CI lint stage failed on utils/date.js and components/Header.jsx. I am the only engineer on the repo today, and I worry that fixing everything at once will hide functional changes. I cannot tell which errors are purely style and which might mask a bug. Which files or patterns should I fix first to unblock CI with minimal risk, and what quick checks catch accidental behavior changes?
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 sprint we waste time on last-minute lint fixes that break tests or hide refactors. I can see…
Become — change the pattern
+We always scramble to fix linter errors right before a release.
Every sprint we waste time on last-minute lint fixes that break tests or hide refactors. I can see common causes: no pre-commit hooks, inconsistent editor configs, and merges from feature branches with differing rules. Which habits should I change first to stop this recurring firefight and keep the linter green between releases?
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 programming language work people do in JavaScript.
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.