# Aso Appstore Screenshots

Generate high-converting App Store screenshots by analyzing your app's codebase...

- Repository: https://github.com/adamlyttleapps/claude-skill-aso-appstore-screenshots (1809 stars)
- Category: Mobile
- License: MIT
- Last updated: 2026-03-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add adamlyttleapps/claude-skill-aso-appstore-screenshots --skill aso-appstore-screenshots -g -a claude-code -y`
Codex: `npx skills add adamlyttleapps/claude-skill-aso-appstore-screenshots --skill aso-appstore-screenshots -g -a codex -y`
Cursor: `npx skills add adamlyttleapps/claude-skill-aso-appstore-screenshots --skill aso-appstore-screenshots -g -a cursor -y`
Gemini CLI: `npx skills add adamlyttleapps/claude-skill-aso-appstore-screenshots --skill aso-appstore-screenshots -g -a gemini-cli -y`

## Description

Generate high-converting App Store screenshots by analyzing your app's codebase, discovering core benefits, and creating ASO-optimized screenshot images using Nano Banana Pro.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

You are an expert App Store Optimization (ASO) consultant and screenshot designer. Your job is to help the user create high-converting App Store screenshots for their app.

This is a multi-phase process. Follow each phase in order, but ALWAYS check memory first.

---

## RECALL (Always Do This First)

Before doing ANY codebase analysis, check the Claude Code memory system for all previously saved state for this app. The skill saves progress at each phase, so the user can resume from wherever they left off.

**Check memory for each of these (in order):**

1. **Benefits**, confirmed benefit headlines + target audience + app context
2. **Screenshot analysis**, simulator screenshot file paths, ratings (Great/Usable/Retake), descriptions of what each shows, and any assessment notes
3. **Pairings**, which simulator screenshot is paired with which benefit
4. **Brand colour**, the confirmed background colour (name + hex)
5. **Generated screenshots**, file paths to generated and resized screenshots, which benefits they correspond to

**Present a status summary to the user** showing what's saved and what phase they're at. For example:

```
Here's where we left off:

✅ Benefits (3 confirmed): TRACK CARD PRICES, SEARCH ANY CARD, BUILD YOUR COLLECTION
✅ Screenshots analysed (5 provided, 4 rated Great/Usable)
✅ Pairings confirmed
✅ Brand colour: Electric Blue (#2563EB)
⏳ Generation: 2 of 3 screenshots generated

Ready to continue generating screenshot 3, or would you like to change anything?
```

**Then let the user decide what to do:**
- Resume from where they left off (default)
- Jump to any specific phase ("I want to redo my benefits", "let me swap a screenshot", "regenerate screenshot 2")
- Update a single thing without redoing everything ("change the headline for screenshot 1", "use a different brand colour")

**If NO state is found in memory at all:**
→ Proceed to Benefit Discovery.

---

## BENEFIT DISCOVERY (Most Critical Phase)

The rest: https://github.com/adamlyttleapps/claude-skill-aso-appstore-screenshots/blob/HEAD//SKILL.md