◆ HTML

Call a function when the page/DOM is ready

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 to make sure my 'initialize-carousel' function runs only after the entire page content…+
I need to make sure my 'initialize-carousel' function runs only after the entire page content is loaded. The marketing team needs the hero carousel working by tomorrow morning.
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 to the client's procurement team, make it easy to approve -- surface the…+
Before I send this to the client's procurement team, make it easy to approve -- surface the savings figure up top, make pricing findable, flag what would make a reviewer hesitate.
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 hero carousel is sometimes broken or not appearing at all when users first land on the…+
The hero carousel is sometimes broken or not appearing at all.
The hero carousel is sometimes broken or not appearing at all when users first land on the page, especially on slower connections. The marketing lead is furious, saying it's impacting conversion rates. I'm afraid we're losing sales. I can't tell if my script is running too early or if there's a conflict. What's the most reliable way to ensure my 'initialize-carousel' function executes only when all necessary page elements are definitely ready, and what's the best next step to diagnose why it's failing intermittently?
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 losing time and credibility because my scripts frequently run before the page is fully…+
I frequently have issues with scripts running before the page is fully loaded, causing errors.
I keep losing time and credibility because my scripts frequently run before the page is fully loaded, leading to broken UI components and errors in the console. This causes user frustration and extra debugging. What habit should I change to ensure my functions always execute at the optimal moment, only when all necessary elements are available, so it reads on a phone?
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.