Menu
Interactive terminal control via tmux for TUI apps, prompts, and long-running CLI workflows.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generates structured .code-task.md files from descriptions or PDD implementation plans. Auto-detects input type, creates properly formatted tasks with Given-When-Then acceptance criteria.
Use when testing Ralph's hat collection presets, validating preset configurations, or auditing the preset library for bugs and UX issues.
Lists all code tasks in the repository with their status, dates, and metadata. Useful for getting an overview of pending work or finding specific tasks.
Introspect, explain, and improve Ralph Orchestrator using its published llms.txt doc map. Use this skill whenever the user asks questions about Ralph's behavior, wants to understand how a Ralph internal works (event loop, hats, memories, tasks, backends, presets), debug an unfamiliar failure mode, or propose a code change to the ralph-orchestrator repo. The skill teaches the agent to discover authoritative answers from the live docs via llms.txt before guessing, and to scope improvements through the published architecture rather than the local checkout alone.
Run, monitor, resume, merge, and debug Ralph loops. Use this skill whenever the user asks to operate `ralph run` or `ralph loops`, inspect loop state, recover suspended loops, analyze diagnostics, or unblock merge queue issues.
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.
| name | tmux-terminal |
| description | Interactive terminal control via tmux for TUI apps, prompts, and long-running CLI workflows. |
| hats | ["developer","qa_tester"] |
| metadata | {"internal":true} |
Use tmux to drive interactive terminal sessions, including TUI workflows like ralph-tui. tmux lets you send keystrokes, capture screen output, and keep processes running between steps.
ralph-tui or any interactive CLI promptstmux installed (pre-installed on macOS)Verify:
tmux -V
Create a detached session:
tmux new-session -d -s <name>
Send commands (append Enter to execute):
tmux send-keys -t <name> "<command>" Enter
Capture screen output:
tmux capture-pane -t <name> -p
Kill session when done:
tmux kill-session -t <name>
Use send-keys with key names:
EnterC-c (Ctrl-C)C-d (Ctrl-D)TabEscapeUp, Down, Left, RightExamples:
tmux send-keys -t <name> Up
tmux send-keys -t <name> C-c
tmux new-session -d -s ralph-tui
tmux send-keys -t ralph-tui "cargo run -p ralph-tui" Enter
tmux send-keys -t ralph-tui Down
tmux send-keys -t ralph-tui Enter
tmux capture-pane -t ralph-tui -p -S -200
Use -S -200 to capture the last 200 lines when the screen is noisy.
capture-pane to confirm health (look for "listening" or "ready" text).C-c then kill-session.Example:
tmux new-session -d -s ralph-web
tmux send-keys -t ralph-web "cargo run -p ralph-cli -- web" Enter
tmux capture-pane -t ralph-web -p | rg -n "listening|ready"
tmux send-keys -t ralph-web C-c
tmux kill-session -t ralph-web