◆ JavaScript

Deep copy data

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 taskI need a reliable deep copy of this userSettings object before I modify it. Copy every nested…+
I need a reliable deep copy of this userSettings object before I modify it. Copy every nested object and array so mutating the copy won’t touch the original. Keep functions, Dates and RegExp intact and preserve prototype links where possible. I will then run transformations for display. Make the copy here and confirm its top-level keys match the original.
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 wire this into the form code, make the deep copy easier to validate: show the total…+
Before I wire this into the form code, make the deep copy easier to validate: show the total number of nested keys, surface any properties that are functions, Dates or RegExp at the top, and flag fields that look like DOM nodes or circular references that would break serialization.
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 just copied sessionState, applied changes in the UI, and found the original mutated.…+
I cloned the object, then the UI started mutating the original.
I just copied sessionState, applied changes in the UI, and found the original mutated. sessionState is used by other modules and I can’t tell where a reference leaked. I’m afraid my copy logic missed nested arrays or prototype-linked objects. I don’t know whether the leak came from a function property or a Date. What likely went wrong and what exact check-and-fix should I run now to prevent mutation escape?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross projects I keep introducing bugs from shallow copies: form edits overwrite shared state…+
Repeated bugs from shallow clones
Across projects I keep introducing bugs from shallow copies: form edits overwrite shared state and tests flake. I spend time tracking down which module mutated the shared object. Which habit should I change in my workflow to stop this recurring pain, and what small checklist or helper function would save the most time on future copies?
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.