How this skill is triggered — by the user, by Claude, or both
Slash command
/de:serveThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Manage development servers using tmux. Reads `serve:` config from `dev-env.yaml`.
Manage development servers using tmux. Reads serve: config from dev-env.yaml.
Subcommands:
start (default) - Start dev servers in tmuxstop - Stop all dev serversattach - Reattach to existing tmux sessionstatus - Show server status and portsStart options:
--windows - One tmux window per process (default: panes in one window)--session - Create a new tmux session (default when not already in tmux)When inside tmux, the default is to open servers in the current session. Combine flags for all four layouts:
| Flags | Behavior |
|---|---|
| (none) | New window with panes in current session |
--windows | Separate window per process in current session |
--session | New tmux session with panes |
--windows --session | New tmux session with separate windows |
Examples:
/de:serve - Start servers (default layout)/de:serve start --windows - One window per process/de:serve start --session - New session with panes/de:serve stop - Stop servers/de:serve status - Check statusRun (script is at the plugin root, two levels above this skill's base directory):
!lib/dev-env.sh serve $ARGUMENTS
After starting, tell the user:
de serve stop)npx claudepluginhub danielcarmingham/dev-envManages TMUX background processes: starts services in named panes of a 'claude-controlled' window, checks output, restarts, finds existing panes by title.
Manages tmux sessions, windows, and panes for persistent remote workflows and shell scripting automation. Useful for long-running processes, SSH disconnects, and multi-pane terminal layouts.
Generates bash scripts for dev server lifecycle (start/stop/status/ports) from detected project structure and package manager (pnpm/bun/yarn/npm/Cargo/Go).