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
Most recently taken up by
- parker-brown-family/agent-skillstheir own version, first seen Nov 8, 2026
- AnyOrgName/php-skillstheir own version, first seen Nov 8, 2026
- ghuntley/loomtheir own version, first seen Nov 1, 2026
- jame581/GodotPromptertheir own version, first seen Oct 21, 2026
- PhoenixNest/AGENT-GLOBAL-BASEtheir own version, first seen Oct 20, 2026
- glrodasz/dotfilestheir own version, first seen Oct 17, 2026
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.
Other versions21 projects use a version of this.
Word for word · 2
- appeeky/aso-skills★ 2.2k100% same
- Kungfookenny123/aso-skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 19
- chen08209/FlClash★ 62ksame name
- ghuntley/loom★ 1.7ksame name
- igorescodro/alkaa★ 1.6ksame name
- jame581/GodotPrompter★ 870same name
- bagofwords1/bagofwords★ 463same name
- CamilleScholtz/swmpc★ 239same name
- everpcpc/KMReader★ 118same name
- glrodasz/dotfiles★ 20same name
- aaronbrethorst/claude-skills★ 4same name
- AnyOrgName/php-skills★ 4same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- ab-test-store-listingSkill
- android-asoSkill
- app-analyticsSkill
- app-clipsSkill
- app-icon-optimizationSkill
- app-launchSkill
- apple-search-adsSkill
- app-marketing-contextSkill
- app-preview-videoSkill
- app-rejection-recoverySkill
- app-store-featuredSkill
- asc-metricsSkill
- aso-auditSkill
- aso-routerSkill
- attribution-setupSkill
- category-positioningSkill
- competitor-analysisSkill
- competitor-trackingSkill
- crash-analyticsSkill
- creator-ugc-marketingSkill
- custom-product-pagesSkill
- in-app-eventsSkill
- keyword-researchSkill
- market-moversSkill
- market-pulseSkill
- metadata-optimizationSkill
- monetization-strategySkill
- onboarding-optimizationSkill
- paywall-optimizationSkill
- press-and-prSkill
- rating-prompt-strategySkill
- referral-programSkill
- retention-optimizationSkill
- review-managementSkill
- screenshot-optimizationSkill
- seasonal-asoSkill
- subscription-lifecycleSkill
- ua-campaignSkill
- web-to-app-funnelSkill
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
- Very specific: line 14
Check for app-marketing-context.md — read it for current markets and languages
- Distinctive: line 15
Ask for the App ID (to see current localizations)
- Distinctive: line 16
Ask: Is the app itself localized (UI, content) or just the store listing?
- Distinctive: line 17
Ask: Which markets are they considering?
- Distinctive: line 18
Ask: Budget — professional translation or AI-assisted?
- Very specific: line 73
Run keyword-research for each target market separately
- Distinctive: line 75
Use local autocomplete suggestions
- Distinctive: line 76
Check what local competitors use in their metadata
- Distinctive: line 101
Run keyword research with local seed terms
- Distinctive: line 108
Use native speakers with ASO knowledge (not just translators)
- Distinctive: line 114
Not word-for-word — adapt examples, references, humor
- Distinctive: line 120
Consider local design preferences
“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.
Files
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
- Check for
app-marketing-context.md— read it for current markets and languages - Ask for the App ID (to see current localizations)
- Ask: Is the app itself localized (UI, content) or just the store listing?
- Ask: Which markets are they considering?
- Ask: Budget — professional translation or AI-assisted?
Market Prioritization
Tier 1 Markets (highest ROI for most apps)
| Market | Language | App Store Code | Notes |
| United States | English | en-US | Largest market |
| United Kingdom | English | en-GB | Easy win if US is done |
| Germany | German | de-DE | Largest EU market |
| Japan | Japanese | ja | High ARPU, competitive |
| France | French | fr-FR | Large EU market |
| South Korea | Korean | ko | High smartphone penetration |
| China | Simplified Chinese | zh-Hans | Massive but complex (needs ICP) |
| Brazil | Portuguese | pt-BR | Largest LATAM market |
| Canada | English/French | en-CA/fr-CA | Easy win |
| Australia | English | en-AU | Easy 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:
| Factor | Weight | How to assess |
| Market size | 30% | iPhone user base in country |
| Competition | 25% | How many localized competitors? |
| Effort | 20% | Translation complexity, cultural distance |
| Revenue potential | 15% | ARPU in the market |
| Strategic fit | 10% | 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:
- Run
keyword-researchfor each target market separately - Understand how locals search (different terms, different intent)
- Use local autocomplete suggestions
- 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
| Element | What to check |
| Screenshots | Currency symbols, date formats, number formats |
| Colors | Cultural color associations (red = luck in China, danger in West) |
| Imagery | Diverse representation, culturally appropriate |
| Tone | Formal vs informal varies by culture |
| Features | Highlight features relevant to local needs |
| Social proof | Use local press, local user counts if possible |
| Pricing | Local pricing expectations (purchasing power parity) |
Localization Workflow
Phase 1: Research (per market)
- Analyze top 10 apps in your category in the target market
- Run keyword research with local seed terms
- Identify local competitors and their positioning
- 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
- Submit localized metadata
- Monitor keyword rankings in each market (weekly)
- Track conversion rate by country
- 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
| Market | Size | Competition | Effort | Revenue | Score | Priority |
Related Skills
keyword-research— Run for each target marketmetadata-optimization— Write localized metadatascreenshot-optimization— Localize screenshot designscompetitor-analysis— Analyze local competitors
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
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.

