indie--localization-prioritizer/SKILL.md
Decide which markets to localize for and in what order. Use when considering localization, choosing languages to support, expanding internationally, or optimizing for global markets.
npx skillsauth add abanoub-ashraf/manus-skills-import indie--localization-prioritizerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an international app growth strategist who helps indie developers prioritize localization efforts for maximum ROI.
Localization is not just translation. It's unlocking entirely new markets with different economics.
The user wants to know which languages/markets to localize for.
Tier 1: High Revenue, English-Saturated | Market | Revenue Potential | Competition | Localization Effort | |--------|-------------------|-------------|---------------------| | 🇺🇸 United States | Very High | Very High | None (baseline) | | 🇬🇧 United Kingdom | High | High | Minor adaptations | | 🇨🇦 Canada | Medium-High | Medium | Minor adaptations | | 🇦🇺 Australia | Medium | Medium | None |
Tier 2: High Revenue, Localization Wins | Market | Revenue Potential | Competition | Localization Effort | |--------|-------------------|-------------|---------------------| | 🇯🇵 Japan | Very High | Medium-Low | High (complex) | | 🇩🇪 Germany | High | Medium | Medium | | 🇫🇷 France | High | Medium | Medium | | 🇰🇷 South Korea | High | Medium | High | | 🇨🇳 China | Massive | Very High | Very High (regulations) |
Tier 3: Growing Markets | Market | Revenue Potential | Competition | Localization Effort | |--------|-------------------|-------------|---------------------| | 🇧🇷 Brazil (PT-BR) | Medium-Growing | Low-Medium | Medium | | 🇲🇽 Mexico (ES-MX) | Medium | Low | Medium | | 🇮🇹 Italy | Medium | Medium | Medium | | 🇪🇸 Spain | Medium | Medium | Medium | | 🇳🇱 Netherlands | Medium | Low | Low (many speak EN) |
Tier 4: Long-tail | Market | Notes | |--------|-------| | 🇸🇪 Sweden | High English proficiency | | 🇵🇱 Poland | Growing market | | 🇹🇷 Turkey | Large but low spending | | 🇮🇩 Indonesia | Huge but low revenue per user | | 🇮🇳 India | Volume over value |
Localization ROI Score = (Market Size × Spending Power × Competition Gap) / Localization Cost
Where:
- Market Size = App Store users in market
- Spending Power = Average revenue per user
- Competition Gap = How much localized competition exists (less = better)
- Localization Cost = Translation + Adaptation + Maintenance
Consumer Productivity/Utility:
1. 🇩🇪 German (high ARPU, low competition when localized)
2. 🇯🇵 Japanese (premium users, loyalty)
3. 🇫🇷 French (large market, appreciates localization)
4. 🇪🇸 Spanish (covers Spain + LATAM)
5. 🇧🇷 Portuguese-BR (growing market)
Lifestyle/Health/Fitness:
1. 🇯🇵 Japanese (health-conscious, high spending)
2. 🇩🇪 German (quality-focused users)
3. 🇰🇷 Korean (tech-savvy, trend-following)
4. 🇫🇷 French (wellness culture)
5. 🇧🇷 Portuguese-BR (fitness culture)
Games/Entertainment:
1. 🇯🇵 Japanese (huge gaming market)
2. 🇰🇷 Korean (gaming culture)
3. 🇨🇳 Chinese (massive but complex)
4. 🇩🇪 German (strong market)
5. 🇷🇺 Russian (volume)
Business/Professional:
1. 🇩🇪 German (business users pay)
2. 🇯🇵 Japanese (corporate culture)
3. 🇫🇷 French (business market)
4. 🇪🇸 Spanish (broad reach)
5. 🇧🇷 Portuguese-BR (emerging businesses)
Minimum (ASO Localization):
Better (Partial):
Full Localization:
| Level | Per Language | Maintenance/Update | |-------|--------------|-------------------| | ASO Only | $50-200 | $20-50/update | | Partial (~500 strings) | $500-1000 | $100-200/update | | Full (~2000 strings) | $2000-4000 | $300-500/update |
Cost-saving options:
Phase 1: Test the Waters
Phase 2: Partial Localization
Phase 3: Full Investment
Translation:
Testing:
Before localizing, research:
Provide the user with:
development
Design principles for building polished, native-feeling SwiftUI apps and widgets. Use this skill when creating or modifying SwiftUI views, iOS widgets (WidgetKit), or any native Apple UI. Ensures proper spacing, typography, colors, and widget implementations that look and feel like quality apps rather than AI-generated slop.
data-ai
Design and implement SwiftUI views, components, and app architecture. Use when creating new SwiftUI views, implementing MVVM/TCA patterns, managing state with @Observable, @State, @Binding, or @Environment, designing navigation flows, or structuring iOS app architecture. Triggers on SwiftUI, view model, state management, navigation, coordinator pattern.
development
Implement, review, or improve SwiftUI animations and transitions. Use when adding implicit or explicit animations with withAnimation, configuring spring animations (.smooth, .snappy, .bouncy), building phase or keyframe animations with PhaseAnimator/KeyframeAnimator, creating hero transitions with matchedGeometryEffect or matchedTransitionSource, adding SF Symbol effects (bounce, pulse, variableColor, breathe, rotate, wiggle), implementing custom Transition or CustomAnimation types, or ensuring animations respect accessibilityReduceMotion.
testing
Audit SwiftUI views for accessibility (iOS + macOS) with patch-ready fixes