Paper 2 · Question 5

A: Glob patterns in .claude/rules/ match files by pattern across the entire codebase. The conventions load automatically when editing any test file, regardless of directory. No maintenance burden as new test files are added.

B: With 50+ directories, this creates massive duplication and maintenance burden. Every new directory with tests would need a copy.

C: Root CLAUDE.md loads for every session. Test conventions would consume tokens even when editing non-test files like API handlers or database models.

D: Skills can auto-activate via a paths frontmatter, but they load on demand as a task-style workflow, not as always-in-context guidance. Test conventions must shape every edit to a matching file, which is what .claude/rules/ provides: rules load into context automatically when Claude reads a matching file, with no invocation step.