◆ HTML

Debug web development issues

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 taskDebug the registration form on the staging site. Specifically, find out why the 'Submit' button…+
Debug the registration form on the staging site. Specifically, find out why the 'Submit' button isn't working when all fields are filled, and fix the underlying issue so it submits data to the backend. Report back 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 acceptBefore I debug the registration form, make sure I'm looking beyond just the 'Submit' button.…+
Before I debug the registration form, make sure I'm looking beyond just the 'Submit' button. Check for any hidden validation errors that aren't showing up, inspect network requests to see if data is even being sent, and flag any potential race conditions between the page elements and JavaScript that could be causing intermittent failures.
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 client just reported that the new contact form isn't sending emails, but it worked…+
The client just reported that the new contact form isn't sending emails, but it worked yesterday for me.
The client just reported that the new contact form isn't sending emails, but it worked yesterday for me, and they're threatening to pull the project if this isn't stable. I'm afraid I missed something critical in the server-side integration or a subtle HTML attribute. I don't know if it's a client-side validation error preventing submission, or a server-side issue. What's the most common reason a contact form stops working intermittently like this, and what's my best first step to diagnose this under intense pressure?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend too much time chasing intermittent bugs that only appear for clients, not in my testing…+
I spend too much time chasing intermittent bugs that only appear for clients, not in my testing.
I spend too much time chasing intermittent bugs that only appear for clients, not in my testing environment. This erodes trust and makes me look unprepared. I keep losing credibility when I can't reproduce issues. What habit should I change in my development or testing workflow to catch these elusive, client-specific bugs before they become critical, especially for interactive components?
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.