◆ HTML

Avoid breaking production 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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskThe content for the 'About Us' page has a broken video embed. Fix the iframe source and ensure…+
The content for the 'About Us' page has a broken video embed. Fix the iframe source and ensure it displays correctly on all devices, so the client can approve it 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 hand off this new feature to QA, review the page structure to ensure there are no…+
Before I hand off this new feature to QA, review the page structure to ensure there are no accessibility issues that would fail our compliance checks. Look for things like missing ARIA attributes or incorrect heading structures so we don't have rework later.
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 merged my branch for the new product grid, and now the entire product listing page is blank…+
I merged my branch for the new product grid, and now the entire product listing page is blank in staging.
I merged my branch for the new product grid, and now the entire product listing page is blank in staging. The product manager is asking for an ETA, and I'm worried I introduced a critical error that affects the main display loop. I can't tell if it's a script dependency or a malformed page structure. What's the quickest way to diagnose if my page structure changes are the root cause, and how do I isolate the problem without affecting other developers' work?
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 debugging production issues that trace back to seemingly minor page…+
I often find myself debugging production issues that trace back to seemingly minor HTML changes I made.
I often find myself debugging production issues that trace back to seemingly minor page structure changes I made. This causes delays and stress for the whole team. What habit can I adopt to proactively identify potential breaking changes in my page structure before they ever reach production?
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.