◆ JavaScript

Scroll to an element

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 taskWhen a user clicks 'view details' on the product card, take them directly to the product…+
When a user clicks 'view details' on the product card, take them directly to the product description section on the product page.
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 acceptWhen a user clicks the 'read more' link on the blog post summary, scroll them smoothly to the…+
When a user clicks the 'read more' link on the blog post summary, scroll them smoothly to the full article text, but make sure the sticky header stays visible so they can still navigate.
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 says users are dropping off after clicking 'learn more' because they land at…+
The marketing team says users are dropping off after clicking 'learn more' because they land at the top of a long page and don't see the relevant content.
The marketing team says users are dropping off after clicking 'learn more' because they land at the top of a long page and don't see the relevant content. I'm afraid if I just scroll them, they might miss important context at the top. Should I scroll them directly to the section, or highlight the section after a general scroll, and what's the best way to handle different screen sizes?
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 manually scrolling to test specific sections of our longer pages during…+
I often find myself manually scrolling to test specific sections of our longer pages during development and QA.
I often find myself manually scrolling to test specific sections of our longer pages during development and QA, which wastes time and sometimes I miss things. This happens across various projects. What habit should I change to make navigating to specific page elements more efficient and less error-prone in my workflow?
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.