본문으로 건너뛰기
cccskills
무료GitHub에 공개

screenshot-optimization

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

appeeky/aso-skills2.2천2026년 10월 7일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

appeeky/aso-skills2.2천2026년 10월 7일 업데이트

When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

appeeky/aso-skills2.2천2026년 10월 7일 업데이트

app-clips

무료

When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to understand how App Clips appear in App Store search. For general App Store discoverability, see aso-audit. For marketing campaigns, see ua-campaign.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

appeeky/aso-skills2.2천2026년 10월 7일 업데이트

When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

appeeky/aso-skills2.2천2026년 10월 7일 업데이트

When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition during launch, see ua-campaign.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

appeeky/aso-skills2.2천2026년 10월 7일 업데이트

appeeky의 스킬 모두 보기

이 스킬의 문제 신고