Shared Component Ownership
Say who maintains each shared component and how changes to it get reviewed.
What it adds
A recorded owner for every shared component, with review rules that scale to how widely the component is used.
What your agent is told to do
5
What your agent is told to do
5-
1
Split the components into the ones that belong to the design system and the ones that belong to a single product area, and record the split explicitly. Most codebases have a middle tier that everyone edits and nobody maintains, and that tier is where the inconsistencies come from.
-
2
Attach an owner to each shared component and make the ownership record live next to the code, so it is updated in the same change as the component rather than in a document that goes stale within a quarter.
-
3
Require review by the owner for any change that alters a component's public shape, its accessibility behaviour, or its default appearance. Internal refactors that leave all three untouched do not need it.
-
4
Define where an accessibility problem escalates and how quickly. An unlabelled control or a keyboard trap in a shared component is not a normal queue item, and the route to getting it fixed must be written down before it is needed.
-
5
Do not make ownership a gate with no bypass. Provide a documented path for an urgent production fix that notifies the owner and requires follow-up review, because a rule that blocks incident response gets abandoned entirely the first time it bites.
Edge cases it handles
7
Edge cases it handles
7- Design-system components and product-area components need different rules, and the boundary between them must be recorded. Treating every shared file identically either slows product work or leaves the system unguarded.
- Changes to a component's public shape, accessibility behaviour, or default appearance need the owner's review, because those are the changes that reach screens the author has never opened.
- Accessibility defects need a named escalation route and a stated response time. Without one they queue behind feature work and stay in a component rendered on every page.
- An urgent production fix must be able to ship without waiting for the owner, provided the owner is notified and the change is reviewed afterwards. Ownership that cannot be bypassed under pressure is ownership that gets deleted.
- An owner who leaves or changes teams must trigger reassignment; an unowned shared component drifts back into the state this feature exists to fix.
- Ownership must be recorded per component or per directory, not per repository, or every change to anything summons the same small group.
- The rules apply to the component's tests and documentation as well as its implementation, or the behaviour stays guarded while its description quietly rots.
Definition of done
8
Definition of done
8- Every shared component is classified as design system or product area, and the classification is stored with the code.
- Each shared component has a recorded owner, and reassignment happens when an owner departs.
- Changes to public shape, accessibility behaviour, or default appearance require owner review.
- There is a written escalation route and response expectation for accessibility defects.
- An urgent fix can ship without the owner present, with notification and follow-up review required.
- Ownership records cover a component's tests and documentation as well as its implementation.
- 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.