home / skills / zpankz / mcp-skillset / terminal

terminal skill

/terminal

This skill helps you design distinctive production-grade terminal UIs for CLIs and TUIs with polished, non-generic aesthetics.

npx playbooks add skill zpankz/mcp-skillset --skill terminal

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
6.6 KB
---
name: terminal-ui-design
description: Create distinctive, production-grade terminal user interfaces with high design quality. Use this skill when the user asks to build CLI tools, TUI applications, or terminal-based interfaces. Generates creative, polished code that avoids generic terminal aesthetics.
---

Create distinctive, production-grade terminal user interfaces with high design quality. Use this skill when building CLI tools, TUI applications, or terminal-based interfaces. Generate creative, polished code that avoids generic terminal aesthetics.

## Design Thinking

Before coding, understand the context and commit to a BOLD aesthetic direction:

1- Purpose: What problem does this interface solve? Who uses it? What's the workflow?
2- Tone: Pick an extreme: hacker/cyberpunk, retro-computing (80s/90s), minimalist zen, maximalist dashboard, synthwave neon, monochrome brutalist, corporate mainframe, playful/whimsical, matrix-style, steampunk terminal, vaporwave, military/tactical, art deco, paper-tape nostalgic
3- Constraints: Technical requirements (Python Rich, Go bubbletea, Rust ratatui, Node.js blessed/ink, pure ANSI escape codes, ncurses)
4- Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember about this terminal experience?

Choose a clear conceptual direction and execute it with precision. A dense information dashboard and a zen single-focus interface both work—the key is intentionality, not intensity.

## Box Drawing & Borders

Choose border styles that match your aesthetic:

- Single line: ┌─┐│└┘ — Clean, modern
- Double line: ╔═╗║╚╝ — Bold, formal, retro-mainframe
- Rounded: ╭─╮│╰╯ — Soft, friendly, modern
- Heavy: ┏━┓┃┗┛ — Strong, industrial
- Dashed/Dotted: ┄┆ — Light, airy, informal
- ASCII only: +-+| — Retro, universal compatibility
- Block characters: █▀▄▌▐ — Chunky, bold, brutalist
- Custom Unicode: Mix symbols like ◢◣◤◥, ●○◐◑, ▲▼◀▶ for unique frames

Avoid defaulting to simple single-line boxes. Consider asymmetric borders, double-thick headers, or decorative corners like ◆, ◈, ✦, ⬡.

## Color & Theme

Commit to a cohesive palette. Terminal color strategies:

- ANSI 16: Classic, universal. Craft distinctive combinations beyond default red/green/blue
- 256-color: Rich palettes. Use color gradients, subtle background variations
- True color (24-bit): Full spectrum. Gradient text, smooth color transitions
- Monochrome: Single color with intensity variations (dim, normal, bold, reverse). Elegant constraint

Create atmosphere with:
- Background color blocks for sections
- Gradient fills using block characters ░▒▓█
- Color-coded semantic meaning (but avoid cliché red=bad, green=good)
- Inverted/reverse video for emphasis
- Dim text for secondary information, bold for primary

Palette examples (invent your own):
- Cyberpunk: Hot pink #ff00ff, electric cyan #00ffff, deep purple #1a0a2e background
- Amber terminal: #ffb000 on black, like vintage CRTs
- Nord-inspired: Cool blues and muted greens on dark blue-gray
- Hot Dog Stand: Intentionally garish yellow/red (for playful/ironic UIs)

## Typography & Text Styling

The terminal is ALL typography. Make it count:
- ASCII art headers: Use figlet-style banners, custom letterforms, or Unicode art
- Text weight: Bold, dim, normal — create visual hierarchy
- Text decoration: Underline, strikethrough, italic (where supported)
- Letter spacing: Simulate with spaces for headers: H E A D E R
- Case: ALL CAPS for headers, lowercase for body, mixed for emphasis
- Unicode symbols: Enrich text with → • ◆ ★ ⚡ λ ∴ ≡ ⌘
- Custom bullets: Replace - with ▸ ◉ ✓ ⬢ › or themed symbols

ASCII Art Styles:
Block:    ███████╗██╗██╗     ███████╗
Slant:    /___  / / // /     / ____/
Small:    ╔═╗┌─┐┌─┐
Minimal:  [ HEADER ]

## Layout & Spatial Composition

Break free from single-column output:
- Panels & Windows: Create distinct regions with borders
- Columns: Side-by-side information using careful spacing
- Tables: Align data meaningfully, use Unicode table characters
- Whitespace: Generous padding inside panels, breathing room between sections
- Density: Match to purpose — dashboards can be dense, wizards should be sparse
- Hierarchy: Clear visual distinction between primary content, secondary info, and chrome
- Asymmetry: Off-center titles, weighted layouts, unexpected alignments

