A school-district SIS app folder needs module-local Claude notes that should not flood the whole monorepo. What scoping fits?
Select an answer to reveal the explanation.
Short Explanation
Drop a CLAUDE.md in the SIS subdirectory—like a department memo on that office door—so local notes stay local instead of wallpapering the whole district monorepo.
Full Explanation
Module-local Claude notes that must not flood the whole monorepo belong in a directory-level CLAUDE.md under that module. For a school-district SIS app folder, placing CLAUDE.md in the SIS subdirectory scopes guidance to work done in that tree without wallpapering unrelated packages.
Why the correct option works: directory-level CLAUDE.md provides subdirectory scoping. SIS-specific enrollment rules, data dictionaries, and coding notes apply when the agent works in that app and stay out of the way elsewhere in the district monorepo.
Why the other three fail by concept: putting SIS-only notes only in a distant unrelated package’s CLAUDE.md scopes them to the wrong place. Requiring every note to live exclusively in global user settings blocks team sharing and pollutes personal scope with module policy. Forbidding any CLAUDE.md below the repository root under all cases denies the subdirectory scoping feature the stem needs.
Exam caveat: nested CLAUDE.md supplements, rather than always replacing, higher-level project guidance—know both layers exist. Operational check: add SIS directory CLAUDE.md, open a session rooted in that app versus another package, and confirm SIS notes appear in the SIS context without dominating unrelated packages.