◆ JavaScript

Validate decimal numbers

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 taskCheck if the 'price' variable, which holds '12.99', is a valid decimal…+
Check if the 'price' variable, which holds '12.99', is a valid decimal number.
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 processing the user's 'priceInput', validate that it's a positive decimal number with no…+
Before processing the user's 'priceInput', validate that it's a positive decimal number with no more than two decimal places, so we can ensure accurate financial calculations and prevent data entry errors.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA user just submitted '10.999' as a product price, and our system accepted it, which is going…+
A user just entered '10.999' as a product price, and our system accepted it, which will cause issues with our payment gateway.
A user just submitted '10.999' as a product price, and our system accepted it, which is going to cause a mismatch with the payment gateway that only handles two decimal places. I'm worried about transaction failures and reconciliation nightmares. How can I immediately validate this input to only allow two decimal places, and what's the most robust way to prevent this from happening again across all price inputs?
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 that decimal numbers from user inputs or external APIs aren't properly…+
I keep encountering malformed decimal numbers from user inputs or external APIs, leading to calculation errors.
I frequently find that decimal numbers from user inputs or external APIs aren't properly validated, leading to silent calculation errors in our financial reports. This erodes trust in our data. What habit should I change to ensure all incoming decimal numbers are rigorously validated for format and precision right at the point of entry, preventing these recurring accuracy issues?
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.