screenshot-optimization

eronred/aso-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/eronred/aso-skills --skill screenshot-optimization
0 commentsdiscussion
summary

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.

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

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 variations
  • aso-audit — Screenshots as part of broader audit
  • competitor-analysis — Analyze competitor creative strategy
  • localization — Localize screenshots for international markets
how to use screenshot-optimization

How to use screenshot-optimization on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add screenshot-optimization
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/eronred/aso-skills --skill screenshot-optimization

The skills CLI fetches screenshot-optimization from GitHub repository eronred/aso-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/screenshot-optimization

Reload or restart Cursor to activate screenshot-optimization. Access the skill through slash commands (e.g., /screenshot-optimization) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.865 reviews
  • Neel Bansal· Dec 28, 2024

    We added screenshot-optimization from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Nikhil Abbas· Dec 24, 2024

    screenshot-optimization reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Chaitanya Patil· Dec 16, 2024

    screenshot-optimization has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Layla Li· Dec 12, 2024

    We added screenshot-optimization from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Yuki Tandon· Nov 23, 2024

    Useful defaults in screenshot-optimization — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Chen Ramirez· Nov 19, 2024

    screenshot-optimization fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aditi Kim· Nov 19, 2024

    Registry listing for screenshot-optimization matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Yusuf Johnson· Nov 15, 2024

    screenshot-optimization has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Piyush G· Nov 7, 2024

    screenshot-optimization reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Aditi Gonzalez· Nov 3, 2024

    screenshot-optimization fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 65

1 / 7