◆ HTML

Automate repetitive browser tasks

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 the new product page live by Friday for the marketing team. It needs to reflect the updated…+
Get the new product page live by Friday for the marketing team. It needs to reflect the updated pricing and the new feature set exactly as approved in the last review, and make sure it renders correctly on mobile devices.
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 we push this product page live, review the layout and content. Make sure the call to…+
Before we push this product page live, review the layout and content. Make sure the call to action is prominent and easy to find, the key benefits are immediately visible, and it loads quickly on a standard connection. I need this to convert better than the last one.
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 client just sent back the draft landing page, saying it feels 'cluttered' and…+
The client just sent back the draft landing page with a vague complaint about 'visual clutter' and 'feeling overwhelmed', but didn't point to anything specific.
The client just sent back the draft landing page, saying it feels 'cluttered' and 'overwhelming' without specifics. I'm afraid if I push back, they'll just dig in, but if I make random changes, I might break something important. What's the most likely underlying issue they're reacting to, and what's the best first step to get clarity without alienating them?
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 losing time fixing layout issues that only appear on specific browsers or screen sizes…+
I keep losing time trying to fix layout issues that only appear on specific browsers or screen sizes after a page has gone live.
I keep losing time fixing layout issues that only appear on specific browsers or screen sizes after a page has gone live. It's a scramble every time. What habit should I change in my build process to catch these inconsistencies earlier, before they become urgent fixes?
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.