◆ HTML

Set cellpadding and cellspacing in CSS

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 taskI need to set the padding and spacing for the product table on the homepage. Make sure the…+
I need to set the padding and spacing for the product table on the homepage. Make sure the cells have 10 pixels of padding and 5 pixels of spacing between them. This needs to be live before the morning meeting.
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 send this table to the marketing team for review, make it easier to read on a phone.…+
Before I send this table to the marketing team for review, make it easier to read on a phone. Adjust the padding and spacing so it looks clean and professional, and flag any values that might make the content manager hesitate about readability.
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 product table I just pushed live for the client's review looks completely broken on mobile…+
The new product table looks terrible on mobile, and the client is about to see it.
The product table I just pushed live for the client's review looks completely broken on mobile devices, and I'm worried about their reaction. The desktop version is fine, but the cells are squished together on phones. I can't tell if it's the padding, spacing, or something else entirely. What's the most likely cause, and what's the fastest way to diagnose and fix it before they see it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently lose time and credibility trying to make tables look good on different screen…+
Tables always look off on mobile, costing me time and rework.
I consistently lose time and credibility trying to make tables look good on different screen sizes. I always get stuck trying to balance padding and spacing with responsiveness. What habit should I change to prevent these constant rework cycles and ensure tables are consistently readable across all devices from the start?
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.