localization▌

Internationalization (i18n) and Localization (L10n) best practices.

Use this skill to bulk-create or bulk-update display names (and descriptions) for subscriptions, subscription groups, and in-app purchases across all App Store Connect locales. This eliminates the tedious manual process of clicking through each language in App Store Connect to set the same display name.

Comprehensive guide to app localization using String Catalogs. Apple Design Award Inclusivity winners always support multiple languages with excellent RTL (Right-to-Left) support.

Guides localization strategy for AI/SaaS products expanding into global markets. Covers i18n implementation, translation, pricing, and marketing adaptation--not just text translation.

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.

Bulk-localize subscription and in-app purchase display names across all App Store Connect locales. \n \n Supports localization of subscriptions, subscription groups, and in-app purchases across 37 App Store locales with separate create and update commands for each entity type \n Workflow includes listing existing localizations to avoid duplicates, creating missing ones per locale, and verifying completion with table output \n Handles both single display names applied uniformly across all locales

Localize VS Code extensions across configurations, walkthrough content, and source code messages. \n \n Three localization approaches: package.nls.LANGID.json for settings, commands, menus, and views; markdown files for walkthrough content; bundle.l10n.LANGID.json for source code strings \n Covers all user-facing resources including contributed configurations, commands, menus, views, ViewsWelcome, and walkthrough titles and descriptions \n Requires creating or updating localization files for all

Internationalization and localization patterns for multi-language app support. \n \n Covers core i18n concepts, implementation patterns for React, Next.js, and Python, and file structure organization for managing translations across locales \n Includes best practices for using translation keys, namespacing, pluralization, date/number formatting, and ICU message format to avoid common pitfalls \n Provides RTL (right-to-left) layout guidance using CSS logical properties for languages like Arabic a

$22

$22