Link in Bio Page
Give each user one shareable mobile page of links behind a handle they choose.
What it adds
A public single-page list of a user's links, served from a chosen handle and editable without a deploy.
What your agent is told to do
5
What your agent is told to do
5-
1
Reuse whatever handle or username the app already assigns for public profile pages instead of introducing a second namespace. Two independent handle systems will eventually collide on the same path.
-
2
Reserve system paths and obvious impersonation risks before opening handle selection, and check the reserved list on every rename rather than only on creation.
-
3
Design for a phone first and for slow connections. The page must render its links from the server with no client-side data fetch, because it will be opened inside social app browsers that block or delay scripts.
-
4
Reuse the app's existing scheduled publishing behaviour for links that should appear or expire on a date, rather than writing a second scheduler for this one page.
-
5
Do not build a general-purpose page builder here. Ship a heading, an avatar, an ordered list of link tiles, and a small set of theme choices, and defer arbitrary blocks and custom layout.
Edge cases it handles
8
Edge cases it handles
8- Handles need a reserved word list covering system routes, support and admin names, and anything that reads as official. Freeing a handle after an account is deleted invites squatting on a name people already trust, so hold it for a period before release.
- Scheduled links must appear and disappear on time in the visitor's experience even if the page is cached, which means the cache key or the render has to account for the schedule boundary.
- Click counts are inflated by social platform link previewers fetching every URL on the page. Filter known preview and bot traffic before counting, and never present raw hits as human clicks.
- In-app browsers strip styles, ignore some navigation, and sometimes block outbound links. Keep the layout functional with no custom styling applied and make every tile a plain link that works without interception.
- A deleted or unreachable destination leaves a broken tile on a live page. Check destinations periodically and flag or hide dead links for the owner rather than silently serving them.
- The page is public and user-generated, so it will be used for spam and phishing. Run new and edited destinations through the app's existing content reporting and moderation path, and give visitors a way to report a page.
- The avatar and any tile images need reserved dimensions and alt text, or the list will jump under a thumb already reaching for the first link.
- Renaming a handle breaks every share of the old one. Redirect the previous handle to the new one for a period and tell the owner that is happening.
Definition of done
9
Definition of done
9- Each page is served from a unique handle validated against a reserved word list on create and on rename.
- The page renders fully from the server and remains usable with scripts and custom styles blocked.
- Scheduled links appear and expire at their configured times even on a cached page.
- Click counts exclude known previewer and bot traffic.
- Links to unreachable destinations are detected and reported to the owner.
- Visitors can report a page, and reports land in the existing moderation path.
- A renamed handle redirects from its previous value.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Newsletter Archive
Newsletter Archive
Turn sent email issues into browsable web pages that new readers can find and read.
What it does
A public archive of past newsletter issues, each with its own permanent page and a subscribe path.
How it works
- 1 Store the sent version of each issue rather than regenerating it. An archive built by re-rendering a template will drift the moment the template changes, and old issues will stop matching what subscribers actually received.
- 2 Convert the email markup to web markup on the way in: strip the table scaffolding, the fixed pixel widths, and the inline styles that only exist to survive an email client, and render the result in the app's normal article styles.
- 3 Reuse the app's existing publishing states rather than adding a second one. An issue should move from sent to archived through the same Draft and Publish States machinery the rest of the content uses.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/newsletter-archive
Help Center
Help Center
Give customers a searchable help site they can read before they open a support ticket.
What it does
A public help site of articles grouped into collections, with search, browse, and a contact fallback.
How it works
- 1 Treat the article as the single source of help content. If the app already has Contextual Help, Knowledge Base Chat, or an AI knowledge base drafting flow, point them at these same records rather than keeping a second copy of the answers that will drift.
- 2 Index articles into the app's existing search rather than standing up a separate search box with its own ranking. Extend Global Search and reuse the existing match highlighting so a result looks the same wherever it appears.
- 3 Give every article a stable slug and every collection an ordered list of articles, and show breadcrumbs from the collection down to the article so a visitor who landed from search knows where they are.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/help-center
Blog
Blog
Publish articles from inside the app to public pages with authors and categories.
What it does
A blog with authored posts, categories, scheduling, and public article and index pages.
How it works
- 1 Scope this honestly. The minimum coherent version is a post with a title, body, author, category, publish state, and a public page at a stable URL, plus an index and a feed. Defer multi-language content, per-post custom layouts, and a general page builder rather than half-building them.
- 2 Do not build a new editor. Extend the app's existing Rich Text Editor or Markdown Editor with whatever a post needs, and inherit its autosave, unsaved-change warning, and undo instead of reinventing them.
- 3 Reuse the app's existing Draft and Publish States and Scheduled Publishing rather than adding a second publish workflow for posts. Reuse SEO Setup for titles, descriptions, and social previews.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/blog
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.