In this repository the documentation is a build artifact: `CLAUDE.md`, `AGENTS.md` and `README.md` are validated by the `claude-code-enforcer` rules, and a `-DenforceClaudeMd` build fails when they drift. Edit them with the rules in mind rather than discovering them in CI.

Add or change a rule in `claude-code-enforcer`, the module of custom `maven-enforcer-plugin` rules that guard this repository's agent-facing files. Every rule follows the same shape, so getting the shape right is most of the work.

Systematic code review for the `tools` multi-module reactor. Start with the rules this repo *enforces at build time* — an ArchUnit or Surefire violation fails the build, not just review — then work through the general Java checks.

Keep `pom.xml` edits and build commands consistent with how the `tools` multi-module reactor is wired. Getting versions in the wrong place, or missing a profile, is the most common source of avoidable build friction here.

Expose functionality over the Model Context Protocol using `mcp-common`, the shared scaffolding behind all three servers here (`data` uniqueness, `code/context`, `adopt`). Transport, registration and error handling are already solved — a new tool writes none of that.

Generate and use the compile-time-safe protobuf builders produced by `code/protogen-maven-plugin`. The point of this module is **shift-left**: stock protobuf builders only detect a missing `required` field at runtime (an `UninitializedMessageException` from `build()`), while the generated builder ch

Review and apply SOLID in the `tools` reactor. The heuristics below are the fast path; long before/after code lives in **`examples.md`** next to this file — load it only when a worked example would actually help.