dotfiles
CLAUDE.md78 starsChanged 4 months agoMITView on GitHub
Personal macOS/Linux dotfiles. Topic-per-directory layout; anything named *.symlink gets linked into $HOME as .<name> by start/link_dotfiles (e.g. zsh/zshrc.symlink → ~/.zshrc, whole dirs too: claude.symlink → ~/.claude). - Bash 3.2 compatibility in start/ — bootstrap runs on fresh macOS before Homebrew exists. No assoc arrays, no ${var,,}. - New shell scripts: run shellcheck before committing. - claude.symlink/CLAUDE.md is the global Claude instructions file (SuperClaude config), not repo documentation — don't put repo docs there. - Secrets live in gitignored .env files…
- Reads credentials
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 39
Commit style: conventional commits (feat:, fix:, chore: …).
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
dotfiles — repo guide
Personal macOS/Linux dotfiles. Topic-per-directory layout; anything named
*.symlink gets linked into $HOME as .<name> by start/link_dotfiles
(e.g. zsh/zshrc.symlink → ~/.zshrc, whole dirs too: claude.symlink → ~/.claude).
Map
| Path | What it is |
start/ | Installers: bootstrap, install, link_dotfiles, setup_linux.sh + shared TUI in start/lib/ (see its CLAUDE.md) |
zsh/ | Modular zsh config, lazy plugin loading (see its CLAUDE.md) |
claude.symlink/ | ~/.claude — global CLAUDE.md/CORE/FLAGS/PERSONAS/RTK, settings.json, 45 skills, hooks. Mostly gitignored; only whitelisted paths are tracked (see .gitignore lines 58–67) |
claude.symlink/go-tools/ | Go source for claude-hooks + claude-statusline binaries (see its CLAUDE.md) |
config.symlink/ | ~/.config — ~90 app configs (nvim, wezterm, kitty, helix, yazi, …) |
config.symlink/nvim/ | Live Neovim config: NvChad v2.5 + lazy.nvim |
neovim/ | Legacy NvChad-custom config (pre-2.5); kept for reference, not linked |
hammerspoon.symlink/ | Hammerspoon: hyper key, vim mode, window management |
tmux/ | tmux.conf + TPM plugins (plugins themselves gitignored) |
git/ | gitconfig (delta pager, difftastic on demand, GPG signing), global ignores |
bin/ | dot (sourced by start/bootstrap for macOS deps), toggle-theme (light/dark for Ghostty/tmux/Claude) |
shellscripts/ | ~70 bash utilities, on PATH via zprofile |
pyscripts.symlink/ | ~47 Python utilities (~/pyscripts, on PATH) |
osx/ | set-defaults.sh — macOS defaults write settings |
system/ | Early-loading zsh env/path fragments |
docs/ | Quarto book (_quarto.yml), deployed via Netlify |
Brewfile | Homebrew bundle (~370 formulae, ~250 casks), consumed by start/install |
Conventions
- Bash 3.2 compatibility in
start/— bootstrap runs on fresh macOS before Homebrew exists. No assoc arrays, no${var,,}. - New shell scripts: run
shellcheckbefore committing. claude.symlink/CLAUDE.mdis the global Claude instructions file (SuperClaude config), not repo documentation — don't put repo docs there.- Secrets live in gitignored
.envfiles (**/.env);.env.exampledocuments the keys. Never commit credentials (gitleaks runs via husky pre-commit). - Commit style: conventional commits (
feat:,fix:,chore:…).
Common tasks
- Relink dotfiles:
start/link_dotfiles - Rebuild hooks after Go changes:
make -C claude.symlink/go-tools install(builds + copiesclaude-hooks/claude-statuslineto~/.local/bin) dp(zsh function) — commit + push dotfiles with AI commit message
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- claude.symlink/CLAUDE.mdCLAUDE.md
- hammerspoon.symlink/CLAUDE.mdCLAUDE.md
- pyscripts.symlink/CLAUDE.mdCLAUDE.md
- shellscripts/CLAUDE.mdCLAUDE.md
- start/CLAUDE.mdCLAUDE.md
- tmux/CLAUDE.mdCLAUDE.md
- zsh/CLAUDE.mdCLAUDE.md
- housekeepingSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.