How do I install the Cmux Localization skill?

Run npx skillmds@latest add manaflow-ai/cmux-localization in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cmux Localization safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cmux Localization?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cmux Localization free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cmux Localization?

manaflow-ai (@manaflow-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cmux Localization by manaflow-ai — Agent Skill

Name: Cmux Localization
Rating: 4.666666666666667 (3 reviews)
Author: manaflow-ai

Cmux Localization

Localization rules and audit workflow for cmux UI strings, settings rows, menus, shortcuts, schema/config text, docs, command/help text, alerts, tooltips, and web messages. Use whenever changing user-facing text.

manaflow-ai d851f47 3 files · 3.9 KB Updated Sep 9, 2026

File contents

cmux Localization

Use this skill for any user-facing string change.

Hard rules

Every user-facing string is localized. Never a bare string literal in SwiftUI Text(), Button(), alert titles, tooltips, menus, or dialogs.
Swift/AppKit/SwiftUI: String(localized: "key.name", defaultValue: "English text"), with keys in Resources/Localizable.xcstrings. Feature PRs add the key and English source value; translations for every supported language are completed in the release PR.
defaultValue, English fallback text, schema descriptions, and copied English strings do not count as localization. They are acceptable in feature PRs only when the release workflow tracks the key for translation.
Localized web/docs content updates every supported message catalog (currently web/messages/en.json and web/messages/ja.json) plus any localized data structures carrying inline translations.
A localization audit is required for every user-facing change.

Audit checklist

Before finishing a task that changes UI, Settings rows, menus, shortcut metadata, schema/config text, docs, command/help text, alerts, or tooltips:

Enumerate the changed user-facing surfaces.
Verify each surface has a catalog key in the feature PR. Verify translated values for every supported locale in the release PR.
Parse the touched localization files and compare changed message keys across locales.
Run rg over changed Swift/TS/TSX/docs files for newly introduced bare English.
State in the final handoff what audit was performed, or explicitly say what could not be verified.

Detailed reference

references/audit-workflow.md: what counts as user-facing, search patterns, and handoff wording.

New keyboard shortcuts also need docs and Settings entries; see ../cmux-keyboard-shortcuts/SKILL.md.

---name: cmux-localizationdescription: Localization rules and audit workflow for cmux UI strings, settings rows, menus, shortcuts, schema/config text, docs, command/help text, alerts, tooltips, and web messages. Use whenever changing user-facing text.--- # cmux Localization Use this skill for any user-facing string change. ## Hard rules - Every user-facing string is localized. Never a bare string literal in SwiftUI `Text()`, `Button()`, alert titles, tooltips, menus, or dialogs. - Swift/AppKit/SwiftUI: `String(localized: "key.name", defaultValue: "English text")`, with keys in `Resources/Localizable.xcstrings`. Feature PRs add the key and English source value; translations for every supported language are completed in the release PR. - `defaultValue`, English fallback text, schema descriptions, and copied English strings do not count as localization. They are acceptable in feature PRs only when the release workflow tracks the key for translation. - Localized web/docs content updates every supported message catalog (currently `web/messages/en.json` and `web/messages/ja.json`) plus any localized data structures carrying inline translations. - A localization audit is required for every user-facing change. ## Audit checklist Before finishing a task that changes UI, Settings rows, menus, shortcut metadata, schema/config text, docs, command/help text, alerts, or tooltips: 1. Enumerate the changed user-facing surfaces. 2. Verify each surface has a catalog key in the feature PR. Verify translated values for every supported locale in the release PR. 3. Parse the touched localization files and compare changed message keys across locales. 4. Run `rg` over changed Swift/TS/TSX/docs files for newly introduced bare English. 5. State in the final handoff what audit was performed, or explicitly say what could not be verified. ## Detailed reference - [references/audit-workflow.md](references/audit-workflow.md): what counts as user-facing, search patterns, and handoff wording. New keyboard shortcuts also need docs and Settings entries; see [../cmux-keyboard-shortcuts/SKILL.md](../cmux-keyboard-shortcuts/SKILL.md).

Frequently asked questions