Run code in console

Run code in console in JavaScript — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

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 run this snippet in the browser console to reproduce a bug a user reported this morning.…
I need to run this snippet in the browser console to reproduce a bug a user reported this morning. Copy the code block below into the console, run it on the site at https://dashboard.acme.local, and tell me the exact console output and any uncaught errors. If it throws, include the stack trace and the line that failed so I can paste it into the issue.

Improve — make it easier to accept

+
Before I paste this into the console for QA, make the snippet safer to execute in a live session:…
Before I paste this into the console for QA, make the snippet safer to execute in a live session: wrap network calls so they can be stubbed, prevent it from modifying DOM outside #test-area, and add logging that shows input, output and elapsed time. Show the modified snippet and explain the three places a reviewer will hesitate.

Decide — diagnose the stuck moment

+
I pasted a short script into the client console on Chrome and there was no output and no errors.…

I pasted the snippet and nothing happened

I pasted a short script into the client console on Chrome and there was no output and no errors. The page has complex client-side routing and a token in localStorage. I worry the code ran in the wrong frame or before app bootstrap. What likely went wrong, how do I check which frame and timing, and what exact minimal change will show me whether the code executed where I expect?

Become — change the pattern

+
Across repeated debugging sessions I open the console, paste ad‑hoc snippets and later lose the…

I keep reproing bugs by running quick snippets that later can't be reproduced

Across repeated debugging sessions I open the console, paste ad‑hoc snippets and later lose the exact state that reproduced the problem. Where am I losing time or credibility — in capturing environment, sequencing steps, or sharing reproducible inputs — and what three habits should I adopt to stop wasting time and to hand someone else a one‑click repro?

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.