◆ JavaScript

Perform reporting and analysis

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 taskGet me the user engagement report for the new landing page, 'Project Phoenix', for the last 30…+
Get me the user engagement report for the new landing page, 'Project Phoenix', for the last 30 days. Break it down by referral source and device type, so I can see what's driving the traffic and how it's performing on mobile versus desktop.
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 present this quarterly performance review to Maria, analyze the 'Add to Cart'…+
Before I present this quarterly performance review to Maria, analyze the 'Add to Cart' conversion rate for the last quarter. Highlight any significant drops or spikes, and suggest the top three potential technical reasons for each, so I'm prepared for her questions.
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 real-time analytics dashboard is showing a huge spike in errors from the payment…+
The new real-time analytics dashboard is showing a huge spike in errors from the payment gateway.
The new real-time analytics dashboard is showing a huge spike in errors from the payment gateway, specifically for international transactions. I'm afraid this is going to impact our Q4 revenue projections, and I don't know if it's a code issue on our side or an external problem. What's the fastest way to diagnose the root cause and mitigate the immediate impact?
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 getting pulled into urgent reporting requests that derail my sprint work, often for data…+
I keep getting pulled into urgent reporting requests that derail my sprint work.
I keep getting pulled into urgent reporting requests that derail my sprint work, often for data that could have been prepared in advance. I lose focus and my team's velocity suffers. What habit can I change to better anticipate these ad-hoc requests and protect my deep work time?
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.