Timeline Component
Give the app one way to render a chronological run of events.
What it adds
A reusable timeline for ordered events — activity feeds, audit trails, order history, comment threads.
What your agent is told to do
5
What your agent is told to do
5-
1
Identify every place the app already lists things in time order and unify them, rather than leaving the order history, the audit log, and the activity feed as three unrelated layouts.
-
2
Define a deterministic sort for events sharing a timestamp — a secondary key such as the record identifier — so the same data always renders in the same order.
-
3
Give each entry an actor, an action, an object, and a time, and let any of the four be absent without the row collapsing.
-
4
Group entries by day or by burst for scanning, but keep the exact time available on each entry rather than replacing it with the group heading.
-
5
Do not resolve event descriptions by looking up live records at render time. An audit entry must still read correctly after the record it refers to has been renamed or deleted.
Edge cases it handles
7
Edge cases it handles
7- Two events written in the same second must not swap places between renders — order them by a stable tiebreaker so pagination does not duplicate or drop an entry.
- Grouping by day is a scanning aid, not a replacement for precision; a user auditing an incident needs the exact timestamp, so keep it on the entry or on hover and in the title attribute.
- A deleted user or a deleted record must still render its entry, showing a preserved name or a neutral placeholder rather than a blank, a null, or a broken avatar.
- On narrow screens the connector rail, avatars, and timestamps compete for width — drop to a single column with the time above the entry rather than truncating the description.
- Relative times such as two hours ago must be rendered in the reader's time zone and must not go stale on a page left open, and they must never be the only representation of the time.
- A long timeline needs paging or windowing that loads older entries without jumping the scroll position of what the user is already reading.
- An empty timeline needs copy explaining that nothing has happened yet, distinct from the state where a filter has excluded everything.
Definition of done
8
Definition of done
8- All chronological lists in the app render through the same timeline.
- Events sharing a timestamp appear in a stable order across reloads and pages.
- Every entry exposes its exact time in the reader's time zone.
- Entries referring to deleted actors or records render intact with a placeholder.
- The timeline reads as a single column on narrow screens with no truncated descriptions.
- Loading older entries preserves the current scroll position.
- 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.