Component Variant API
Give every component one consistent way to express size, tone, emphasis, and state.
What it adds
A shared variant vocabulary applied across the component set, with stable defaults and impossible combinations refused.
What your agent is told to do
5
What your agent is told to do
5-
1
Inventory how the existing components already express difference — a primary flag on one, a kind string on another, a boolean per style on a third — and collapse them onto one vocabulary of size, tone, emphasis, and state.
-
2
Name variants for their meaning rather than their appearance. A tone called danger survives a redesign; a tone called red does not, and it lies the moment the palette changes or the theme inverts.
-
3
Give every variant prop a default that produces the most common correct result, so a component rendered with no variant props at all is still valid and typical.
-
4
Refuse combinations that cannot be rendered coherently, at development time and with a message naming the conflict. A quiet emphasis with a destructive tone and a loading state may have no sensible appearance, and guessing one produces a control nobody designed.
-
5
Do not add a variant for every one-off design request. Each new value multiplies the combinations that must be checked; if a screen needs something the vocabulary cannot express, that is a design conversation, not a new enum member.
Edge cases it handles
7
Edge cases it handles
7- Conflicting variant combinations must be rejected rather than resolved by precedence. Silently letting one variant win produces a control that looks deliberate but was never designed, and the bug surfaces only when someone screenshots it.
- Defaults must be stable across releases. Changing what an unspecified variant means re-styles every call site that relied on the default, and those call sites are exactly the ones nobody reviews.
- Variant names must be semantic, not visual. Names describing colour, weight, or position break as soon as the theme changes, and they read as lies in a dark theme or a high-contrast mode.
- The variant vocabulary must not defeat static typing or dead-code elimination. Values assembled dynamically from strings cannot be checked at build time and force the whole style surface to ship even when a handful of variants are used.
- State variants such as loading, disabled, and invalid must not be settable in ways that contradict the component's actual behaviour — a control styled disabled while remaining clickable is a trap.
- Every tone must remain legible against every surface it can appear on, including inverted panels and the dark theme, otherwise a valid combination produces unreadable text.
- How a variant value varies across breakpoints belongs to Responsive Prop System; this brief owns the set of allowed values and their meaning, and the two must draw on one shared vocabulary.
Definition of done
9
Definition of done
9- Every component in the set expresses difference through the same variant vocabulary, with no leftover per-component flags.
- Variant names describe meaning rather than appearance.
- A component rendered with no variant props produces a valid, typical result.
- Incoherent variant combinations raise a development-time error naming the conflict.
- Variant values are statically known, so unused styles are eliminated from the build.
- Every tone is legible on every surface it can appear on, in both light and dark themes.
- State variants match the component's real interactive behaviour.
- 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.