◆ HTML

Fix HTML code mistakes

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 taskThe new product page content has a broken image link and some unclosed tags. Fix the image…+
The new product page content has a broken image link and some unclosed tags. Fix the image source for the hero banner and ensure all tags are properly closed so it renders correctly on desktop and mobile.
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 publish this new landing page, check the page content for any issues that would make…+
Before I publish this new landing page, check the page content for any issues that would make it hard for search engines to understand, like missing alt tags on images or non-semantic markup. Make sure it's easy for them to crawl and index.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just pushed a small page content update to the blog, and now the entire navigation menu is…+
I just pushed a small HTML update to the blog, and now the entire navigation menu is gone on the live site.
I just pushed a small page content update to the blog, and now the entire navigation menu is gone on the live site. The marketing team is furious because it's Friday afternoon, and we have a big campaign launching. I'm afraid I introduced a syntax error somewhere, but I can't see it. What's the most likely cause of a complete navigation failure from a minor page content change, and what's the fastest way to roll it back or fix it without making things worse?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep introducing small page content errors that break layouts or functionality, especially…+
I keep introducing small HTML errors that break layouts or functionality, especially when I'm under pressure.
I keep introducing small page content errors that break layouts or functionality, especially when I'm under pressure. This costs me time and credibility with the content team. What habit should I change to catch these simple but impactful mistakes before they go live and cause panic?
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.