Email Editor
Build a formatted email from blocks and send it or keep it as a template.
What it adds
A block-based email composer plus the exported markup and plain-text alternative it sends as.
What your agent is told to do
5
What your agent is told to do
5-
1
Ship the small set of blocks a real email needs: text, image, button, divider, spacer, and a two-column row. Build those properly rather than a general layout engine.
-
2
Extend the app's existing Rich Text Editor for text blocks instead of adding a second editing surface with its own toolbar and its own paste handling.
-
3
Export to table-based markup with every style written inline. Modern layout techniques that look right in the preview are stripped or ignored by desktop mail clients and the email arrives unstyled.
-
4
Send through the app's existing transactional email path, with its sender identity, unsubscribe handling, and delivery logging. Do not open a second send route from the editor.
-
5
Generate the plain-text version from the block tree at export and let the author review it, rather than sending an empty alternative or a dump of the markup.
Edge cases it handles
8
Edge cases it handles
8- Older desktop clients ignore modern layout entirely. Export nested tables with fixed pixel widths and confirm a three-block email survives a client that honours none of the preview's styling.
- Styles declared in a head block are discarded by several clients. Inline every declaration at export and drop the ones no client honours rather than shipping markup that only renders in your own preview.
- An email with no plain-text alternative scores badly with spam filters and is unreadable in text-only clients. Build one from the block tree, keeping link destinations visible in the text.
- Images referenced by a relative or session-scoped address arrive as broken boxes. Rewrite every asset to an absolute, publicly readable, long-lived address at export, and cap the total image weight.
- Clients that force dark mode invert light backgrounds and can leave dark text sitting on a dark panel. Check the colour pairs before send and warn on the ones that will vanish.
- Many recipients block images by default. Every image needs alt text, and an email whose entire content is one large image arrives blank.
- A half-finished campaign must not be lost to a closed tab. Autosave the draft and reuse the app's existing unsaved-changes warning on navigation away.
- Sending is irreversible. Require a confirmation that names the recipient list and its size, and offer a test send to the author first.
Definition of done
9
Definition of done
9- Authors assemble an email from text, image, button, divider, and column blocks and save it as a template.
- Exported markup is table-based with inline styles and renders in older desktop clients.
- Every send carries a plain-text alternative generated from the same content.
- Image assets are rewritten to absolute hosted addresses and total weight is capped.
- Colour pairs that invert badly in dark mode are flagged before send.
- Sending uses the app's existing transactional email path and unsubscribe handling.
- Drafts autosave and a test send is available before the real one.
- 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.