domain-cli

Design Rust command-line interfaces with clap, figment, and indicatif.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill domain-cli-jmduea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-cli
Source: https://github.com/jmduea/emotiv-cortex-rs/tree/main/.github/skills/domain-cli
Command: npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill domain-cli-jmduea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured approach to building Rust command‑line applications that satisfy ergonomic, configurability, exit‑code, and interrupt handling constraints.

Core Features & Use Cases

  • Domain constraints mapped to Rust crate choices such as clap for argument parsing and figment for layered configuration.
  • Recommended key crates list including clap, dialoguer, indicatif, colored, ratatui, crossterm, and console.
  • Design patterns for type‑safe argument structs, subcommand hierarchies, progress bars, and error handling.
  • Guidance on common mistakes and how to avoid them in CLI projects.

Quick Start

Ask the domain-cli skill to generate a starter Rust CLI project with clap and proper config layering.

Frequently Asked Questions about domain-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Rust command-line interface with argument parsing and layered configuration?

Build a Rust command-line interface by using clap for type-safe argument parsing and figment for layered configuration, ensuring ergonomic and reliable CLI applications.

What are the recommended Rust crates for building terminal UI components and progress displays?

For terminal UI components in Rust CLI tools, use indicatif for progress bars, ratatui and crossterm for terminal interfaces, colored for text coloring, and dialoguer for interactive prompts.

How do I handle errors and exit codes properly in a Rust CLI application?

Handle errors and exit codes in a Rust CLI application by enforcing standard exit-code conventions and applying robust error handling patterns to satisfy reliability and interrupt handling constraints.

What is the best way to structure type-safe argument structs and subcommand hierarchies in Rust?

Structure type-safe argument structs and subcommand hierarchies in Rust by using clap to define design patterns that ensure ergonomic and reliable command-line argument parsing.

Can I generate a starter Rust CLI project with proper config layering automatically?

Yes, you can generate a starter Rust CLI project by requesting the domain-cli skill to scaffold a project equipped with clap argument parsing and proper figment config layering.