ux-cli
Terminal application UX standards — color encodes semantics, output is self-sufficient, failure paths are first-class.
- License 许可
- Apache-2.0
- 所属仓库
- usurobor/cnos
- 最近更新
- 2026-11-07
- Stars
- ★ 9
- Forks
- 0
01 前言 Front Matter
- name
- ux-cli
- scope
- task-local
- triggers
- [ "UX", "CLI", "interface", "usability", "ergonomics" ]
- description
- Terminal application UX standards — color encodes semantics, output is self-sufficient, failure paths are first-class.
- governing_question
- How do we make a terminal interface where an expert spots failures in under two seconds and a novice can fix using only the terminal output?
03 SKILL.md 正文
UX CLI
Terminal application UX standards.
Principles
- Color encodes semantics, never decoration
- Output must be self-sufficient (what happened, what's blocked, what to do)
- Failure paths are first-class
- No blame, no vibes
Colors
| Color | Meaning |
|---|---|
| Green | OK / success |
| Red | Error / blocking |
| Yellow | Warning / non-blocking |
| Cyan | Info / headings |
| Magenta | Commands to run |
| Gray | Dim / inactive |
Symbols
| Symbol | Meaning |
|---|---|
| ✓ | OK |
| ✗ | Fail |
| ⚠ | Warning |
| ⏸ | Blocked |
| → | Next step |
Patterns
Success
✓ All prerequisites satisfied.
Warning
⚠ Warning: impact
Continue possible.
Error
✗ Cannot continue — cause
Fix by running:
1) cmd args
2) cmd args
Then rerun: cmd
Anti-Patterns
- Color as decoration
- Color-only signaling (no symbols)
- Paragraph errors (action buried in prose)
- Silent assumptions
- "Something went wrong" (non-causal)
Checklist
- [ ] Expert can identify failures in <2s
- [ ] Novice can fix using only terminal output
- [ ] Usable with NO_COLOR
04 同仓库更多 Skills
issues/triage
Issue triage doctrine pointer. Use when classifying a new issue, deciding dispatch eligibility, or deciding whether to close/supersede/defer.
issues/taxonomy
Issue label taxonomy pointer. Use when classifying an issue's kind/area/priority/effort/status/protocol/dispatch labels, or when the board needs to interpret them.
issues/map
Issue-board (Issue Pivot) generation domain. Use when reasoning about `cn issues map`'s fetch, taxonomy-parse, effort-computation, and render pipeline, or about the board's JSON/HTML output contract.
issues
cnos.issues package entrypoint. Use when reasoning about issue taxonomy, the Issue Pivot / issue-board (`cn issues map`), the read-only CDS issue-state evaluator (`cn issues fsm evaluate`), or the current command-dispatch disposition of issue tooling.
receipt-stream
Cross-cycle receipt-stream doctrine for protocol-iteration. Use when γ closes a cycle and writes the per-cycle iteration artifact (`cdd-iteration.md`), when γ updates the cross-cycle aggregator at `.cdd/iterations/INDEX.md`, when ε reads the receipt stream across cycles to surface protocol-gap patterns, when a finding's disposition lands a cross-repo patch and the cross-repo trace bundle attaches, or when a courtesy empty-findings stub is written for a `protocol_gap_count == 0` cycle.
mid-flight
Mid-flight γ→in-flight-α rescue channel. Use when γ needs to change a load-bearing fact (pinned axis, scope, AC, blocker) after α has begun coding, when γ edits the cycle's GitHub issue body mid-cycle, or when a spec change lands on origin/main while α/β polling sessions are in-flight.