◆ HTML

Change an HTML input's placeholder color with 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
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 taskChange the placeholder text color in the 'email-input' field to a light gray, #CCCCCC, so it's…+
Change the placeholder text color in the 'email-input' field to a light gray, #CCCCCC, so it's less obtrusive for the user.
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 the marketing team reviews this form, make sure the placeholder text in all input fields…+
Before the marketing team reviews this form, make sure the placeholder text in all input fields is subtle and consistent with our brand's muted color palette. It needs to be clear enough to read but not compete with actual user input.
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 placeholder text in the 'name' and 'email' fields on the new contact form is showing up as…+
The placeholder text in the contact form is too dark and clashes with the design.
The placeholder text in the 'name' and 'email' fields on the new contact form is showing up as a dark gray, which clashes badly with the light background and the overall design. The design lead just pointed it out and wants it fixed before the client demo tomorrow. I've tried changing the input color, but it affects the actual text, not the placeholder. What's the specific way to target just the placeholder color so it's a lighter, more subtle gray?
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 stuck on styling specific, nuanced parts of standard HTML elements, like…+
I often forget how to style specific, less common parts of standard HTML elements.
I frequently get stuck on styling specific, nuanced parts of standard HTML elements, like placeholder text or scrollbars. It feels like I'm always searching for obscure selectors. What habit should I change to more efficiently recall or discover these specific styling techniques without constantly interrupting my workflow?
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.