◆ HTML

Make a placeholder for a select box

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 taskAdd a placeholder to the 'Country' select box on the registration form that says 'Select your…+
Add a placeholder to the 'Country' select box on the registration form that says 'Select your country'. This needs to be done before user testing starts on Wednesday.
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 the registration form to the UX team, make the 'Country' select box more…+
Before I send the registration form to the UX team, make the 'Country' select box more intuitive. Add a placeholder that guides the user, but also ensure it doesn't interfere with accessibility or validation, flagging anything that might make the UX lead 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 momentI added a placeholder to the 'Country' select box on the registration form, but it's not…+
The 'Country' select box placeholder isn't showing up, and the client wants to see it.
I added a placeholder to the 'Country' select box on the registration form, but it's not appearing when the page loads. The client is expecting to see it in their demo this afternoon. I'm not sure if I've used the wrong attribute, or if there's a conflict with existing styling. What's the most likely reason it's not showing, and what's the fastest way to get it working before the demo?
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 run into issues with form element placeholders, especially for select boxes or…+
Form element placeholders often behave unexpectedly, causing delays.
I frequently run into issues with form element placeholders, especially for select boxes or more complex inputs. They often don't render as expected or conflict with existing JavaScript, costing me time and rework. What habit should I change to ensure placeholders consistently work correctly and efficiently across all form elements from the initial implementation?
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.