◆ HTML

Automate HTML 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
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 taskConvert the attached spreadsheet of product features into a basic web list. Each row should be…+
Convert the attached spreadsheet of product features into a basic web list. Each row should be a list item.
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 manually create all 50 product pages, help me set up a script that takes the product…+
Before I manually create all 50 product pages, help me set up a script that takes the product data from our inventory system and generates a basic web structure for each page. It should include the product name, description, and price.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy script to generate the weekly sales reports as web pages is failing every Friday morning,…+
My script to generate weekly sales reports is failing on Friday mornings.
My script to generate the weekly sales reports as web pages is failing every Friday morning, right when Priya in procurement needs them. It worked all week, but on Fridays, the data source seems to be locked or unavailable. I'm afraid of missing the deadline again. What's the most common reason for a data source to become inaccessible for an automated script on a specific day, and what's the best way to diagnose and work around this?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI constantly find myself manually applying the same formatting to new blog posts or product…+
I spend too much time on repetitive HTML formatting for content updates.
I constantly find myself manually applying the same formatting to new blog posts or product descriptions, like adding specific classes or wrapping elements. This is tedious and error-prone. What habit should I change to automate these repetitive content formatting tasks more effectively, freeing up time and ensuring consistent styling across all new content?
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.