◆ JavaScript

Convert string to integer

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 taskThe user entered '45' into the quantity field. Convert this to a number so it can be added to…+
The user entered '45' into the quantity field. Convert this to a number so it can be added to the total items in the cart.
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 acceptWhen a user types a quantity into the order form, make sure it's always treated as a whole…+
When a user types a quantity into the order form, make sure it's always treated as a whole number for calculations, even if they accidentally add spaces or other characters, so the total price is accurate.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentAfter a large order came in this morning, our inventory system is showing a discrepancy. I'm…+
The inventory count is off after a new order, and I suspect a quantity input error.
After a large order came in this morning, our inventory system is showing a discrepancy. I'm worried a quantity entered by the sales team, like '20 units', might have been read as text, throwing off the stock count. I can't tell if it's a data entry mistake or a system misinterpretation. What's the most likely cause for this kind of inventory error and what's the quickest way to verify how the system is processing those quantity 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 myself debugging calculation errors on order forms and reports because…+
I frequently encounter issues where user-entered numbers cause calculation errors.
I frequently find myself debugging calculation errors on order forms and reports because user-entered numbers aren't being treated as actual numbers. This leads to incorrect totals and frustrated customers. What habit should I change to proactively ensure all user input intended for calculations is correctly interpreted as a numerical value every single 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.