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
Reading Progress Bar
Reading Progress Bar
A slim bar showing how far through an article the reader has scrolled.
What it does
A thin progress indicator pinned to the top of article pages, tracking scroll through the body text.
How it works
- 1 Measure progress against the article body element only. Take the top and bottom of the prose, not the height of the document.
- 2 Recalculate the body height when the page reflows: late-loading images, expanded sections, embeds, and font swaps all change the total after first paint.
- 3 Reuse the app's existing Progress Indicator System tokens for the bar's colour and height rather than introducing a new accent, and keep it visually distinct from Route Change Progress so the two are not confused.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/reading-progress-bar
Press Kit
Press Kit
Give journalists your logos, colours, screenshots, and boilerplate on one public page.
What it does
A public page of downloadable brand assets, colour values, screenshots, and approved boilerplate copy.
How it works
- 1 Serve every asset through the app's existing file download path so that access, headers, and content types are handled the same way as everywhere else, rather than linking directly at raw storage.
- 2 Store the correct format and media type per asset and derive the filename and extension from the stored record, never from the label an author typed.
- 3 Present each logo variant on the background it is designed for, and reuse the app's theme-aware asset switching so the page shows the right variant in light and dark rather than a washed-out logo on the wrong panel.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/press-kit
FAQ Section
FAQ Section
Add an expandable list of questions and answers to any page, in the order you choose.
What it does
A reorderable set of question and answer pairs rendered as an accessible expand-collapse list on any page.
How it works
- 1 Build it on real disclosure semantics with a button that toggles its own panel, so keyboard and screen reader users get the behaviour for free.
- 2 Give every question a stable anchor derived from its text and keep it after edits, so a support reply can link straight to one answer.
- 3 Allow answers to contain formatted text, lists, and links, and reuse the app's existing content editor and its sanitisation rules rather than accepting raw markup.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/faq-section
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.