菜单
Terminal orchestration via tmux. Use for long-running processes, server management, parallel terminal sessions, and background task monitoring.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Interview the user relentlessly about a plan or design until branch-level decisions are resolved for execution.
Access Figma designs, extract design systems, and retrieve component specifications. Use when implementing UI from Figma mockups, extracting design tokens, or analyzing design files.
Enforce cost-aware MCP usage. Use when a task might trigger heavy external tools, web search, or broad context expansion. Prevents token burn by ensuring MCPs are only used when local context is insufficient.
Navigate the Warmplane mcp0 facade efficiently. Use when the active config exposes provider capabilities through `mcp0_*` tools and you need to discover or call provider tools without brute-force describing large capability sets. Trigger on requests involving mcp0, Warmplane, or provider work through the facade such as Linear, Notion, Figma, New Relic, Context7, grep.app, or Storybook tools.
Use this when the user needs to control Chrome, navigate to a page, inspect a tab, click or fill elements, take screenshots, or automate a browser flow with aeroxy/chrome-devtools-cli.
Guidelines for creating and managing implementation plans with citations
| name | tmux |
| description | Terminal orchestration via tmux. Use for long-running processes, server management, parallel terminal sessions, and background task monitoring. |
# Create new session
tmux new-session -d -s "op-dev"
# Run command in session
tmux send-keys -t "op-dev" "npm run dev" Enter
tmux list-sessions
tmux attach -t "op-dev"
tmux kill-session -t "op-dev"
Use op-{purpose} pattern for OpenCode-managed sessions:
| Session | Purpose |
|---|---|
op-dev | Development server |
op-test | Test watcher |
op-build | Build process |
op-db | Database |
op-logs | Log tailing |
# Kill existing if any
tmux kill-session -t "op-dev" 2>/dev/null || true
# Create fresh session
tmux new-session -d -s "op-dev"
tmux send-keys -t "op-dev" "cd /path/to/project && npm run dev" Enter
# Capture last 50 lines
tmux capture-pane -t "op-dev" -p -S -50
# Create session with multiple windows
tmux new-session -d -s "op-work"
tmux send-keys -t "op-work" "npm run typecheck" Enter
tmux new-window -t "op-work"
tmux send-keys -t "op-work" "npm run lint" Enter
tmux new-window -t "op-work"
tmux send-keys -t "op-work" "npm run test" Enter
# Send command
tmux send-keys -t "op-build" "npm run build" Enter
# Wait and check output
sleep 5
tmux capture-pane -t "op-build" -p -S -20
# New window in session
tmux new-window -t "op-dev"
# New window with name
tmux new-window -t "op-dev" -n "logs"
# Horizontal split
tmux split-window -h -t "op-dev"
# Vertical split
tmux split-window -v -t "op-dev"
# Send to specific pane
tmux send-keys -t "op-dev:0.1" "tail -f logs.txt" Enter
tmux send-keys -t "op-dev" C-c
tmux send-keys -t "op-dev" C-d
tmux kill-pane -t "op-dev:0.1"
op- prefix# Start server in background
tmux new-session -d -s "op-server" "npm run dev"
# Verify it started
sleep 3
OUTPUT=$(tmux capture-pane -t "op-server" -p -S -10)
echo "$OUTPUT" | grep -q "Server started" && echo "✅ Server running"
# When done
tmux kill-session -t "op-server"