◆ JavaScript

Automate repetitive data 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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGo through the list of pending invoices in the accounting system, extract the invoice number…+
Go through the list of pending invoices in the accounting system, extract the invoice number and due date for each, and send a reminder email to suppliers whose invoices are due in the next three days.
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 out these monthly customer statements, verify that the total amount due matches…+
Before I send out these monthly customer statements, verify that the total amount due matches the sum of the line items for each customer. If there's a discrepancy, flag that customer's statement for manual review so we don't send incorrect bills.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur inventory system is showing a negative stock count for our best-selling widget, but a quick…+
The inventory system is showing a negative stock count for a popular product, but physical count confirms we have plenty.
Our inventory system is showing a negative stock count for our best-selling widget, but a quick physical check confirms we have over 200 in the warehouse. Sales are being blocked online because of this. I can't tell if it's a recent transaction error, a batch import gone wrong, or a deeper system issue. What's the quickest way to correct the stock level to unblock sales, and how do I figure out the root cause without disrupting other operations?
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 reconciling discrepancies between our payment processor…+
I frequently manually reconcile discrepancies between our payment processor and internal sales records.
I keep spending too much time manually reconciling discrepancies between our payment processor reports and our internal sales records. It's usually small differences, but they accumulate and cause headaches for finance. I need a more automated way to flag these mismatches or prevent them from happening. What habit should I change to reduce this recurring manual effort?
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.