Localization logo

Localization

CommunityPopular
Eronred
localization

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.

Overview

PublisherEronred
Repositoryaso-skills
Skill namelocalization
Stars
1.9K
Forks
116
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Eronred on GitHub. Read the source before you install it.

Installation

Install the Localization AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Eronred/aso-skills.git /tmp/aso-skills
mkdir -p .claude/skills
cp -r /tmp/aso-skills/skills/localization .claude/skills/localization
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Localization in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Localization on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Localization is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Frequently asked questions

What does the Localization AI skill do?

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.

Why use Localization on TypingMind?

Because you install it once and use it with any model. Localization is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Localization in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Eronred/aso-skills/tree/main/skills/localization. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Localization?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Localization?

As many as you like. As long as a model supports skills, you can use Localization with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Localization AI skill free?

Yes. It is published on GitHub by Eronred under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