store-listing-assets
Store Listing Assets & Copy
Prepare the metadata, copy, and visual assets that go into an App Store / Google Play phone listing, sized and length-fit to each store's exact requirements. This is the listing production skill; pair it with a separate review-readiness audit at submission time so the fields are polished and the app itself is ready for review.
Two references hold the authoritative specs; consult them for exact numbers rather than reciting from memory (they drift):
references/mobile_listing_checklist.md— the actionable checklist (shared prep → per-store required → recommended → final check)references/spec_reference.md— the full spec tables, minimal valid examples, store-specific traps, and known gaps to verify live
Default scope is phone-only. Skip tablet, iPad, desktop, Chromebook, TV, watch, Mac, and visionOS assets unless the user says the app supports them — and if they do, note that those are separate asset families outside these specs.
How to use this skill
- Gather the inputs once (shared prep): final app name, what the app does in one sentence, primary category, whether it has ads, whether it collects/shares/tracks data, privacy policy URL, support contact, and launch languages. These feed both stores.
- Confirm which store(s) the user is targeting — the required set differs enough that doing both blindly wastes effort.
- Produce copy AND/OR assets per the requests below, always checking generated text against the live character/byte limits and generated images against the exact pixel/format specs.
Writing store copy (fit to limits)
Character limits are hard constraints — always count and show the count. Key limits (full set in the references):