Skip to content
Gerrrt edited this page Jun 14, 2026 · 3 revisions

dotfiles-core

The single source of truth for the Core layer shared across every machine in a nine-repo dotfiles system. Core is the config that is identical on every box — zsh modules, tmux base, Neovim, git — authored once here and vendored into each OS repo's core/ directory via git subtree.

If it changes when the operating system changes, it does not belong here. If it changes when you as an operator change, it does not belong here. Everything left over is Core, and it lives here.

This wiki is the deep-dive companion to the repo's README: the README tells you what Core is and how to consume it; the wiki explains how each piece works and how to use it day to day.

Start here

Pick the path that matches why you're here.

"I want to understand the system"

  1. Architecture & the Three-Layer Model — Core vs OS-native vs Role, and why this uses git subtree.
  2. The Zsh Module System — the load-bearing module order that is the heart of Core.

"I want to use it day to day"

  • Tools, Aliases & Functions — the modern-CLI stack, the shell functions (mkcd, extract, up, …), the fzf widgets, and every custom keybinding. Run core-help (alias cheat) in any shell for the same cheat sheet live.

"I want to contribute or adopt it"

The 30-second mental model

Layer Lives in Examples
Core this repo, vendored into each OS repo zsh modules, tmux base, nvim, git
OS-native dotfiles-{MacBook,Debian,Fedora,Arch,…} package manager, clipboard, paths
Role dotfiles-Kali engagement scaffolding, C2, wordlists

Core is authored once here, then each machine repo pulls it in as a vendored core/ subtree — no submodule flags, clone-and-go.

Page index

Concepts

Reference

Operating it

Project

Clone this wiki locally