Pablo’s dotfiles

Overview

This is the public source repository for my command-line, Emacs, macOS, keyboard, application, and AI-agent configuration. It is a working personal configuration rather than a portable installer: many files assume my directory layout, installed applications, or local accounts. The README in each directory records what the tracked files do and how, if at all, they become live.

Activation model

Cloning the repository does not activate most of it. The main activation patterns are:

• home-directory or application-configuration symlinks pointing into this checkout;
• literate source files that are tangled into executable configuration;
• application exports that must be imported or copied deliberately; and
• commands, hooks, skills, or LaunchAgents that run only after they have been registered with their owner.

Some files are historical records or development inputs and are never loaded. The directory READMEs distinguish these cases. In particular, the repository’s .claude/ and .codex/ directories are project-local agent configuration; global Claude and Codex configuration lives under claude/ and codex/.

Directory map

The first column is deliberately machine-readable: bin/docs-audit checks it against the tracked top-level tree.

Directory	Documentation
.agent-learnings	Pending and archived agent-learning workflow state
.claude	Dotfiles-local Claude skills and shared agent topology
.codex	Dotfiles-local Codex skills and shared agent topology
.github	GitHub Actions workflow for Emacs extras
agents	Skills and configuration for Codex and Claude Code
ai-marketplace-monitor	AI marketplace monitor configuration
aider	Aider configuration and conventions
archive	Retired agent skills and their retained output
aspell	Aspell dictionaries
bin	Command index
claude	Global Claude Code configuration
codex	Global Codex configuration
colima	Colima configuration
dark-reader	Dark Reader settings export
docs	Design records, plans, and documentation policy
emacs	Emacs configuration and extras packages
enchant	Enchant dictionaries
enhancer-for-youtube	Enhancer for YouTube settings export
karabiner	Karabiner and Goku keyboard configuration
ledger	Ledger configuration
letterboxd-extras	Letterboxd browser extension assets
lib	Shared library code loaded from multiple tools
macos	macOS defaults, scheduled jobs, and security tools
mbsync	mbsync mail configuration
moon+reader	Moon+ Reader settings export
moonlander	Moonlander keyboard firmware source
mpv	mpv configuration
pantalaimon	Pantalaimon configuration
qBittorrent	qBittorrent settings export
rectangle	Rectangle settings export
shell	zsh startup files, shims, and history filtering
tests	Repository test suite
uBlacklist	uBlacklist subscription list
uBlock	uBlock Origin filters and settings
vimium	Vimium settings export

Public and private material

The repository is public by default. A tracked path is therefore public unless Git attributes explicitly send it through git-crypt. The encrypted classes are declared in the repository and subsystem .gitattributes files; examples include the shell secrets file, private agent skills, and private Emacs snippets. The public documentation may name an encrypted file and explain its role, but it must never reproduce its contents.

Ignored paths are not part of the published configuration. They include machine-local state as well as unencrypted private inputs and workflow records, such as local environment files, voice samples, and agent-learning candidates. Before publication, the guarded dotfiles workflow scans the exact outgoing history and candidate tree with deterministic rules and a model review. Ordinary git push is blocked; the publication design and controls are documented in the agent configuration manual.

Maintenance and verification

Documentation ownership and links are checked with:

bin/docs-audit audit

The generated tracked-skill inventory is refreshed with bin/docs-audit generate. Paired Claude/Codex configuration is checked with bin/ai-config-sync audit. The Python test suite runs with:

python3 -m unittest discover -s tests -v

Emacs extras also have their own batch runner and the GitHub Actions workflow. Changes to literate sources should be made in the source Org file, regenerated through its documented command, and reviewed as a source/generated pair.