Skip to content
cccskills
FreePublished on GitHub

cmux-localization

Update cmux interface text across supported languages and audit the results. The workflow identifies changed messages, prepares translation entries, and checks for missing translations, plural forms, and placeholders that insert values into text.

OriginalShow the original 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.

See how to install

Good for

  • Translating new interface and settings text
  • Finding translation gaps after English edits
  • Checking plural forms and placeholders
  • Keeping web and documentation languages aligned

Files included (3)

  • SKILL.md5.2 KB
  • agents/openai.yaml324 B
  • references/audit-workflow.md1.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

cmux Localization

Use this skill for any user-facing string change.

Normal contributor flow

After adding or changing user-facing copy, run ./scripts/localize-changes.

The command compares the current worktree with the mainline base, discovers changed Swift localization keys and English web messages, prepares simple new or changed macOS catalog entries with minimal edits, and writes a machine-readable translation packet under git metadata. Fill value for simple translations or localization for plural or variant entries, then run the same command again. When an existing translation is still correct after an English change, fill value with that same text; the packet remembers the confirmation so later runs do not mark it for review again. Completed macOS rows are imported through scripts/localization_catalog.py merge, and scripts/localization_catalog.py check remains the final authoritative validator.

Use --base <ref> for another comparison base and --work-file <path> when a translation helper needs a visible packet. The default packet stays outside the worktree. Ambiguous catalog ownership, a key whose Swift call sites (changed or not) disagree on defaultValue, count-like new strings, unsupported Swift literal forms, and invalid generated translations stop with a concrete human-attention item so the existing placeholder, plural, bidi, omission, identity-translation, copied-English, and catalog checks stay intact.

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. Every feature PR includes translated entries for all supported macOS languages required by scripts/localization_catalog.py (currently en, de, fr, ar, es, zh-Hant, zh-Hans, ko, ja), subject to the exact omission records below. English and Japanese entries are always required.
  • defaultValue, English fallback text, schema descriptions, and copied English strings do not count as localization. Record deliberate invariant literals in scripts/localization-allowed-omissions.json, with the exact source and omission class. A correct translation that shares the English spelling needs a documented identityLocales exception for that key and locale; the translated entry remains required.
  • Localized web/docs content updates every locale declared by web/i18n/routing.ts, with a matching web/messages/<locale>.json entry 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:

Run ./scripts/localize-changes first and resolve every reported translation row or human-attention item.

  1. Enumerate the changed user-facing surfaces.
  2. Verify each surface has a catalog key and translated values for every supported macOS locale (en, de, fr, ar, es, zh-Hant, zh-Hans, ko, ja) in the feature PR, unless an exact omission record allows an absent value. Omission records still require en and ja entries.
  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.

Resources/Localizable.xcstrings, Resources/InfoPlist.xcstrings, and the linked macOS package catalogs must pass python3 scripts/localization_catalog.py check. New keys must carry all nine macOS locale entries unless covered by an exact omission record; en and ja entries remain required. Preserve printf placeholders and use plural variations for count strings where the source has a count.

Count strings are recorded in scripts/localization-plurals.json with the English source and the argument numbers that select plurals. Every required plural category must contain translated text. Use substitutions when more than one count varies or when the count is not the first argument. Arabic requires zero/one/two/few/many/other; French and Spanish include many. Keep every message inside the catalog's strings object so Xcode compiles it.

For a shared-spelling word inside a plural substitution, use an identityLocales object with reason and an explicit values list. This permits the listed leaf text (for example French %d machines) while continuing to reject an untranslated English sentence around it.

Detailed reference

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

cmux

FreeSummary

Organize cmux windows, workspaces, and split panes so an agent can target the right terminal reliably. Create terminals with startup commands, move or reorder panels, change focus, and flash a panel to identify it.

  • Arrange terminals for several tasks
  • Start a development command in a new split
  • Move or reorder panels
manaflow-ai/cmux28.3KUpdated Oct 18, 2026

Guide substantial Swift changes in cmux with rules for package boundaries, dependency direction, state management, concurrency, and API documentation. Structure code so public package types can be tested without launching the app.

  • Extracting a large app feature into Swift Packages
  • Reviewing dependencies between UI, domain models, and services
  • Restructuring state management and Swift 6 concurrency
manaflow-ai/cmux28.3KUpdated Oct 18, 2026

cmux-backend

FreeSummary

Guide cmux backend changes with consistent rules for Effect, a TypeScript library for structured error handling. Covers Cloud VM state, database migrations, provider integrations, and authentication and payment checks so changes follow the intended architecture.

  • Implementing API error handling
  • Updating Cloud VM lifecycle logic
  • Preparing database migrations
manaflow-ai/cmux28.3KUpdated Oct 18, 2026

cmux-billing

FreeSummary

Maintain cmux billing code with guidance on Stripe checkout, pricing, subscriptions, and access rights. It maps the relevant services and provides workflows for testing purchases, handling payment events, and rolling out billing changes.

  • Debugging checkout and subscription records
  • Updating prices and plan switching
  • Checking paid access and Cloud VM limits
manaflow-ai/cmux28.3KUpdated Oct 18, 2026

cmux-browser

FreeSummary

Automate browsing in cmux panels without taking focus away from current work. Target a specific panel to open pages, fill forms, click controls, wait for page changes, extract content, and inspect download history.

  • Open and inspect sites without changing focus
  • Fill forms and check the result
  • Extract page text or HTML
manaflow-ai/cmux28.3KUpdated Oct 18, 2026

cmux-capture

FreeSummary

Capture cmux windows as screenshots or video clips from the CLI. Create visual evidence for pull requests and bug reports, with region selection and captions to explain drags, animations, or layout changes.

  • Attaching screenshots of visual changes to a pull request
  • Recording drags and animations for a bug report
  • Capturing a specific window region with explanatory captions
manaflow-ai/cmux28.3KUpdated Oct 18, 2026

See all skills by manaflow-ai

Report a problem with this skill