Skip to main content
skill CX Codex

apple-aso — Claude Code skill: App Store metadata and ASO

Checks store.config.json against Apple's character limits and keyword rules. Useful before a release or when adding a new locale.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Prisma-Labs-Dev/apple-skills --skill apple-aso -a claude-code
Open on GitHub

What apple-aso does

The skill reads store.config.json — the file you later push with eas metadata:push. It checks each field against Apple's limits: title and subtitle at 30 characters, keywords at 100, description at 4000. It also flags words repeated across fields.

Inside you get a ranking-weight table and the rules for the keyword field. Words from the title and subtitle should not be repeated, because Apple indexes those on its own. Spaces after commas eat roughly a tenth of the limit, so they go. A separate section covers locales: codes like en-US, de-DE, zh-Hans, plus cross-localization, where one territory indexes keywords from several languages at once.

There is a before-and-after walkthrough on a Santa-calling app, showing which terms were wasted and what replaced them. The skill advises leaving keywords alone for 3-4 weeks between edits — constant changes muddy the stats. You need the store.config.json file itself, and eas CLI access if you plan to push metadata.

What it helps with

  • fit a title and subtitle into 30 characters
  • strip duplicate words shared by title, subtitle and keywords
  • pick keywords for a new locale
  • validate metadata before eas metadata:push
  • find wasted characters in the keyword field

Example prompts for the agent

  • check store.config.json for character limits and duplicate keywords
  • add a de-DE localization and suggest keywords for the German market
  • why aren't my keywords indexing — walk through the keyword field

How to install apple-aso

1Skills CLI (Vercel)

npx skills add Prisma-Labs-Dev/apple-skills --skill apple-aso -a claude-code

2Manually: put the files in place

~/.claude/skills/apple-aso/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/apple-aso/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about apple-aso

How do I install apple-aso in Claude?

Run npx skills add Prisma-Labs-Dev/apple-skills --skill apple-aso -a claude-code. The skill lands at ~/.claude/skills/apple-aso/SKILL.md.

What does apple-aso do?

It reviews and rewrites App Store metadata in store.config.json: title, subtitle, keywords, description. It enforces character limits and removes repeats across fields.

What are the App Store character limits?

Title and subtitle are 30 characters each, keywords 100, description and release notes 4000, promo text 170. Title carries the most ranking weight, with subtitle and keywords next.

Source text

SKILL.md · MIT
---
name: apple-aso
user-invocable: true
description: 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.
---

# 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

| Field | Limit | Ranking Weight | Indexed |
|-------|-------|----------------|---------|
| **Title** | 30 chars | Highest | Yes |
| **Subtitle** | 30 chars | 2nd highest | Yes |
| **Keywords** | 100 chars | 3rd (same as subtitle) | Yes |
| **Description** | 4,000 chars | None | No |
| **Promo Text** | 170 chars | None | No |
| **Release Notes** | 4,000 chars | None | No |

## 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

| Language | Code | | Language | Code |
|----------|------|-|----------|------|
| English (US) | `en-US` | | German | `de-DE` |
| English (UK) | `en-GB` | | French (France) | `fr-FR` |
| English (AU) | `en-AU` | | French (Canada) | `fr-CA` |
| Spanish (Spain) | `es-ES` | | Portuguese (Brazil) | `pt-BR` |
| Spanish (Mexico) | `es-MX` | | Portuguese (Portugal) | `pt-PT` |
| Italian | `it` | | Dutch | `nl-NL` |
| Japanese | `ja` | | Russian | `ru` |
| Korean | `ko` | | Chinese Simplified | `zh-Hans` |
| Arabic | `ar-SA` | | Chinese Traditional | `zh-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)
```json
{
  "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)
```json
{
  "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

```json
{
  "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

- [Apple Developer: App Store Search](https://developer.apple.com/app-store/search/)
- [EAS Metadata Schema](https://docs.expo.dev/eas/metadata/schema/)
- Project guidelines: `docs/aso-guidelines.md`

## Commands

```bash
# 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)
```

© Prisma-Labs-Dev · MIT · Prisma-Labs-Dev/apple-skills

Similar skills

Everything for Mobile →

From the same set22

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor