◆ JavaScript

Debug runtime error

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskThe app crashes on page load with a runtime error. Inspect the stack trace, identify the…+
The app crashes on page load with a runtime error. Inspect the stack trace, identify the failing file and line, add a defensive guard and a clear error message, then re-run to confirm the page loads. Commit the fix with a one-line description referencing the stack trace top line.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I push a runtime error fix, make it easier for the reviewer to accept. Highlight the…+
Before I push a runtime error fix, make it easier for the reviewer to accept. Highlight the stack trace top file and line, show the minimal guard you propose, and call out any assumptions (null value, undefined API response) that would make the guard wrong so the reviewer can challenge them.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI added a component and now users hit TypeError: cannot read property 'map' of undefined in…+
Console shows TypeError: cannot read property 'map' of undefined at renderList
I added a component and now users hit TypeError: cannot read property 'map' of undefined in renderList. I don't know whether data failed to load or I passed the wrong prop. The component is used in three places. Which is most likely, how do I quickly confirm it, and what minimal code change will make the UI resilient without hiding a real bug?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross sprints we keep shipping code that assumes API arrays always exist and it blows up in…+
We repeatedly deploy crashes caused by unchecked API responses
Across sprints we keep shipping code that assumes API arrays always exist and it blows up in production when responses change. I need a pattern to stop these runtime errors at source. Recommend one coding practice, one automated check for CI, and a short PR review question that catches dangerous assumptions about external data.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.