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 to select the rectangular block of column three through five from lines 120 to 200 in…
Execute — do the immediate task
+I need to select the rectangular block of column three through five from lines 120 to 200 in data/fixtures/sample.csv and replace that block with trimmed values. Do the column selection then apply the trim across the selected block only.
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 change the CSV block, make approval straightforward: show how many rows will change,…
Improve — make it easier to accept
+Before I change the CSV block, make approval straightforward: show how many rows will change, preview the first five transformed rows, and flag rows where trimming would remove significant leading characters like '+' or '-' so I can handle exceptions.
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 made a column selection from lines 120–200 in sample.csv and I'm seeing rows with embedded commas…
Decide — diagnose the stuck moment
+I selected a column block in sample.csv but some rows have embedded commas and quotes.
I made a column selection from lines 120–200 in sample.csv and I'm seeing rows with embedded commas and quoted fields that might shift columns. I don't know how many rows are malformed or whether my block selection misaligned. What's the likely diagnosis and the safest next step to avoid corrupting the CSV data?
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 time my manual column or block edits in CSV fixtures keep introducing subtle format errors…
Become — change the pattern
+Manual column edits regularly corrupt CSV fixtures
Over time my manual column or block edits in CSV fixtures keep introducing subtle format errors that break tests. Where am I wasting time and what single habit or tool should I adopt to keep column edits safe and fast? Recommend a single change to my workflow and a lightweight check to run before committing.
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.