◆ JavaScript

Compile charts and graphs

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 taskTake the sales data from last quarter and generate a bar chart showing revenue per product…+
Take the sales data from last quarter and generate a bar chart showing revenue per product line, and a line graph tracking customer acquisition cost over the same period. Make sure both charts are ready to embed on the investor relations page by Friday.
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 these analytics to Maria, make these charts easier to interpret for a…+
Before I present these analytics to Maria, make these charts easier to interpret for a non-technical audience. Simplify the labels, highlight the most significant trends, and ensure they load quickly on a mobile device.
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 analytics dashboard is live, but its engagement numbers are 20% lower than what I just…+
The new analytics dashboard is showing wildly different numbers for user engagement than our old system, and I just showed the old numbers to the VP of Product.
The new analytics dashboard is live, but its engagement numbers are 20% lower than what I just reported to the VP of Product from the old system. I'm afraid to tell her, but I also can't trust the new data yet. What's the most likely reason for this discrepancy, and how should I approach this with her without losing credibility?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly losing hours manually formatting charts for executive presentations, tweaking…+
I keep spending too much time manually adjusting chart layouts and data labels for every new report.
I'm constantly losing hours manually formatting charts for executive presentations, tweaking layouts and labels to make them clear. This slows down every report. What habit should I change to automate more of this visual data preparation, so I can focus on analysis instead of presentation mechanics?
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.