Screenshot Optimization
Design and optimize App Store screenshots and preview creatives so mobile browsers convert to installs in the first few seconds on the product page.
Overview
screenshot-optimization is an agent skill for the Launch phase that designs and evaluates App Store screenshots and previews to maximize product-page conversion.
Install
npx skills add https://github.com/eronred/aso-skills --skill screenshot-optimizationWhat is this skill?
- Initial assessment checklist: app-marketing-context.md, App ID, audience, top three features, and designer vs DIY path
- Screenshot psychology: 3–6 seconds on product page; first three visible shots drive roughly 80% of conversion decisions
- Slot 1 Hook framework answers what the app does before users scroll
- Explicit handoffs to ab-test-store-listing for experiments and aso-audit for full-store reviews
- Expert ASO creative guidance for UI clarity, ease-of-use signals, and quality/social proof framing
- Users spend 3–6 seconds on an App Store product page before deciding
- First three screenshots (no scroll) influence roughly 80% of the conversion decision
- Initial assessment includes 5 discovery prompts (context file, App ID, audience, top 3 features, designer/DIY)
Adoption & trust: 1.7k installs on skills.sh; 1.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a live or upcoming App Store listing but screenshots do not communicate the value prop fast enough to stop the scroll.
Who is it for?
Solo iOS app makers preparing a store refresh who know their features but need ASO-framed creative sequencing and copy angles.
Skip if: Web-only SaaS landing pages or teams wanting full metadata/keyword audits without creative work—use aso-audit instead.
When should I use this skill?
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos, or mentions screenshots, app preview, product page design, screenshot design, or creative assets.
What do I get? / Deliverables
You leave with a slot-by-slot screenshot strategy, hook-first messaging, and clear next steps to A/B test listings or run a full ASO audit when needed.
- Screenshot slot strategy with Slot 1 Hook narrative
- Feature ordering recommendations for first three visible frames
- Creative brief guidance for designers or DIY asset production
Recommended Skills
Journey fit
Screenshot and preview work directly affects App Store conversion at Launch when you are polishing the listing before or during distribution pushes. ASO is the canonical shelf because the skill follows App Store psychology, slot strategy, and creative evaluation—not general web SEO.
How it compares
ASO creative brief skill for App Store frames—not a generic design system or automated screenshot renderer.
Common Questions / FAQ
Who is screenshot-optimization for?
Indie mobile developers and micro-teams optimizing App Store product pages with agent help for hooks, feature order, and conversion-focused layouts.
When should I use screenshot-optimization?
At Launch when you design new screenshots, evaluate an existing App ID listing, or plan preview videos before a version submission.
Is screenshot-optimization safe to install?
It is advisory creative guidance only; review the Security Audits panel on this Prism page and avoid pasting untrusted assets into store consoles.
Workflow Chain
Then invoke: ab test store listing, aso audit
SKILL.md
READMESKILL.md - Screenshot Optimization
# 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 1. Check for `app-marketing-context.md` — read it for positioning and audience 2. Ask for the **App ID** (to see current screenshots) 3. Ask for **target audience** — who is browsing the App Store for this? 4. Ask for **top 3 features** they want to highlight 5. 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:** 1. "Does this solve my problem?" (first screenshot) 2. "Is it easy to use?" (UI clarity) 3. "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**