Cmux Shared Behavior
- 2.5k installs
- 25.6k repo stars
- Updated August 5, 2026
- manaflow-ai/cmux
cmux-shared-behavior is an agent skill that enforces unified mutation paths and optimistic UI rules across cmux entrypoints for developers building features exposed via CLI, settings, shortcuts, and command palette.
About
cmux-shared-behavior is a cross-cutting agent skill in the manaflow-ai/cmux repository, added alongside skills like cmux-backend, cmux-socket-policy, and cmux-release in a PR wiring repo skills into .claude/skills and .agents/skills. The SKILL.md defines shared behavior policy extracted from CLAUDE.md: when a feature appears on multiple surfaces—keyboard shortcut, command palette, context menu, CLI, settings, or debug menu—implement one shared action/model path and verify every entrypoint. Optimistic UI and CLI updates must use a single mutation path with request IDs, authoritative reconciliation, and explicit rollback on failure. Agents also add behavior-level tests around exact repro paths when users report missed bugs. Use cmux-shared-behavior when patching cmux features that span UI and socket/CLI surfaces to prevent duplicated logic and divergent optimistic state.
- Cross-client behavior contracts
- State and event consistency rules
- Agent capability alignment
- Reusable interaction patterns
Cmux Shared Behavior by the numbers
- 2,453 all-time installs (skills.sh)
- +303 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #357 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/manaflow-ai/cmux --skill cmux-shared-behaviorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.5k |
|---|---|
| repo stars | ★ 25.6k |
| Last updated | August 5, 2026 |
| Repository | manaflow-ai/cmux ↗ |
How do cmux features stay consistent across entrypoints?
Enforce consistent cmux interaction patterns, state handling, and cross-surface UX rules so agents and clients behave uniformly.
Who is it for?
Developers contributing to cmux who expose the same behavior through CLI socket commands, settings UI, and keyboard shortcuts.
Skip if: Projects unrelated to cmux or features confined to a single UI surface with no shared mutation path.
When should I use this skill?
A cmux behavior spans keyboard shortcuts, command palette, CLI, settings, or optimistic UI and risks duplicated logic.
What you get
Shared action/model implementation, verified multi-entrypoint coverage, and behavior-level tests on the repro path.
- Unified shared action/model code path
- Multi-entrypoint verification checklist
- Behavior-level regression tests
By the numbers
- SKILL.md defines policy across 6 named entrypoint types
- Added among 6 new cmux agent skills in repository PR #5614
Files
cmux Shared Behavior
Use one shared action/model path when behavior is exposed through multiple entrypoints.
Shared entrypoints
When a behavior is exposed through multiple surfaces, implement one shared action/model path and verify every entrypoint that should invoke it.
Common entrypoints include:
- keyboard shortcut
- command palette
- context menu
- CLI/socket command
- settings UI
- debug menu
Do not patch one surface while leaving the others with duplicated logic.
Optimistic updates
For optimistic UI or CLI updates:
- keep one mutation path
- record pending state with a request id or previous snapshot
- reconcile from the authoritative result
- handle failure with an explicit rollback or error state
Do not 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.
interface:
display_name: "cmux Shared Behavior"
short_description: "Keep multi-entrypoint behavior and optimistic updates on one shared path."
default_prompt: "Use this skill when changing behavior exposed through multiple cmux entrypoints, optimistic UI or CLI mutation flows, or tests that previously missed a user-visible bug."
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Use cmux-shared-behavior for cross-surface consistency; use cmux-socket-policy when the issue is main-thread blocking or socket threading rules.
FAQ
Which cmux entrypoints does cmux-shared-behavior cover?
cmux-shared-behavior applies when behavior is exposed through keyboard shortcuts, command palette, context menu, CLI/socket commands, settings UI, or debug menu, requiring one shared implementation verified on each surface.
How should optimistic updates work in cmux?
cmux-shared-behavior mandates a single mutation path, pending state tracked with a request id or snapshot, reconciliation from the authoritative result, and explicit rollback or error handling—never per-entrypoint optimistic copies.