◆ HTML

Create a web-based to-do list app

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 HTML tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCreate a web page that displays a list of tasks and allows adding new…+
Create a web page that displays a list of tasks and allows adding new ones.
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 the client demo on Friday, create the web-based to-do list so it's responsive on phones…+
Before the client demo on Friday, create the web-based to-do list so it's responsive on phones and tablets, and new tasks can be added by hitting the Enter key, making it feel intuitive for daily use.
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 lead just requested that the web-based to-do list update in real-time for everyone…+
The project lead wants real-time updates for the to-do list across multiple users, but I've only built a local version.
The project lead just requested that the web-based to-do list update in real-time for everyone on the team, but my current version only stores data locally in the browser. I'm afraid of choosing a complex backend solution that will delay our launch or require too much setup. What's the most straightforward way to enable real-time, multi-user synchronization for this list without over-complicating the architecture?
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 build web tools that function perfectly for a single user, but when the team needs…+
I often build web tools that work great for one user but struggle to scale for collaborative use.
I frequently build web tools that function perfectly for a single user, but when the team needs to collaborate, like on this to-do list, I realize I haven't accounted for real-time updates or shared states. I end up doing major reworks. What habit should I change to consider multi-user and real-time requirements earlier in the design phase, so I stop rebuilding core functionality?
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 HTML'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.