3 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+Find the symbol for loadCsv in the repository and open its implementation file. If there are…
Execute — do the immediate task
+Find the symbol for loadCsv in the repository and open its implementation file. If there are multiple matches, open the one under services/io and jump to the function definition. Confirm the file shows the correct signature and tests referencing it are visible in the Explorer.
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 search for loadCsv across the repo, make it easy for a reviewer: show the closest call…
Improve — make it easier to accept
+Before I search for loadCsv across the repo, make it easy for a reviewer: show the closest call sites, the most recent changes to that symbol, and surface any TODOs or FIXME comments near it. Highlight which match is exported publicly and which are internal utilities so I can pick the right one quickly.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Frequently I waste time finding the wrong symbol because we duplicate utility names across the…
Become — change the pattern
+I keep hunting for symbols with conflicting names
Frequently I waste time finding the wrong symbol because we duplicate utility names across the repo. This creates merge friction and debugging delays. What naming or module-organizing habit should I change to reduce collisions, how do I get the team to adopt it, and what immediate repo clean-up steps will cost the least but give the biggest short-term payoff?
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.