cc-pulseline

Render every cc-pulseline layout against a synthetic fixture so visual differences (tools/agents/todo/quota/sparkline) all show without touching the live Claude Code session. Use when the user says "preview layouts", "show all layouts", "render layouts at width N", "compare layouts", or wants to see them side-by-side. Also use when adding/removing/renaming a layout, adding a new theme, or vetting a redesign before implementation.

Use this skill when the user wants to bump the cc-pulseline crate version — triggers on "bump version", "release X.Y.Z", "prepare release", "ship 1.X", "tag a release", or any phrasing that signals a version is about to be cut. Always invoke this skill before touching Cargo.toml or CHANGELOG.md, even if the user names a specific file directly. Do NOT use for npm-package version bumps in `npm/*/package.json` (CI-driven `0.0.0` placeholders) or unrelated dependency upgrades.

Preview and add cc-pulseline color themes. Use when user pastes a theme JSON with palette_mapping, asks to preview a theme, says "try this theme", or wants to add a new theme to the codebase. Also use when user shares a color palette design or asks to render theme colors in the terminal.

Diagnose and fix cc-pulseline statusline issues. Use when the user mentions their statusline is blank, broken, not updating, showing wrong data, or displaying rendering problems. Also use when users report missing segments, broken icons, or color issues.