One repository · several daily tools
A home for the tools behind my Mac.
Shell, editor, terminal and backup configuration, kept together without turning the home directory into a mystery. Explore how each piece works and where its source lives.
❯ tree -L 2 home/ home/ ├── .config/ │ ├── nvim/ # editor │ ├── wezterm/ # terminal │ ├── theme/ # shared colors │ └── scripts/ # macbackup + tools ├── .zshrc └── .zprofile ❯ ./scripts/dot.sh plan # review changes before applying links
Explore the system
Start with a tool.
Each page explains the role of a module, its safety boundaries, and where to find the complete source or guide.
macbackup
Selected files on Google Drive, private paths encrypted before upload, and a history you can inspect and clean deliberately.
02 / EDITORNeovim
A modular setup with a small core, lazy-loaded plugins, LSP tooling and a theme shared with the terminal.
03 / BOOTSTRAPSymlink manager
See what would change, apply only safe links, and handle existing files explicitly with dot.sh.
04 / INTERFACETheme & terminal
Shared color tokens connect Zsh, WezTerm and Neovim; Karabiner and other modules shape the surrounding workflow.
The structure
One source, explicit boundaries.
The repository stores configuration. The symlink manager connects it to the home directory. The backup tool independently selects what should reach cloud storage.
Repository
home/ mirrors paths below the home directory. Neovim is tracked as a separate submodule.
Local setup
dot.sh links managed paths and reports conflicts before replacing anything.
Cloud copy
macbackup applies its own plain, private, exclusion and history rules.
Before you run anything
Inspect first.
The setup favors commands that explain the next change before they make it. Start with the repository guide or read the documentation for the tool you need.
./scripts/dot.sh plan macbackup check macbackup preview --local # Full guides macbackup/docs/ nvim/docs/