Block Editor
Edit long-form content as a stack of blocks you can reorder, nest, and mix with embeds.
What it adds
A typed-block editing surface for the app's long-form content, backed by a versioned block tree.
What your agent is told to do
5
What your agent is told to do
5-
1
Define the block types the content actually needs: paragraph, heading, list, image, quote, code, divider, embed. Give each a stable stored shape and ship those, rather than an open-ended block system in the hope that types get added later.
-
2
Extend the app's existing Rich Text Editor for inline formatting inside a block rather than running two editing engines side by side. The block editor owns the structure; the existing editor owns the text.
-
3
Reuse the app's existing Autosave, Version History, and Undo Actions. A second history stack that only covers this editor will disagree with the record's real history.
-
4
Convert pasted content into known block types on the way in. Storing pasted markup verbatim means storing whatever the source page happened to contain, scripts included.
-
5
Reuse Drag-and-Drop Reordering for moving blocks, and make sure every reorder is also reachable from the keyboard.
Edge cases it handles
8
Edge cases it handles
8- Content written today must still open after the block types change. Store a version on the tree, migrate forward on read, and keep unrecognised blocks intact rather than dropping them.
- Pasted markup from a document or another site carries styles, scripts, and tracked-change annotations. Map what you recognise onto real block types and discard the rest.
- Splitting a paragraph with Enter and merging it back with Backspace must leave the caret exactly where the writer expects. A caret that jumps to the top of the document on every merge makes the editor unusable.
- Dragging to reorder on a touch screen competes with scrolling. Require a deliberate long press or a dedicated handle so a scroll gesture never moves a block.
- A crashed or reloaded tab must not cost an hour of writing. Keep a local copy of unsaved blocks and offer to restore it, clearly distinguished from the saved version.
- Images inside blocks must reserve their dimensions so the document does not reflow under the writer's cursor while they load, and each needs alt text.
- An embed block renders somebody else's page. Show the source link and a readable fallback for when the third party is blocked, deleted, or down.
- Two people opening the same document must not silently overwrite each other. Detect that the stored version has moved and say so rather than saving on top of it.
Definition of done
9
Definition of done
9- Content is stored as a versioned tree of typed blocks that survives schema changes.
- Blocks can be added, reordered, nested, and deleted with both pointer and keyboard.
- Pasted content becomes known block types and no raw markup is stored.
- The caret stays where the writer expects across block splits and merges.
- Touch drag moves blocks only on a deliberate gesture and never blocks page scroll.
- Unsaved work is recoverable after a crashed or reloaded tab.
- Autosave, undo, and version history come from the app's existing implementations.
- 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.