AI Smart Defaults
Suggest sensible starting values for a form instead of leaving every field blank.
What it adds
Pre-filled but fully editable default values on the app's forms, derived from the current user, workspace, and related records.
What your agent is told to do
5
What your agent is told to do
5-
1
Identify the forms where users repeatedly type the same value, then assemble the context that would predict it: the acting user's recent entries, the workspace's conventions, and the parent record the form was opened from.
-
2
Render every suggestion as a normal editable field value that is visibly marked as suggested, and clear that marking the moment the user edits it. Never write a suggested value into a record the user has not submitted.
-
3
Build the deterministic default first and keep it in place. The model layer only overrides it when it returns a well-formed value the field would accept and its own stated confidence clears a threshold you configure.
-
4
Give the user a way to see why a value was suggested in plain language, and a single control that clears all suggestions on the form back to the deterministic defaults.
-
5
Do not learn from the user's corrections by silently feeding their edits back as training or long-term memory. Correction data is only reused where the user has agreed to it, and never across tenant boundaries.
Edge cases it handles
8
Edge cases it handles
8- A suggestion is a default, not a decision. If the user submits without looking, they must still get a value they could have arrived at themselves, so a suggestion must never populate a field with legal, financial, or destructive consequences.
- The context assembled for one workspace must never include another tenant's records. Scope every lookup to the acting user's permissions before the request is composed, not after the response comes back.
- Sensitive attributes about a person must not be part of the context or the reasoning, even when they correlate well with the right answer. Exclude them at the point the context is built.
- A surprising suggestion with no explanation reads as a bug. If the app cannot say in one sentence where a value came from, do not show it as a suggestion.
- When the model is slow, unavailable, or returns something the field cannot parse, the form must render immediately with deterministic defaults rather than blocking on the suggestion.
- A suggestion that arrives after the user has already started typing in that field must be discarded, not applied over their input.
- Suggestions must respect field-level validation and permissions. A value the user is not allowed to set must never be offered.
- Cap the spend: a form opened repeatedly in a loop must not issue a request every time. Reuse a recent result for the same context and enforce a per-workspace ceiling on suggestion calls.
Definition of done
8
Definition of done
8- Every suggested value is editable, visibly marked as a suggestion, and unmarked once edited.
- Deterministic defaults render immediately and remain in place when the model is slow, unavailable, or returns unusable output.
- No suggestion is derived from another tenant's data or from sensitive personal attributes.
- Each suggestion can be explained in one sentence in the interface.
- Nothing is written to a record until the user submits the form.
- Suggestion calls are rate limited and capped per workspace, with reuse of recent results for identical context.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
AI Support Triage
AI Support Triage
Summarise each incoming support request and estimate how urgent it really is.
What it does
An automatic summary, urgency estimate, and likely problem area attached to every inbound support request, with the evidence behind each.
How it works
- 1 Run triage as a background job on arrival, using the app's existing queue and retry behaviour. The ticket must be visible and workable in its raw form the moment it lands, whether or not triage has finished.
- 2 Produce three separate outputs — a short summary, an urgency level, and a likely problem area — and store each with the quoted source statements from the ticket that support it, so a human can check the reasoning.
- 3 Define urgency in terms of business impact: who is blocked, how many, whether money or data is at risk. Compute it from what the ticket describes, not from how the writer sounds.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-support-triage
AI Chat Attachments
AI Chat Attachments
Attach files to a conversation and let the assistant use what it is allowed to read.
What it does
File upload on an AI conversation, with parsing, retrieval of relevant sections, and per-conversation access scoping.
How it works
- 1 Reuse the app's existing upload, storage, and virus-scanning path rather than adding a second one, and declare an explicit list of accepted file types and a size ceiling per file and per conversation.
- 2 Parse each attachment into text and structure in a background job, store the result, and show the attachment as pending until parsing succeeds so the user is never told the assistant has read something it has not.
- 3 Retrieve and send only the sections relevant to the current question. Sending whole documents on every turn burns the context window and the budget for no gain.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-chat-attachments
AI Suggested Support Answers
AI Suggested Support Answers
Give support agents a grounded first draft instead of a blank reply box.
What it does
A draft reply composed for the agent from the ticket, the customer's account state, and the approved internal knowledge, with sources attached and no ability to send itself.
How it works
- 1 Ground every draft in retrieved material: the ticket thread, the account's real state, and articles from the approved knowledge set. Attach the sources used to the draft so the agent can open and check each one.
- 2 Load the draft into the agent's normal reply editor, unsent and fully editable. There is no path in this feature that sends a message to a customer without an agent pressing send.
- 3 Define the commitments the app is not allowed to make in a draft — refunds, credits, delivery dates, guarantees of a fix — and strip or refuse any draft containing them, leaving that part for the agent to write.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-suggested-support-answers
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.