capacitor-localizationlisted
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(