◆ JavaScript

Assist with online transaction policies

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 taskUpdate the checkout page to disallow purchases from IP addresses originating in sanctioned…+
Update the checkout page to disallow purchases from IP addresses originating in sanctioned countries, as per the new legal directive from the compliance team. Make sure it provides a clear, polite message to the user.
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 we go live with the new discount code feature, review our existing online transaction…+
Before we go live with the new discount code feature, review our existing online transaction policies. Flag any areas where the new feature might create loopholes for abuse, especially regarding stacking discounts or unauthorized resales, so we don't lose money.
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 fraud detection system just flagged a series of high-value transactions from a single…+
Our fraud detection system just flagged a series of high-value transactions from a single account, all using different credit cards.
Our fraud detection system just flagged a series of high-value transactions from a single account, all using different credit cards, within an hour. I'm afraid of blocking legitimate customers, but also of significant financial loss. I don't know if this is a sophisticated attack or a user error. What's the best next move to investigate without disrupting service?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find myself manually reviewing transactions that fall into a 'gray area' of our…+
I frequently find myself manually reviewing transactions that fall into a 'gray area' of our policy.
I frequently find myself manually reviewing transactions that fall into a 'gray area' of our policy, taking up valuable time and delaying order fulfillment. This happens every week. What habit can I change to either clarify these edge cases in our automated rules or empower customer support to handle them more effectively?
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.