← ClaudeAtlas

capacitor-localizationlisted

Audit and manage the in-app localization of a Capacitor / web-shell app, whose UI strings live in JavaScript and HTML rather than in .strings, .xcstrings or strings.xml. Use whenever such an app needs a language checked, added or fixed, when a screen shows the wrong language or an empty label, when asked to find untranslated or hardcoded UI text, or when handling RTL in a bilingual app ("שפה לא נכונה", "תרגום באפליקציה"). It finds the failure this architecture hides: a lookup that falls back instead of failing, so a missing translation ships silently as the wrong language. For an Xcode project whose strings really are in String Catalogs, use localization-i18n instead — that skill has nothing to work on here. It covers the web layer's strings; native Apple localization is localization-i18n's job.
yybd/app-factory · ★ 5 · AI & Automation · score 77
Install: claude install-skill yybd/app-factory
# Capacitor Localization — strings that live in JS and HTML > **Conversational language:** talk to the user — questions, summaries, reports — in the `conversational language` set in the hub `DATA.md` (`$APP_HUB/DATA.md`); fall back to the language the user writes in if it is unset. This sets the *conversation* language only. ## Prerequisites - **Tools:** none beyond Claude Code — `scan_web_strings.py` is stdlib Python 3. - **Credentials:** none. - **Hub (`$APP_HUB`):** optional — only the conversational language from `DATA.md`; falls back to the language the user writes in. - **Other tracks:** `copy-edit` and `app-identity` (shared-track); `localization-i18n` (apple-track) for `.xcstrings` and Info.plist keys. ## Why this exists as its own skill A Capacitor app has native shells, and it is tempting to look for strings in them. They are not there. In one measured app: `strings.xml` holds **four lines** of plumbing (app name, activity title, package, url scheme), there are **no** `.strings` or `.xcstrings` files at all, and every user-facing word is in JavaScript object literals and paired HTML spans. `localization-i18n` — built on String Catalogs and Swift scanning — would report a clean bill of health on an app with no localization at all. The native surface that *does* exist (the launcher label, `CFBundleDisplayName`, the Play title) is owned by **`app-identity`**, not here. ## The failure this architecture hides The usual lookup is a fallback: ```js function t(