◆ JavaScript

Generate web reports

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 taskTake the sales data from the last quarter, aggregate it by product line, and generate a new…+
Take the sales data from the last quarter, aggregate it by product line, and generate a new report showing revenue and profit margin for each line item. Ensure the report is formatted for easy viewing on a mobile device.
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 this quarterly sales report to Maria in leadership, make sure the key performance…+
Before I send this quarterly sales report to Maria in leadership, make sure the key performance indicators for our new product launch are highlighted at the top, and add a summary of any significant deviations from our Q3 targets so she can quickly grasp the situation.
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 client just called about a discrepancy in their monthly usage report for October, and I…+
The client just called, asking about a discrepancy in their monthly usage report, and I can't reconcile it with our internal logs.
The client just called about a discrepancy in their monthly usage report for October, and I can't reconcile it with our internal logs for their account. I'm afraid if I can't explain it quickly, we'll lose their trust. I don't know if it's a data lag, a reporting bug, or a unique edge case. What's the most likely diagnosis, and what's my best first step to get them an answer by end of day?
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 losing hours every week manually reformatting raw database exports into presentable…+
I keep spending too much time manually reformatting data for ad-hoc reports.
I keep losing hours every week manually reformatting raw database exports into presentable reports for ad-hoc requests from sales and marketing. This isn't sustainable. What habit or process change should I adopt to automate this data preparation so I can focus on analysis instead of manual cleanup?
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.