Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rshankras/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.
Passed 19 of 22 test cases with the skill, and 11 of 22 without it.
and 8 more in the full report
9 fixed10 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have a SwiftUI productivity app for iOS with roughly 1,200 user-facing strings. Currently, we only support English, but we want to expand into high-value global markets. Could you put together a complete localization roadmap report? Please include target market recommendations categorized by priority tiers, estimated budget breakdowns for different localization levels (from metadata-only to full content), recommended translation workflows using Xcode string catalogs, cultural and formatting adaptations we'll need, an App Store optimization plan for keywords and screenshots, a testing and QA checklist, and a phased timeline with success metrics.
| Checked | Without skill | With skill |
|---|---|---|
| recommends exporting localization packages via Xcode Export Localizations to generate .xcloc files | Missed | Passed |
| recommends Level 0 metadata testing in 2 to 3 Tier 1 markets prior to full UI string translation | Missed | Passed |
| recommends Japanese or German as Tier 1 markets for a productivity app | Passed | Passed |
The instructions your model reads when the skill loads.
End-to-end localization planning for Apple platform apps — from market prioritization through translation workflow to localized App Store optimization.
Use this skill when the user:
Not all languages are equal. Prioritize by revenue potential, not just speaker count.
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-1.2x | Extremely high willingness to pay, especially for subscriptions |
| Chinese (Simplified) | 0.6-0.9x | Massive volume, growing per-user spend, competitive market |
| German | 0.4-0.6x | High per-user spend, values quality and privacy |
| French | 0.3-0.5x | Large market across France, Canada, Africa |
| Korean | 0.3-0.5x | Tech-savvy users, high app spending per capita |
| Spanish | 0.3-0.4x | Huge population, lower per-user spend, growing market |
| Portuguese (Brazilian) | 0.2-0.4x | Large market, mobile-first users, growing economy |
Key insight: Japanese and German users often pay 2-3x more per user than Spanish or Portuguese users. Volume vs. value is the fundamental tradeoff.
test cases passed, vs 11 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.