◆ JavaScript

Mount a component

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 taskMount this component into the DOM so it appears on the product-list page. Take the card…+
Mount this component into the DOM so it appears on the product-list page. Take the card component function that returns an element and append it into the container with id product-list. Ensure you clean up any previous placeholder node with class loading-skeleton before appending, and return the mounted element so the caller can attach events.
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 call mount in production, make mounting predictable: add a check that the container…+
Before I call mount in production, make mounting predictable: add a check that the container product-list exists, log a clear error if it does not, and make the mount function idempotent so reruns replace the old card rather than duplicating. Highlight any race conditions if async data is still loading.
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 mounted the card into product-list during a navigation handler and users reported duplicated…+
Multiple mounts duplicated elements after route change.
I mounted the card into product-list during a navigation handler and users reported duplicated items after fast route changes. The engineering manager and the QA lead are watching. I don't know whether to cancel previous mounts, debounce the handler, or use a marker to prevent duplicates. What's the most likely root cause and the minimal fix that stops duplication without refactoring routing logic?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe have six mount functions doing almost the same DOM replacement with tiny differences in…+
Mounting logic is repeated in six modules with slight variations.
We have six mount functions doing almost the same DOM replacement with tiny differences in cleanup and error messages. This causes bugs when we change how we identify the container. Where are we losing consistency and what habit should we change to make mounts reliable and maintainable across the codebase?
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.