◆ HTML

Analyze 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.

3prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need to find all instances of the old company logo image, 'logo-v1.png', across the entire…+
I need to find all instances of the old company logo image, 'logo-v1.png', across the entire website codebase so we can replace them with the new one.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BDecide — diagnose the stuck momentThe new SEO report shows our latest blog posts have poor readability scores and missing heading…+
The new SEO report shows our blog posts have poor readability scores and missing heading structures.
The new SEO report shows our latest blog posts have poor readability scores and missing heading structures, impacting their search ranking. The content team is pushing out new articles daily, and I'm afraid if I don't address this quickly, our traffic will drop further. I don't know if it's a content generation issue or a template problem. What's the best way to diagnose the root cause and implement a fix without disrupting the content pipeline?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CBecome — change the patternI consistently find myself debugging layout issues caused by poorly nested or improperly closed…+
I consistently find myself debugging layout issues caused by poorly nested or improperly closed HTML tags.
I consistently find myself debugging layout issues caused by poorly nested or improperly closed HTML tags, especially in pages touched by multiple developers. This costs significant time and introduces unexpected visual bugs. What habit should I change in my code review or development process to proactively identify and prevent these fundamental structural errors before they become hard-to-find problems?
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.