How to add a new tool config to Slicker.
Create configs/<tool>/ with files mirroring the target layout relative to $HOME.
Examples:
- File in
$HOME:configs/<tool>/.mytoolrc - File in
~/.config/:configs/<tool>/.config/<tool>/config
At the end of the base config, add a silent include of the user override. The mechanism depends on the tool:
# shell-like
[[ -f "$SLICKER_ROOT/user/<tool>/user.conf" ]] && source "$SLICKER_ROOT/user/<tool>/user.conf"
# gitconfig-like
[include]
path = ~/.config/slicker/user/<tool>/user.conf
# ghostty-like
config-file = ~/.config/slicker/user/<tool>/user.confThe include must fail silently if the file doesn't exist.
Create user.example/<tool>/ with a template for the user config. This directory is copied into user/ on first install and during update (if user/<tool>/ doesn't exist yet).
Add <tool> to the stow command in three places:
scripts/install.sh— thestow -v -tlinescripts/update.sh— thestow -v -R -tlinescripts/status.sh— thefor pkg in ...loop
If the tool creates a config in a standard location, add the path to the targets array in scripts/backup.sh.
If the tool is installed via Homebrew, add brew "<tool>" to Brewfile.
Add a row to the two-layer pattern table in README.md.