localization-strategy
Localization and internationalization strategy for iOS/macOS apps. Covers market prioritization, language tier recommendations, minimum viable localization levels, translation workflows, cultural adaptation, localized ASO, and testing. Use when planning localization, expanding to new markets, deciding which languages to support, or planning translation workflow.
Profile →npx skills add rshankras/claude-code-apple-skills --skill localization-strategy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
End-to-end localization planning for Apple platform apps — from market prioritization through translation workflow to localized App Store optimization.
How it works
- Phase 1: Market Prioritization Framework ranks languages by revenue potential and category-specific priorities, then uses AskUserQuestion to gather app category, current markets, and budget.
- Phase 2: Language Tier Recommendations split into Tier 1 (highest ROI), Tier 2 (good ROI), and Tier 3 (volume play); provides per-language markets and estimated revenue lift, with a plan to localize 2-3 Tier 1 languages first and iterate.
- Phase 3: Minimum Viable Localization Levels defines Level 0 (metadata-only), Level 1 (metadata + UI strings), Level 2 (full localization) with costs, effort, and best-use cases; prescribes a stepwise rollout.
- Phase 4: Translation Workflow covers Xcode String Catalogs usage, export/import steps, best practices for commenting and placeholders, translation service options with costs, and an AI+human review workflow including validation steps.
- Phase 5: Cultural Adaptation addresses date/time/number formats using Foundation formatters, currency display, color meanings, layout direction for RTL, and image/icon localization guidance.
- Phase 6: Localized App Store Optimization (ASO) explains why localization matters, keyword research by market, and localized screenshot strategies, plus competitor analysis via WebSearch.
When to use it
Use when planning localization, expanding to new markets, deciding which languages to support, or planning translation workflow.
What it can touch
- Xcode String Catalogs (.xcstrings) for export/import workflows
- Translation services and costs per language
- App Store metadata, screenshots, and in-app localization considerations
- WebSearch and native speaker reviews for keyword and competitor analysis
Caveats
- Costs and timelines are language- and app-size dependent (e.g., Level 0 vs Level 2, per-language costs). Specific figures are provided in the plan but subject to translation scope and market conditions.
- RTL and cultural adaptations introduce additional dev considerations (layout mirroring, UI adjustments).
- Review requires native speaker validation.
# Localization Strategy End-to-end localization planning for Apple platform apps — from market prioritization through translation workflow to localized App Store optimization. ## When This Skill Activates Use this skill when the user: - Wants to localize their app for new markets - Asks "which languages should I support?" - Needs help deciding market expansion priorities - Wants to plan a translation workflow - Asks about internationalization (i18n) best practices - Mentions "localization", "translation", "multi-language", or "global markets" - Wants to understand localization ROI by language - Needs cost estimates for translation - Asks about right-to-left (RTL) layout support - Wants to localize App Store metadata (title, description, keywords, screenshots) ## Process ### Phase 1: Market Prioritization Framework Not all languages are equal. Prioritize by revenue potential, not just speaker count. #### Revenue Potential by Language Based on App Store revenue data and per-user spending patterns: | Language | Relative Revenue Potential | Why | |----------|---------------------------|-----| | English | Baseline (1.0x) | Largest single market, highest per-user spend | | Japanese | 0.8
- When This Skill Activates
- Process
- Phase 1: Market Prioritization Framework
- Phase 2: Language Tier Recommendations
- Phase 3: Minimum Viable Localization Levels
- Phase 4: Translation Workflow
- Phase 5: Cultural Adaptation Beyond Translation
- Phase 6: Localized App Store Optimization (ASO)
- Phase 7: Testing Localized Builds
- Output Format
- Integration with Other Skills
- Common Mistakes to Avoid
- Translating keywords literally
- Hardcoding date/number formats
What does the localization-strategy skill do?
Localization and internationalization strategy for iOS/macOS apps. Covers market prioritization, language tier recommendations, minimum viable localization levels, translation workflows, cultural adaptation, localized ASO, and testing. Use when planning localization, expanding to new markets, deciding which languages to support, or planning translation workflow.
How do I install it?
Run `npx skills add rshankras/claude-code-apple-skills --skill localization-strategy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rshankras/claude-code-apple-skills, a repository with 589 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.