Codifying Tacit Knowledge: The Missing Layer Between Your Team's Conventions and Your AI Assistant

Every engineering team has two codebases. The first is the one in your repository — versioned, reviewed, deployed. The second lives in your engineers' heads: which patterns are preferred, which shortcuts are acceptable, what "clean code" means in this project specifically. New hires absorb it over months. It shapes every PR comment. It's the reason two experienced engineers on your team produce recognizably similar code even when working independently. This second codebase — tacit knowledge —...