Repository Cartography
- Read root and nested instruction files first:
AGENTS.md,CLAUDE.md,MASKSHIFT.md, package manifests, and build files. - Map entry points, package boundaries, generated code, tests, and ownership patterns. Prefer
git ls-files,rg, language manifests, and the repository index over broad file reads. - Trace one representative request or data path end to end before deciding where new code belongs.
- Name the minimal edit set and the tests/build commands that prove the change.
- Do not create a parallel architecture when an existing extension point already exists.