← ClaudeAtlas

localization-i18nlisted

Audit and manage IN-APP localization for a macOS or iOS Xcode project — the user-facing strings inside the app (Localizable.strings / .xcstrings String Catalogs), NOT the App Store listing text. Use this whenever the user wants to localize or translate the app's UI ("תתרגם את האפליקציה", "תוסיף שפה"), add or check a language, find hardcoded (un-localized) strings in Swift, check that all locales have all keys (no missing / empty / untranslated strings), find unused or undefined string keys, migrate to String Catalogs, or handle RTL (e.g. Hebrew) and pluralization. For App Store listing metadata (name/description/keywords per language), that's the separate app-store-metadata skill.
yybd/app-factory · ★ 5 · AI & Automation · score 77
Install: claude install-skill yybd/app-factory
# Localization & i18n (in-app strings) > **Conversational language:** talk to the user — questions, summaries, reports — in **the language the user writes in** — unless a `conversational language` is set in the hub `DATA.md` (`$APP_HUB/DATA.md`), which overrides it. This sets the *conversation* language only — content/deliverables follow the app's target locales. This is about the strings **inside the app** that users read — buttons, labels, messages — across languages. The goal: every user-facing string is localizable, every locale is complete, and nothing is hardcoded or left untranslated. (App Store *listing* text is a different concern — `app-store-metadata`.) ## Prerequisites - **Tools:** none beyond Claude Code and Xcode; `scripts/scan_localization.py` is stdlib Python 3. - **Credentials:** none. - **Hub (`$APP_HUB`):** optional — only the conversational-language default in `DATA.md`. - **Other tracks:** `copy-edit` (shared-track) for the pass over added or translated strings; `capacitor-localization` (capacitor-track) owns the web layer of a Capacitor app. ## Workflow ### 1. Audit the current state ```bash python3 ${CLAUDE_PLUGIN_ROOT}/skills/localization-i18n/scripts/scan_localization.py <project-root> ``` It reports, across `Localizable.strings` and `.xcstrings` catalogs: - **Per-locale completeness** vs the base language: keys **missing**, **extra**, **empty**, or **untranslated** (value identical to the base — a strong hint it was never translated).