Menu
Designing terminal user interfaces
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
Index of Build Systems Skills
Coordination patterns for distributed dataflow systems including barriers, epochs, and distributed snapshots
Windowing, sessionization, time-series aggregation, and late data handling for streaming systems
Comprehensive guide to GNU Debugger (GDB) for debugging C/C++/Rust programs. Covers breakpoints, stack traces, variable inspection, TUI mode, .gdbinit customization, Python scripting, remote debugging, and core file analysis.
Paxos consensus algorithm including Basic Paxos, Multi-Paxos, roles, phases, and practical implementations
Gossip protocols for disseminating information, failure detection, and eventual consistency in large-scale distributed systems
| name | tui-best-practices |
| description | Designing terminal user interfaces |
Use this skill when:
Use consistent, discoverable shortcuts:
Standard Conventions:
- q / Ctrl+C: Quit
- h/j/k/l or arrows: Navigate
- Enter: Select/Confirm
- Esc: Cancel/Back
- /: Search
- ?: Help
- Tab: Next field
- Shift+Tab: Previous field
Principles:
- Clear visual hierarchy
- Consistent spacing
- Meaningful borders
- Status information visible
- Help text always available
Optimization:
- Limit redraws (only when state changes)
- Use double buffering
- Batch terminal updates
- Cache rendered content
- Throttle high-frequency events
Guidelines:
- Support screen readers
- High contrast colors
- Keyboard-only navigation
- Clear focus indicators
- Avoid color-only information
Best Practices:
- Show errors inline
- Provide actionable messages
- Don't crash on terminal resize
- Handle missing terminal features
- Graceful degradation