◆ HTML

Create an unordered list without bullets

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 taskTake the list of product features on the 'About Us' page and remove the default bullet points,…+
Take the list of product features on the 'About Us' page and remove the default bullet points, so it looks cleaner.
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 acceptFor the new 'Our Services' section, display the list of offerings without bullets, but make…+
For the new 'Our Services' section, display the list of offerings without bullets, but make sure it indents nicely and has enough visual separation between items, so it's easy to read.
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 legal team just sent over 15 disclaimers that absolutely cannot have bullet points, but…+
The legal team insists on a list of disclaimers that can't have bullets, but it looks like a wall of text.
The legal team just sent over 15 disclaimers that absolutely cannot have bullet points, but when I remove them, it just looks like a giant paragraph and nobody will read it. I'm afraid if I just add line breaks, it'll still be too dense. What's the best way to present this list of bullet-less items so it's readable and doesn't overwhelm the user, without adding any visual adornments the legal team will reject?
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 need to display lists of items that aren't traditional bullet points, like steps in a…+
I frequently need to present lists that are not traditional bullet points but still need clear structure.
I often need to display lists of items that aren't traditional bullet points, like steps in a process or a series of short facts. I usually just remove the bullets and hope for the best. What habit should I change to consistently create visually distinct and readable non-bulleted lists that guide the user's eye without looking messy or like a solid block of text?
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.