One Claude, Two Lives

A few days ago I wrote about solving portable Claude context with a symlink instead of an MCP server. The setup was simple: a private GitHub repo with my CLAUDE.md , cloned on two machines, symlinked into place. Two commands. Done. That was the right solution for the original problem. But the original problem was small: make Claude remember who I am on both machines. The problem grew. The toolkit outgrew the file The first version of claude-context had three things: a CLAUDE.md file, a persona definition, and six agent markdown files (code review, technical writing, editing, specs, research, test analysis). Everything Claude needed to know about how I work, loaded at session start. Then I started building skills — custom slash commands that Claude Code executes like macros. /checkpoint stages and pushes all my repos. /pdf converts markdown to styled PDFs. /runbook generates operational documentation with rollback steps and escalation contacts. Then came templates. Meeting notes with de