Reference terminal documentation for TTY/PTY, streams, signals, and cross-platform patterns
View on GitHubmwguerra/claude-code-plugins
terminal-specialist
February 1, 2026
Select agents to install to:
npx add-skill https://github.com/mwguerra/claude-code-plugins/blob/main/terminal-specialist/skills/terminal-docs/SKILL.md -a claude-code --skill terminal-docsInstallation paths:
.claude/skills/terminal-docs/# Terminal Documentation Reference Skill ## Overview This skill provides access to comprehensive terminal and shell systems documentation. Use this skill to look up exact configurations, code patterns, and best practices for terminal-related development. ## Documentation Location All documentation is stored in: `/home/mwguerra/projects/mwguerra/claude-code-plugins/terminal-specialist/skills/terminal-docs/references/` ## Directory Structure ``` references/ ├── 01-fundamentals.md # TTY/PTY concepts, terminal stack, device files ├── 02-streams.md # stdin, stdout, stderr, buffering behavior ├── 03-exit-codes.md # Exit status, POSIX codes, signal exits ├── 04-shells.md # Shell types, startup files, options ├── 05-dimensions.md # Terminal size, SIGWINCH, resize handling ├── 06-modes.md # Canonical/raw mode, termios flags ├── 07-job-control.md # Sessions, process groups, background jobs ├── 08-environment.md # TERM, PATH, locale, prompt variables ├── 09-signals.md # Signal handling, keyboard signals ├── 10-escape-sequences.md # ANSI codes, colors, cursor control ├── 11-redirection.md # Pipes, file descriptors, here docs ├── 12-windows.md # Windows console, ConPTY, PowerShell ├── 13-cross-platform.md # Portable patterns, platform differences └── 14-advanced.md # tmux, screen, recording, graphics ``` ## Usage ### When to Use This Skill 1. Before implementing terminal-related functionality 2. When debugging I/O or stream issues 3. To verify correct escape sequence syntax 4. To understand terminal mode behavior 5. For signal handling patterns 6. For cross-platform compatibility guidance ### Search Workflow 1. **Identify Topic**: Determine what documentation is needed 2. **Navigate to File**: Go to relevant documentation file 3. **Read Documentation**: Extract exact patterns 4. **Apply Knowledge**: Use in implementation ### Common Lookups | Topic | File | |-------