Help Center
Give customers a searchable help site they can read before they open a support ticket.
What it adds
A public help site of articles grouped into collections, with search, browse, and a contact fallback.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Ship the minimum coherent version: title, body, collection, slug, published state, and a last-updated date. Defer translations, approval workflows, and article versioning rather than half-building them.
-
5
Do not build a second content editor for this. Reuse the app's existing rich text or markdown editing surface, including its autosave and unsaved-change warnings.
Edge cases it handles
8
Edge cases it handles
8- A collection with no published articles must not render as a dead-end page. Either hide the collection from navigation or show what is coming and a route to contact support.
- Moving an article to a different collection changes its URL. Keep the old path working with a permanent redirect, because that link is already in support emails and search results.
- A search that returns nothing is the moment a customer gives up. Show the zero-result state with the most-read articles and a direct way to contact support.
- Was-this-helpful votes must be rate limited per visitor and per article, or one frustrated person refreshing will bury an article that is actually fine.
- Draft and unpublished articles must be unreachable by direct URL for anyone without authoring permission, and must be excluded from the search index and the sitemap.
- Articles referencing screens or plans the visitor cannot access should still render, but must not imply a feature is available to everyone.
- Images and embedded video inside an article need reserved dimensions and alt text, so a long article does not reflow while it loads.
- A deleted article that still has inbound links needs a real page explaining it has been removed, with a search box, not a bare 404.
Definition of done
9
Definition of done
9- Articles are grouped into collections and reachable by browsing and by search.
- Help articles appear in the app's existing search index rather than a parallel one.
- Draft articles return not-found for unauthorised visitors and never appear in search or the sitemap.
- Renamed or moved articles redirect from their previous URLs.
- Zero-result searches offer popular articles and a contact route.
- Helpfulness votes are rate limited and cannot be submitted repeatedly by one visitor.
- Every article shows a last-updated date.
- 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
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
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
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.