Link Styling System
Give links one set of rules so they read as links wherever they appear.
What it adds
Defined treatments for links in prose, in navigation, in muted contexts, for external destinations, and for destructive actions.
What your agent is told to do
5
What your agent is told to do
5-
1
Separate links by the job they do — inline prose links, navigation links, muted or secondary links, external links, and destructive ones — and give each a treatment that holds in every theme the app supports.
-
2
Underline links that sit inside a paragraph of text. Colour alone is not enough to distinguish them, and a reader scanning body copy has no other signal.
-
3
Mark links leaving the app for another domain, and make that marker part of the accessible name so it is announced rather than only drawn.
-
4
Decide deliberately where visited styling helps and where it misleads. It is useful in documentation and search results; it is noise on a list of records where every row has been opened once.
-
5
Do not render a disabled-looking link. A link that cannot be followed should either not be a link at all or should lead somewhere that explains why access is unavailable — a greyed anchor is still focusable, still clickable, and explains nothing.
Edge cases it handles
7
Edge cases it handles
7- Links distinguished only by colour disappear for colourblind readers and in greyscale printing. Every link style needs a second signal, usually an underline or a weight change.
- Visited styling applied indiscriminately makes an application look stale and can leak browsing history in shared-screen contexts, so it belongs on content links rather than on record navigation.
- Forced-colours and high-contrast modes override custom colours but respect text decoration, so a link whose only distinction is colour becomes invisible there.
- A link styled to look disabled remains in the tab order and remains activatable, which produces a control that appears inert and then navigates anyway.
- Link colours must clear the contrast threshold against their own background and remain distinguishable from surrounding body text, not merely legible.
- Underlines must not run through descenders illegibly, and must not be removed on hover in a way that makes the link harder to identify than at rest.
- Links opening in a new tab or window must say so, since an unannounced context switch strands users who expect the back button to work.
Definition of done
8
Definition of done
8- Every link in the app maps to one of the defined link roles.
- Inline prose links are distinguishable without relying on colour.
- External links are marked visually and in their accessible name.
- Visited styling is applied only where it was deliberately chosen.
- No disabled-looking anchors remain; unavailable destinations are handled explicitly.
- Link styles survive forced-colours and high-contrast modes with their distinction intact.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Stepper Component
Stepper Component
Show people where they are in a multi-step flow and what is still ahead of them.
What it does
A single stepper used by every staged flow in the app, showing step order, completion, and errors.
How it works
- 1 Find every staged flow the app already has — onboarding, checkout, import wizards, multi-page settings — and render them all through one stepper rather than the three variants that have grown up separately.
- 2 Keep completion and navigation as two distinct concepts. A step can be complete without being current, and a step the user is allowed to jump back to is not the same as a step they have finished.
- 3 Model optional and skippable steps explicitly, and show a skipped step as skipped rather than as complete or as untouched. A user who skipped payment details needs to see that it is still outstanding.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/stepper-component
Avatar Group
Avatar Group
Show who is involved in a compact space without a pile of broken images.
What it does
A stacked set of member avatars with deterministic ordering, an overflow count, and access to the full list.
How it works
- 1 Find the places that show several people at once — assignees, collaborators, workspace members, comment participants — and render them through one grouped component.
- 2 Order the stack deterministically by a stable rule such as role then name, so the same group renders in the same order on every load and every device.
- 3 Cap the number shown and collapse the remainder into a single count that is announced meaningfully, not as a bare number sitting after a row of pictures.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/avatar-group
Dropdown Menu Primitive
Dropdown Menu Primitive
Give every action menu in the app the same keyboard, pointer, and dismissal behaviour.
What it does
A reusable menu primitive covering triggering, item navigation, selection, disabled items, and closing.
How it works
- 1 Find every action menu in the app — row overflow menus, account menus, bulk-action menus, toolbar menus — and rebuild them on one primitive so they stop behaving differently from each other.
- 2 Implement the full keyboard model: arrows move between items, Home and End jump to the ends, typing letters jumps to the matching item, Enter and Space activate, and Escape closes and returns focus to the trigger.
- 3 Close on outside pointer press, on Escape, and on the trigger being pressed again, and always return focus to the trigger so the user is not dropped at the top of the document.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/dropdown-menu-primitive
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.