◆ HTML

Disable browser autocomplete on form fields

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 taskOn the checkout page, disable autocomplete for the credit card number field and the CVV field.…+
On the checkout page, disable autocomplete for the credit card number field and the CVV field. We need to ensure users manually enter these for security reasons before the end of the week.
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 we push the new user registration form live, review all sensitive fields like email and…+
Before we push the new user registration form live, review all sensitive fields like email and password. Disable browser autocomplete on those fields to enhance user privacy and prevent accidental data leakage, especially on shared computers. Make sure it doesn't interfere with password managers.
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 security team just flagged our login form, saying some users' browsers are pre-filling…+
The security team just flagged a potential risk with pre-filled sensitive data on the login form.
The security team just flagged our login form, saying some users' browsers are pre-filling sensitive data, which is a potential risk if someone else uses their computer. I thought I had disabled autocomplete everywhere. Now the head of security is asking for an immediate fix, and I'm not sure if I missed a specific attribute or if there's a broader issue. What's the best next step to diagnose and resolve this quickly without breaking existing functionality?
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 missing the step to disable autocomplete on new form fields, especially for sensitive…+
I frequently miss disabling autocomplete on new form fields, leading to security concerns.
I keep missing the step to disable autocomplete on new form fields, especially for sensitive data. This often leads to security team flags or user privacy concerns after deployment. What habit can I change to consistently remember and correctly apply the necessary attributes from the start, avoiding rework and potential security vulnerabilities?
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.