[FEATURE] stop_traversal directive for CLAUDE.md

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Why this matters:

In monorepos, legacy solutions, and mixed-team environments, different parts of the codebase are owned by different teams with different
levels of AI adoption and tooling maturity. A frontend team that wants to use Claude Code effectively shouldn't be blocked or forced to
pull strings at higher organizational levels just because the root CLAUDE.md doesn't exist, is poorly maintained, or contains irrelevant
backend-specific instructions.

As a frontend developer, I want to define a clean CLAUDE.md for my sub-project and have it be self-contained - without inheriting noise
from parent directories I have no ownership over. stop_traversal would let each team own their AI tooling configuration independently,
which is especially important when:

• Not all team members are into AI tooling yet
• AI skills and adoption vary across teams
• The root project is legacy and nobody wants to touch shared config
• Sub-projects are effectively independent despite sharing a repo

Proposed Solution

When working in a subdirectory of a monorepo (e.g. cd frontend && claude), all parent CLAUDE.md files are loaded automatically via upward
directory traversal. There's currently no way to prevent this.

Requested: A stop_traversal directive, either in CLAUDE.md or .claude/settings.json, that tells Claude Code "don't look further up the
directory tree."

Alternative Solutions

To my knowledge there is no easy way to do this so what I'm stuck with is too be involved with other teams and their structure. In many (not all) instances when it's legacy projects they revolve around backend so trying to convince people to structure things in a specific way isn't always easy.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_