◆ HTML

Create a checkbox with a clickable label

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 checkbox for 'Subscribe to newsletter' next to the email input on the contact form, and…+
Add a checkbox for 'Subscribe to newsletter' next to the email input on the contact form, and ensure clicking the text also toggles the box. Set it to be unchecked by default.
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 acceptOur legal team wants the 'I agree to terms' checkbox to be highly visible and easy to interact…+
Our legal team wants the 'I agree to terms' checkbox to be highly visible and easy to interact with, especially on mobile, before the user can proceed. Make sure clicking the text activates the checkbox and it's clearly associated with the agreement statement.
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 'Remember Me' checkbox on the login page isn't working for some users; they're reporting…+
The signup form is getting complaints that users can't check the 'Remember Me' box.
The 'Remember Me' checkbox on the login page isn't working for some users; they're reporting that clicking the label doesn't toggle the checkbox, and sometimes even clicking the box itself is unresponsive. I'm afraid this is causing frustration and abandoned logins, and I can't tell if it's a browser issue or something I messed up. What's the likely diagnosis, and what's the best next step to fix this quickly?
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 get feedback that checkboxes, especially those with associated labels, are not…+
I frequently get bug reports about checkboxes being hard to click or unresponsive.
I frequently get feedback that checkboxes, especially those with associated labels, are not user-friendly, leading to frustration and lost conversions. This often comes up during user testing, making me look like I'm not paying attention to detail. What habit should I change to ensure all my checkboxes are consistently accessible and intuitive to use?
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.