cmux-localization

Name: cmux-localization
Availability: InStock
Author: manaflow-ai

Enforce localization coverage for cmux user-facing strings across English and Japanese locales.

25.8k|2.2k|Updated Jan 28, 2026

Search Tags:#documentation #audit #localization #i18n #ui-strings #web-messages

Ready to run

npx skills add https://github.com/manaflow-ai/cmux --skill cmux-localization

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cmux-localization
Source: https://github.com/manaflow-ai/cmux/tree/main/skills/cmux-localization
Command: npx skills add https://github.com/manaflow-ai/cmux --skill cmux-localization

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Localization of all user-facing strings across cmux, with an auditable workflow to ensure consistency and compliance across languages.

Core Features & Use Cases

Enforces the use of localized strings via String(localized:..., defaultValue:...) in Swift code to avoid bare literals.
Centralizes translations in Resources/Localizable.xcstrings and synchronizes web/docs catalogs (web/messages/en.json, web/messages/ja.json).
Provides an auditable workflow described in references/audit-workflow.md to cover UI, settings, menus, tooltips, docs, and alerts.

Quick Start

Run a localization audit whenever you modify any cmux user-facing text to ensure full coverage.

Frequently Asked Questions about cmux-localization

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

FAQPage Schema

How do I audit and enforce localization coverage for user-facing UI strings?▼

You audit localization by enforcing String(localized: "key.name", defaultValue: "English text") in Swift code to eliminate bare literals, ensuring full coverage across English and Japanese locales.

What is the best way to synchronize web messages across en.json and ja.json files?▼

You synchronize web messages by updating web/messages/en.json and web/messages/ja.json alongside Resources/Localizable.xcstrings, maintaining translation consistency through an auditable workflow.

When do I need to run a localization audit during UI development?▼

You need to run a localization audit whenever you modify any cmux user-facing text, including settings changes, documentation updates, and web content, to ensure all strings have localized equivalents.

Does the String(localized:defaultValue:) Swift API work with xcstrings catalogs?▼

Yes, the String(localized:defaultValue:) Swift API centralizes translations in Resources/Localizable.xcstrings, providing an auditable workflow that covers UI, settings, menus, tooltips, docs, and alerts.

Why does my localized UI text show bare string literals instead of translated content?▼

Bare string literals appear because Swift code lacks the String(localized:..., defaultValue:...) wrapper; enforcing this pattern during a localization audit resolves the missing translation coverage.