Review password fields for security and ease of use. Check autocomplete settings, accessible visibility controls, strength indicators, and password manager support, then verify relevant browser and HTTP behavior in an environment resembling production.
Use when reviewing headers, forms, cookies, or third-party integrations related to Secure password input fields. Validate the effective browser and HTTP behavior in a production-like environment.
password-field-security reviews password fields for security and ease of use, then identifies what needs fixing. It checks type='password', the different autocomplete values needed for login and registration, and input names that password managers can recognize. The review also covers accessible show/hide buttons, password strength and requirement displays, and whether passwords are stored or transmitted in plain text.
Use it when reviewing a login screen or registration form. It also helps when you want to check actual browser and HTTP behavior in an environment resembling production, alongside the code itself.
autocomplete values to support password managers.”Verifying behavior requires examining actual responses in an environment resembling production. Detailed implementation examples and guidance for individual frameworks are provided in the accompanying references/rule.md.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Properly implemented password fields improve security by working with password managers, helping users create strong passwords, and providing accessible controls for all users.
Verify password fields use type='password', have proper autocomplete values, and include accessible show/hide toggles.
Implement password fields with autocomplete='new-password' or 'current-password', accessible toggle buttons, and optional strength meters.
Explain security and UX best practices for password fields including autocomplete attributes and accessible reveal functionality.
Review server config, headers, forms, and integration points related to Secure password input fields. Flag exact responses, cookies, or browser behaviors that violate the rule, and verify them against the effective production-like response.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/security/password-field-security
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.