Survey Builder
Build a multi-question survey, send it out, and read all the answers in one place.
What it adds
An authoring tool for multi-question surveys, a respondent flow, and a results view with export.
What your agent is told to do
5
What your agent is told to do
5-
1
Ship a small, honest set of question types first: single choice, multiple choice, short text, long text, and a rating scale. That covers most real surveys. Defer matrix grids, file uploads, and calculated fields rather than half-building them.
-
2
Render the respondent flow with the app's existing Multi-Step Form and Conditional Form Fields, and reuse Form Field Shell for the inputs, so a survey looks and behaves like every other form in the product.
-
3
Give surveys the app's existing Draft and Publish States. Editing a live survey while responses are arriving is the main way survey data gets corrupted, so publishing must be a deliberate act with a clear boundary.
-
4
Autosave the author's work through the app's existing Autosave and warn on unsaved changes. Losing a twenty-question survey to a closed tab is the failure that makes people stop using the builder.
-
5
Do not build your own results export. Extend the app's existing CSV Export so survey results arrive in the same format, with the same permissions and the same delivery path as every other export.
Edge cases it handles
8
Edge cases it handles
8- Editing a published survey changes the meaning of answers already collected. Version the survey on publish, store the version against each response, and read historical responses against the version they were answered under so old data stays interpretable.
- Skip logic makes it easy to author a branch that leads nowhere, or a loop that traps the respondent. Validate the branch graph before publishing and refuse to publish a survey where any path fails to reach the end.
- Anonymous and identified responses need different handling throughout, not a flag on a row. Decide per survey, tell respondents plainly which one applies, and make sure an anonymous survey does not quietly retain the identifiers its request carried.
- A public survey URL will be submitted by scripts. Cap responses per survey and per source, apply the app's existing Rate Limiting, and give the author a way to see and discard a suspicious burst without deleting genuine responses alongside it.
- Exporting one row per answer produces a file nobody can analyse. Export one row per response with one column per question, keeping the column order stable across exports so a saved spreadsheet formula does not silently point at the wrong question.
- A partially completed response is real data. Decide whether partials are saved and counted, say so in the results view, and do not let an abandoned response quietly disappear or quietly skew a completion rate.
- Long text answers are user-generated content shown to the survey author. Escape them on display and route them through the app's existing moderation so a response cannot inject markup into the results view.
- Deleting a question after responses exist must not delete the answers. Retire the question so its historical answers remain visible in results and exports, marked as no longer asked.
Definition of done
9
Definition of done
9- An author builds, previews, publishes, and closes a survey with a defined draft and published boundary.
- Each response records the survey version it was answered under, and results remain interpretable after edits.
- Skip logic is validated before publish, with no branch that fails to reach the end.
- Anonymous surveys retain no respondent identifiers, and respondents are told which mode applies.
- Submissions are rate limited and capped, and suspicious bursts can be reviewed and discarded separately.
- Results export through the app's existing export path as one row per response with stable columns.
- Author work autosaves and warns before unsaved changes are lost.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Automation Builder
Automation Builder
Let customers wire a trigger, some conditions and an action so routine work runs itself.
What it does
A visual builder where a customer connects a trigger to conditions and actions, plus the runtime that executes it and a log of what happened.
How it works
- 1 Ship a fixed, curated set of triggers, conditions and actions drawn from what the app already does. A general-purpose scripting environment is not the minimum version, and offering one you cannot support is worse than offering ten steps that work.
- 2 Run automations through the app's existing background job system. If Background Job Dashboard or Scheduled Job Monitor exists, automation runs appear there rather than in a separate queue nobody watches.
- 3 Make the run log the centre of the feature, not an afterthought. A customer whose automation did nothing needs to see which run fired, what data entered each step, and where it stopped.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/automation-builder
Quiz Builder
Quiz Builder
Build a scored quiz with branching questions and a result page that reflects the answers.
What it does
An authoring tool for multi-question quizzes with scoring rules and answer-based branching, plus the taking experience and a result page.
How it works
- 1 Reuse the app's existing form machinery for the taking experience. If Multi-Step Form and Conditional Form Fields exist, the quiz runner is those features driven by the quiz definition, not a second form engine.
- 2 Support a small set of question types that actually score: single choice, multiple choice, and short text with an exact or pattern match. Free-text grading and media questions are a separate scope and should be deferred.
- 3 Give the author a way to see the quiz as a taker would, including a specific answer path, before it is published. A branching quiz cannot be checked by reading the editor.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/quiz-builder
Subtitle Editor
Subtitle Editor
Fix wrong words and bad timing on a caption track next to the video itself.
What it does
A side-by-side editor pairing the video player with an editable, time-aligned list of caption cues.
How it works
- 1 Build this on top of the caption tracks produced by Auto Captions rather than as a standalone tool. Editing a machine track is the main reason anyone opens this screen.
- 2 Show the cue list beside the player, keep the active cue highlighted as the video plays, and make clicking a cue seek the player to its start.
- 3 Let a cue be retimed by dragging its edges on a timeline and by typing exact timecodes. Dragging is faster; typing is the only way to be precise.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/subtitle-editor
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.