store-listing-assets
Use when writing store copy to character limits (name, subtitle, descriptions, keywords) or preparing listing images (icon, feature graphic, screenshots, preview video).
npx skills add evanca/flutter-ai-rules --skill store-listing-assets --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 1. **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 poli
- How to use this skill
- Writing store copy (fit to limits)
- Producing visual assets (exact specs)
- Deliverables
What does the store-listing-assets skill do?
Use when writing store copy to character limits (name, subtitle, descriptions, keywords) or preparing listing images (icon, feature graphic, screenshots, preview video).
How do I install it?
Run `npx skills add evanca/flutter-ai-rules --skill store-listing-assets --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From evanca/flutter-ai-rules, a repository with 604 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.