◆ HTML

Develop web-accessible software

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskAdd a new 'Contact Us' button to the main navigation bar of the internal portal, linking to the…+
Add a new 'Contact Us' button to the main navigation bar of the internal portal, linking to the existing contact form. Make sure it's visible to all employees by end of day.
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 I build this new dashboard for the sales team, I need to make sure the data refreshes…+
When I build this new dashboard for the sales team, I need to make sure the data refreshes automatically every hour, and that the key performance indicators are highlighted clearly. It needs to be intuitive for someone who isn't a data expert.
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 new expense reporting tool I just launched is getting complaints that it's slow to load for…+
The new expense reporting tool I just launched is getting complaints that it's slow to load for users in the European office.
The new expense reporting tool I just launched is getting complaints that it's slow to load for users in the European office. I'm worried about adoption if it's not snappy, and I can't tell if it's a server issue or a front-end rendering problem. What's the most likely bottleneck, and what's the best first step to pinpoint the performance issue quickly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly getting bug reports about small UI inconsistencies or broken links after new…+
I'm constantly getting bug reports about small UI inconsistencies or broken links after new features are deployed.
I'm constantly getting bug reports about small UI inconsistencies or broken links after new features are deployed. It's eroding trust in our releases and adding unexpected rework. What habit can I change in my testing or deployment process to catch these minor but frustrating issues before they impact users?
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.