dotfiles-core
The keystone. Single source of truth for everything identical on every machine — shell modules, tmux base, Neovim, git, starship, mise.
Highlights
- zsh module chain
- lazy.nvim tree
- tmux + starship + mise
- audited & benchmarked
How it fits
The keystone. Every OS repo vendors this into its core/ directory via
git subtree, so a change here fans out to the whole fleet. See the three-layer model and vendoring with git subtree.
Getting started
Core is never installed directly — clone the repo for your platform (macOS, Kali, Fedora, …), which already carries Core vendored inside it.
What actually bites
- Load order is load-bearing — The zsh chain is tools → ui → options → history → aliases → git → functions → fzf → bindings → plugins → op → maint → update → os → local. Reordering it breaks detection and completion.
- Modern-CLI swaps are guarded — tools.zsh resolves HAVE_* flags at load time, so every alias (eza/bat/zoxide/…) falls back to the classic command on a box that lacks the newer one. Nothing breaks; it just gets nicer where it can.
- One gate defines healthy — scripts/audit-core.sh (make audit) checks manifest drift, exec-bits, syntax, shellcheck, luacheck, markdownlint, and a behavioral suite. A red tree must never be vendored out.
- A change here fans out N-way — Core is vendored into every OS repo via git subtree, so a defect fixed once lands everywhere on the next make sync. Treat every change as if it ships to all of them — because it does.