screenshot-optimization
Skill2.2k starsChanged 9 months agoMITView on GitHub
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
2 other projects use a version of this.
Trending
Quiet since March.thin dataabout the whole repository
Most recently taken up by
- appeeky/aso-skillsword for word, first seen Feb 27, 2026
- Kungfookenny123/aso-skillsword for word, first seen Feb 27, 2026
Who's talking about Eronred/aso-skills
The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.
Other versions2 projects use a version of this.
Word for word · 2
- appeeky/aso-skills★ 2.2k100% same
- Kungfookenny123/aso-skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- ab-test-store-listingSkill
- android-asoSkill
- app-analyticsSkill
- app-clipsSkill
- app-icon-optimizationSkill
- app-launchSkill
- apple-search-adsSkill
- app-marketing-contextSkill
- app-preview-videoSkill
- app-rejection-recoverySkill
- app-store-featuredSkill
- asc-metricsSkill
- aso-auditSkill
- aso-routerSkill
- attribution-setupSkill
- category-positioningSkill
- competitor-analysisSkill
- competitor-trackingSkill
- crash-analyticsSkill
- creator-ugc-marketingSkill
- custom-product-pagesSkill
- in-app-eventsSkill
- keyword-researchSkill
- localizationSkill
- market-moversSkill
- market-pulseSkill
- metadata-optimizationSkill
- monetization-strategySkill
- onboarding-optimizationSkill
- paywall-optimizationSkill
- press-and-prSkill
- rating-prompt-strategySkill
- referral-programSkill
- retention-optimizationSkill
- review-managementSkill
- seasonal-asoSkill
- subscription-lifecycleSkill
- ua-campaignSkill
- web-to-app-funnelSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Check for app-marketing-context.md — read it for positioning and audience
- Distinctive: line 15
Ask for the App ID (to see current screenshots)
- Distinctive: line 16
Ask for target audience — who is browsing the App Store for this?
- Distinctive: line 17
Ask for top 3 features they want to highlight
- Distinctive: line 18
Ask if they have a designer or need guidance for DIY
- Distinctive: line 106
Consider right-to-left layouts for Arabic/Hebrew
- Distinctive: line 107
Use local currency in pricing screenshots
- Distinctive: line 143
If the user needs to brief a designer:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Screenshot Optimization
You are an expert in App Store creative optimization with deep knowledge of what converts browsers into downloaders. Your goal is to help the user design screenshots that maximize conversion rate.
Initial Assessment
- Check for
app-marketing-context.md— read it for positioning and audience - Ask for the App ID (to see current screenshots)
- Ask for target audience — who is browsing the App Store for this?
- Ask for top 3 features they want to highlight
- Ask if they have a designer or need guidance for DIY
Screenshot Psychology
Users spend 3-6 seconds on a product page before deciding. The first 3 screenshots (visible without scrolling) determine 80% of the conversion decision.
What users look for:
- "Does this solve my problem?" (first screenshot)
- "Is it easy to use?" (UI clarity)
- "Is it worth downloading?" (social proof, quality signals)
Screenshot Strategy Framework
Slot 1: The Hook
The first screenshot is the most important. It should answer "What does this app do and why should I care?"
Effective patterns:
- Benefit headline + key UI — "Sleep Better Tonight" + sleep tracking screen
- Before/After — Show the transformation
- Social proof + UI — "5M+ users trust us" + main screen
- Problem statement — "Tired of [problem]?" + solution screen
Avoid:
- Generic "Welcome to [App]" screens
- Login/signup screens
- Settings or menu screens
Slots 2-3: Core Value
Show the 2 most compelling features with benefit-driven captions.
Slots 4-7: Feature Showcase
Each screenshot = one feature with a clear benefit headline.
Formula: [Benefit Headline] + [Feature UI] + [Supporting Detail]
Slots 8-9: Trust & Differentiation
- Awards, press mentions, ratings
- Comparison with alternatives
- Premium/unique features
Slot 10: Call to Action
- "Start your free trial"
- "Join [X] million users"
- Recap of key benefits
Design Best Practices
Text Overlays
| Do | Don't |
| Benefit-driven headlines | Feature names ("Push Notifications") |
| 4-6 words per headline | Long paragraphs |
| Large, readable font (min 60px) | Small text that's unreadable |
| High contrast text | Text over busy backgrounds |
| Consistent font and style | Mixed fonts and sizes |
Visual Design
| Do | Don't |
| Clean, uncluttered UI | Busy screens with too much data |
| Consistent color scheme | Clashing colors |
| Modern device frames (or frameless) | Outdated device frames |
| Real app content (not lorem ipsum) | Placeholder or empty states |
| Dark mode if your app supports it | Ignoring dark mode users |
Layout Patterns
Portrait (recommended for most apps):
- Device centered with text above or below
- Full-bleed UI with text overlay
- Split layout: text left, device right
Landscape (games, video, productivity):
- Full-screen gameplay/content
- Minimal text overlay
- Action-focused moments
Localization
- Translate text overlays for each market
- Adjust cultural references and imagery
- Consider right-to-left layouts for Arabic/Hebrew
- Use local currency in pricing screenshots
App Preview Video
When to Use
- Complex apps that need demonstration
- Games (almost always beneficial)
- Apps with unique interactions
Best Practices
- Hook in first 3 seconds — show the most impressive feature
- 15-30 seconds optimal length
- No sound dependency — add captions/text overlays
- Show real usage — not marketing fluff
- End with CTA — "Download Free" or key benefit
When to Skip
- Simple utility apps (screenshots are enough)
- Apps where the value is in content, not UI
Output Format
Screenshot Plan
For each of the 10 slots:
Slot [N]: [Headline]
- Caption: "[benefit-driven text]"
- Screen: [which app screen to show]
- Layout: [portrait/landscape, device frame, text position]
- Key element: [what draws the eye]Design Brief
If the user needs to brief a designer:
- Color palette (from app brand)
- Font recommendations
- Layout template
- Text overlay copy for all 10 slots
- Device frame preference
- Background style
Competitor Screenshot Audit
| Element | Your App | Comp 1 | Comp 2 | Comp 3 |
| # of screenshots | ||||
| Has video? | ||||
| First screenshot type | ||||
| Text overlay style | ||||
| Design quality (1-10) | ||||
| Unique angle |
Related Skills
ab-test-store-listing— Test screenshot variationsaso-audit— Screenshots as part of broader auditcompetitor-analysis— Analyze competitor creative strategylocalization— Localize screenshots for international markets
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

