app-store-screenshots
Skill5 starsChanged 8 months agoMITView on GitHub
Create App Store and Google Play screenshots with exact platform specs. Covers iOS/Android dimensions, gallery ordering, device mockups, captions, preview videos, localization, and A/B testing. Use when: app store screenshots, ASO, app preview, store listing, app mockup.
12 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- MoizIbnYousaf/marketing-clitheir own version, first seen Nov 1, 2026
- aidvgg/operator-ostheir own version, first seen Oct 17, 2026
- hsynozdamar-byte/claude-skills-editedtheir own version, first seen Oct 17, 2026
- gug007/lpmtheir own version, first seen Oct 13, 2026
- AngelescuCiprian/claude-skillsedited, first seen Aug 22, 2026
- nikunj812/claude-skilledited, first seen Jul 1, 2026
Used with
Projects with it also use operational-enterprise-ai, product-proof-saas and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
boraoztuncSkilloperational-enterprise-ai
Create or redesign enterprise AI, automation, security, and operations product pages that explain system boundaries, approvals, auditability, exceptions, and rollback. Use for dark cinematic heroes, hairline grids, metric pauses, expandable solution rows, case-study evidence, security proof, and qualified demo or waitlist handoffs.
Also in 3 projects that use this
boraoztuncSkillproduct-proof-saas
Create or redesign SaaS and AI product landing pages where a real workflow, interface, or deterministic demo is the central proof. Use for pale atmospheric shells, product UI in the hero, prompt-to-output stories, audience tabs, compact feature modules, honest pricing comparisons, and FAQ handoffs.
Also in 3 projects that use this
Dragoon0xSkillpricing-page
Present pricing in ways that reduce friction and increase clarity. Handles tier naming, feature comparison, anchor pricing, and plan selection psychology. Use when designing pricing pages, plan selectors, or upgrade prompts.
Also in 3 projects that use this
brpazSkilltailwind-v4
Configure Tailwind CSS v4 with Oxide, CSS-first directives, migration steps, and production guidance.
Also in 3 projects that use this
silvainfmSkillcopy-editing
When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.
Also in 4 projects that use this
silvainfmSkillpage-cro
When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
Also in 3 projects that use this
- +1 more from boraoztunc
- +1 more from silvainfm
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- AngelescuCiprian/claude-skills★ 091% same
- nikunj812/claude-skill★ 087% same
Wrote their own version · 10
- ParthJadhav/app-store-screenshots★ 7.8ksame name
- boraoztunc/skills★ 454same name
- gug007/lpm★ 150same name
- MoizIbnYousaf/marketing-cli★ 33same name
- aidvgg/operator-os★ 4same name
- hsynozdamar-byte/claude-skills-edited★ 4same name
- ImSebass/app-store-screenshots★ 2same name
- Sebas05c/app-store-screenshots★ 2same name
- florattu/claude-skills★ 0same name
- nvm1410/claude-skills★ 0same name
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 repository29 other files it gives its agents.
- skills/architect/CLAUDE.mdCLAUDE.md
- skills/council/CLAUDE.mdCLAUDE.md
- agent-browserSkill
- architectSkill
- architecture-reviewerSkill
- c-cpp-analyzerSkill
- councilSkill
- c-to-rust-migrationSkill
- demo-pipelineSkill
- e2e-pipelineSkill
- founder-modeSkill
- full-evalSkill
- hackathon-jurySkill
- idea-labSkill
- ios-glass-ui-designerSkill
- learn-by-mistakeSkill
- maestro-mobile-testingSkill
- migration-validatorSkill
- mobile-design-systemSkill
- noricum-devSkill
- oss-readinessSkill
- pdf-presentationSkill
- playwright-recordingSkill
- post-run-analysisSkill
- rust-migrationSkill
- ui-ux-polishSkill
- vc-evaluatorSkill
- webreelSkill
- youtube-devrelSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
6
Distinctive
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 13
Create app store screenshots and preview videos via inference.sh CLI.
- Distinctive: line 231
Test different screenshot orders
- Distinctive: line 232
Test with/without device frames
- Distinctive: line 234
Test different color schemes
- Distinctive: line 235
Run for 7+ days with 50%+ traffic for significant results
- Distinctive: line 267
Wrong dimensions: Check platform specs table above — App Store and Play Store have different requirements
- Distinctive: line 269
AI mockup looks generic: Add specific details to the prompt (your app's actual color scheme, specific screen content, real feature names)
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
App Store Screenshots
Create app store screenshots and preview videos via inference.sh CLI.
Quick Start
Requires inference.sh CLI (
infsh). Get installation instructions:npx skills add inference-sh/skills@agent-tools
infsh login
# Generate a device mockup scene
infsh app run falai/flux-dev-lora --input '{
"prompt": "iPhone 15 Pro showing a clean modern app interface with analytics dashboard, floating at slight angle, soft gradient background, professional product photography, subtle shadow, marketing mockup style",
"width": 1024,
"height": 1536
}'Platform Specifications
Apple App Store (iOS)
| Device | Dimensions (px) | Required |
| iPhone 6.7" (15 Pro Max) | 1290 x 2796 | Required |
| iPhone 6.5" (11 Pro Max) | 1284 x 2778 | Required |
| iPhone 5.5" (8 Plus) | 1242 x 2208 | Optional |
| iPad Pro 12.9" (6th gen) | 2048 x 2732 | If iPad app |
| iPad Pro 11" | 1668 x 2388 | If iPad app |
- Up to 10 screenshots per localization
- First 3 screenshots are visible without scrolling (critical)
- Formats: PNG or JPEG (no alpha/transparency for JPEG)
Google Play Store (Android)
| Spec | Value |
| Min dimensions | 320 px (any side) |
| Max dimensions | 3840 px (any side) |
| Aspect ratio | 16:9 or 9:16 |
| Max screenshots | 8 per device type |
| Formats | PNG or JPEG (24-bit, no alpha) |
- Feature graphic: 1024 x 500 px (required for featuring)
- Promo video: YouTube URL (optional but recommended)
The First 3 Rule
80% of App Store impressions show only the first 3 screenshots (before the user scrolls). These three must:
- Communicate the core value proposition
- Show the best feature/outcome
- Differentiate from competitors
Screenshot Gallery Order
| Position | Content | Purpose |
| 1 | Hero -- core value, best feature | Stop the scroll, communicate what the app does |
| 2 | Key differentiator | What makes you unique vs competitors |
| 3 | Most popular feature | The thing users love most |
| 4 | Social proof or outcome | Ratings, results, testimonials |
| 5-8 | Additional features | Supporting features, settings, integrations |
| 9-10 | Edge cases | Specialized features for niche users |
Screenshot Styles
1. Device Frame with Caption
The standard: device mockup showing the app, caption text above/below.
+----------------------------+
| "Track Your Habits | <- Caption (benefit-focused)
| Effortlessly" |
| |
| +--------------------+ |
| | | |
| | App Screen | | <- Actual app UI in device frame
| | Content | |
| | | |
| | | |
| +--------------------+ |
| |
+----------------------------+2. Full-Bleed UI (No Device Frame)
The app UI fills the entire screenshot. Works for immersive apps.
3. Lifestyle Context
The device shown in a real-world context (person holding phone, on desk, etc.).
4. Feature Highlight with Callouts
UI screenshot with arrows/circles pointing to specific features.
Caption Writing
Rules
- Max 2 lines of text
- Benefit-focused, not feature-focused
- 30pt+ equivalent font size (must be readable in store)
Examples
Bad (feature-focused):
"Push Notification System"
"Calendar View with Filters"
"Data Export Functionality"
Good (benefit-focused):
"Never Miss a Deadline Again"
"See Your Week at a Glance"
"Share Reports in One Tap"Generating Screenshots
Hero Screenshot (Position 1)
# Clean device mockup with hero feature
infsh app run falai/flux-dev-lora --input '{
"prompt": "modern iPhone showing a beautiful fitness tracking app with activity rings and workout summary, device floating at slight angle against soft purple gradient background, professional product shot, clean minimal composition, subtle reflection",
"width": 1024,
"height": 1536
}'Feature Highlight
# Feature callout style
infsh app run bytedance/seedream-4-5 --input '{
"prompt": "app store screenshot style, iPhone showing a messaging app with AI writing suggestions highlighted, clean white background, subtle UI callout arrows, professional marketing asset, modern design",
"size": "2K"
}'Lifestyle Context
# Device in real-world setting
infsh app run falai/flux-dev-lora --input '{
"prompt": "person holding iPhone showing a cooking recipe app, kitchen background with ingredients, warm natural lighting, over-the-shoulder perspective, lifestyle photography, authentic feeling",
"width": 1024,
"height": 1536
}'Before/After
# Split comparison
infsh app run infsh/stitch-images --input '{
"images": ["before-screenshot.png", "after-screenshot.png"],
"direction": "horizontal"
}'Preview Videos
Apple App Store
| Spec | Value |
| Duration | 15-30 seconds |
| Orientation | Portrait or landscape (match app) |
| Audio | Optional (loops silently in store) |
| Format | H.264, .mov or .mp4 |
Google Play
| Spec | Value |
| Source | YouTube URL |
| Duration | 30s-2min recommended |
| Orientation | Landscape preferred |
Preview Video Structure
| Segment | Duration | Content |
| Hook | 0-3s | Show the core outcome/wow moment |
| Feature 1 | 3-10s | Demonstrate top feature in action |
| Feature 2 | 10-18s | Second key feature |
| Feature 3 | 18-25s | Third feature or social proof |
| CTA | 25-30s | End screen with app icon |
# Generate preview video scenes
infsh app run google/veo-3-1-fast --input '{
"prompt": "smooth screen recording style, finger tapping on a modern mobile app interface, swiping between screens showing charts and data visualizations, clean UI transitions, professional app demo"
}'Localization
Each language gets its own set of screenshots. Priorities:
| Market | Localization Level |
| Primary markets | Full: new screenshots + translated captions |
| Secondary markets | Translated captions, same screenshots |
| Other | English defaults |
Key localization markets: English, Japanese, Korean, Chinese (Simplified), German, French, Spanish, Portuguese (Brazilian)
A/B Testing (Google Play)
Google Play Console supports store listing experiments:
- Test different screenshot orders
- Test with/without device frames
- Test different captions
- Test different color schemes
- Run for 7+ days with 50%+ traffic for significant results
Common Mistakes
| Mistake | Problem | Fix |
| Settings screen as screenshot | Nobody cares about settings | Show core value, not infrastructure |
| Onboarding flow screenshots | Shows friction, not value | Show the app in-use state |
| Too much text | Unreadable in store | Max 2 lines, 30pt+ font |
| Wrong dimensions | Rejected by store | Use exact platform specs |
| All screenshots look the same | No reason to scroll | Vary composition and content |
| Feature-focused captions | Doesn't communicate benefit | "Never Miss a Deadline" > "Push Notifications" |
| Outdated UI | Looks abandoned | Update screenshots with each major release |
| No hero screenshot | Weak first impression | Position 1 = your best shot |
Important
AI-generated images (via inference.sh) produce marketing mockups, not real app screenshots. For actual screenshots of your running app, use maestro-mobile-testing or playwright-recording to capture real screens, then use this skill for framing, captions, and store optimization.
Example Output
App Store Screenshot Set Generated:
- hero-iphone15pro.png (1290x2796) — "Track Your Habits Effortlessly"
- feature-calendar.png (1290x2796) — "See Your Week at a Glance"
- social-proof.png (1290x2796) — "Join 50,000+ Users"
- ipad-pro.png (2048x2732) — "Beautiful on Every Screen"
- feature-graphic.png (1024x500) — Google Play feature graphicError Handling
- Wrong dimensions: Check platform specs table above — App Store and Play Store have different requirements
- Store rejection: Common causes: transparency in JPEG (use PNG), text too small (30pt+ minimum), screenshots show non-final UI
- AI mockup looks generic: Add specific details to the prompt (your app's actual color scheme, specific screen content, real feature names)
Checklist
- Correct dimensions for target platform
- First 3 screenshots communicate core value
- Captions are benefit-focused, max 2 lines
- No onboarding or settings screens
- Preview video is 15-30s with hook in first 3s
- Localized for top markets
- Feature graphic (1024x500) for Google Play
- Screenshots updated for current app version
- A/B test variant prepared
Related Skills
npx skills add inference-sh/skills@ai-image-generation
npx skills add inference-sh/skills@ai-video-generation
npx skills add inference-sh/skills@image-upscaling
npx skills add inference-sh/skills@prompt-engineeringBrowse all apps: infsh app list
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.

