◆ HTML

Optimize HTML code

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 taskThe contact form's page structure has a lot of redundant classes and deeply nested divs.…+
The contact form's page structure has a lot of redundant classes and deeply nested divs. Refactor it to use more semantic tags and fewer classes, so it's cleaner and easier for the next developer to understand.
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 push the updated navigation bar, optimize its structure. Ensure it uses semantic tags,…+
Before I push the updated navigation bar, optimize its structure. Ensure it uses semantic tags, is lean, and avoids unnecessary wrapper divs, so it's maintainable and performs well across all browsers and devices.
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'm trying to add a new component to an old page, and the existing page structure is a tangled…+
I'm trying to add a new component to an old page, and the existing HTML is a tangled mess of inline styles and deeply nested elements.
I'm trying to add a new component to an old page, and the existing page structure is a tangled mess of inline styles and deeply nested elements. The project manager wants this done by Friday, but I'm afraid if I touch anything, it will break the existing layout, which is already fragile. I don't know whether to refactor the whole section or try to shoehorn my new code in. What's the best strategy for optimizing old, messy page structure without introducing new bugs or blowing past my deadline?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself spending too much time trying to understand and modify complex, unoptimized…+
I often find myself spending too much time trying to understand and modify complex, unoptimized HTML from previous projects.
I often find myself spending too much time trying to understand and modify complex, unoptimized page structure from previous projects. This slows down development and increases the risk of errors. What habit should I adopt in my daily coding to consistently write cleaner, more optimized page structure that future me (or another developer) will thank me for?
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.