Saved Blocks Library
Save a section once and reuse it anywhere, with copies that stay linked if you want.
What it adds
A workspace library of reusable saved sections, each insertable as a linked instance or a detached copy.
What your agent is told to do
5
What your agent is told to do
5-
1
Let an author save any section they have built into the library with a name, and insert it into another page from a picker. Reuse the app's existing Template Picker rather than building a second chooser.
-
2
Ask at insert time whether the copy stays linked to the original or detaches immediately, and mark which it is on the canvas. An author who cannot tell will eventually edit a linked block and change six live pages by accident.
-
3
When a linked original changes, merge the update into its instances field by field and leave locally overridden fields alone. Define which fields an instance may override at all.
-
4
Scope the library to the workspace that owns it, and check that scope on insert and on render, not only when listing the picker.
-
5
Do not build a general component system with parameters and slots. A named saved section with a small set of overridable fields covers the real use; anything beyond that is a programming language nobody asked for.
Edge cases it handles
8
Edge cases it handles
8- Linked and detached copies behave completely differently and look identical on the page. Mark every instance and state plainly what editing it will affect.
- Publishing a change to a linked original must not wipe the text an instance overrode locally. Merge per field rather than replacing the instance wholesale.
- Deleting a saved block still used on live pages breaks all of them. Show the usage list, refuse the deletion, and offer to detach every instance instead.
- A saved block containing an instance of itself, directly or through another block, renders forever. Refuse the save that would create the cycle rather than catching it at render time.
- One workspace must never see another's library. A picker filtered correctly but a render path that is not will leak content across tenants.
- Renaming or reorganising the library must not change what a published page renders. Identity lives in a stable identifier, never in the name.
- Editing a linked block changes pages the author may not have open. Report how many places will change and treat the action as a publish rather than an ordinary save.
- A saved block referencing a deleted image or a removed section type must degrade to something renderable rather than blanking the page it sits on.
Definition of done
9
Definition of done
9- Any built section can be saved to the library and inserted elsewhere.
- Each insert is explicitly linked or detached, and its state is visible on the canvas.
- Updating a linked original updates its instances without discarding local overrides.
- Deleting a saved block that is in use is blocked, with a usage list and a detach-all option.
- A saved block cannot be made to contain itself.
- The library is scoped to its workspace on listing, insert, and render.
- Editing a linked block reports how many published places will change before it is applied.
- 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.