recall

To understand a codebase's architecture quickly, you can query existing project documentation and codebase structure. This approach retrieves design rationale and contextual information by prioritizing research documents before falling back to code exploration.

The best way to find out how a specific module works is to ask a general question about its behavior. The system will first search existing research and plan directories for relevant documentation, and if none is found, it will explore the codebase directly.

Yes, you can retrieve project context and design rationale without manually reading all the code. By querying for project specifics, the tool intelligently searches existing documentation and performs codebase exploration to provide quick answers.

Yes, this approach prioritizes existing documentation over codebase exploration. It prefers relevant existing research and plan documents to explain system design, only falling back to exploring the codebase if the documentation lacks the needed answers.

To get explanations for existing behaviors and component interrelations, you can inquire about project specifics. The system retrieves information about architecture and structure by querying existing documentation, satisfying the need for quick contextual understanding.

You should use a documentation-first approach for codebase information retrieval when you need quick, contextual understanding of project components. It intelligently searches existing research and plans to explain design decisions before attempting deeper codebase exploration.