◆ HTML

Set up alerts for web applications

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 taskSet up an alert for the 'Contact Us' form on the main website. If the form submission fails for…+
Set up an alert for the 'Contact Us' form on the main website. If the form submission fails for any reason, I need an email notification sent to support@example.com immediately.
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 acceptConfigure an alert system for the 'Contact Us' form on the main website. I need to know if any…+
Configure an alert system for the 'Contact Us' form on the main website. I need to know if any part of the submission process fails, from client-side validation errors in the webpage content to server-side processing issues, so we can address potential customer loss quickly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentUsers are reporting that the 'Request Demo' button on the landing page isn't working, but our…+
Users are reporting that the 'Request Demo' button isn't working, but our logs show no errors.
Users are reporting that the 'Request Demo' button on the landing page isn't working, but our backend logs aren't showing any errors. I'm worried there's a client-side webpage content or JavaScript issue preventing the submission, but I can't pinpoint it. What's the likely diagnosis for this discrepancy, and what's the best next move to quickly identify the root cause?
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 always reacting to user reports of broken form submissions or unresponsive buttons on our…+
I'm constantly reacting to user reports of broken form submissions or unresponsive buttons.
I'm always reacting to user reports of broken form submissions or unresponsive buttons on our web applications, which leads to frustrated customers and rushed fixes. This cycle costs us credibility. What habit should I change in how I set up and monitor interactive web elements to catch these 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.