◆ JavaScript

Automate repetitive browser tasks

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 taskLog into the support portal, navigate to the open tickets section, and for each ticket, extract…+
Log into the support portal, navigate to the open tickets section, and for each ticket, extract the customer's email and the issue description. Compile this into a spreadsheet for the new support agent, Alex, by tomorrow morning.
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 start processing these new product images for the website, check if any of them are…+
Before I start processing these new product images for the website, check if any of them are duplicates of existing images or have resolutions too low for our current standards. If they are, flag them so I don't waste time uploading them.
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 marketing campaign launched an hour ago, and we're getting traffic to the landing page,…+
The new marketing campaign launched, and the landing page form submissions are not showing up in our CRM.
The new marketing campaign launched an hour ago, and we're getting traffic to the landing page, but no form submissions are appearing in Salesforce. The marketing team is already asking for conversion numbers. I've checked the basic integrations, but I can't tell if the form isn't submitting correctly or if there's a delay in the CRM sync. What's the fastest way to diagnose this and get the data flowing?
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 spending too much time manually populating test data in our staging environment every…+
I frequently get stuck manually updating test data in our staging environment for new feature testing.
I keep spending too much time manually populating test data in our staging environment every time a new feature needs to be tested. It's tedious and error-prone. I need a more reliable way to generate consistent, varied test data quickly without having to click through forms for hours. What habit should I change to make this less painful?
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.