Press Kit
Give journalists your logos, colours, screenshots, and boilerplate on one public page.
What it adds
A public page of downloadable brand assets, colour values, screenshots, and approved boilerplate copy.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Publish the usage rules as text on the page and include them as a file inside every archive, so the rules travel with the assets rather than staying behind on a page nobody bookmarked.
-
5
Do not build the archive on demand in the web request. Generate it in the background when assets change and serve the stored file, because zipping a large asset set inline will time out.
Edge cases it handles
8
Edge cases it handles
8- A bulk download of a large asset archive built during the request will time out or die behind a proxy. Prepare the archive ahead of time and serve it as a static file with a resumable download.
- Light and dark logo variants look broken on the wrong background. Render each on its intended background, label which is which, and never let the page theme swap one for the other silently.
- Superseded assets stay linked from press coverage published years ago. Keep the old URL alive but serve a page explaining the asset is retired and pointing at the current one, rather than deleting the file.
- Vector and raster files served with the wrong extension or content type download as something the recipient cannot open. Match the extension, the stored media type, and the response headers.
- Usage rules that only appear on the page get separated from the files immediately. Include them in the archive and reference them next to every individual download.
- Colour values need to be copyable as text in more than one notation, because a journalist and a designer want different formats.
- Screenshots go stale faster than logos. Show when each asset was last updated so nobody ships a picture of a two-year-old interface.
- The page is public and links to real files, so it will be scraped. Rate limit the archive download and keep individual asset requests cheap.
Definition of done
9
Definition of done
9- Every asset downloads with a filename, extension, and content type derived from its stored record.
- The full archive is pre-generated and served as a stored file rather than built during the request.
- Light and dark logo variants each render on an appropriate background and are labelled.
- Usage rules appear on the page and are included inside every archive.
- Retired assets keep their URLs and resolve to a page pointing at the current version.
- Colour values can be copied in more than one notation.
- Each asset shows when it was last updated.
- 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
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
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.