I work on multiple git worktrees of the same repo simultaneously, so I keep my Claude config in a parent directory and symlink it into each worktree. One place to update settings, policies, skills - they all stay in sync.
I use a policy MCP server that serves my coding standards as markdown files. I reference them with a § notation and they get pulled into context automatically. The server recursively resolves references, so if one policy points to another (like general code rules pointing to C++ specific rules), it follows the chain and pulls in everything needed. I have general rules, code quality rules, and C++ specific style all defined once and injected when needed.
I've set up a few skills to streamline things. The engineer skill loads the relevant policies before any code gets written. The continue/restart skills let me save session state to a continuation plan and pick up where I left off later.
Checkmate handles linting validation - different rules for different parts of the codebase (C++ engine code vs TypeScript cloud workers vs shell scripts).
Basically: policies keep the code consistent, skills keep the workflow consistent, and the shared config keeps everything in sync across worktrees.
I work on multiple git worktrees of the same repo simultaneously, so I keep my Claude config in a parent directory and symlink it into each worktree. One place to update settings, policies, skills - they all stay in sync.
I use a policy MCP server that serves my coding standards as markdown files. I reference them with a § notation and they get pulled into context automatically. The server recursively resolves references, so if one policy points to another (like general code rules pointing to C++ specific rules), it follows the chain and pulls in everything needed. I have general rules, code quality rules, and C++ specific style all defined once and injected when needed.
I've set up a few skills to streamline things. The engineer skill loads the relevant policies before any code gets written. The continue/restart skills let me save session state to a continuation plan and pick up where I left off later.
Checkmate handles linting validation - different rules for different parts of the codebase (C++ engine code vs TypeScript cloud workers vs shell scripts).
Basically: policies keep the code consistent, skills keep the workflow consistent, and the shared config keeps everything in sync across worktrees.
(edited for formatting)