cmux-shared-behavior
/cmux-shared-behavior
Shared behavior and mutation-path rules for cmux. Use when a behavior is exposed through multiple entrypoints such as keyboard shortcuts, command palette, context menu, CLI, settings, menu bar, optimistic UI, or tests that previously missed a bug.
- Author
- legotec73 ↗
- Repository
- CMUX ↗
- Licence
- GPL-3.0
- Last repository change
- 03.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.10.2026, without references to retired models or APIs.
GPL-3.0, otwarta.
What it does and when to use it
Shared behavior and mutation-path rules for cmux. Use when a behavior is exposed through multiple entrypoints such as keyboard shortcuts, command palette, context menu, CLI, settings, menu bar, optimistic UI, or tests that previously missed a bug.
Original author description
Shared behavior and mutation-path rules for cmux. Use when a behavior is exposed through multiple entrypoints such as keyboard shortcuts, command palette, context menu, CLI, settings, menu bar, optimistic UI, or tests that previously missed a bug.
How it works
- Shared entrypoints
- Optimistic updates
- Missed-bug coverage
SKILL.md preview
--- name: cmux-shared-behavior description: "Shared behavior and mutation-path rules for cmux. Use when a behavior is exposed through multiple entrypoints such as keyboard shortcuts, command palette, context menu, CLI, settings, menu bar, optimistic UI, or tests that previously missed a bug." --- # cmux Shared Behavior ## Shared entrypoints When a behavior is exposed through multiple surfaces (keyboard shortcut, command palette, context menu, CLI/socket command, settings UI, menu bar), implement one shared action/model path and verify every entrypoint that should invoke it. Do not patch one surface and leave the others with duplicated logic. In the app this path is one `ActionDescriptor` in `CmuxNextActions` plus one handler; the palette, shortcuts, menus, context menus and `cmux action` CLI are generated from the registry ([action contract](../../plans/cmux-next/REWRITE.md#action-contract-user-requirement-2026-09-28-every-feature-every-entrypoint)). ## Optimistic updates Keep one mutation path. Record pending state with a request id or a previous snapshot, reconcile from the authoritative result, and handle failure with an explicit rollback or error state. Never let each entrypoint maintain its own optimistic copy. ## Missed-bug coverage When a user says tests missed a bug, add or adjust behavior-level coverage around the exact repro path before claiming the fix is complete.
Files in this package (2)
- SKILL.md 1 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named cmux-shared-behavior.
Database snapshot: 13.11.2026 · package version 335e9436b1d1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100cmux-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. - 100cmux-settings
View and edit cmux settings in ~/.config/cmux/cmux.json. Use when the user wants to change cmux preferences (appearance, sidebar, notifications, automation, browser, shortcuts), set a value by JSON path, validate the file, open it in an editor, or look up which keys cmux… - 90cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs. - 100cmux-cli
Comprehensive cmux CLI usage guide. Use when the user asks about cmux CLI, cmux --help, socket commands, command discovery, workspaces, panes, surfaces, browser CLI, hooks, feed, settings, or automation through the cmux command. - 90cmux-next-feature
Lawrence's standing rules for every cmux-next feature, design or agent task. Use whenever you add or change any user-facing feature, action, setting, pane, sidebar item, daemon/store op, backend op, app/extension API, or agent capability in cmux-next (Swift app, Rust… - 100cmux-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.