From terminal-guru
This skill should be used when the user asks to "configure sesh.toml", "create a dev environment", "build a session template", "set up sesh config", "add a sesh wildcard", "configure startup command", "create workspace with sesh", "clean up worktrees", "resume my session", "debug environment decay", or needs help composing development environments from sesh, claude CLI, direnv, and git worktrees. Also trigger on mentions of sesh.toml, environment composition, session templates, sesh wildcards, or teardown patterns. Do NOT use for general tmux session management, display issues, or keybindings (use terminal-emulation instead). Do NOT use for worktree lifecycle management (use chronicle instead). Do NOT use for signal handling or system logging (use signals-monitoring instead).
How this skill is triggered — by the user, by Claude, or both
Slash command
/terminal-guru:environment-compositionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Compose development environments by combining sesh (tmux session manager), claude CLI, direnv, and git worktrees. Sesh's config system (`sesh.toml`) is the foundation layer — it already implements most of the composition pattern natively through session declarations, wildcard templates, reusable windows, and startup commands.
Compose development environments by combining sesh (tmux session manager), claude CLI, direnv, and git worktrees. Sesh's config system (sesh.toml) is the foundation layer — it already implements most of the composition pattern natively through session declarations, wildcard templates, reusable windows, and startup commands.
When suggesting compositions, use the Lens framework as a mental checklist: Selection (which project/directory/worktree), Arrangement (tmux windows, startup commands, claude session), Purpose (what task this environment serves), Activation (how to trigger it — sesh wildcard, picker, zoxide). Favor sesh-native solutions — output sesh.toml config snippets that users add to their own config.
sesh.toml configurations (sessions, wildcards, windows, startup commands)Sesh's sesh.toml is the primary tool for defining and managing development environments. It supports named sessions, wildcard patterns for project categories, reusable window definitions, startup commands, config imports, and multiple picker integrations.
See references/sesh_config_guide.md for the complete config reference including all sesh.toml sections, subcommands, picker integrations, and naming strategies.
The claude --continue flag resumes the most recent conversation in the current directory — this naturally pairs with sesh's directory-based session creation. Combined with --worktree --tmux for native worktree+session creation, claude CLI integrates directly into the sesh workflow.
See references/claude_cli_composition.md for session management flags, project configuration (CLAUDE.md, .claude/, MCP), worktree integration, and direnv patterns.
Four workflow categories cover the full environment lifecycle:
--continue or startup_commandSee references/workflow_patterns.md for patterns, commands, and diagnostic checklists.
Users' sesh.toml (at ~/.config/sesh/sesh.toml) naturally serves as local state for environment composition. The agent suggests config snippets — [[session]], [[wildcard]], startup_command entries — that users add to their own config. No separate state file needed. Proven patterns can graduate to skill references.
[[session]] or [[wildcard]] entry in sesh.toml with startup_command and windowssesh connect <project> to create the sessionclaude --continue to resume AI contextgit worktree add ../project-feat feat-branchsesh connect to each worktree directory (auto-named by sesh)claude --continue contextsesh picker or sesh connect --roottmux list-sessionsgit worktree list + branch verificationsesh list -c against actual directoriesreferences/workflow_patterns.md for the full decay detection checklistsesh clone [email protected]:org/repo.git — clones and creates sessionsesh.toml automatically apply startup commands and windowsclaude --continue to start AI-assisted work in the new projectsesh_config_guide.md — Comprehensive sesh v2.24+ reference: config system, subcommands, picker integrations, naming strategyclaude_cli_composition.md — Claude CLI features for environment composition: session management, project config, worktree integration, direnv patternsworkflow_patterns.md — Environment lifecycle patterns: setup, worktree composition, teardown, decay detectiontmux_session_management.md — General tmux keybindings, pane logging, session persistenceworktrees-experiments.md — Git worktree lifecycle patterns (create, evaluate, cleanup)npx claudepluginhub totallygreg/claude-mp --plugin terminal-guruCreates, lists, and cleans up Git worktrees for parallel Claude Code sessions on separate branches, enabling conflict-free multi-feature development.
Creates and manages multi-repo workspaces for AI coding assistants (Claude Code, Codex) by unifying configs from sibling git repos and supporting worktree-based feature branches.
Spawns and manages persistent tmux-based Claude Code CLI sessions with bidirectional communication. Subcommands: spawn, send, read, status, list, kill for parallel peer orchestration and multi-turn steering.