claude-statusbar

claude-statusbar control skill

Use this skill any time the user wants to inspect, change, customize, or diagnose the cs status bar. Replaces the older individual slash commands (/statusbar, /statusbar-theme, /statusbar-style, /statusbar-preview, /statusbar-doctor, /statusbar-reset) — they still work but this skill covers all of them with conversational intent.

Decision tree

Match the user's intent to the right cs command. Run it via Bash, then give a short confirmation (one line, no lecture).

User intent	Command
Inspect current config	cs config show
List themes	cs themes
List styles	cs styles
Switch theme to <name>	cs config set theme <name>
Switch style to <name>	cs config set style <name>
Change density	cs config set density <compact|regular|cozy>
Show all 27 combinations	cs preview
Filter preview to one style/theme	cs preview --style <s> or cs preview --theme <t>
Diagnose problem	cs doctor
Wipe config	cs config reset
Install / first-time setup	cs --setup
Enable fast mode (daemon)	cs --setup --fast
Disable fast mode	cs daemon stop then re-run cs --setup
Toggle session cost display	cs config set show_cost true|false
Toggle prompt-cache countdown	cs config set show_cache_age true|false
Toggle project + branch 2nd line	cs config set show_project_branch true|false (default true)
Hide weekly bar	cs config set show_weekly false
Set warning threshold	cs config set warning_threshold <0-100>
Set critical threshold	cs config set critical_threshold <0-100>
Auto-collapse to hairline below width	cs config set auto_compact_width <px>

Per-severity color overrides (v3.4.1+)

The user can override the three severity colors independently of theme:

cs config set color_ok   "#4ec85b"   # calm / safe
cs config set color_warn "#e8b260"   # warning
cs config set color_hot  "#e87474"   # critical

cs config set color_ok ""            # clear back to theme default

Accepts #rrggbb, #rgb, or bare rrggbb. The override layers on top of whatever theme is active — no need to switch theme just to tune one color.

When user says "make 余量颜色 / safe color / green sharper", "warning 偏淡", "critical too red" — go to the override, not the theme.

Vibe → theme suggestion

If the user describes a vibe instead of naming a theme, suggest one and ask before switching:

Vibe / context	Theme
Muted, professional, dark terminal	graphite (default)
Soft, warm, dark	twilight
Classic dev / Nord-inspired	nord
High contrast, vivid	dracula
Warm, cute, light bg	sakura
Light terminal	linen
Pure grayscale / no color	mono
Popular pastel, easy on long viewing	catppuccin-mocha
Deeper neon-blue mood	tokyo-night

Render anatomy (so you can explain what you're changing)

5h[██16% ░░░]⏰2h27m | 7d[██32%  ░░]⏰4d05h | Opus 4.7(280k/1M) | $ 1.42 | cache 4m23s
└─ 5h ─────┘└──5h──┘  └─ 7d ──┘ └─7d─┘   └────context───────┘  └cost┘  └─cache─┘

Every numeric segment colors itself by its own severity (since v3.4):

• 5h → theme.s_* chosen from msgs_pct
• 7d → theme.s_* chosen from weekly_pct
• model+context → theme.s_* chosen from ctx_used_pct (None → neutral)
• cache → its own string-age severity (COLD → red, <1m → yellow, else green)
• [ ], ( ), | → theme.mute (recede behind data)

Common diagnostic flows

"Status bar isn't showing" → cs doctor. It self-checks:

• Claude Code's ~/.claude/settings.json has the statusLine block
• the cs binary is on PATH
• whether the daemon is alive (if fast-mode configured)
• whether the cache files are stale

"refreshInterval too high" → cs doctor will recommend cs --setup --fast when it sees refreshInterval ≤ 2s on the inline command. Fast mode drops 1Hz CPU from ~6% to ~2%.

"Color won't change after cs config set theme X" → check the user isn't on a Claude Code session that read settings.json at start. Ask them to send a new prompt; the next render picks up the new theme.

Don't

• Don't lecture about ANSI codes or terminal compatibility unless asked.
• Don't suggest editing ~/.claude/claude-statusbar.json by hand. Use cs config set <key> <value>.
• Don't change theme just to fix one color — use color_ok / color_warn / color_hot overrides.
• Don't run destructive commands (cs config reset, cs daemon stop) without confirming with the user.

Style of response

Be terse. Run the command, paste the one-line confirmation, point at the next step if relevant. The status bar is on screen — they can see the result immediately, no need to describe it.