swift-missing-translations

End-to-end loop: audit → translate → wire up Swift-side leaks → verify. Use when the user wants to localize an iOS app or hunt down strings that haven't been translated yet.

Step 0 — Reach shared understanding

Before running anything, derive what you can from the repo, then ask only what's left in a single batched message. Don't assume the source language.

Read first:

• find . -name "*.xcstrings" → catalog paths.
• For each catalog: sourceLanguage field, set of locales used (union of localizations keys).
• UI source roots — typical: Features/, Views/, App/, Components/, Screens/.
• In-app language picker? grep -rn "selectedLanguage\|@AppStorage.*lang" and look for \.locale injected at the root view. Determines whether references/wire-up.md §d applies.
• Sample 3 translated keys with placeholders to learn existing tone and the project's placeholder convention.

Ask only when not derivable:

• Tone and audience (kid-friendly second-person, professional B2B, etc.). Critical, not in the repo.
• Adding a brand-new locale? Only if the user named one not in the catalog.
• Dev/TestFlight quality vs App Store quality (the latter wants a native-speaker review pass after).