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
Screen Reader Only Utility
Screen Reader Only Utility
One tested way to add text for assistive technology without it appearing on screen.
What it does
A single visually hidden utility used for labels, instructions, and context that assistive technology needs and sighted users do not.
How it works
- 1 Find every place the app currently hides text from sight — off-screen positioning, zero dimensions, transparent colour, tiny font sizes, aria-label strings duplicating nearby copy — and consolidate them onto one utility.
- 2 Build it by clipping the element to nothing while keeping it rendered and in the accessibility tree: it must occupy no visual space and contribute nothing to layout, yet still be read in document order.
- 3 Provide a second variant that becomes visible when it receives focus, and use it for skip links and any other hidden content that is itself focusable.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/screen-reader-only-utility
Progress Indicator System
Progress Indicator System
Tell people how far along the work is, in the same way every time.
What it does
A consistent set of bars, rings, step trackers, and accompanying text for work that takes measurable time.
How it works
- 1 Identify every operation in the app that takes long enough to need feedback — uploads, imports, exports, batch actions, multi-step flows — and decide for each whether its progress is genuinely measurable.
- 2 Use a determinate form only when a real proportion is known. Where the total is unknown, use an indeterminate form and say what is happening in words rather than inventing a percentage.
- 3 Pair every indicator with text that names the operation and its current position, so the information survives for someone who cannot see the graphic.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/progress-indicator-system
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
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.