◆ JavaScript

Add a table row

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 taskAdd a new row to the `userTable` with 'Jane Doe', 'jane@example.com', and 'Active' as the…+
Add a new row to the `userTable` with 'Jane Doe', 'jane@example.com', and 'Active' as the values.
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 add this new row to the `transactionHistory` table, make sure the date is formatted as…+
Before I add this new row to the `transactionHistory` table, make sure the date is formatted as 'YYYY-MM-DD' and the amount is always shown with two decimal places, even if it's a whole number, so it looks consistent for the finance team.
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 user just clicked 'Add Item', but the new row isn't appearing in the table, even though the…+
The user just clicked 'Add Item', but the new row isn't appearing in the table.
The user just clicked 'Add Item', but the new row isn't appearing in the table, even though the console shows the data was successfully sent to the server. I'm afraid the user will think the system is broken and stop trying. I can't tell if the issue is with the data not being rendered correctly or if there's a problem with the table's update mechanism. What's the likely diagnosis, and what's the best next move to get that item visible to the user immediately?
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 struggle with ensuring dynamic table updates are reflected immediately and…+
I frequently struggle with ensuring dynamic table updates are reflected immediately and correctly for users.
I frequently struggle with ensuring dynamic table updates are reflected immediately and correctly for users, leading to confusion and support tickets. This costs me credibility with product owners and users. What habit should I change to consistently ensure new rows are added and displayed without a hitch, especially in complex data grids, before I push updates?
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.