← ClaudeAtlas

store-screenshotslisted

Use when producing Google Play or App Store listing screenshots, a store carousel, a feature graphic, or social 4:5 slides cut from the same source — including choosing which screens to show, writing the caption on each, and exporting at store-legal sizes.
vishal-mandhane/divinity · ★ 2 · Code & Development · score 75
Install: claude install-skill vishal-mandhane/divinity
# Store Screenshots ## Overview The store carousel is the highest-leverage marketing surface an app has, and the part that gets shipped wrong is almost never the taste. Baseline testing on a doc-rich repo showed the creative work — narrative order, positioning, caption voice — comes out good unaided. What came out broken every time: **dimensions that violate store rules, on-screen strings quoted from memory instead of from source, and features framed that are not in the shipping build.** This skill is about those three. Do not let it flatten the copy into a template; the copy should be specific to this product or it is worthless. ## When to Use - Building the Play Store or App Store listing screenshot set - Writing the caption/headline that sits on each screenshot - Producing the 1024×500 Play feature graphic - Re-cutting the same set as 4:5 social slides **Not for:** launch videos, in-app onboarding, or press kits. ## Rule 1 — Frames 1–3 carry the entire pitch Published ASO benchmarks all point the same way, even though their exact numbers disagree. Treat the numbers as direction, not fact — they come from vendors (StoreMaven, ASO tool blogs), not from Apple or Google: | Commonly cited | Consequence | |---|---| | Most visitors (figures range 70–83%) never scroll past screenshot 1 | Frame 1 alone must answer *what is this* | | Very few (figures around 10%) see past screenshot 3 | The pitch is complete by frame 3 | | About 2.5 frames sit above the fold on a large phon