AddThisFeature
Sign in

Press Kit

Give journalists your logos, colours, screenshots, and boilerplate on one public page.

moderate Content & Publishing

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
  1. 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. 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. 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. 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. 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
  • 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
  • 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

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 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.