store-screenshots

Produces App Store and Google Play screenshots through a five-step brief, capture, review, and render workflow.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/allen-hsu/mobile-shipkit --skill store-screenshots-allen-hsu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: store-screenshots
Source: https://github.com/allen-hsu/mobile-shipkit/tree/main/skills/store-screenshots
Command: npx skills add https://github.com/allen-hsu/mobile-shipkit --skill store-screenshots-allen-hsu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Store screenshots often fail to convert because teams capture screens first and write captions as an afterthought. This Skill enforces a copy-first workflow where headlines are written, reviewed, and approved before any rendering happens, then handles capture, styling, sizing, upload, and post-launch measurement for both stores. ## Core Features & Use Cases - Five-step reviewable pipeline: app brief, Release-build captures via sim-use, style selection from a 30-style catalogue, size/platform/locale configuration, and a sign-off review page before rendering. - Copy rules and headline checklist: 58 copywriting rules, 15 before/after rewrites, and a 10-item checklist distilled from DesignerAnts and Paul Solt, including the cover-the-UI test. - End-to-end store delivery: renders via the store-art skill, uploads with gpc (Google Play) and asc (App Store Connect), and re-tests conversion after 30 days. - Use Case: A developer preparing a dual-store launch uses the skill to import the live listing, capture Release-build screenshots on iPhone and Android emulators per locale, get headline approval from a teammate via review.html, then render and upload both stores' assets. ## Quick Start Ask the agent to create store screenshots for your app by building a brief from your listing, capturing screens on a Release build, and producing a review page before rendering.

Frequently Asked Questions about store-screenshots

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create App Store and Google Play screenshots that convert?▼

Write headlines before capturing screens, following the pain, shift, proof, feature sequence. This skill scaffolds a brief.json, captures Release-build screens with sim-use, renders via store-art, and uploads with gpc or asc after a review page is approved.

What screenshot sizes do the App Store and Google Play require?▼

App Store requires iPhone 6.9 inch at 1320x2868, plus iPad 13 inch at 2064x2752 for universal apps. Google Play accepts the same iPhone size for phone screenshots and requires a 1024x500 feature graphic.

Why does Expo Go's floating toolbar appear in my screenshots?▼

Expo Go always shows its toolbar in captures. Build a Release configuration with npx expo run:ios --configuration Release and capture with sim-use instead, which produces clean 1320x2868 frames.

Can I reuse iPhone screenshots for Google Play?▼

Play accepts the iPhone 1320x2868 size, but you should not place iPhone captures inside a Pixel frame. For authentic Android shots, install the release AAB with bundletool on an emulator and capture with adb screencap.

How do I handle multi-locale store screenshots?▼

Create one brief per locale and rewrite headlines rather than translating them. Capture one raw folder per locale by switching the app or emulator language, then render and upload each locale folder separately.