◆ JavaScript

Remove property from object

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 taskRemove the `password` property from this `userObject` before I send it to the frontend. It's…+
Remove the `password` property from this `userObject` before I send it to the frontend. It's sensitive data.
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 log this `transactionDetails` object, remove the `creditCardNumber` and `cvv`…+
Before I log this `transactionDetails` object, remove the `creditCardNumber` and `cvv` properties. We don't want to store sensitive financial information in our logs.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe `customerData` object contains a `secretKey` that must not be exposed to the analytics…+
I just received a `customerData` object from an external service that includes a `secretKey` property, and I need to pass a sanitized version to another internal service, but I'm not sure if I should modify the original or create a new object.
The `customerData` object contains a `secretKey` that must not be exposed to the analytics service. I need to remove this property before sending it. I'm afraid of accidentally modifying the original `customerData` object, which might be used elsewhere. What's the safest way to remove the property without side effects on the original object, and what's the best next move to ensure data integrity?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself needing to remove specific properties from objects, especially for security…+
I frequently need to strip sensitive or unnecessary properties from objects before passing them to different parts of the application or external APIs.
I often find myself needing to remove specific properties from objects, especially for security or data minimization reasons, before they leave a boundary (like an API response). I keep writing ad-hoc deletion logic. What habit should I change to build a more consistent and less error-prone way to sanitize objects, so I can confidently manage data exposure?
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.