Avatar Group
Show who is involved in a compact space without a pile of broken images.
What it adds
A stacked set of member avatars with deterministic ordering, an overflow count, and access to the full list.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Make the group activatable to reveal the full list of people with their full names, since the stack itself can only ever be a summary.
-
5
Do not rely on a photograph being present. Every member needs a fallback built from their name, and every fallback needs to survive a missing name, a single-character name, and a name in a non-Latin script.
Edge cases it handles
7
Edge cases it handles
7- Unstable ordering makes the same group look like different groups across two pages. Sort by a stable field rather than by whatever order the API returned.
- The overflow indicator must be a real count with an accessible name explaining what it counts, and activating it must reach the same full list as the group itself.
- Two members with the same initials produce two identical circles. Vary the fallback deterministically per person and make sure hovering or activating still resolves who is who.
- The full membership must be reachable without hovering, since hover is unavailable on touch and unreliable with a keyboard.
- Avatar images fail to load often enough that the failure is the normal case. The fallback must render immediately and must not leave a broken image icon or an empty hole in the stack.
- A group with one member should not render as a stack, and a group with none needs a defined empty treatment rather than a lone overflow bubble.
- Overlapping avatars must not overlap their hit areas if each is individually interactive; either give each a clear target or make only the group activatable.
Definition of done
8
Definition of done
8- The same set of people renders in the same order on every load.
- Overflow collapses into a count with an accessible description.
- The full member list is reachable by keyboard and on touch.
- Missing images fall back to a generated placeholder with no broken image state.
- Members with identical initials are visually and textually distinguishable.
- Groups of zero and of one have defined treatments distinct from the stacked case.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Screen Reader Only Utility
Screen Reader Only Utility
One tested way to add text for assistive technology without it appearing on screen.
What it does
A single visually hidden utility used for labels, instructions, and context that assistive technology needs and sighted users do not.
How it works
- 1 Find every place the app currently hides text from sight — off-screen positioning, zero dimensions, transparent colour, tiny font sizes, aria-label strings duplicating nearby copy — and consolidate them onto one utility.
- 2 Build it by clipping the element to nothing while keeping it rendered and in the accessibility tree: it must occupy no visual space and contribute nothing to layout, yet still be read in document order.
- 3 Provide a second variant that becomes visible when it receives focus, and use it for skip links and any other hidden content that is itself focusable.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/screen-reader-only-utility
Landmark Shell
Landmark Shell
Give every page the same navigable regions so people can jump straight to the content.
What it does
A reusable application shell providing labelled banner, navigation, main, complementary, and contentinfo regions on every route.
How it works
- 1 Find the layouts the app already renders and identify what each region actually is — the top bar, the primary navigation, the page body, any inspector or sidebar, the footer — then express them as landmarks once in the shell rather than per page.
- 2 Give the shell exactly one main region per rendered page, and make it the target of a skip link that is the first focusable thing in the document.
- 3 Label every landmark that appears more than once so they can be told apart — primary navigation, breadcrumb, pagination — using a short distinct name rather than the word navigation repeated.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/landmark-shell
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
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.