Agent Skills › manaflow-ai/cmux › cmux-localization

cmux-localization

GitHub

规范 cmux UI 字符串本地化流程，强制所有用户可见文本必须通过键值对进行国际化。要求修改涉及 UI、文档或配置时执行本地化审计，确保关键文件与多语言目录同步更新。

skills/cmux-localization/SKILL.md manaflow-ai/cmux

触发场景

修改 SwiftUI 或 AppKit 界面文本更新 Web 消息目录或文档内容变更设置项、菜单或工具提示文案

安装

npx skills add manaflow-ai/cmux --skill cmux-localization -g -y

更多选项

不安装直接使用

npx skills use manaflow-ai/cmux@cmux-localization

指定 Agent (Claude Code)

npx skills add manaflow-ai/cmux --skill cmux-localization -a claude-code -g -y

安装 repo 全部 skill

npx skills add manaflow-ai/cmux --all -g -y

预览 repo 内 skill

npx skills add manaflow-ai/cmux --list

SKILL.md

Frontmatter

{
    "name": "cmux-localization",
    "description": "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:

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.