App Store Optimization skills for Claude Code, for anyone shipping an iOS app. This repo is a marketplace of two independent plugins — install either one alone, or both together. Neither depends on the other.
| Plugin | What it does | Install |
|---|---|---|
super-aso | The full funnel: keyword research, 50-locale metadata, localized screenshot headings, worldwide pricing, in-app string localization, a verified submission checklist, custom product pages + A/B experiments, an AI-discoverability audit, and continuous rank/review monitoring. Bring your own App Store Connect API key. | /plugin install super-aso@super-aso-marketplace |
aso-appstore-screenshots | Generates the actual screenshot images with AI (Nano Banana Pro): analyzes your codebase, researches real competitors, discovers your core benefits, and produces polished screenshots in a Bold/Agency or Editorial/Organic style. A fork of adamlyttleapps/claude-skill-aso-appstore-screenshots. | /plugin install aso-appstore-screenshots@super-aso-marketplace |
What is a "Claude Code skill"? It's a set of instructions that teaches Claude Code a specific workflow — in this case, everything involved in getting an iOS app ready for the App Store. Once installed, you don't run scripts or memorize commands: you just describe what you want in plain English (or Portuguese, or any language) inside a Claude Code session opened in your app's project folder, and the skill takes it from there, asking you questions along the way.
What is ASO? App Store Optimization — the practice of making your app easier to find (keywords, metadata) and more likely to be downloaded once found (screenshots, description, pricing). It's the App Store equivalent of SEO.
Do I need to code anything? No. You need a Mac (for the fonts/rendering pieces) and Claude Code installed. Some phases need your own free API keys — see No signup, no SaaS below for exactly which ones and why.
I don't have any screenshots yet — where do I even start? Install aso-appstore-screenshots and say "generate App Store screenshots for my app". It works from your app's own codebase, so there's nothing to prepare beforehand.
- You already have screenshot images (from a designer, Figma, or your own
mockups) and just want them localized into 50 languages with translated
headings burned on top, then uploaded — use
super-asoalone. Its screenshots phase expects background PNGs you already have. - You don't have screenshot images yet and want AI to design them from
your app's actual codebase and competitor research — use
aso-appstore-screenshotsfirst to generate the English originals, then feed those intosuper-aso's screenshots phase to localize and upload them. - You want the whole thing — keywords, metadata, pricing, submission, monitoring, and AI-generated screenshots — install both. They don't conflict; nothing in either plugin assumes the other is installed.
Register the marketplace once:
/plugin marketplace add deckameron/Super-ASO
Then install whichever plugin(s) you want:
/plugin install super-aso@super-aso-marketplace
/plugin install aso-appstore-screenshots@super-aso-marketplace
If an install summary says Run /reload-plugins to activate., run that (or
restart Claude Code). Each plugin also supports a manual clone install if you
don't want to use the plugin marketplace — see that plugin's own README.
Open Claude Code in your app's repo and just say what you want — each skill loads itself from its own description, so you don't need to remember exact names:
do the ASO for my app
generate App Store screenshots for my app
These are shortened, illustrative transcripts — the real conversation asks more follow-up questions and shows more detail, but this is the shape of it.
Generating screenshots with aso-appstore-screenshots (click to expand)
You: generate App Store screenshots for my app
Claude: I'll start by looking at your codebase to find the core benefits
worth leading with. Give me a moment...
[reads your source files]
I found 4 candidate benefits based on what your app actually does:
1. Track your collection's value in real time
2. Scan cards instantly with your camera
3. Get alerts when prices spike
4. Compare prices across marketplaces
Do these look right, or is there a stronger benefit I'm missing?
You: looks right, maybe drop #4, nobody asked for that
Claude: Got it, dropping #4 — down to 3 confirmed benefits.
Now, competitive research: who are 2-5 real competitors I should
look at? A name or App Store link is enough for each.
You: CardWatch, PriceHawk
Claude: [looks both up via Apple's free iTunes API, downloads their current
screenshots into competitors/]
Both lean hard into bold centered text on solid color — that look is
everywhere in this category now. I'd recommend the Editorial/Organic
style instead so yours doesn't blend in. Full write-up saved.
That's competitor research done — you have a `competitors/` folder
and a written analysis, useful on its own even if you stop here.
Next is pairing your screenshots and generating the images, which
needs a Gemini API key. Want to continue, or stop here for now?
You: continue
Claude: [reviews your simulator screenshots, pairs each with a benefit,
generates 3 versions per benefit with Nano Banana Pro, crops each
to exact App Store dimensions, and builds a showcase preview]
Running the full funnel with super-aso (click to expand)
You: do the ASO for my app
Claude: First time running this — I'll walk you through connecting your App
Store Connect API key (free, from your Apple Developer account).
Have your key file, key ID, and issuer ID ready?
You: yes
Claude: [walks through the setup wizard, saves config to ~/.super-aso/]
Setup done. Where do you want to start — keyword research, metadata,
screenshots, pricing, submission checklist, or all of it in order?
You: keyword research first
Claude: [researches keyword popularity/difficulty, proposes a name,
subtitle, and keyword field, shows you the reasoning behind each]
Here's what I'd set: title "CardWatch — Price Tracker", subtitle
"Track, Scan & Compare Prices". Want any changes before I show you
the full 50-locale metadata plan?
You: looks good, keep going
Claude: [builds a diff table across all 50 locales before writing anything,
asks for explicit go-ahead, then writes via App Store Connect]
See each plugin's own README for the full phase list, setup requirements, and what each phase needs from you:
Both plugins run entirely from your own Claude Code session plus your own API keys — nothing is sent to a third-party service beyond Apple's own App Store Connect API and Google's Gemini API.
| Key | Needed for | Cost | Where to get it |
|---|---|---|---|
| App Store Connect API key | super-aso — metadata, pricing, screenshots upload, monitoring | Free (Apple Developer account) | App Store Connect → Users and Access → Integrations |
| Gemini API key | aso-appstore-screenshots — only the AI image-enhancement step | Free tier available | Google AI Studio |
Nothing else is required. You don't need either key just to explore what a
plugin does — aso-appstore-screenshots's Benefit Discovery and Competitive
Research phases, for example, run with no key at all (see that plugin's
README for details).
super-aso/ # this repo (marketplace root)
.claude-plugin/marketplace.json # lists both plugins below
super-aso/ # plugin 1 — full-funnel ASO
.claude-plugin/plugin.json
skills/super-aso/
aso-appstore-screenshots/ # plugin 2 — AI screenshot generation
.claude-plugin/plugin.json
skills/aso-appstore-screenshots/
Each plugin ships its own LICENSE (both MIT). aso-appstore-screenshots
is a fork — see its LICENSE for the original copyright holder.