Duplicate Component Detector
Find the components that solve the same problem twice before a third one appears.
What it adds
An analysis that groups components with near-identical structure, styling, or usage and reports them as consolidation candidates.
What your agent is told to do
5
What your agent is told to do
5-
1
Compare components on both what they render and how they are used. Structural similarity alone groups every small wrapper together, and usage similarity alone misses two implementations of the same card that happen to sit in different areas.
-
2
Read the component list produced by Component Inventory rather than walking the source again. Inventory owns enumeration and usage counts; this feature owns similarity and the consolidation decision.
-
3
Report candidates with the evidence attached — which parts matched, how many usages each has, and which is older — so a human can judge rather than being handed a verdict.
-
4
Treat domain differences as real. Two dialogs that look alike but one confirms a destructive action and the other collects payment details are not duplicates, and the report must have a way to record that permanently.
-
5
Do not consolidate by deleting the loser and rewriting its call sites in one change. Migrate call sites incrementally behind the deprecation route already defined, checking behaviour and accessibility at each site, because the differences that matter are usually the ones not visible in the markup.
Edge cases it handles
7
Edge cases it handles
7- Detection needs both structural and usage similarity. Either signal on its own produces a list dominated by false matches, and a report that is mostly noise stops being read after the second run.
- Legitimate domain differences must be respected and recordable. Components that look identical but carry different consequences, permissions, or copy obligations are not candidates, and marking them as such must persist across runs.
- Usage counts must be shown before any consolidation is proposed, because the component with the better implementation and the component with two hundred call sites are frequently not the same one.
- Behaviour and accessibility must be preserved when a call site is switched over. The surviving component often lacks a focus behaviour, a keyboard shortcut, or an announcement that the retired one had, and none of that shows up in a structural diff.
- Components that differ only in an inline style value or a single class are the most common duplicates and the easiest to miss, so normalise trivial formatting differences before comparing.
- A pair flagged as duplicates but deliberately kept must be suppressible with a recorded reason, or the same pair reappears at the top of every report.
- Consolidation must not silently change a component's rendered element or its default variant, since callers depend on both even when they never pass them.
Definition of done
8
Definition of done
8- Candidates are identified using both structural and usage similarity, not either alone.
- The component list is read from the inventory rather than re-derived.
- Each candidate is reported with matched regions, usage counts, and age.
- Pairs kept apart for domain reasons can be suppressed with a recorded reason that persists across runs.
- Call sites are migrated incrementally through the existing deprecation route, not replaced in a single change.
- Focus behaviour, keyboard handling, and announcements are verified at each migrated call site.
- 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
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
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.