Feedback Widget
Let anyone report a bug or send a comment from the page they are looking at.
What it adds
An always-available launcher that opens a short feedback form and submits it with page context attached.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Route submissions into the app's existing support, ticketing, or moderation destination rather than creating a second inbox nobody watches.
-
5
Do not require a category, a severity, or a rating before someone can type. Every required field ahead of the message box loses reports.
Edge cases it handles
8
Edge cases it handles
8- Capture the current page and session context automatically at the moment the widget opens, not at submit, or a redirect during typing will file the report against the wrong screen.
- If submission fails, keep the typed draft in place with the error shown above it and let the user retry. Losing a bug report to a network blip is the one failure that guarantees it is never re-filed.
- Strip sensitive values out of the captured context before it leaves the browser: password fields, card numbers, tokens, and any field the app marks as private.
- The launcher must not sit on top of a chat bubble, a cookie banner, or a scroll-to-top control. Detect other fixed corner elements and offset, or place it where nothing else lives.
- Confirm receipt with a visible reference the user can quote, so the same issue is not sent four times while they wait.
- Anonymous feedback from public pages needs rate limiting and spam handling, or the inbox fills with automated submissions.
- The form must be reachable and dismissable by keyboard, with focus trapped while open and returned to the launcher on close.
- Very long pasted logs need a size limit that truncates with a note rather than rejecting the whole submission.
Definition of done
9
Definition of done
9- The widget is reachable from every page of the app without navigating away.
- Page URL, app version, account, and recent client errors are attached automatically and shown to the user before sending.
- Sensitive field values are excluded from the captured context.
- A failed submission preserves the draft and offers a retry.
- Successful submissions return a visible reference and land in the app's existing support destination.
- Anonymous submissions are rate limited.
- The launcher does not overlap other fixed corner elements at any viewport width.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Interactive Transcript
Interactive Transcript
Put the transcript next to the player so clicking any line jumps playback to that moment.
What it does
A time-aligned transcript panel beside the audio or video player, with click-to-seek, a moving highlight, and in-transcript search.
How it works
- 1 Render the transcript from the timestamps the app already stores. If Voice Transcription exists, extend its output and its data model rather than producing a second transcript with its own timings.
- 2 Make every line a real seek target: clicking or pressing enter on a line moves playback to that time and keeps focus where the user left it.
- 3 Highlight the line currently being spoken and keep it in view as playback advances, using the player's own time updates rather than a separate timer.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/interactive-transcript
Reschedule and Cancel Links
Reschedule and Cancel Links
Give every booking confirmation a link the person can use to move or cancel it.
What it does
Tokenised self-service links in booking confirmations and reminders that let the attendee change or cancel without signing in.
How it works
- 1 Put the two links in the booking confirmation, in every reminder, and on the confirmation screen itself. A person looking for the link is usually looking in the last message they received.
- 2 Land the link on a page that restates the booking in plain terms before offering any action, so someone who opened it by accident can see what they are about to change and back out.
- 3 Reuse the app's existing Signed Share Links mechanism for token generation, expiry, and revocation rather than inventing a second token scheme. If the app has Magic Link Sign-In, note that this link grants access to one booking only and must never establish a full session.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/reschedule-and-cancel-links
Permission-Aware Action
Permission-Aware Action
Decide once how a control behaves when the user is not allowed to use it.
What it does
A shared wrapper for buttons, menu items, and links that resolves visibility, disabled state, and the reason a user cannot proceed.
How it works
- 1 Inventory every action in the app that any role can be denied, and give each one a named capability rather than scattering role comparisons through the components that render it.
- 2 Pick one of three treatments per action and record the choice: hide it, show it disabled with a reason, or show it enabled and let the attempt fail into an upgrade or request-access path. Defaulting everything to hidden makes the product look smaller than it is.
- 3 Whenever an action is disabled, say why in words the user can act on — the role that is required, the prerequisite that is missing, the plan limit that has been reached — and where possible offer the next step.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/permission-aware-action
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.