/cg-store-listing

name: cg-store-listing
description: Generate App Store, Mac App Store, and Google Play Store listing metadata for apps. Use this skill whenever the user wants to create or optimize store listings, app descriptions, keywords, subtitles, short descriptions, category suggestions, or localized metadata for any app store. Trigger on phrases like "write my App Store description", "Play Store listing", "store metadata", "ASO", "app keywords", "app subtitle", "prepare my app for the store", "localize my listing", or when the user is preparing to submit an app to any store. Also trigger when the user asks to improve or optimize an existing store listing.

Store Listing Skill

Generate complete, ASO-optimized store listing metadata for Apple App Store (iOS), Mac App Store, and Google Play Store. The output is a structured metadata file ready to copy into App Store Connect or Google Play Console.

Input sources

Before asking the user to describe their app from scratch, check if the project already contains useful context:

1. **DEVPLAN.md** — If present, extract: app name, overview, feature list, target platform, and target audience. This is the richest source. 2. **README.md** — If present, extract: app description, feature list, tech stack (useful for developer-facing tools), and screenshots descriptions. 3. **Neither exists** — Ask the user for a brief description (3-5 sentences about what the app does, who it's for, and what makes it different).

Always confirm extracted information with the user before generating. A quick "I found this in your DEVPLAN — does this capture it?" is enough.

Workflow

Step 1: Gather context

From DEVPLAN/README or user input, identify:

• App name
• What it does (core value proposition)
• Target audience
• Key features (top 3-5)
• What makes it different from alternatives
• Target store(s): Apple App Store, Mac App Store, Google Play, or multiple

Step 2: Ask what's missing

Only ask questions the source material doesn't answer:

• **Tone**: Professional/serious, friendly/approachable, playful/fun, minimal/understated? This shapes all copy.
• **Competitor landscape**: Any specific apps this competes with? Helps avoid overlapping keywords and find differentiation angles.
• **Localization languages**: Which languages beyond the primary? (Suggest EN + user's native language as a minimum if the app is localized.)
• **Pricing model**: Free, paid upfront, freemium, subscription? Affects how the description frames value.

Do NOT ask about:

• Features already listed in DEVPLAN/README
• Technical implementation details
• Screenshot content (out of scope for this skill)

Step 3: Generate metadata

Produce a single markdown file with all store metadata, organized by store. Structure below.

---

Character limits — the hard rules

These limits are enforced by the stores. Every piece of generated metadata must respect them. Count characters carefully including spaces.

Apple App Store (iOS & Mac App Store)

| Field | Limit | Indexed for search | Visible to users | |-------|-------|--------------------|------------------| | App Name | 30 chars | Yes | Yes | | Subtitle | 30 chars | Yes | Yes | | Keyword Field | 100 chars | Yes | No | | Promotional Text | 170 chars | No | Yes | | Description | 4000 chars | No | Yes |

**Apple-specific rules:**

• Keywords: comma-separated, no spaces after commas, no duplicates from title/subtitle (Apple already indexes those)
• Subtitle: must form a readable phrase, not a keyword list — Apple rejects keyword stuffing
• Don't repeat words across title + subtitle + keywords — each word only needs to appear once across all three fields to be indexed
• Singular/plural: Apple indexes both forms in most languages, so don't waste keyword space on both
• The last word of a 30-char subtitle may not get indexed — keep critical keywords earlier
• Promotional text can be updated without a new app version — use this for seasonal messaging, announcements, and freshness signals
• Description can only be updated with a new version submission

Google Play Store

| Field | Limit | Indexed for search | Visible to users | |-------|-------|--------------------|------------------| | App Title | 30 chars | Yes | Yes | | Short Description | 80 chars | Yes | Yes | | Full Description | 4000 chars | Yes | Yes |

**Google Play-specific rules:**

• No dedicated keyword field — Google extracts keywords from title, short description, and full description
• Full description IS indexed (unlike Apple) — this is where keyword strategy lives
• Natural keyword placement in descriptions — Google penalizes stuffing
• Repeat primary keyword 3-5 times naturally across the full description — but never awkwardly
• Don't use: "free", "best", "#1", "top", "download now", promotional claims, emoji/emoticons in title
• No ALL CAPS unless it's the brand name
• Short description: treat as an elevator pitch, not a keyword dump — it appears in search results
• **Custom Store Listings**: Google Play allows different metadata per country — suggest this for apps targeting multiple regions
• **A/B testing**: Google Play Console supports native A/B testing for descriptions, icons, and screenshots — recommend the user test variations

Mac App Store

Same limits as iOS App Store. Key differences:

• Users are on desktop — description should emphasize productivity, workflow integration, keyboard shortcuts, and how the app fits into a desktop workflow
• Mac users expect more detail about system requirements, compatibility, and Apple Silicon support
• Menu bar / utility apps should clearly state they live in the menu bar and describe what's accessible without opening a full window
• Mac users are more willing to pay upfront — frame the value proposition around professional use and time saved
• Mention Spotlight, Shortcuts, or Widgets integration if applicable — these are differentiators Mac users actively search for
• Developer Tools category is less competitive on Mac