OUR SERVICES

CLI & Developer Experience

CLI & Developer Experience

Command line interface design for developer tools, infrastructure products and technical workflows.

Waldo makes commands, errors, configuration and documentation clearer, more usable and easier to adopt.

Developer experience is user experience

Most designers don't touch CLIs. They're seen as "too technical" or "not design." We disagree.

Developers are users. The tools they interact with daily - CLIs, APIs, documentation, error messages - shape their productivity and satisfaction. A well-designed CLI can be the difference between adoption and abandonment.

We've designed command-line interfaces for enterprise security tools, cloud governance platforms, and developer infrastructure; we even created a CLI Design System for one of the most popular Linux distributions.

We understand the conventions, the constraints, and the opportunities.

HOW WE DO THIS

Command Structure Design

We design intuitive command hierarchies, verb-noun patterns, and flag conventions that feel natural to experienced developers.

Output Formatting

We craft terminal output that's scannable - using colour, spacing, tables, and progressive disclosure to surface what matters to humans using it.

Error Messaging

We write error messages that explain what went wrong, why, and what to do next — not cryptic codes that send developers to Stack Overflow.

Help Systems

We design --help output, man pages, and inline guidance that answers questions without leaving the terminal.

Interactive Flows

We design multi-step CLI wizards and prompts that guide users through complex operations without overwhelming them.


Inclusive CLI Design

We design terminal experiences with clear language, keyboard-first workflows, screen-reader-friendly output and cues that never rely on colour alone.

Configuration UX

We make config files, environment variables, and settings discoverable and understandable — not buried in documentation.

CLI-to-UI

We design seamless handoffs between CLI and web interfaces - consistent concepts, shared mental models, complementary workflows.

FAQ

Frequently asked questions

Still got questions? Feel free to reach out. We're happy to help.

Do you actually design command-line interfaces?

Yes. It's a specialty. We've designed CLIs for enterprise security (SPIRL), cloud governance (Stacklet), and developer infrastructure (Citibank). Most design agencies avoid CLIs - we actively seek them out. Developers are users, and their tools deserve good design.

What does CLI design include?

Command structure and naming, output formatting and colour systems, error messages that actually help, help text and documentation, interactive prompts for complex operations, configuration UX, and onboarding flows. It's user experience design applied to text-based interfaces.

Do you write the copy for CLIs?

Yes. Help text, error messages, and documentation are core to CLI UX. We write (or rewrite) them to be clear, actionable, and human. Good error messages explain what went wrong, why, and what to do next - not cryptic codes.

Can you design both CLI and web UI for the same product?

Absolutely. We often design both, ensuring consistent mental models, shared terminology, and complementary workflows. The CLI and web interface should feel like parts of the same product, not separate tools.

What about API documentation?

Yes. API docs are part of developer experience. We design documentation structure, navigation, code examples, and the overall experience of learning and using your API. Good documentation reduces support burden and accelerates adoption.

Do you work with open source projects?

We have. Several projects we've designed build on open source foundations (Ubuntu, Cloud Custodian, MAAS (Metal-as-a-Service), SPIFFE). We understand open source conventions, community expectations, and the balance between community and enterprise features.