A press kit page writers can use in two minutes

Paste into any coding agent: Claude Code, Cursor, Codex, Copilot, Windsurf or Cline.

# A press kit page writers can use in two minutes

Writers, newsletter authors and launch sites covering the production site need the facts and assets fast, and they use whatever they find first. Build a press kit page that gives them accurate copy, logos and screenshots in two minutes, from one data source.

Site: not given. Find the production URL in the project config, or ask me.

## Ground rules

1. Read before you write. Explore the parts of the codebase this job touches and tell me what is already in place.
2. Plan, then stop. Give me a numbered plan: what you will change, in which files, and why. Wait for my approval before editing anything.
3. Fix things at their source (the shared layout, the config, the generator), not with one-off patches page by page.
4. Keep the project's conventions: its framework APIs, file layout, naming and code style. Add no new dependency without asking.
5. Where something is already done well, say so and leave it alone.

## You will not

- Edit `.env` files, secrets or API keys, or print their values.
- Deploy, push, merge or publish anything.
- Delete data, or run migrations or scripts against a production database.
- Add tracking, third-party scripts or links to any site I did not ask for.
- Change copy, design or behaviour that this job does not need.
- Invent coverage, numbers or quotes.

## Your stack

- Framework: Work out the framework, router and build output from the project files (package.json, lockfiles, framework config) before planning, and say which you found.
- Host: Work out where the site is hosted from the config files (vercel.json, netlify.toml, wrangler config, Dockerfile, fly.toml) and say which you found.

## Steps

### 1. Gather the facts

From the site, the about page and the code, collect: the company and product name, a one-line, a 50-word and a 150-word description, founding year, location, founders with roles and photos, key numbers I approve, and a press contact. Ask me for what is missing; never invent numbers.

### 2. Assets

Provide logos (SVG and PNG, light and dark versions), an app icon, and three to six product screenshots at full resolution, each downloadable individually and as a zip if the stack makes that easy. Give each a descriptive filename and alt text.

### 3. The page

A `/press` page with the boilerplates in copyable blocks, the facts as a short list, founders with photos and links, the assets with download buttons, brand colors, recent coverage if any, and the press contact. Link it from the footer.

### 4. Keep it in sync

Read names, descriptions and facts from the same constants the about page and structured data use, so the press kit cannot drift from the rest of the site.

## Done means

- [ ] A /press page has boilerplates in three lengths, key facts and a press contact.
- [ ] Logos, icon and screenshots download individually at full resolution.
- [ ] Facts come from the same source as the about page and structured data.
- [ ] The footer links the press page.

## Report back

When you finish, give me:

- what you changed, file by file;
- anything you skipped, and why;
- anything I must do by hand (DNS records, dashboards, accounts, deploys);
- how to check each change on the live site.