Monospace Design TUI

As terminal user interfaces grew beyond simple scripts into full applications — dashboards, file managers, configuration wizards — a problem became clear. Every project invented its own conventions. Keyboard shortcuts varied from app to app. Layouts followed no shared logic. Color meant different things in different tools. The experience of using one TUI taught you nothing about using the next.

This seemed wrong. Graphical interfaces had solved this decades ago. Apple published the Human Interface Guidelines. Google developed Material Design. These standards meant that a user who learned one application could sit down in front of another and already know how it worked. But for terminal interfaces — nothing. No shared vocabulary, no common rules, no design system.

We suspected the raw material already existed. The history of text-mode computing is rich with thoughtful design: IBM's CUA keyboard model from 1987, the window management conventions of OS/2, Norton Commander's dual-pane paradigm, Borland's Turbo Vision component framework. These weren't ad hoc — they were carefully engineered systems that millions of people used daily. The knowledge was there, scattered across manuals, technical references, and the muscle memory of experienced developers.

So we collected it. We studied seven research vectors — CUA, OS/2, Material Design 3, Apple HIG, the Keystroke-Level Model, modern terminal capabilities, and historical TUI applications — and synthesized them into a single, prescriptive design language. Not guidelines. Not suggestions. Falsifiable, auditable rules that a reviewer can check against an implementation and declare it compliant or in violation.

The result is Monospace Design TUI: a design standard and Designer toolset for terminal applications that want to look and behave like they belong to the same family.