localization-setup

Generate type-safe localization infrastructure for iOS and macOS apps.

27|5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/bocan/bocan-music --skill localization-setup-bocan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localization-setup
Source: https://github.com/bocan/bocan-music/tree/main/.claude/skills/generators/localization-setup
Command: npx skills add https://github.com/bocan/bocan-music --skill localization-setup-bocan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually setting up internationalization for iOS and macOS apps is time-consuming and error-prone, requiring careful configuration of localization files, type-safe string wrappers, RTL layout adjustments, and pluralization rules that often lead to missing translations or broken layouts for global users.

Core Features & Use Cases

  • Automated i18n infrastructure generation: Creates type-safe string access enums, runtime localization managers, and SwiftUI preview helpers tailored to your project's deployment target.
  • Flexible localization support: Works with modern Xcode String Catalogs (recommended for iOS 16+/macOS 13+) or legacy .strings files, with built-in migration guidance for existing projects.
  • Global language compatibility: Includes built-in patterns for right-to-left (RTL) languages, pluralization rules, number/date formatting, and device-specific string variations.
  • Use Case: A developer building a native macOS music player can use this skill to quickly add support for 12+ languages, including Arabic RTL layout and pluralized track count strings, without manually writing hundreds of lines of localization boilerplate.

Quick Start

Use the localization-setup skill to generate complete multi-language support infrastructure for your iOS/macOS app, including type-safe string access, runtime language switching, and RTL layout helpers.

Frequently Asked Questions about localization-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up internationalization in a SwiftUI app?

Setting up internationalization in a SwiftUI app requires type-safe string access enums and runtime localization managers. This process generates production-ready code and SwiftUI preview helpers to eliminate manual boilerplate.

What is the best way to migrate legacy .strings files to Xcode String Catalogs?

Migrating legacy .strings files to Xcode String Catalogs is streamlined through built-in migration guidance. This approach updates your project to modern String Catalogs while preserving existing translations and adopting type-safe localized string access.

How do I handle right-to-left (RTL) language layouts in iOS and macOS apps?

Handling right-to-left (RTL) language layouts requires built-in pattern recognition for RTL compatibility. The setup automatically configures SwiftUI views and layout direction to properly support languages like Arabic without breaking your interface.

Does this localization approach work with both iOS and macOS deployment targets?

Yes, this localization infrastructure supports both iOS and macOS deployment targets. It generates code tailored to your project's specific deployment target, ensuring compatibility whether you use modern String Catalogs or legacy .strings files.

How do I implement pluralization rules for localized strings in Swift?

Implementing pluralization rules for localized strings involves generating built-in patterns for number and date formatting. This handles device-specific string variations and pluralized text automatically, preventing missing translations for global users.

Why does manual internationalization setup often lead to missing translations?

Manual internationalization setup leads to missing translations due to error-prone configuration of localization files and pluralization rules. Automating this infrastructure generates consistent, type-safe wrappers to prevent broken layouts and incomplete global support.