Heroshot
…
Claude integration

Connect Claude.

Store screenshots are three chores in a trench coat: capturing clean shots, designing them, and fighting App Store Connect's upload form. Connect Heroshot to Claude and you only have to do the middle one — the fun one.

  1. 01

    Capture

    Claude does it

    Claude drives your simulator, sets the status bar to 9:41 with full battery and signal the way Apple's own marketing shots do, and grabs each screen at its native resolution.

  2. 02

    Design

    You do it

    The project lands in the Heroshot editor with your screenshots already in the slots. Pick a template, colours and copy — this part stays yours, because taste isn't automatable.

  3. 03

    Ship

    Claude does it

    Hit Publish for release, then ask Claude to ship it. Screenshots and listing copy go straight to App Store Connect. It shows you the plan first, and it never submits your app for review.

Setting it up

Two steps. First create a personal access token in your workspace — it's shown once and lets Claude work on your account. Then point Claude at Heroshot with whichever of these matches how you work.

Create a token
  1. 1

    Add the marketplace and install the plugin

    Type these in Claude Code, one after the other.

    /plugin marketplace add popyapp/heroshot-plugin
/plugin install heroshot@popy
  2. 2

    Put your token in your shell profile

    The plugin reads HEROSHOT_TOKEN from the environment, so it has to be set before Claude Code starts — not inside a session.

    echo 'export HEROSHOT_TOKEN=hsk_your_token_here' >> ~/.zshrc
source ~/.zshrc
  3. 3

    Restart Claude Code

    You'll get the Heroshot tools plus two commands: /heroshot:capture to grab clean simulator screenshots, and /heroshot:ship to push a finished release to App Store Connect.

Create a token above and these snippets fill themselves in.

Then just ask

“Make App Store screenshots for my app.”

Claude captures the screens from your simulator, creates a Heroshot project and hands you a link. You pick the template, colours and copy in the editor, then hit Publish for release. Back in Claude, /heroshot:ship uploads the finished set to App Store Connect — it shows you the plan first, and it never submits your app for review.

What we can and can't see

The App Store Connect push runs on your machine, not on our servers. Your Apple API key (the .p8) never touches Heroshot — we don't ask for it, don't store it, and couldn't use it if we wanted to.

It works the other way too: the push script never sees your Heroshot token. It gets a signed, one-hour download link for the screenshots you approved, and that's all it needs.

Your Heroshot token is stored only as a SHA-256 hash, so we can't show it to you twice — lost tokens get revoked and replaced, never recovered.

What you'll need

  • A paid Heroshot plan to publish a release — the free tier watermarks its render, and a watermark has no business on a store listing.
  • Claude Code for the capture and push steps, since both run locally. On claude.ai the connector can still create projects and read your release history.
  • An App Store Connect API key with the Admin or App Manager role, from Users and Access → Integrations. Apple lets you download it once.
  • Xcode's command line tools for iOS capture (xcrun simctl), or the Android SDK platform tools (adb).

Ready?

Create a token, paste two commands, and ask Claude for App Store screenshots.

Create a tokenSee pricing