agentleFS
Prisma-Labs-DevPrisma-Labs-Dev/apple-skills/skills/apple-aso/SKILL.md

apple-aso

Skill336 starsChanged 7 months agoMITView on GitHub

Optimize Apple App Store metadata in store.config.json for ASO (App Store Optimization). Use when working with store.config.json, App Store keywords, titles, subtitles, descriptions, or localizing app metadata. Helps maximize app visibility and downloads.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No plurals: if you have the singular form

    line 46
  2. Distinctive:

    No generic terms: - avoid "app", "game", "free", "best", "new"

    line 48
  3. Distinctive:

    Check for these issues:

    line 99
  4. Distinctive:

    Remove all duplicates from title/subtitle

    line 115
  5. Distinctive:

    Remove plurals if singular exists

    line 116
  6. Distinctive:

    Add action verbs users search for

    line 117
  7. Distinctive:

    Add regional/cultural variants

    line 118
  8. Distinctive:

    Remove diacritics for better matching

    line 120
  9. Distinctive:

    No duplicates from title/subtitle

    line 156
  10. Distinctive:

    Frequent changes: - Wait 3-4 weeks between keyword updates

    line 193

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Apple ASO (App Store Optimization)

Optimize App Store metadata following Apple's guidelines and ASO best practices to maximize visibility and downloads.

When to Use

  • Creating or editing store.config.json
  • Optimizing App Store keywords
  • Localizing app metadata for new markets
  • Reviewing existing metadata for ASO issues
  • Adding new language localizations

Character Limits

FieldLimitRanking WeightIndexed
Title30 charsHighestYes
Subtitle30 chars2nd highestYes
Keywords100 chars3rd (same as subtitle)Yes
Description4,000 charsNoneNo
Promo Text170 charsNoneNo
Release Notes4,000 charsNoneNo

Keyword Field Rules

Format

keyword1,keyword2,multi word phrase,keyword3

Critical formatting:

  • Comma-separated with NO spaces after commas (saves characters)
  • Spaces allowed within multi-word phrases
  • 100 characters total

Must Follow

  1. Never duplicate words from title/subtitle - Apple indexes them automatically
  2. Use single words when possible - Apple creates combinations automatically
  3. No plurals if you have the singular form
  4. No special characters - @, #, - are replaced with spaces
  5. No generic terms - avoid "app", "game", "free", "best", "new"
  6. No competitor names or trademarks
  7. No category names - already indexed from category selection

Should Include

  • Synonyms not in title/subtitle
  • Alternate spellings (with/without accents)
  • Related concepts and features
  • Long-tail niche terms
  • Regional variations
  • Action verbs users search for

Localization Best Practices

Apple App Store Language Codes

LanguageCodeLanguageCode
English (US)en-USGermande-DE
English (UK)en-GBFrench (France)fr-FR
English (AU)en-AUFrench (Canada)fr-CA
Spanish (Spain)es-ESPortuguese (Brazil)pt-BR
Spanish (Mexico)es-MXPortuguese (Portugal)pt-PT
ItalianitDutchnl-NL
JapanesejaRussianru
KoreankoChinese Simplifiedzh-Hans
Arabicar-SAChinese Traditionalzh-Hant

Localization Rules

  1. Don't just translate - Research native search terms
  2. Include English keywords in non-English locales (users often search in English)
  3. Remove diacritics for keywords (users skip accents when typing)
  4. Add regional terms - Different countries use different words
  5. Consider cross-localization - Apple indexes multiple locales per territory

Cross-Localization (Free Extra Keywords)

Apple indexes keywords from multiple locales per territory:

  • US: English (US) + Spanish (Mexico)
  • UK: English (UK) + English (US)
  • Canada: English (Canada) + French (Canada)
  • Australia: English (AU) + English (UK)

This effectively gives you 200 characters in some markets.

Optimization Workflow

Step 1: Analyze Current Metadata

Check for these issues:

  • Keywords duplicating title/subtitle words
  • Redundant synonyms (e.g., "kids" and "children")
  • Generic terms that waste space
  • Missing regional variants
  • Unused character space

Step 2: Research Keywords

Consider:

  • Relevance: Does it describe your app?
  • Volume: Are people searching for it?
  • Competition: Can you realistically rank?

Step 3: Optimize Keywords

  1. Remove all duplicates from title/subtitle
  2. Remove plurals if singular exists
  3. Add action verbs users search for
  4. Add regional/cultural variants
  5. Fill remaining space with related terms
  6. Remove diacritics for better matching

Step 4: Validate

  • Title ≤ 30 characters
  • Subtitle ≤ 30 characters
  • Keywords ≤ 100 characters (count with no spaces after commas)
  • No duplicates across fields
  • No prohibited terms

Example: Before & After

Before (Poor ASO)

{
  "title": "Call Santa Claus Now",
  "subtitle": "Magical Santa Voice Calls",
  "keywords": ["santa", "call santa", "santa claus", "voice call", "kids", "children"]
}

Issues:

  • "santa", "call santa", "santa claus" duplicate title
  • "voice call" duplicates subtitle
  • "kids" and "children" are synonyms

After (Optimized)

{
  "title": "Call Santa Claus Now",
  "subtitle": "Magical Santa Voice Calls",
  "keywords": "christmas,xmas,holiday,north pole,father christmas,talk,phone,festive,rudolph,elves,family"
}

Improvements:

  • No duplicates from title/subtitle
  • Regional variant (father christmas for UK)
  • Related terms (rudolph, elves, north pole)
  • Alternate spellings (xmas)
  • Action verb (talk)

store.config.json Schema

{
  "configVersion": 0,
  "apple": {
    "info": {
      "en-US": {
        "title": "App Name (max 30 chars)",
        "subtitle": "Value proposition (max 30 chars)",
        "description": "Full description (max 4000 chars)",
        "keywords": "comma,separated,no spaces,after commas",
        "releaseNotes": "What's new in this version",
        "promoText": "Short promotional text (max 170 chars)",
        "privacyPolicyUrl": "https://example.com/privacy",
        "supportUrl": "https://example.com/support",
        "marketingUrl": "https://example.com"
      }
    },
    "categories": ["PRIMARY_CATEGORY", "SECONDARY_CATEGORY"]
  }
}

Common Mistakes to Avoid

  1. Duplicating keywords across fields - Wastes precious character space
  2. Direct translation - Doesn't account for local search behavior
  3. Keyword stuffing in title - Hurts readability and conversion
  4. Ignoring subtitle - Second most important ranking factor
  5. Using spaces after commas - Wastes ~10% of keyword space
  6. Frequent changes - Wait 3-4 weeks between keyword updates
  7. Including app/game - Already indexed from category

Resources

Commands

# Push metadata to App Store
eas metadata:push

# Pull current metadata from App Store
eas metadata:pull

# Validate metadata locally
# (Check JSON syntax and character limits)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.