App Store Screenshots icon

App Store Screenshots

App Store Screenshots is an open-source skill for coding agents that generates localized App Store and Google Play screenshot assets from an app description and source screenshots. It helps developers create, edit, and export store-ready layouts across Apple and Android formats.

App Store Screenshots

AI-assisted app store screenshot generation

App Store Screenshots is an open-source skill for Claude Code, Codex, Cursor, Windsurf, OpenCode, and other agents that support skills. It generates App Store and Google Play screenshot sets from a description of an app, its features, target devices, languages, visual direction, and desired slide count.

The workflow runs locally: install the skill, answer the agent’s questions, refine the generated layouts in a connected editor, and export store assets. It is intended for developers who need platform-specific, localized promotional screenshots without manually preparing every required size and language.

Key features

Agent-guided screenshot generation

Describe the app, features, target devices, languages, visual direction, and slide count in an agent conversation instead of manually assembling each screen.

Multi-platform store coverage

Create store assets for iPhone, iPad, Mac, Apple Watch, Apple TV, CarPlay, Android phones and tablets, plus the Google Play feature graphic and App Store creative assets.

Localized screenshot sets

Generate screenshot sets in every requested language, with the example workflow showing English, Japanese, German, French, and Spanish output.

Local editing workflow

Adjust headlines, screenshots, and layouts in a local editor after generation, or ask the coding agent to make revisions.

18 visual styles and copy formulas

Choose from 18 curated visual styles, including editorial, playful, minimal, colorful, calm, and other style directions, with headline formulas for slide copy.

Project-based saved configuration

Save the set in `app-store-screenshots.json` alongside the app screenshots so the work can be committed and restored on another machine.

Practical use cases

  • Preparing a new app launch

    A developer can describe an app once, supply simulator or device screenshots, and generate a coordinated set for the store formats required by an iOS or Android launch.

  • Localizing store listings

    Teams releasing in multiple markets can request several languages and export localized screenshot sets rather than rebuilding each deck manually.

  • Creating a consistent visual presentation

    An app maker can start with one of 18 styles and use the included headline formulas to establish a consistent visual and messaging direction for the screenshot sequence.

  • Refining an existing screenshot set

    After generation, developers can use the local editor to replace screenshots, revise headlines, or adjust layouts before exporting the final assets.

  • Keeping screenshot work with the codebase

    Projects that need to be resumed or moved between machines can commit `app-store-screenshots.json` together with the screenshots and restore the set in the project.

Pros and Cons

Pros

  • Supports multiple coding agents, including Claude Code, Codex, Cursor, Windsurf, and OpenCode.
  • Covers a broad range of Apple and Android device formats and Google Play assets.
  • Provides localized output and 18 curated visual styles with headline copy guidance.
  • Allows local post-generation editing and stores configuration in the project for reuse.

Cons

  • The available evidence does not describe advanced collaboration controls, hosted storage, or workflow constraints beyond the local setup requirements.
  • The tool requires Node.js 18 or newer, a package manager, and source screenshots from a simulator, emulator, or device.

FAQ

What is needed to set up App Store Screenshots?

Install Node.js 18 or newer and use a package manager such as bun, pnpm, yarn, or npm. Add the skill with `npx skills add ParthJadhav/app-store-screenshots`, then provide your app details and screenshots from a simulator, emulator, or device.

Which coding agents are supported?

It works with Claude Code, Codex, Cursor, Windsurf, OpenCode, and other agents that support skills.

How does the screenshot workflow work?

The agent asks about the app, key features, target devices and languages, visual direction, and slide count, then generates a screenshot set that can be adjusted in the local editor.

Can I edit the generated screenshots?

Yes. The local editor lets you change headlines, screenshots, and layouts yourself, or ask your agent to make changes.

What does the product export?

Exports are opaque PNGs at the exact sizes requested by App Store Connect and Google Play. Supported outputs include screenshots for Apple and Android devices, the Google Play feature graphic, and App Store creative assets.

Quick Facts

Category
Developer Tool; Design Tool
License
Open source under the MIT license
Setup
Node.js 18+ and bun, pnpm, yarn, or npm
Install command
npx skills add ParthJadhav/app-store-screenshots
Supported agents
Claude Code, Codex, Cursor, Windsurf, OpenCode, and other skills-compatible agents
Output
Opaque PNGs for App Store Connect and Google Play sizes

Alternative a App Store Screenshots