◆ JavaScript

Profile memory usage

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
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskA memory leak was reported on the long-lived single-page app; run the browser memory profiler…+
A memory leak was reported on the long-lived single-page app; run the browser memory profiler while exercising the user journey from login to 30 minutes of use, take heap snapshots at 0, 5, 15, and 30 minutes, and produce a minimal report showing any growing retained object types and their retaining paths.
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 send the memory report to the engineering lead, make it easy to act on: summarize the…+
Before I send the memory report to the engineering lead, make it easy to act on: summarize the top three retained object types with their allocation counts, show the code locations that retain them (file and line if possible), and note whether the leak grows linearly or in spikes. Suggest one practical stopgap change to reduce retained memory immediately.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWhile exercising the app for 20 minutes, the heap steadily grows and never recovers; snapshots…+
Heap keeps growing during a long user session
While exercising the app for 20 minutes, the heap steadily grows and never recovers; snapshots show increasing Detached DOM nodes but I don't know whether they come from event listeners, virtual DOM mismatches, or forgotten timers. What targeted check should I run next to distinguish between those causes and what exact profiler view will prove it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross several projects I keep chasing memory growth that surfaces only after long sessions,…+
Memory spikes recur on long sessions in multiple apps
Across several projects I keep chasing memory growth that surfaces only after long sessions, costing time to reproduce and fix. Where am I most likely introducing lingering references during feature development and which consistent coding habit should I adopt to prevent these leaks going forward?
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.