App Store Screenshots
An open-source AI-agent skill that scaffolds a Next.js editor for App Store and Google Play marketing screenshots — device frames, per-locale sets, and one-click store-ready export bundles
app-store-screenshots is an open-source skill for AI coding agents like Claude Code and Cursor that scaffolds a production-ready Next.js editor for your App Store and Google Play marketing screenshots — a connected canvas with real device frames, an inspector for headlines and layout, git-trackable project state, and one-click export bundles at every store-required size. It has 6,043 GitHub stars as of July 2026, is MIT-licensed, and is built in TypeScript. For an app founder it removes a real chore: turning raw screen captures into the polished, benefit-led slides that decide whether a store visitor installs. But it builds the asset; it does not run the listing afterward — the reviews you answer, the metadata you iterate, and the audience you send to the store are where installs are actually won or lost.
What app-store-screenshots is
app-store-screenshots (github.com/ParthJadhav/app-store-screenshots) is an open-source skill for AI coding agents — you install it into a tool like Claude Code, Cursor, Windsurf, or Codex with a single skills-add command. Instead of producing one static mockup, it scaffolds a full Next.js editor: you describe your app and hand it your raw screen captures, and it builds a connected canvas where phones, captions, and decorative elements can span adjacent slides. Every deck saves to a git-trackable project file, so the work is version-controllable and resumable, and export produces exact PNG bundles for all required App Store and Google Play sizes. It is MIT-licensed and built in TypeScript.
- A real editor, not a one-off A connected canvas, a screen sidebar with drag-to-reorder, and an inspector for headlines, layout, and device frames — closer to a design tool than a template.
- Every store format iPhone, iPad, Android phone, Android tablet, and the Play Store feature graphic, each exported at the exact sizes the stores require.
- Localized and RTL-aware Generate per-locale screenshot sets with layout guidance that treats right-to-left languages as native rather than bolted on.
- Git-trackable project state Each deck is saved to a project file you can commit, so screenshots stay reviewable and reproducible like the rest of your code.
Where it fits an app founder's growth stack
For an app, the store listing is the conversion page you do not fully control — and its screenshots are the single biggest lever on it. Most people scan the first two or three images and decide in seconds, so benefit-led slides that show the app's value beat raw UI captures. That is exactly the asset this skill produces, which is why it sits early in an app founder's growth stack, right where traffic turns into installs. Its own README notes that screenshots made with it were accepted for a live App Store app, which is a fair check on whether the output clears the store's bar.
| Listing lever | Why it moves installs | Where this skill helps |
|---|---|---|
| Screenshots | The first images decide most install choices in seconds | Its core job — turns raw captures into benefit-led, store-sized slides. |
| Localization | Localized listings lift installs in non-English markets | Generates per-locale, RTL-aware screenshot sets from one project. |
| Consistency | A coherent visual set reads as a credible, cared-for app | Reusable themes and a shared editor keep every slide on-brand. |
| Iteration | Testing new slides is how you raise a listing's conversion | Git-trackable decks make each version reviewable and repeatable. |
Screenshots are one half of app-store optimization; the other half is the ongoing work of the listing — the reviews, ratings, metadata, and keywords that keep it converting after launch. This skill nails the creative asset, but it does not run that loop for you.
What it doesn't do — and what to pair it with
The skill builds a strong store asset, but a listing is not a growth strategy. Screenshots convert visitors you already brought to the store; they do not create the demand, answer the reviews, or iterate the listing over the months that decide whether an app compounds. That upstream and ongoing work is a different job entirely.
- Builds the screenshots — but the installs still depend on the traffic you drive to the listing and the story those first two slides tell.
- Ships a polished listing — but the reviews and ratings that sit above your screenshots are earned in-product, not in an editor.
- Produces the asset once — but keeping a listing converting means iterating metadata and creative as you learn, closer to an ongoing growth loop than a one-time export.
This is where AgentCeres — the AI Growth Officer at agentceres.com fits alongside a tool like this. AgentCeres is a managed AI marketing team that connects to App Store Connect and Google Play to watch reviews and ratings, draft metadata and reply updates, and run the listing as ongoing work — with a human approving anything that goes out. The skill makes the screenshots; the team helps you drive traffic to the store and keep the listing working after the export. For a related creative tool, see OpenCut for short-form video, and umami for the analytics to see which channels actually send installs.
FAQ
- Is app-store-screenshots free?
- Yes. It is open-source under the MIT license, so you can use and adapt it freely; you install it into an AI coding agent and run it locally, and the screenshots it generates are yours. Check the repository for the current feature set and any external tools it expects.
- Do I need to be a designer to use it?
- No — that is much of the point. You describe your app, its top features, the style you want, and the platforms and locales you need, and the skill guides your coding agent to build the editor and the slides. You still make the taste calls, but you are editing a real project rather than starting from a blank canvas in design software.
- How is this different from a screenshot template in Figma?
- A template gives you a static file you nudge by hand for every size, locale, and update. This skill scaffolds a code project: a connected-canvas editor, exact store-size exports, per-locale sets, and a git-trackable file you can version and regenerate. If you already live in a coding agent, it keeps screenshots in the same reproducible workflow as your app.
- Will good screenshots get my app more installs?
- Better screenshots usually raise store conversion, because the first images are what most visitors judge before installing — but there is no fixed number, and screenshots only convert the traffic you already send to the listing. Treat them as one high-leverage input alongside reviews, ratings, and the channels that bring people to the store in the first place.
You built it. Now grow it.
AgentCeres is a managed AI marketing team — specialists draft the SEO, social, and outreach that fill your links, you approve what ships. 14-day free trial, from $19/month.