Dotfiles

Personal dev environment configuration files — shell, terminal, editor, and prompt.

What's included

Tool	Config location	Description
Zsh	.zshrc, .zsh_plugins.txt	Shell config with Antidote plugin manager
Ghostty	ghostty/config	Terminal emulator (Dracula theme, Fira Code, vim-style splits)
NeoVim	nvim/	AstroNvim user config with Mason auto-installed LSPs
Starship	starship.toml	Cross-shell prompt with git integration

Requirements

• A Unix-like system (macOS or Linux). Windows is not supported.

Quick start

# Clone
git clone <repo-url> ~/agentic/tooling/dotfiles
cd ~/agentic/tooling/dotfiles

# Install packages (macOS — optional, see below)
brew bundle

# Create symlinks
./setup.sh

Platform notes

The symlink setup (setup.sh) is platform-independent. Package installation varies:

• macOS — Install Homebrew, then run brew bundle to install everything from the Brewfile.
• Linux — Install the equivalent packages manually:

  # Example (Ubuntu/Debian)
  sudo apt install neovim fzf
  # Install starship, antidote, zoxide, and ghostty per their docs

Directory structure

dotfiles/
  .zshrc                 # Shell config (symlinked to ~/.zshrc)
  .zsh_plugins.txt       # Antidote plugin list (symlinked to ~/.zsh_plugins.txt)
  ghostty/config         # Ghostty terminal config (symlinked to ~/.config/ghostty)
  nvim/                  # AstroNvim user config (symlinked to ~/.config/nvim)
  starship.toml          # Starship prompt config (symlinked to ~/.config/starship.toml)
  Brewfile               # Homebrew package list
  setup.sh               # Idempotent symlink script

How setup.sh works

setup.sh creates symlinks from standard config locations into this repo. If a file or directory already exists at a target location, it's backed up to ~/.dotfiles-backup/<timestamp>/ before being replaced. Running the script multiple times is safe — it skips symlinks that already point correctly.