◆ JavaScript

Build a to-do list application

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 taskI need to build a simple to-do list for the internal project tracker. It needs to show tasks,…+
I need to build a simple to-do list for the internal project tracker. It needs to show tasks, allow adding new ones, marking them complete, and deleting them. Make sure it saves to local storage so the list persists across browser sessions.
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 this to the team, make the to-do list feel responsive and intuitive. When a task…+
Before I show this to the team, make the to-do list feel responsive and intuitive. When a task is marked complete, it should visually reflect that immediately without a full page reload, and the 'Add Task' input should clear automatically. Make sure the local storage updates are seamless so users don't lose their progress.
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 project manager needs a simple to-do list, something that's super easy to use and doesn't…+
The project manager just asked for a simple way to track daily tasks, but they're not tech-savvy and need something that just works without any fuss.
The project manager needs a simple to-do list, something that's super easy to use and doesn't require logins. I'm worried about making it too complex or buggy, which would just add to their workload. I'm not sure if I should focus on a bare-bones UI first or ensure robust local storage persistence. What's the best first step to get a working, reliable version in their hands quickly, and what's the biggest pitfall to avoid for someone who just wants to check off tasks?
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 adding too many features or architectural layers to simple internal…+
I often get bogged down in over-engineering simple tools, delaying their release and sometimes missing the core user need.
I frequently find myself adding too many features or architectural layers to simple internal tools, like this to-do list, before the core functionality is solid. This delays delivery and sometimes makes the tool harder to use for its intended audience. What habit should I change to prioritize core functionality and user experience for simple applications, ensuring I deliver value quickly without getting lost in unnecessary complexity?
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.