◆ JavaScript

Integrate multiple JavaScript applications

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 taskMerge the new user authentication module into the main branch, ensuring all dependencies are…+
Merge the new user authentication module into the main branch, ensuring all dependencies are updated and tests pass before it goes live.
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 integrate these two applications, make sure the data flow between them is secure and…+
Before I integrate these two applications, make sure the data flow between them is secure and handles potential conflicts gracefully, flagging any areas where performance might degrade.
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 new user profile service is failing to connect to the existing data store, but only for…+
The new user profile service is failing to connect to the existing data store, but only for certain user types.
The new user profile service is failing to connect to the existing data store, but only for certain user types. I'm afraid of a cascading failure if I push a fix without understanding the root cause, but the product manager needs this live by end of day. I can't tell if it's a configuration issue or a deeper architectural mismatch. What's the likely diagnosis here and what's the best next move to stabilize without breaking more?
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 when integrating new features because existing applications have…+
I keep losing time when integrating new features because existing applications have inconsistent data structures.
I keep losing time when integrating new features because existing applications have inconsistent data structures. It makes every new integration a bespoke puzzle, costing us days. What habit should I change to standardize data contracts and make future integrations smoother, without rebuilding everything right now?
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.