Badge Component
Use one small label component instead of a dozen coloured pills.
What it adds
A compact label with fixed tone, shape, and size rules for counts, categories, and short attributes.
What your agent is told to do
5
What your agent is told to do
5-
1
Collect the coloured pills, chips, tags, and counts already scattered across the app and reduce them to one component with a defined set of tones.
-
2
Give each tone a stated meaning and use it consistently — a neutral tone for categories, and any semantic tone reserved for meaning rather than decoration.
-
3
Constrain the content: a badge holds a short word, a very short phrase, or a number. Set an upper bound and decide what happens beyond it, including how a count above the bound is rendered.
-
4
Keep badges non-interactive. If something needs to be clicked, dismissed, or filtered on, it is a chip or a button and belongs to the relevant control, not here.
-
5
Where a badge is being used to show the state of a record, that meaning is owned by Status Indicator System; this brief owns only the visual container and its constraints. Do not define a status vocabulary here.
Edge cases it handles
7
Edge cases it handles
7- Long or translated labels will overflow a badge sized for English. Set a maximum width with predictable truncation and keep the full value available on hover and in the accessible name.
- Small text on a tinted background frequently fails contrast even when the same colours pass at body size. Verify each tone at the badge's actual text size in both light and dark themes.
- A badge that carries an interaction — a remove cross, a click-to-filter — becomes a control and inherits every requirement of one, including focus, keyboard operation, and a hit area. Keeping labels and controls separate avoids that entirely.
- In a dense table cell or a narrow card, a row of badges must wrap or collapse to a count rather than forcing the column wider or clipping at the edge.
- Numeric badges need a defined ceiling, so a count of nine thousand does not stretch a navigation item.
- A badge conveying meaning by colour alone is unreadable to colourblind users; the text inside it must carry the information.
- Badges placed inside a link or button must not be announced as separate interactive elements.
Definition of done
8
Definition of done
8- One badge component covers every compact label in the app.
- Each tone has a documented meaning and is used only for that meaning.
- Badge text passes contrast at its actual size in every supported theme.
- Overlong content truncates predictably with the full value still available.
- Badges contain no interactive controls.
- Badge groups in tables and cards wrap or collapse without widening or clipping their container.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
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
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
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.