Landing Page Builder
Assemble a marketing page from ready-made sections and publish it at its own URL.
What it adds
A section-based editor for public pages, with a separate draft tree, a publish step, and a live address.
What your agent is told to do
5
What your agent is told to do
5-
1
Ship a fixed set of sections the marketing team actually uses: hero, feature row, logo strip, testimonial, pricing, call to action, footer. Each gets configurable content and a couple of layout options. A general-purpose layout engine is a far larger product and should not be attempted here.
-
2
Keep the draft tree and the published tree as separate records. Editing must never change what a visitor sees until publish is pressed.
-
3
Reuse the app's existing Draft and Publish States and Scheduled Publishing rather than inventing a second publishing model that only pages understand.
-
4
Emit per-page title, description, canonical address, and social preview tags through the app's existing SEO Setup, with defaults derived from the page's own first heading and image.
-
5
Do not let a section reference an asset by raw address. Pull images from the app's media storage so the system knows which assets a published page depends on.
Edge cases it handles
8
Edge cases it handles
8- An editor that writes straight to the live page will publish somebody's half-finished paragraph. Hold every change in the draft tree and promote it only on an explicit publish.
- A chosen slug can collide with an existing page or with an application route such as sign-in or admin. Check both when the slug is saved and refuse with a clear reason rather than shadowing a real route.
- A page shared without title, description, and preview image renders as a bare link in chat and search results. Generate defaults from the content and let the author override them.
- Published pages must be cached to survive traffic, and republishing must clear that cache immediately. An author who still sees the old page after publishing will publish again and again.
- An asset deleted from the media library leaves a section pointing at nothing. Render the section without the image rather than a broken frame, and warn the author at deletion time rather than afterwards.
- Changing the slug of a page that has already been shared breaks every existing link. Keep the old path redirecting to the new one.
- Anything at a public address gets indexed and shared. Unpublished and scheduled pages must return not found to a direct visit, not merely be hidden from the page list.
- Sections must reserve their image dimensions so the published page does not jump while photos load, and alt text should be required before publish is allowed.
Definition of done
9
Definition of done
9- Authors build a page from the shipped sections and publish it at its own address without a deploy.
- Draft edits are invisible to visitors until publish.
- Slug collisions and reserved application routes are refused when the slug is saved.
- Every published page emits title, description, canonical, and social preview tags.
- Republishing invalidates the cached page immediately.
- A renamed slug keeps the old path redirecting to the new one.
- A section whose asset was deleted renders without breaking the page.
- 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.