# Cmux Shared Behavior

Shared behavior and mutation-path rules for cmux.

- Repository: https://github.com/manaflow-ai/cmux (28635 stars)
- Category: Design
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add manaflow-ai/cmux --skill cmux-shared-behavior -g -a claude-code -y`
Codex: `npx skills add manaflow-ai/cmux --skill cmux-shared-behavior -g -a codex -y`
Cursor: `npx skills add manaflow-ai/cmux --skill cmux-shared-behavior -g -a cursor -y`
Gemini CLI: `npx skills add manaflow-ai/cmux --skill cmux-shared-behavior -g -a gemini-cli -y`

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

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