← ClaudeAtlas

store-screenshotslisted

Create App Store and Google Play marketing screenshot sets that look like top-chart apps - a headline-led story of 5-8 frames with a poster-style first frame, zoomed real UI fragments, a dominant brand colour, panoramic links between frames, social proof and human touches - generated frame by frame with Codex (GPT Image) using the app's real screens as reference images, text-checked and edit-passed, then fitted to the exact store sizes. Use whenever the user wants store screenshots, "App Store screenshots", "Play Store images", listing graphics, a screenshot redesign or "before/after" for a store page, or wants their app's store page to convert better, even if they only say "screenshots" for an app. Takes real app screens (for example from app-design-studio) as input.
zohaibmushwani/agent-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill zohaibmushwani/agent-skills
# store-screenshots Store screenshots are an ad, not a gallery of screens. Visitors decide in one or two seconds, mostly from the first 2-3 frames, so each frame sells **one benefit** with a big headline and only the slice of UI that proves it. The patterns here come from studying high-performing sets (see `references/patterns.md`); use them as principles, never copy another app's layout, brand or art. ## Inputs (gather first) - Real UI screens of the app (PNG). From the `app-design-studio` skill or captures. Without them, stop: invented UI in store screenshots misrepresents the app. - `tokens.json` or brand colours, logo/wordmark, app name, the one-line promise. - Keywords and competitor claims (the `aso-research` skill, if available) so headlines use the words people search. - Platform(s) and languages. Default: Google Play phone 1080 x 1920 and iPhone 6.9" 1290 x 2796. ## Workflow (Codex is the renderer; this skill writes its instructions) 1. **Message map.** List 5-8 benefits, ordered by what makes someone install. Frame 1 = the promise (poster); frames 2-3 = the core loop; then differentiators, proof, retention. Write `story.md`: per frame a headline (2-4 words), optional 3-6 word subline, and the real screen that proves it. Rules in `references/copy.md`. 2. **set.json.** Fill the set style once (look, colours with text-on-accent, headline font description, art direction, panorama motif) and the frames (schema in `references/frame-recipes.md`). The style block is repe