◆ JavaScript

Format number with thousands separators

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 taskI need to display the total sales for Q3, which is 1234567.89, in the dashboard. Make sure it…+
I need to display the total sales for Q3, which is 1234567.89, in the dashboard. Make sure it has the commas in the right places for readability before it goes live.
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 show these financial figures to the client, format all the large numbers across the…+
Before I show these financial figures to the client, format all the large numbers across the report with thousands separators. It needs to be clear whether we're talking about hundreds or hundreds of thousands, especially for the budget review committee.
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 showing raw numbers, and the client's CEO just asked why the…+
The new analytics dashboard is showing raw numbers, and the client's CEO just asked why the figures look unreadable.
The new analytics dashboard is showing raw numbers, and the client's CEO just asked why the figures look unreadable. I'm worried this makes us look sloppy right before the big Q4 presentation. I can't just push a fix without testing it, but I also can't leave it like this. What's the fastest way to get the numbers formatted with thousands separators without introducing a new bug, and how can I quickly confirm it's correct before the meeting starts in an hour?
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 last-minute requests to format numbers for client-facing reports, which always…+
I keep getting last-minute requests to format numbers for client-facing reports, which always takes me away from core development.
I keep getting last-minute requests to format numbers for client-facing reports, which always takes me away from core development. This is costing us time and I'm losing focus on bigger features. What habit should I change to make number formatting a non-issue, so it's handled consistently and automatically without me having to drop everything every 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.