◆ HTML

Make a div not larger than its contents

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 taskMake the 'product-description' div on the item detail page only as wide as its text content,…+
Make the 'product-description' div on the item detail page only as wide as its text content, not spanning the full width of its parent.
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 layout for the blog post comments, make sure the comment boxes don't…+
Before I push this new layout for the blog post comments, make sure the comment boxes don't create awkward empty spaces. They should only take up the room they need, even if a comment is very short, so the page looks clean and professional.
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 'call-to-action' div on the landing page is taking up too much horizontal space, pushing…+
The 'call-to-action' div on the landing page is taking up too much horizontal space, pushing other elements out of alignment.
The 'call-to-action' div on the landing page is taking up too much horizontal space, pushing other elements out of alignment, and it looks messy. The marketing team wants this fixed before the ad campaign goes live on Tuesday. I've tried setting its width, but it's still behaving unexpectedly. I'm not sure if it's a display property conflict or a parent element issue. What's the most reliable way to make sure this div only takes up the space its content requires, without breaking the layout?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently fight with div elements expanding unnecessarily and breaking layouts, especially…+
I frequently fight with div elements expanding unnecessarily and breaking layouts.
I frequently fight with div elements expanding unnecessarily and breaking layouts, especially on responsive designs. This costs me a lot of time in debugging and adjusting. What habit should I change in how I style or structure div elements to ensure they consistently only take up the space they need, without me having to micro-manage their dimensions?
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.