Dialog Size Rules
Fix a small set of dialog widths so every modal in the app looks deliberate.
What it adds
A defined set of dialog sizes with agreed maximum widths, scroll behaviour, and responsive treatment.
What your agent is told to do
5
What your agent is told to do
5-
1
Inventory every dialog in the app and record its current width. The list will contain a spread of arbitrary values, and collapsing them onto four named sizes is most of the work.
-
2
Define the sizes by intent, not by pixel value in the calling code: a confirmation size, a standard form size, a wide size for tables and comparisons, and a full-screen size for genuinely large tasks.
-
3
Give every size the same internal structure — a header that stays, a body that scrolls, a footer that stays — so the action buttons never scroll out of reach in a long dialog.
-
4
Cap the dialog's height against the real viewport height rather than a fixed value, and put the overflow on the body region.
-
5
Do not let callers pass arbitrary widths as an escape hatch. The moment one screen can specify its own, the scale stops being a scale and the inventory you just consolidated grows back.
Edge cases it handles
7
Edge cases it handles
7- The scroll must live in the body region only. If the whole dialog scrolls, the header and footer leave the screen; if the page behind scrolls instead, the user loses their place entirely.
- A confirmation with one sentence and two buttons stretched to a wide dialog reads as a mistake and makes the destructive button look far from the text it refers to. Match size to content, and keep confirmations small.
- Sticky headers and footers must survive at every size and at every content length, including when the body is short enough not to scroll, without leaving a gap or a doubled border.
- Below the mobile breakpoint, small and standard dialogs should become full-width sheets and the wide size should become full-screen, rather than a shrunken desktop dialog with cramped margins.
- A dialog containing a table wider than the dialog needs that table to scroll horizontally inside its own region, not to force the dialog wider or spill past its edge.
- The on-screen keyboard on mobile reduces the usable height sharply, and a dialog sized against the full screen height will push its footer under the keyboard.
- Long unbroken content — a pasted identifier, a URL, a stack trace — must wrap or scroll rather than widening the dialog past its declared size.
Definition of done
9
Definition of done
9- Every dialog in the app uses one of the named sizes, with no arbitrary widths remaining.
- Each size has a documented intent and a maximum width.
- Scrolling happens in the dialog body while the header and footer stay in place.
- Dialog height is capped against the real viewport, including when the on-screen keyboard is open.
- Confirmations use the small size and are never stretched.
- Small and standard dialogs become full-width sheets on mobile, and wide dialogs become full-screen.
- No dialog exceeds its declared size because of its content.
- 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
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
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
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.