◆ HTML

Add HTML entities using CSS content

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 taskAdd a non-breaking space entity before the units in the price display for the new product…+
Add a non-breaking space entity before the units in the price display for the new product listings, so '12 USD' always reads correctly on a phone.
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 this article goes to the copy editor, use CSS content to add the correct copyright…+
Before this article goes to the copy editor, use CSS content to add the correct copyright symbol after the company name in the footer. It needs to appear consistently without being manually added to every page.
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 flagged that the trademark symbol isn't appearing correctly on some…+
The legal team just flagged that the trademark symbol isn't appearing correctly on some dynamically loaded product descriptions, showing up as a box.
The legal team just flagged that the trademark symbol isn't appearing correctly on some dynamically loaded product descriptions, showing up as a box. I used a CSS :before pseudo-element with content:'\2122', but it's inconsistent. I'm afraid this will open us to legal issues. I can't tell the legal team I'm guessing. What's the most robust way to ensure special characters like ™ always render correctly, especially with dynamic content, and what might be causing my current approach to fail?
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 getting caught by inconsistent rendering of special characters and symbols across…+
I keep getting caught by inconsistent rendering of special characters and symbols across different browsers and content sources.
I keep getting caught by inconsistent rendering of special characters and symbols across different browsers and content sources. This often leads to last-minute fixes and delays. It makes me question my understanding of character encoding. What habit should I change to reliably handle text entities and special characters from the start, avoiding these frustrating inconsistencies?
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.