◆ HTML

Make a div 100% height of the browser window

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 taskI need this main content area to take up the full browser screen height for the user, so they…+
I need this main content area to take up the full browser screen height for the user, so they don't see a scroll bar immediately. Make sure it's responsive for different screen sizes.
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 hand this off to the content team, make sure this main div always fills the entire…+
Before I hand this off to the content team, make sure this main div always fills the entire browser window vertically. If it doesn't, users will see an awkward blank space or unnecessary scroll, which looks unfinished. Ensure it adapts smoothly when the window is resized.
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 client just complained the hero section isn't filling their screen on a laptop, but it…+
The client just complained the hero section isn't filling their screen on a laptop, but it looks fine on my monitor.
The client just complained the hero section isn't filling their screen on a laptop, but it looks fine on my monitor. I'm worried it's a viewport unit issue or some inherited style I'm missing. What’s the most likely cause for inconsistent full-height behavior across different screens, and what's the first thing I should check to fix 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 keep getting caught by hero sections not consistently filling the viewport on various…+
I keep getting caught by hero sections not consistently filling the viewport on various devices.
I keep getting caught by hero sections not consistently filling the viewport on various devices, leading to last-minute client complaints. I'm wasting time debugging what feels like the same problem. What habit should I change in my initial setup to ensure consistent full-height sections that adapt reliably to all screen sizes, right 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.