starship-config

Starship presets are starter configurations you apply using `starship preset <preset-name> -o ~/.config/starship.toml`. This command downloads a preconfigured prompt setup and writes it to your Starship config file, letting you customize modules like git, nodejs, and directory display without building from scratch.

Starship supports common modules including golang, nodejs, git, and directory. Edit `~/.config/starship.toml` to customize each module's behavior, format, and display conditions. You can also adjust timings and loading behavior to optimize how quickly your prompt renders.

Performance tuning in Starship involves adjusting module timings and loading behavior in your config file to reduce prompt rendering latency. Disable expensive modules, set timeouts, or use context-aware variables to show information only when relevant, speeding up shell startup.

Yes. Set `export STARSHIP_CONFIG=./config/starship/starship.toml` and run `exec fish -l` (or your shell) to test a config file in isolation. This lets you preview module changes and performance tuning without affecting your active prompt.

Starship includes context-aware modules that display kubectl, AWS, and Docker information when available in your environment. Configure these modules in your preset or custom config to show deployment context only when relevant to your current shell session.

Starship is a cross-shell prompt that works across different shells and environments. Presets and module configurations apply consistently, and you can test setup across shells by setting the config path and executing your shell of choice.