Password Strength Meter
Show whether a password is actually hard to guess, and how to fix it.
What it adds
A live strength indicator based on guessability — length, common passwords, and terms drawn from the user's own details — with specific advice.
What your agent is told to do
5
What your agent is told to do
5-
1
Score guessability, not character classes. 'P@ssw0rd1' satisfies every composition rule and is one of the first guesses any attacker makes.
-
2
Penalise the user's own email, name, workspace and product name — those are the first things a targeted attacker tries.
-
3
Give one concrete suggestion at a time, tied to the actual weakness. 'Add a symbol' is theatre; 'this is a common password' is useful.
-
4
Evaluate entirely in the app. Never send a password, or anything derived from it that could be reversed, to a third-party service.
-
5
Do not let the meter and the server disagree. If the server rejects something the meter called strong, the meter is lying — derive both from the same policy.
Edge cases it handles
6
Edge cases it handles
6- The meter must be advisory unless server policy sets a real minimum; blocking on a subjective score frustrates people using password managers.
- Very long passphrases must score well even without symbols or digits.
- Pasted passwords from a manager must be scored the same as typed ones, and paste must not be blocked.
- A large common-password list must not be shipped in a way that stalls the first keystroke — load it lazily or check server-side.
- The score must be announced to assistive technology, and must not rely on colour alone to signal weakness.
- Never log, echo, or include the password in error reports while scoring it.
Definition of done
8
Definition of done
8- Scoring accounts for length, common passwords, and user-specific terms.
- Client feedback and server acceptance come from the same policy and never contradict each other.
- No password data leaves the application.
- Long passphrases score strongly without symbol requirements.
- The strength level is conveyed by text as well as colour and is announced to screen readers.
- Paste is allowed and scored identically to typing.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
User Roles
User Roles
Not everyone should be able to do everything.
What it does
Role-based permissions, enforced on the server, with a UI that reflects them.
How it works
-
1
Define roles and their permissions in ONE place. Scattering
if user.admin?through the codebase is how authorization bugs happen. - 2 Enforce every permission server-side, at the controller or service layer.
- 3 Hide UI the user can't use — but never rely on hiding as the enforcement.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/user-roles
Member Directory
Member Directory
Show who is in the workspace and how to identify them.
What it does
A searchable, read-only roster of workspace members with their role, status, and the profile fields they have chosen to share.
How it works
- 1 Build this as a read view. Inviting members is owned by Team Invitations, changing roles is owned by User Roles, and seat counts are owned by Seat Management — link out to those rather than duplicating their controls here.
- 2 Show each member's display name, avatar, role, and status. Status is not decoration: pending, active, suspended, deactivated, and external guest must be visually distinct and filterable.
- 3 Respect per-field profile visibility. A field the member marked private is not rendered, not returned by the API, and not searchable — hiding it in the template while shipping it in the payload is not privacy.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/member-directory
Account Linking
Account Linking
Let one account sign in several ways without spawning duplicates.
What it does
Attach and detach sign-in methods — password, OAuth providers, SSO — on a single existing account.
How it works
- 1 Model sign-in methods as separate identity records attached to one account, rather than columns on the user.
- 2 Require a fresh re-authentication before any link or unlink. A stale session is enough to read the app; it is not enough to change how the account is entered.
- 3 Refuse to link an identity that is already attached to another account. Explain the conflict and point the user at recovery — do not silently steal the identity or silently create a second account.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/account-linking
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.