## Motion & Animation

Terminals support dynamic content:
- Spinners: Beyond basic |/-. Use Braille patterns ⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏, dots ⣾⣽⣻⢿⡿⣟⣯⣷, custom sequences
- Progress bars: ▓░, █▒, [=====>    ], or creative alternatives like ◐◓◑◒
- Typing effects: Reveal text character-by-character for drama
- Transitions: Wipe effects, fade in/out with color intensity
- Live updates: Streaming data, real-time charts

## Data Display
- Sparklines: ▁▂▃▄▅▆▇█ for inline mini-charts
- Bar charts: Horizontal bars with block characters
- Tables: Smart column sizing, alternating row colors, aligned numbers
- Trees: ├── └── │ for hierarchies
- Status indicators: ● green, ○ empty, ◐ partial, ✓ complete, ✗ failed
- Gauges: [████████░░] with percentage

## Decorative Elements

- Add character without clutter:
- Dividers: ───── ═════ •••••• ░░░░░░ ≋≋≋≋≋≋
- Section markers: ▶ SECTION, [ SECTION ], ─── SECTION ───, ◆ SECTION
- Background textures: Patterns using light characters like · ∙ ░
- Icons: Nerd Font icons if available:     󰊢

## Anti-Patterns to Avoid

NEVER use generic terminal aesthetics like:

- Plain unformatted text output
- Default colors without intentional palette
- Basic [INFO], [ERROR] prefixes without styling
- Simple ---- dividers
- Walls of unstructured text
- Generic progress bars without personality
- Boring help text formatting
- Inconsistent spacing and alignment

Library Quick Reference
Python: Rich, Textual Go: Bubbletea, Lipgloss
 Rust: Ratatui Node.js: Ink, Blessed

ANSI Escape Codes:
\x1b[1m       Bold
\x1b[3m       Italic
\x1b[4m       Underline
\x1b[31m      Red foreground
\x1b[38;2;R;G;Bm  True color
\x1b[2J       Clear screen

The terminal is a canvas with unique constraints and possibilities. Don't just print text—craft an experience.

Match implementation complexity to the aesthetic vision. A dense monitoring dashboard needs elaborate panels and live updates. A minimal CLI needs restraint, precision, and perfect alignment. Elegance comes from executing the vision well.

Overview

This skill helps you design and implement distinctive, production-grade terminal user interfaces with strong visual identity and polished interactions. It focuses on intentional aesthetics, practical layouts, and creative use of terminal capabilities to avoid generic CLI output. Use it when you want a memorable, maintainable TUI or CLI that feels designed, not dumped.

How this skill works

The skill guides you through design decisions (purpose, tone, constraints, differentiation) and translates them into concrete terminal patterns: borders, color palettes, typography, layout, motion, and data display. It suggests libraries and ANSI techniques for multiple languages and generates themed components, composable panels, and animated widgets. It enforces anti-patterns to avoid unstyled, cluttered, or inconsistent terminals.

When to use it

  • Building a production CLI with a clear visual identity
  • Designing a TUI dashboard for real-time data or monitoring
  • Creating install wizards, onboarding flows, or setup UIs in the terminal
  • Polishing help output and error messaging with deliberate typography and layout
  • Prototyping themed terminal tools (cyberpunk, retro, minimalist, corporate)

Best practices

  • Choose one bold aesthetic direction and keep it consistent across color, borders, and icons
  • Match implementation complexity to purpose: minimal for wizards, richer for dashboards
  • Use semantic color coding and text weight (bold/dim) instead of raw tags like [ERROR]
  • Prefer structured panels, columns, and whitespace over wall-of-text output
  • Use appropriate libraries (Rich/Textual, Bubbletea, Ratatui, Ink/Blessed) for maintainability and accessibility
  • Design one memorable element (custom header, animated meter, or unique border) as the UI hook

Example use cases

  • A cyberpunk-themed CLI for a developer tool with neon gradients and custom spinners
  • A dense operations dashboard showing live metrics, sparklines, and colored gauges
  • A minimalist installer wizard with clear hierarchy, generous whitespace, and typing transitions
  • A retro mainframe-style report generator with double-line frames and monospaced ASCII art headers
  • A playful developer assistant CLI with custom bullets, animated progress, and themed icons

FAQ

Which libraries should I pick for my language?

Choose the library that best matches your constraints: Python—Rich/Textual, Go—Bubbletea/Lipgloss, Rust—Ratatui, Node.js—Ink/Blessed. Use libraries for layout and animation to avoid reinventing low-level terminal handling.

How do I pick a palette that works in terminals?

Start with ANSI 16 for broad compatibility, 256-color for richer palettes, or truecolor when supported. Commit to a cohesive palette and use dim/bold variants for hierarchy rather than many unrelated colors.