The command line never went away — it just moved. Terminal design takes the visual vocabulary of the shell and makes it a design system: the prompt character, the blinking cursor, the command-response pattern, the monospace type that knows it's monospace and leans into it. But this isn't a developer tool in disguise — it's a design philosophy. Apps built with Terminal style look like they were designed by someone who deeply understood what made early computer interfaces beautiful and then rebuilt that understanding for the modern web. Structured, honest, and strangely timeless.
Terminal.
The prompt, the cursor, the monospace grid. Terminal design takes the CLI's honest visual vocabulary and turns it into a complete design system.
The prompt is the interaction model
Every interaction in a terminal follows the same pattern: prompt, input, response. This call-and-response rhythm — > user input, then system output — is the most honest representation of how computers work. Terminal design makes this pattern visible in the UI, even when the user isn't literally typing commands. Labels are prefixed. Responses are indented. The structure of the interface tells the story of how it works.
Monospace is not a constraint — it's the grid
Fixed-width type creates a grid that no layout system can replicate. Every column aligns. Every row is the same height. Numbers stack with perfect precision. Terminal design uses this grid as the primary layout system — not a backdrop, but the structure itself. When designers work with monospace rather than against it, the results have a mathematical coherence that proportional type can never match.
The cursor blinks, therefore it lives
The blinking cursor is the oldest animation in computing — and still one of the most meaningful. It says: the system is alive, it is waiting, it is ready. Terminal design brings this aliveness to UI through small, purposeful animations: text that appears character by character, prompts that blink while waiting for input, progress shown as a stream of output rather than a spinning circle. The interface communicates its inner life.
Before building with Claude Code, drop SKILL.md and DESIGN.md into Claude Design first. Use it to generate mockups and nail the visual direction — then hand those references to Claude Code. You'll get significantly higher quality output than going straight to code.
Cyberpunk
Neon light, dark interfaces, and information overload as atmosphere. The aesthetic of Blade Runner terminals and Cyberpunk 2077 for gaming and creative tools.
Matrix
Green on black. One font. One grid. The design language of the digital void — code rain, terminal readouts, and interfaces that feel like they're running the world.
Two files. That's it.
Drop them into your Claude project or Cursor rules and build normally. No CLI, no package manager, no setup.