| name | tool-starship |
| description | Use Starship for prompt configuration, module tuning, and cross-shell prompt consistency. Trigger when prompt rendering, startup latency, or shell prompt content needs changes. |
tool-starship
When To Use
- Tune prompt modules, symbols, and formatting behavior.
- Diagnose why prompt segments are missing or slow.
- Keep prompt UX consistent across shell environments.
Trusted Commands
starship --version
starship explain
starship module directory
starship module git_branch
starship timings
Safe Defaults
- Keep prompt layout readable and minimal.
- Validate changes in a fresh shell session.
- Prefer single-line prompt defaults unless multi-line is explicitly requested.
Common Pitfalls
- Invalid TOML or unsupported module keys break rendering.
- Multi-line formatting can reduce readability in narrow panes.
- Heredoc-based writes can expand
$module placeholders unintentionally.
Output Interpretation
starship explain shows active modules and config resolution.starship timings highlights slow modules and startup impact.
Why It Matters For Agents
- Prompt clarity improves command confidence and context visibility.
- Small config mistakes can break every new shell session.
Repo Conventions
- Default prompt should remain single-line for readability.
- Keep config deployment idempotent and template-driven.
Trigger Examples
- Should trigger: "Tune starship prompt modules for cleaner git status display."
- Should trigger: "Debug why starship is not loading in zsh startup."
- Should not trigger: "Search for all TODO comments in the repo."
