You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(AGENTS.md): Add CLI Color Semantics guide (Revision 1)
Document the semantic color system for CLI output:
- Hierarchy-based color assignment (L0-L3 levels)
- Status-based color overrides
- Design principles from jq, ripgrep, mise/just
- Available Colors class methods
- Key rule: never use same color for adjacent hierarchy levels
Copy file name to clipboardExpand all lines: AGENTS.md
+62Lines changed: 62 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -194,3 +194,65 @@ $ uv run pytest --cov
194
194
- **QA every edit**: Run formatting and tests before committing
195
195
- **Minimum Python**: 3.10+ (per pyproject.toml)
196
196
- **Minimum tmux**: 3.2+ (as per README)
197
+
198
+
## CLI Color Semantics (Revision 1, 2026-01-04)
199
+
200
+
The CLI uses semantic colors via the `Colors` class in `src/tmuxp/cli/_colors.py`. Colors are chosen based on **hierarchy level** and **semantic meaning**, not just data type.
colors.muted("label:") # Blue dim (metadata, labels)
251
+
colors.success("ok") # Green (success states)
252
+
colors.warning("caution") # Yellow (warnings)
253
+
colors.error("failed") # Red (errors)
254
+
```
255
+
256
+
### Key Rule
257
+
258
+
**Never use the same color for adjacent hierarchy levels.** If headers and items are both blue, they blend together. Each level must be visually distinct.
0 commit comments