codebase-search

Navigating a multi-module repository requires consulting the `.codebase/` directory documentation such as ARCHITECTURE.md and DIRECTORY.md first. This identifies project architecture and module relationships to guide efficient code search and reduce exploration scope.

The best way to find the right API surface is by reading the `.codebase/API.md` file before executing a code search. This provides the intended API structure and context, allowing you to pinpoint target files efficiently without guessing directory locations.

You need to check `.codebase/` documentation when exploring new modules or APIs across a multi-module repository. Reading files like MODULES.md and PATTERNS.md beforehand clarifies the architecture and intended implementation patterns before you search the codebase.

Yes, you can use project context to narrow down code search scope by leveraging `.codebase/DATABASE.md` and `.codebase/MODULES.md` first. Understanding these documented contexts directs you to the correct directory structure and implementation locations efficiently.

Searching code directly misses the intended architecture because it skips the `.codebase/ARCHITECTURE.md` and `.codebase/PATTERNS.md` context. Without consulting these documents first, raw code search ignores the project's structural design and module boundaries, leading to inefficient exploration.