AGENT SKILL

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.

License 许可
MIT
所属仓库
Necmttn/skills
最近更新
2026-11-07
Stars
★ 0
Forks
0

01 前言 Front Matter

name
localization
metadata
{ "version": "1.0.0" }
description
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.

03 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)

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:

  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

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)

  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

Market Size Competition Effort Revenue Score Priority

Related Skills

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

04 同仓库更多 Skills

Necmttn
Necmttn/skills

wiki

Recall from the personal LLM wiki at ~/wiki. Use when the user asks what the wiki says, wants prior thinking/intuition on a concept, or when grounding a design or decision in previously synthesized knowledge. Read-only - never writes to the wiki.

★ 0
Necmttn
Necmttn/skills

wiki-ingest

Curate a source into the personal LLM wiki at ~/wiki following its SCHEMA.md - a file, URL, research output, ax session, or a pending ~/wiki/inbox/ brief. Use when the user says "add this to the wiki", "ingest this", "promote the inbox", or after research worth keeping long-term.

★ 0
Necmttn
Necmttn/skills

wiki-harvest

Propose-only sweep of recent coding sessions (via the ax CLI) for recurring concepts that are missing from, or should update, the personal LLM wiki at ~/wiki. Writes candidate briefs to ~/wiki/inbox/ only - never wiki pages. Use on schedule or when the user asks "harvest the wiki" or "what concepts am I repeating".

★ 0
Necmttn
Necmttn/skills

no-ai-slop

Strip AI-slop patterns from a draft while preserving the writer's voice, or detect slop without rewriting. Use as the mandatory final pass on any copy before shipping, when the user wants a draft clearer/less AI-sounding, or when asked "is this AI slop?", "audit this writing", "does this read as AI".

★ 0
Necmttn
Necmttn/skills

aso-appstore-screenshots

Generate high-converting App Store screenshots by analyzing your app's codebase, discovering core benefits, and creating ASO-optimized screenshot images using Nano Banana Pro.

★ 0
Necmttn
Necmttn/skills

app-idea

Run a new or existing consumer/AI app idea through the golden-track playbook (~/wiki/playbook/apps.md) from intake to verdict, write a verdict card, stop for the owner, and ratchet owner overrides back into the doctrine. Use when the user shares an app idea, asks "should I build X", "audit <app>", "re-score <app>", or pastes an idea in a product context. Never builds; never promotes a rule on its own.

★ 0