◆ HTML

Write code for websites

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 taskGet this product description onto the website, exactly as written, under the 'New Arrivals'…+
Get this product description onto the website, exactly as written, under the 'New Arrivals' section. Make sure it's live before Friday's newsletter goes out, so it shows up correctly on phones.
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 this new landing page live for the campaign, make sure the button text is clear…+
Before I push this new landing page live for the campaign, make sure the button text is clear and actionable, and that the images load quickly across different devices. I need it to feel inviting and professional for new visitors.
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 new product page looks fine on my desktop, but marketing just called saying it's a mess on…+
The new product page looks fine on my desktop, but I just got a call from marketing saying it's a mess on their iPhone.
The new product page looks fine on my desktop, but marketing just called saying it's a mess on their iPhone. I'm afraid we'll lose early sales if it's not fixed fast. I can't tell if it's a styling issue or something deeper with the content container. What's the most likely cause, and what's the fastest way to diagnose and fix it before the morning rush?
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 spending too much time fixing layout issues that only appear on certain devices after…+
I keep spending too much time fixing layout issues that only appear on certain devices after content goes live.
I keep spending too much time fixing layout issues that only appear on certain devices after content goes live. It's eating into other project deadlines and making me look reactive. What habit can I change in my development process to catch these responsiveness problems earlier, before they become urgent fire drills for the team?
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.