tmux
tmux Process Management
Session Reuse Rules
These are hard requirements, not suggestions:
- MUST check
tmux has-sessionbefore ever callingtmux new-session - MUST derive session name from
git rev-parse --show-toplevel, never hardcode - MUST add windows to an existing project session, never create a parallel session
- MUST use
send-keysto run commands, never pass inline commands tonew-session - NEVER create a new session if one already exists for the current project
One project = one tmux session. Multiple processes = multiple windows within that session.
Interactive Shell Requirement
Use send-keys pattern for reliable shell initialization. Creating a session spawns an interactive shell automatically. Use send-keys to run commands within that shell, ensuring PATH, direnv, and other initialization runs properly.
More from 0xbigboss/claude-code
react-best-practices
Use when reading or writing React components (.tsx, .jsx files with React imports).
2.6Ktypescript-best-practices
Use when reading or writing TypeScript or JavaScript files (.ts, .tsx, .js, tsconfig.json).
2.1Kpython-best-practices
Use when reading or writing Python files (.py, pyproject.toml, requirements.txt).
1.3Kweb-fetch
Fetches web content as clean markdown by preferring markdown-native responses and falling back to selector-based HTML extraction. Use for documentation, articles, and reference pages at http/https URLs.
780zig-best-practices
Use when reading or writing Zig files (.zig, build.zig, build.zig.zon).
349nix-best-practices
Use when working with Nix flakes, overlays, shell.nix, or flake.nix files.
318