Component Deprecation Path
Retire old components and props gradually instead of breaking every screen at once.
What it adds
A defined route from marking a component or prop as obsolete to removing it, with warnings, replacements, and a dated milestone.
What your agent is told to do
5
What your agent is told to do
5-
1
Mark the deprecation in all three places a developer might look: the static type layer, the component's documentation, and a development-time warning at the call site. A note in one place only will be missed by whoever is not reading that place.
-
2
Never deprecate without naming the replacement. State which component or prop takes over, and where the mapping is not mechanical, describe what the caller has to decide.
-
3
Where the change is mechanical, supply an automated rewrite so the migration is a single reviewed change rather than months of incidental edits. Where it is not, say so plainly rather than shipping a rewrite that produces plausible but wrong output.
-
4
Count remaining usages continuously and make the number visible, drawing on the record built by Component Inventory rather than maintaining a second list. Inventory owns the counting; this feature owns the lifecycle state attached to each entry.
-
5
Do not leave a deprecation open-ended. Attach a removal milestone at the moment of marking, because a deprecation with no end date is a permanent second implementation that everyone still copies from.
Edge cases it handles
7
Edge cases it handles
7- The deprecation must appear in the types, the documentation, and a runtime warning together. A deprecated prop that only warns at runtime is invisible to anyone reading the documentation before they write the call.
- A replacement has to be named and a rewrite supplied where the mapping is mechanical. Telling callers a component is deprecated without saying what to use instead guarantees they keep using it.
- Remaining usage must be tracked as a live number rather than counted by hand at removal time, or the removal lands on a screen nobody knew still depended on it.
- A removal milestone must be a real date on a real release, and the deprecation must be reviewed when it arrives. Deprecations that slip indefinitely train everyone to ignore the warnings.
- Deprecation warnings must not fire in production for end users, and must not be so noisy in development that they drown the diagnostics developers actually need.
- Something consumed outside this codebase — an embed, a published package, a template — cannot be removed on the same schedule as an internal component, and needs its own longer window.
- The replacement must be in place and stable before the warning goes out, otherwise callers migrate onto something that is itself about to change.
Definition of done
8
Definition of done
8- Every deprecated component or prop is marked in the type layer, the documentation, and a development-time warning.
- Each deprecation names its replacement and provides an automated rewrite where the mapping is mechanical.
- Remaining usage counts are derived from the component inventory rather than a separate hand-maintained list.
- Each deprecation carries a removal milestone that is reviewed when it falls due.
- Deprecation warnings are absent from production builds and deduplicated in development.
- No component is removed while its usage count is above zero.
- 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.