cmux-shared-behavior

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗

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, debug menu, optimistic UI, or tests that previously missed a bug.

skills/cmux-shared-behavior/SKILL.md

Download bundle ↓
main · 6f118af2 bundle filesScanned 2026-09-15

SKILL.md

216 tokens · o200k_base · 1,095 bytes

Source excerpt starting at line 1.
---name: cmux-shared-behaviordescription: "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, debug menu, 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, debug menu), 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. ## 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. 
Discovery context

Discovered by repository scan. No exact path reference found in the snapshot’s root CLAUDE.md.