◆ JavaScript

Replace all occurrences of a string

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 taskReplace all instances of 'temp-id' with 'prod-id' in the configuration string I'm about to…+
Replace all instances of 'temp-id' with 'prod-id' in the configuration string I'm about to deploy to staging.
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 this user-generated comment to the moderation queue, replace all occurrences of a…+
Before I send this user-generated comment to the moderation queue, replace all occurrences of a specific profanity with asterisks, ensuring we don't store or display inappropriate content.
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 marketing team just announced we're rebranding 'Alpha-product' to 'Beta-product' and I need…+
The marketing team just changed the product name from 'Alpha' to 'Beta' across all documentation.
The marketing team just announced we're rebranding 'Alpha-product' to 'Beta-product' and I need to update all existing content. I'm afraid of missing an instance in our legacy articles, which would create confusion for users and a headache for support. Should I run a global find-and-replace on the entire content database, or is there a more targeted approach to ensure every mention is updated without breaking anything else?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time manually searching and replacing hardcoded strings, like API endpoints or…+
I often find myself manually updating hardcoded strings that should be dynamic or configurable.
I keep losing time manually searching and replacing hardcoded strings, like API endpoints or feature flags, every time an environment changes or a partner updates their spec. This is a recurring source of errors and deployment delays. What habit should I change to make these values configurable and easily swappable, so I stop playing whack-a-mole with string replacements?
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.