manaflow-ai/cmux

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.

All-time #3757 Trending #2547 First seen Jun 9, 2026
8-week activity · all time api

Installation

$ npx skills add manaflow-ai/cmux --skill cmux-localization

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from manaflow-ai/cmux · top by installs.

npx skills add manaflow-ai/cmux

Browse all from manaflow-ai/cmux

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 26.9K
License LICENSE
Default branch main
Open issues 1,826
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,149 B
  • docs SUMMARY.md 237 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3,700 installs

SKILL.md

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).