Component Inventory
Keep a searchable record of every component, its variants, its owner, and where it is used.
What it adds
A generated, browsable list of the components in the codebase with their variants, owners, usage counts, and lifecycle state.
What your agent is told to do
5
What your agent is told to do
5-
1
Derive the inventory from the source rather than from a maintained document. Anything a person has to remember to update is wrong within a month, and a wrong inventory is worse than none because decisions get made from it.
-
2
Record for each entry the variants it accepts, the owner recorded by Shared Component Ownership, the number of usages, and the files that use it. Ownership is defined by that feature; this one only reads and displays it.
-
3
Follow re-exports, wrappers, and renamed imports back to the component that actually renders, so a thin local wrapper does not appear as its own component and hide the real usage count.
-
4
Exclude generated output, vendored code, and third-party sources from the count, and say in the inventory that they were excluded rather than quietly dropping them.
-
5
Do not present the inventory as a one-off report. Regenerate it in the same automated checks that run on every change, and fail the check when the committed inventory no longer matches the source.
Edge cases it handles
7
Edge cases it handles
7- Wrappers, aliases, and re-exports must resolve to the underlying component. Counted naively, a component used through three local wrappers looks like four rarely-used components and survives a cleanup it should not have survived.
- Generated files, vendored dependencies, and third-party components must be excluded from the inventory, or the list is dominated by code nobody in this codebase can change.
- Deprecated and experimental entries must be labelled as such in the listing, so someone searching for a component to reuse does not adopt one that is scheduled for removal.
- The inventory has to be regenerated automatically on every change and checked for drift, because a stale inventory is consulted with the same confidence as a current one.
- Components reached only through dynamic or data-driven rendering will show zero usages by static analysis, so those call sites need to be recognised or the entry flagged as uncertain rather than reported as unused.
- Usage counts must distinguish production code from tests, stories, and examples, or a component used nowhere but its own tests appears healthy.
- The listing needs to be searchable by variant and by owner, not only by name, since the common question is which components already solve a given problem.
Definition of done
9
Definition of done
9- The inventory is generated from source and regenerated by the automated checks on every change.
- Each entry lists variants, owner, usage count, and the files that use the component.
- Wrappers, aliases, and re-exports resolve to the component that actually renders.
- Generated, vendored, and third-party code is excluded, and the exclusion is stated in the listing.
- Deprecated and experimental components are labelled in the listing.
- Usage counts separate production usage from tests, stories, and examples.
- A drifted inventory fails the automated check rather than being silently accepted.
- 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
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
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.