Roving Tabindex Utility
Give composite widgets one tab stop, with arrow keys moving inside them.
What it adds
A shared keyboard-navigation behaviour for toolbars, tab strips, menus, option lists, and grids.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the composite widgets where the keyboard currently steps through every child — toolbars, tab strips, menus, segmented controls, option lists, calendar grids, card grids — and give each a single tab stop with arrow keys operating inside it.
-
2
Track the active item by stable identity rather than by index, so items appearing, disappearing, or being reordered cannot move the active position onto an unrelated control.
-
3
Support the orientations these widgets genuinely take: a horizontal row, a vertical list, and a two-dimensional grid where up and down move between rows. Include Home and End, and decide explicitly whether the ends wrap.
-
4
Skip hidden and unavailable items when moving, and if the active item disappears, move to the nearest remaining one rather than leaving the widget with no tab stop at all.
-
5
Do not simply remove every child from the tab order and hope focus is managed elsewhere. Exactly one item must be reachable by tab at any moment, and returning to the widget must land on the item the user left rather than the first one. Which item is focused belongs here; which items are selected belongs to Selection State Pattern, and the two must be free to differ.
Edge cases it handles
7
Edge cases it handles
7- An active item that is filtered out, collapsed, or removed leaves the widget with nothing focusable, and the next tab press lands somewhere unrelated on the page.
- In a grid, arrow keys must move by row and column rather than through a flattened list, and rows of unequal length need a defined behaviour at the short end.
- A list that re-renders after a fetch or a filter must keep the same item active. Restoring by index quietly moves focus to a different control.
- Exactly one item carries the tab stop at any moment; letting two claim it produces a widget that is entered twice, and letting none claim it produces one that cannot be entered at all.
- Typing a letter in a menu or option list is expected to jump to the matching item, and that typeahead must not collide with a search field inside the same widget.
- Arrow keys pressed inside a text input or a native select belong to that control, so the utility has to yield rather than intercepting them.
- Moving the active item must scroll it into view within its own scrolling container without dragging the whole page along with it.
Definition of done
9
Definition of done
9- Each composite widget occupies exactly one stop in the tab order.
- Arrow keys, Home, and End move between items within a widget.
- The active item is tracked by identity and survives re-renders, sorting, and filtering.
- Hidden and unavailable items are skipped, and losing the active item never leaves the widget unreachable.
- Returning to a widget by tab restores the item the user last had active.
- Horizontal, vertical, and grid arrangements are all supported.
- Focus and selection are represented separately and may point at different items.
- 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
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
Progress Indicator System
Progress Indicator System
Tell people how far along the work is, in the same way every time.
What it does
A consistent set of bars, rings, step trackers, and accompanying text for work that takes measurable time.
How it works
- 1 Identify every operation in the app that takes long enough to need feedback — uploads, imports, exports, batch actions, multi-step flows — and decide for each whether its progress is genuinely measurable.
- 2 Use a determinate form only when a real proportion is known. Where the total is unknown, use an indeterminate form and say what is happening in words rather than inventing a percentage.
- 3 Pair every indicator with text that names the operation and its current position, so the information survives for someone who cannot see the graphic.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/progress-indicator-system
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.