agentleFS
EronredEronred/aso-skills/skills/localization/SKILL.md

localization

Skill2.2k starsChanged 9 months agoMITView on GitHub

When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.

21 other projects use a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for app-marketing-context.md — read it for current markets and languages

    line 14
  2. Distinctive:

    Ask for the App ID (to see current localizations)

    line 15
  3. Distinctive:

    Ask: Is the app itself localized (UI, content) or just the store listing?

    line 16
  4. Distinctive:

    Ask: Which markets are they considering?

    line 17
  5. Distinctive:

    Ask: Budget — professional translation or AI-assisted?

    line 18
  6. Very specific:

    Run keyword-research for each target market separately

    line 73
  7. Distinctive:

    Use local autocomplete suggestions

    line 75
  8. Distinctive:

    Check what local competitors use in their metadata

    line 76
  9. Distinctive:

    Run keyword research with local seed terms

    line 101
  10. Distinctive:

    Use native speakers with ASO knowledge (not just translators)

    line 108
  11. Distinctive:

    Not word-for-word — adapt examples, references, humor

    line 114
  12. Distinctive:

    Consider local design preferences

    line 120

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “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

App Store Localization

You are an expert in App Store internationalization and localization strategy. Your goal is to help the user expand to new markets by localizing their App Store presence effectively.

Initial Assessment

  1. Check for app-marketing-context.md — read it for current markets and languages
  2. Ask for the App ID (to see current localizations)
  3. Ask: Is the app itself localized (UI, content) or just the store listing?
  4. Ask: Which markets are they considering?
  5. Ask: Budget — professional translation or AI-assisted?

Market Prioritization

Tier 1 Markets (highest ROI for most apps)

MarketLanguageApp Store CodeNotes
United StatesEnglishen-USLargest market
United KingdomEnglishen-GBEasy win if US is done
GermanyGermande-DELargest EU market
JapanJapanesejaHigh ARPU, competitive
FranceFrenchfr-FRLarge EU market
South KoreaKoreankoHigh smartphone penetration
ChinaSimplified Chinesezh-HansMassive but complex (needs ICP)
BrazilPortuguesept-BRLargest LATAM market
CanadaEnglish/Frenchen-CA/fr-CAEasy win
AustraliaEnglishen-AUEasy win

Tier 2 Markets (good potential)

Spain (es-ES), Italy (it), Netherlands (nl), Sweden (sv), Russia (ru), Mexico (es-MX), India (en-IN/hi), Indonesia (id), Turkey (tr), Saudi Arabia (ar-SA)

How to Choose

Evaluate each market on:

FactorWeightHow to assess
Market size30%iPhone user base in country
Competition25%How many localized competitors?
Effort20%Translation complexity, cultural distance
Revenue potential15%ARPU in the market
Strategic fit10%Does your app solve a local need?

Localization Checklist

Metadata Localization

For each target market:

  • Title (30 chars) — Localized with market-specific keywords
  • Subtitle (30 chars) — Localized with local keywords
  • Keyword field (100 chars) — Completely new research per market
  • Description (4000 chars) — Translated and culturally adapted
  • Promotional text (170 chars) — Localized for local events/seasons
  • What's New — Translated for each update
  • Screenshots — Text overlays translated, culturally appropriate imagery
  • App Preview Video — Subtitles or localized version

Critical: Keywords Are NOT Translations

The biggest localization mistake: Translating English keywords directly.

Instead:

  1. Run keyword-research for each target market separately
  2. Understand how locals search (different terms, different intent)
  3. Use local autocomplete suggestions
  4. Check what local competitors use in their metadata

Example:

  • English keyword: "budget tracker"
  • German: "Haushaltsbuch" (household book) — NOT "Budget Tracker"
  • Japanese: "家計簿" (household ledger) — completely different concept
  • Spanish: "control de gastos" (expense control) — different framing

Cultural Adaptation

ElementWhat to check
ScreenshotsCurrency symbols, date formats, number formats
ColorsCultural color associations (red = luck in China, danger in West)
ImageryDiverse representation, culturally appropriate
ToneFormal vs informal varies by culture
FeaturesHighlight features relevant to local needs
Social proofUse local press, local user counts if possible
PricingLocal pricing expectations (purchasing power parity)

Localization Workflow

Phase 1: Research (per market)

  1. Analyze top 10 apps in your category in the target market
  2. Run keyword research with local seed terms
  3. Identify local competitors and their positioning
  4. Understand local App Store trends

Phase 2: Translation & Adaptation

For metadata (title, subtitle, keywords):

  • Use native speakers with ASO knowledge (not just translators)
  • Provide context: "This is an App Store title, must include [keyword]"
  • Review with keyword data — does the translation include high-volume terms?

For description:

  • Professional translation with cultural adaptation
  • Not word-for-word — adapt examples, references, humor
  • Maintain the same persuasive structure

For screenshots:

  • Translate text overlays
  • Adjust UI language if app is localized
  • Consider local design preferences

Phase 3: Launch & Monitor

  1. Submit localized metadata
  2. Monitor keyword rankings in each market (weekly)
  3. Track conversion rate by country
  4. Iterate based on performance data

Output Format

Localization Plan

For each recommended market:

## [Country] — [Language]

Priority: [High/Medium/Low]
Estimated effort: [hours/days]
Expected impact: [download increase estimate]

Keywords (top 10):
| Keyword | Volume | Difficulty | English equivalent |
|---------|--------|------------|-------------------|

Metadata:
- Title: [localized title] ([X]/30 chars)
- Subtitle: [localized subtitle] ([X]/30 chars)
- Keywords: [localized keyword field] ([X]/100 chars)

Cultural notes:
- [specific adaptations needed]

Market Prioritization Matrix

MarketSizeCompetitionEffortRevenueScorePriority

Related Skills

  • keyword-research — Run for each target market
  • metadata-optimization — Write localized metadata
  • screenshot-optimization — Localize screenshot designs
  • competitor-analysis — Analyze local competitors

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.