Copy to Clipboard
Make copying an exact value one click, with feedback the user can trust.
What it adds
A copy control on every value people currently select by hand — IDs, API keys, share links, snippets.
What your agent is told to do
5
What your agent is told to do
5-
1
Find every value a user would plausibly copy: record IDs, tokens, invite links, code blocks, error references.
-
2
Copy the exact value. Strip the surrounding whitespace and any zero-width or formatting characters the UI added for display.
-
3
Confirm the copy in place, next to the control, and revert to the idle state after a couple of seconds.
-
4
Do not copy a masked or truncated value. If the UI shows dots or an ellipsis, either copy the full underlying value or require the user to reveal it first.
-
5
Do not move focus on copy. The user is usually mid-flow and about to paste somewhere else.
Edge cases it handles
6
Edge cases it handles
6- The Clipboard API fails on insecure origins and when permission is denied. Fall back to a selectable field and tell the user to copy manually.
- Code snippets keep their line breaks and indentation; IDs and URLs must not carry a trailing newline.
- A secret shown masked must never end up on the clipboard by accident.
- Confirmation must be announced to screen readers, not conveyed by a colour change alone.
- Copying twice in quick succession must not stack two confirmations on top of each other.
- On mobile the confirmation must not appear under the user's thumb.
Definition of done
7
Definition of done
7- Every copyable value in the app has a copy control.
- The copied value matches the real value exactly, with no stray whitespace.
- Masked secrets cannot be copied without being revealed.
- A blocked or unavailable Clipboard API degrades to a manual fallback rather than failing silently.
- Success is announced accessibly and focus does not move.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Feedback Widget
Feedback Widget
Let anyone report a bug or send a comment from the page they are looking at.
What it does
An always-available launcher that opens a short feedback form and submits it with page context attached.
How it works
- 1 Put a single persistent launcher in one corner of the app and open a compact form in place. Do not route the user to a separate feedback page and lose the context they were about to describe.
- 2 Attach the current URL, the app version, the viewport size, the signed-in account, and a short trail of recent client errors automatically, so the reporter does not have to describe where they were.
- 3 Show the captured context to the user before they send it, in a collapsible section, and let them remove it. Silent collection of screen state is a trust problem.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/feedback-widget
Booking Page
Booking Page
A shareable page where someone picks an open time and confirms it in a few clicks.
What it does
A public scheduling page listing open slots, taking a booking, and confirming it to both sides.
How it works
- 1 Build the visitor path first: pick a date, see open times in their own zone, fill a short form, confirm, and receive an email with the details and a cancellation link. That is the minimum coherent version.
- 2 Derive open slots from the owner's availability rules and existing bookings on the server at request time. Do not trust a slot list the browser has been holding since page load.
- 3 Reuse the app's existing Time Zone-Aware Scheduling for conversion and storage, store every time as an absolute instant, and display it converted to the visitor's detected zone with the zone named on screen.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/booking-page
Date and Time Display Component
Date and Time Display Component
Render every date and time through one component so none of them are ambiguous.
What it does
A single shared way of displaying dates and times, covering absolute format, time zone, and optional relative phrasing.
How it works
- 1 Find every place the app renders a date or a time — tables, activity feeds, audit logs, exports, emails, tooltips — and route them all through one display path rather than formatting at each call site.
- 2 Never render an all-numeric date whose day and month could be swapped. Spell or abbreviate the month, or use an unambiguous ordering consistently, because a reader has no way to tell 04/07 from 07/04.
- 3 State the time zone whenever the value is a specific moment rather than a calendar day, and be explicit about whose zone it is — the viewer's, the record's, or the account's — rather than leaving it implied.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/date-and-time-display-component
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.