The infrastructure-as-code repository contains Terraform modules (/terraform/), Kubernetes manifests (/kubernetes/), and CI/CD pipeline scripts (/pipelines/). Each needs distinct conventions, yet the single root CLAUDE.md has grown beyond 500 lines. When developers work on Kubernetes files, Terraform-specific rules are unnecessarily loaded into context and consume tokens.
What is the best way to reorganize this so that only relevant guidance loads when editing particular file types?
Community Discussion
No comments yet. Be the first to start the discussion!
Community Discussion