dotfiles

This is my dotfiles repo. There are many like it, but this one is mine.

Agents

Aggregated instructions and skills shared by all agents.

Setup

Run the installation script:

./agents/install.sh

It copies AGENTS.md and skills/ into ~/.agents/, links Claude's instructions and skills to them, and links Pi's AGENTS.md to the shared instructions. Pi discovers ~/.agents/skills/ directly. Re-running the script picks up every skill directory in that location.

What's included

• AGENTS.md: Global instructions defining my coding preferences.
• skills/find-skills: Finds and installs skills from the open skill ecosystem, from vercel-labs/skills.
• skills/my-servers: My registry of remote servers and how to reach them over SSH.

Pi

Pi is my currently preferred harness because CC is driving me insane since Opus 5.

Setup

1. Install Pi:

   npm install -g --ignore-scripts @earendil-works/pi-coding-agent

2. Install the shared instructions and skills (see Agents).

3. Install the Pi-specific settings and resources:

   ./pi/install.sh

4. Install or update the configured Pi packages:

   pi update --extensions

What's included

• settings.json: Theme, default model and thinking level, and package declarations.
• extensions/statusline.ts: Custom footer showing model, context usage, diff statistics, token counts, cost, and Pi version.
• themes/sukiboo.json: Custom theme based on my terminal palette.
• package.json and tsconfig.json: Local TypeScript diagnostics for the extension.
• Authentication, sessions, generated images, package caches, and other machine-local state are intentionally excluded.

Install the development dependencies before editing or checking the extension:

npm install --prefix pi
npm run check --prefix pi

Claude Code

Claude is love, Claude is life.

Setup

1. Install the shared instructions and skills (see Agents).

2. Copy the Claude-specific files from claude/ to ~/.claude/:

   mkdir -p ~/.claude && cp claude/settings.json claude/statusline-command.sh ~/.claude/

3. Ensure bash, bc, and jq are installed for the custom status line.

What's included

• settings.json: Permission rules, enabled plugins, and model, theme, and effort preferences.
• statusline-command.sh: Custom status line showing model, context usage, token counts, and cost.
• Global instructions and skills are symlinked from ~/.agents/, not stored here.

VS Code

VSCode is my IDE of choice nowadays (again!), mainly because of seamless Claude Code integration. When every "Agentic IDE" is a "VSCode fork", why not use the original?

Setup

1. Copy files from code/User/ to ~/.config/Code/User/:

   cp -r code/User/* ~/.config/Code/User/

What's included

Editor settings, Python/Lua/Jupyter config, Claude Code integration, and UI preferences.

Cursor

Cursor is where the work happens nowadays because AI (well, maybe not anymore...). My preferred configuration -- minimal UI, no AI suggestions, format on save.

Setup

To use this Cursor configuration:

1. Install Cursor (if not already installed):

   • Download from cursor.sh

2. Copy files from cursor/User/ to ~/.config/Cursor/User/:

   cp -r cursor/User/* ~/.config/Cursor/User/

What's included

Editor settings, keybindings (F5 for Python), Python config, and UI preferences.

Terminal

My GNOME Terminal color scheme. Nothing fancy, just a dark theme with a custom color palette that I find a bit more pleasant to look at -- and I do have to look at terminals a lot.

Setup

To use this terminal color configuration:

1. Navigate to the terminal/ directory:

   cd terminal/

2. Run the installation script:

   ./install.sh

   The script will automatically generate a new profile UUID and set it as default.

3. Restart your terminal for changes to take effect.

What's included

Custom 16-color dark palette, bold-is-bright, and profile settings.

Geany

My Geany configuration. It's a nice lightweight IDE that was my go-to prior to Cursor, and I still choose it for non-AI workflows (even though those are becoming excessively rare).

Setup

To use this Geany configuration:

1. Install Geany, the Auto-mark plugin, and built-in terminal support:

   sudo apt install geany geany-plugin-automark libvte9

2. Copy files from geany/ to ~/.config/geany/:

   cp -r geany/* ~/.config/geany/

3. Enable the Auto-mark plugin:

   • Tools → Plugin Manager → Enable Auto-mark

4. Change colorscheme (optional):

   • View → Change Color Scheme... → Select desired scheme

5. Configure build commands (optional):

   • Build → Set Build Commands
   • Execute commands:
     • Run: python3 %f
     • Run in Python: python3 -i %f

What's included

Colorschemes, keybindings, filetype definitions, and editor settings.

Pre-commit

Pre-commit configuration (.pre-commit-config.yaml) that I use in my Python projects so that my code doesn't look like shit.

Setup

To use this pre-commit configuration in a repository:

1. Copy the .pre-commit-config.yaml file from precommit/ to the project root
2. Install pre-commit (if not already installed):

   pip install pre-commit

3. Install the git hooks:

   pre-commit install

Usage

• Pre-commit hooks will automatically run on git commit
• To run hooks manually on all files:

  pre-commit run --all-files

• To update hooks to latest versions:

  pre-commit autoupdate

What it checks

File validation, code quality, security (bandit), Python tools (mypy, isort, flake8, black), and Jupyter support via nbQA.

Texmaker

My Texmaker configuration. An open source LaTeX editor with syntax highlighting and integrated PDF viewer from the good old PhD days.

Setup

To use this Texmaker configuration:

1. Install Texmaker:

   sudo apt install texmaker

2. Copy the Texmaker configuration to ~/.config/xm1/:

   mkdir -p ~/.config/xm1
   cp -r texmaker/xm1/. ~/.config/xm1/

What's included

Editor settings, build commands, spell checker dictionary, and view preferences.