app-localization

Manage .strings localization files for Tuist-based iOS and macOS apps.

38|6|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/tddworks/claude-skills --skill app-localization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-localization
Source: https://github.com/tddworks/claude-skills/tree/main/skills/tuist-app-localization
Command: npx skills add https://github.com/tddworks/claude-skills --skill app-localization

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of managing localization files (.strings) for iOS and macOS applications built with Tuist, ensuring consistency and reducing errors.

Core Features & Use Cases

  • Key Management: Add new translation keys across all supported languages.
  • Validation: Detect missing keys, duplicate keys, and placeholder mismatches in .strings files.
  • Translation Syncing: Identify and report missing translations between languages.
  • AI-Assisted Translation: Translate English strings to other locales, preserving placeholders.
  • Code Integration: Update Swift code to use generated type-safe localization accessors.
  • Use Case: You've added a new feature to your app and need to add new strings for French, Spanish, and German. This Skill helps you add the keys, validate them, and even provides AI-powered translations for the new content.

Quick Start

Use the app-localization skill to add a new translation key named "newFeature.title" with the English value "New Feature" to all .strings files in the "MyApp" module.

Frequently Asked Questions about app-localization

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

FAQPage Schema
How do I automate .strings file localization for a Tuist iOS project?

You can automate .strings file localization for a Tuist iOS project by using a skill that manages translation keys, validates file integrity, and syncs translations across all supported locales. It handles adding keys and checking placeholder consistency automatically.

What is the best way to sync missing translations across iOS locales?

The best way to sync missing translations across iOS locales is to run a validation process that identifies missing keys and reports discrepancies between languages. This ensures your .strings files remain consistent and complete across all supported regions.

Can I generate AI-powered translations for English strings in macOS apps?

Yes, you can generate AI-powered translations for English strings in macOS apps. The translation process converts English content to other locales while preserving placeholders, ensuring structural integrity within your .strings files.

How do I validate .strings files for duplicate keys and placeholder mismatches?

You validate .strings files for duplicate keys and placeholder mismatches by running an automated integrity check. This process detects missing keys, duplicates, and placeholder formatting errors to ensure localization files remain structurally sound.

Does this localization tool work with Swift code to use type-safe localized strings?

Yes, this localization tool works with Swift code to use type-safe localized strings. It updates Swift code by integrating generated type-safe localization accessors, ensuring your application directly references the validated .strings entries.

Why do I need Tuist for managing iOS app localization?

You need Tuist for managing iOS app localization because this skill is specifically designed for Tuist-based projects to handle .strings files. It relies on the Tuist project structure to properly sync translations, validate keys, and update Swift code.