appeeky/aso-skills

screenshot-optimization

When the user wants to design, optimize, or evaluate App Store screenshots and preview videos.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/appeeky/aso-skills --skill screenshot-optimization

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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

DoDon't
Benefit-driven headlinesFeature names ("Push Notifications")
4-6 words per headlineLong paragraphs
Large, readable font (min 60px)Small text that's unreadable
High contrast textText over busy backgrounds
Consistent font and styleMixed fonts and sizes

Visual Design

DoDon't
Clean, uncluttered UIBusy screens with too much data
Consistent color schemeClashing 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 itIgnoring 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

ElementYour AppComp 1Comp 2Comp 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 variations
  • aso-audit — Screenshots as part of broader audit
  • competitor-analysis — Analyze competitor creative strategy
  • localization — Localize screenshots for international markets

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
appeeky
コミュニティ

android-aso

When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.

導入数
5
GitHub Stars
2197
更新日
10月6日
appeeky
コミュニティ

localization

When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.

導入数
4
GitHub Stars
2197
更新日
10月6日
appeeky
コミュニティ

review-management

When the user wants to analyze, respond to, or improve their app reviews and ratings. Also use when the user mentions "reviews", "ratings", "negative reviews", "how to get more reviews", "review response", or "my rating is dropping". For broader ASO audit, see aso-audit. For retention issues causing bad reviews, see retention-optimization.

導入数
4
GitHub Stars
2197
更新日
10月6日
appeeky
コミュニティ

web-to-app-funnel

When the user wants to design or optimize the funnel that takes web visitors into installing and onboarding the app — including smart app banners, web-to-app deep links, deferred deep links, web onboarding (Stripe-paid web flow before app install), QR codes, "open in app" CTAs, and the trade-off between paying on web vs in-app. Use when the user mentions "web to app", "smart app banner", "Stripe before app", "web paywall before install", "Branch web SDK", "web funnel for app", "AppsFlyer OneLink

導入数
4
GitHub Stars
2197
更新日
10月6日