terminal-ui-design
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.
What this skill does
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.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.