How I Manage Claude Code Context Across 20+ Repositories

This post was originally published on graycloudarch.com . Every new Claude Code session starts cold. Claude doesn't know your naming conventions, your Terraform state backend configuration, your Jira workflow, or the architecture decisions you made six months ago. It doesn't know you prefer Terragrunt over raw Terraform, that your AWS accounts follow a specific naming scheme, or that your team's PR descriptions follow a particular format. You either re-explain everything at the start of each session, or you watch Claude suggest patterns that don't fit your environment. I run Claude Code daily across a 6-account AWS platform monorepo, a personal consulting site, homelab infrastructure, and a handful of side projects. After six months of experimentation, I landed on a three-tier context hierarchy that loads the right context automatically depending on which directory I'm working in --- and I manage all of it from a single dotfiles repo. The Problem with Single-File Context Claude Code lo