skills.rest
evanca
evancaCOMMUNITY
Explore all skills by this author →
Website𝕏@ivannahereGitHub

store-listing-assets

Generate App Store and Google Play listing copy and image assets sized to exact store specifications.

628|64|Updated Apr 22, 2025
Search Tags:#screenshots#launch checklist#aso#App Store#app metadata#store listing#Google Play
One-click install
npx skills add https://github.com/evanca/flutter-ai-rules --skill store-listing-assets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: store-listing-assets
Source: https://github.com/evanca/flutter-ai-rules/tree/main/skills/store-listing-assets
Command: npx skills add https://github.com/evanca/flutter-ai-rules --skill store-listing-assets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Preparing an app store listing requires hitting dozens of exact constraints — character limits for names, subtitles, descriptions, and keywords, plus precise pixel dimensions and formats for icons, feature graphics, and screenshots — and getting any of them wrong causes listing errors or rejection. This Skill produces store-ready copy and visual assets validated against the current Google Play and Apple App Store requirements.

Core Features & Use Cases

  • Limit-checked store copy: Writes app names, subtitles, short/full descriptions, keywords, and promotional text with character and byte counts shown against each store's limits (e.g., Apple keywords capped at 100 bytes).
  • Spec-exact visual assets: Produces or resizes icons (512×512 PNG with alpha for Play), feature graphics (1024×500, no alpha), and iPhone screenshots (1320×2868 and other required sizes) using tools like ImageMagick.
  • Submission checklists: Walks through required console declarations — Data Safety, content rating, privacy policy URLs, account deletion, export compliance — adapted to the app's actual behavior.
  • Use Case: You are launching a Flutter notes app on both stores. The Skill drafts a 30-character name, an 80-character Play short description, a 4,000-character full description, a byte-counted Apple keywords line, and a screenshot spec sheet, then flags that Play also requires a 1024×500 feature graphic to publish.

Quick Start

Prepare the App Store and Google Play listing copy and screenshot specs for my app, targeting both stores with English and German localizations.

Frequently Asked Questions about store-listing-assets

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

FAQPage Schema
How do I write an app store description within character limits?▼

Google Play allows 4,000 characters for the full description and 80 for the short description; Apple allows 4,000 characters of plain text. Lead with what the app does in the first sentence, avoid claim words like "best" or "#1", and always count characters against the limit before submitting.

What screenshot sizes are required for App Store and Google Play?▼

Apple requires 1–10 iPhone screenshots, preferably 1320×2868, 1290×2796, or 1260×2736 for 6.9-inch devices (1284×2778 or 1242×2688 for 6.5-inch). Google Play requires 2–8 phone screenshots, JPEG or 24-bit PNG without alpha, minimum side 320 px, recommended 1080×1920 portrait.

How do Apple App Store keywords work with the 100-byte limit?▼

Apple keywords are limited to 100 bytes total, not characters, so non-ASCII characters consume multiple bytes. Separate keywords with commas and no spaces, keep each keyword over 2 characters, and avoid repeating the app name or category since those are already indexed.

Does Google Play require a feature graphic to publish an app?▼

Yes, Google Play requires a 1024×500 px feature graphic in JPEG or 24-bit PNG without alpha to publish, alongside a 512×512 px 32-bit PNG icon with alpha (max 1024 KB) and at least 2 phone screenshots.

What words should I avoid in app store listing copy?▼

Avoid claim words such as "best", "#1", "free" (unless unconditionally true), rankings, awards, and pricing claims in both text and images. These trigger rejection under both stores' policies and must not appear in titles, icons, screenshots, or feature graphics.

Do I need separate assets for iPad or tablet store listings?▼

This workflow covers phone-only listings; tablet, iPad, desktop, TV, and watch assets are separate families with their own requirements. Only prepare those if your app explicitly supports those device types, and verify their specs separately at submission time.

Related Skills

Explore More Marketing & Sales Skills→
exilonXexilonX

vtex-io-auth-and-policies

Define authorization and policy boundaries for VTEX IO app manifests.

Community
Advanced
marvelousempiremarvelousempire

aso-audit

Audit App Store and Google Play listings and generate optimization reports.

Community
Advanced
joshka0joshka0
3

apple-submission-packet-readiness

Generate Apple App Review submission packets with reviewer access and verification checklists.

Community
Intermediate
decentpastedecentpaste
232

appstore-screenshots

Resizes screenshots to App Store dimensions using Python and Pillow for iPhone/iPad models.

Official
Basic