2 ready prompts
Written for the moment this actually comes up.
Improve — make it easier to accept
+Before I hand this to QA, make the reduction easy to verify: place the total at the top of the…
Improve — make it easier to accept
+Before I hand this to QA, make the reduction easy to verify: place the total at the top of the function, use a clear variable name totalSum, handle empty arrays by returning 0, and add one short in-line comment showing the initial value. Keep the code compact so reviewers can spot arithmetic errors 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
+Every quarter I patch reducers because unexpected values like null, strings, or empty arrays cause…
Become — change the pattern
+I keep shipping reducers that break on edge data
Every quarter I patch reducers because unexpected values like null, strings, or empty arrays cause exceptions or NaN on the dashboard. I want one change that stops most of these incidents without bloating code in every module. What habit or small wrapper should I adopt to prevent these bugs going forward?
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.