Individual skill
ape-cli-terminal-experience
Designs the terminal experience of a CLI app the way Claude Code does it -- palette, status glyphs, spinners, progress narration, prompts, confirmations, listings, key hints, and full-screen TUI views. Trigger on "ape cli terminal experience", or whenever the task involves printing to a terminal from a CLI: adding or restyling output, adding a spinner or progress indicator, writing a prompt or confirmation, building a TUI, choosing exit codes, or deciding stdout vs stderr. Also trigger on casual phrasings like "make the output nicer", "add colour", "this CLI looks ugly". Read this before writing the first line of output code.
ape-cli-terminal-experience/SKILL.md
Source commit db7ad939cc944eb71f61790a72b9a0d79008d226
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 57
- Repository last updated
- Oct 24, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-skills Repository topic
- skills Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# CLI Terminal Experience
A terminal UI that reads like Claude Code: mostly grey, a few deliberate accents, one
line per fact, animation only while something is actually happening, and a plain-text
fallback the moment the output stops being a terminal.
Every rule below is enforceable and testable. Follow them exactly rather than
approximating the vibe.
---
## 1. The two laws
**Subtle by default.** Colour marks meaning -- a failure, a value the user will act on