Form Builder
Let an admin build a form and change its fields without a developer touching the schema.
What it adds
An admin-facing form designer plus a stored definition that renders, validates, and collects submissions.
What your agent is told to do
5
What your agent is told to do
5-
1
Store the form as a definition of ordered fields, each with a type, a stable key, a label, and validation rules. Do not generate a database column per field; answers belong in a submission record tied to the definition.
-
2
Render the built form with the app's existing Form Field Shell, Inline Validation, and Conditional Form Fields so a generated form is indistinguishable from a hand-written one.
-
3
Enforce every builder rule again on the server. Client validation is a convenience, and a public endpoint will receive submissions that never touched the rendered form.
-
4
Version the definition whenever a field is removed or retyped, and render and export old submissions against the version they were made under.
-
5
A file field on a public form lets an anonymous visitor put bytes into the app's storage, so route it through the existing File Upload and inherit the accepted types and the size ceiling already enforced there. A form the admin built must not be able to accept what the rest of the app rejects.
Edge cases it handles
8
Edge cases it handles
8- Deleting a field must not blank the answers already given for it. Keep the version each submission was made against so an export from last month still has its columns.
- Rules configured in the builder must be enforced server-side as well as in the browser. A field that is only required in the page is not required at all.
- A field key that is edited or duplicated silently orphans every answer stored under the old key. Generate keys once, keep them immutable, and let the visible label change freely instead.
- A public form endpoint will be found by bots within days. Rate limit by address and by form and screen for spam without a visible puzzle, reusing the app's existing Rate Limiting rather than adding a second one.
- File fields are the easiest route for arbitrary content into your storage. Enforce size and type server-side, scan what the app already scans, and set a retention period for submitted files.
- Submissions routinely contain personal data. Decide who in the workspace may read them back, and make deleting a submission actually delete its uploaded files.
- A form the author is still editing must not be collecting real answers. Keep an explicit published state and a preview mode that does not write a submission.
- A submission rejected by the server must return the person to the form with their typed answers intact, not to an empty one.
Definition of done
9
Definition of done
9- An admin adds, reorders, retypes, and removes fields and publishes the result without a code change.
- Every builder rule is enforced on the server at submission time.
- Field keys are stable and stored answers survive label and ordering changes.
- Submissions made under an earlier version still render and export correctly.
- Public form endpoints are rate limited and spam screened.
- A file submitted through a public form is restricted to the same types and sizes as any other upload in the app.
- A failed submission returns the person's answers rather than an empty form.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Survey Builder
Survey Builder
Build a multi-question survey, send it out, and read all the answers in one place.
What it does
An authoring tool for multi-question surveys, a respondent flow, and a results view with export.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/survey-builder
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
Alignment Guides and Snapping
Alignment Guides and Snapping
Line elements up exactly while dragging, instead of landing a few pixels off.
What it does
Live guide lines and snapping that align a dragged element to the edges, centres, and spacing of its neighbours.
How it works
- 1 Snap to more than edges. Match left, right, top, bottom, horizontal centre, vertical centre, and equal spacing between three or more elements, and draw a guide for whichever match wins.
- 2 Hold a modifier key to suspend snapping entirely for the duration of a drag, so an author who genuinely wants an element two pixels off the grid can place it.
- 3 Compute the snap threshold in canvas coordinates, not screen pixels, so the pull feels the same at every zoom level. A fixed pixel threshold becomes unusable when zoomed out.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/alignment-guides-and-snapping
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.