tui-cli-rules

Standardize secure TUI and CLI interfaces for UMRS crates.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/jamieadams-nerd/umrs-project --skill tui-cli-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tui-cli-rules
Source: https://github.com/jamieadams-nerd/umrs-project/tree/main/.claude/skills/tui-cli-rules
Command: npx skills add https://github.com/jamieadams-nerd/umrs-project --skill tui-cli-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TUI/CLI design principles and I/O discipline ensure consistent, secure user interfaces for UMRS tools, preventing miscommunication and unsafe reads.

Core Features & Use Cases

  • NO_COLOR compliance: always honor NO_COLOR across all terminals and tools.
  • Consistent --json output: provide machine-friendly results without verbose labels.
  • Clear error messages: describe what happened and what to do next for operators and developers.
  • Platform abstraction: all system reads must go through the umrs-platform layer, with no hard-coded paths.

Quick Start

Set up or audit UMRS TUI/CLI crates to honor NO_COLOR, emit --json outputs, support --verbose, and rely on the platform abstraction layer.

Frequently Asked Questions about tui-cli-rules

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

FAQPage Schema
How do I enforce NO_COLOR compliance in CLI tools?

To enforce NO_COLOR compliance in CLI tools, you must configure all terminal interfaces to consistently honor the NO_COLOR environment variable across all platforms. This prevents miscommunication by ensuring safe, standardized text outputs.

What is the best way to standardize CLI JSON output format?

The best way to standardize CLI JSON output format is to emit machine-friendly results without verbose labels. Providing consistent --json output allows downstream tools to reliably parse system state data.

How do I abstract system reads in CLI binaries to avoid hardcoded paths?

To avoid hardcoded paths and abstract system reads in CLI binaries, route all state access through a dedicated platform abstraction layer. This requires using the umrs-platform dependency to standardize secure reads and prevent unsafe file access.

Why do CLI tools need clear error messages for operators?

CLI tools need clear error messages to describe exactly what happened and what operators should do next. This I/O discipline ensures consistent, secure user interfaces and prevents miscommunication during system state reads.

Does UMRS TUI design require platform abstraction for all binary crates?

Yes, UMRS TUI design requires the platform abstraction layer for all binary crates that read system state. This dependency prevents hardcoded paths and standardizes secure I/O discipline across tools like umrs-ls and umrs-c2pa.