read-docs

To search internal project documentation, provide specific keywords to retrieve relevant patterns, conventions, architecture details, or domain knowledge. The search prioritizes exact filename matches, filename content matches, and content matches within Markdown files.

Finding project-specific conventions before implementing a feature requires searching internal documentation with relevant keywords. This retrieves documented patterns and potential pitfalls, prioritizing exact filename matches and Markdown content matches to quickly deliver needed architectural context.

You can use keyword search to find domain knowledge across Markdown files by matching provided terms against file contents. The search mechanism applies targeted queries to quickly retrieve relevant project-specific information and architectural details.

Targeted search prioritizes results by relevance and file location when looking for project architecture details. It ranks findings based on exact filename matches, filename content matches, and content matches found specifically within Markdown files.

Searching for internal documentation works for finding database schema information by applying targeted keyword queries to the project knowledge base. It retrieves relevant details by matching search terms against filenames and Markdown file contents.

Limitations of retrieving project info using keyword search include its reliance on exact filename matches, filename content matches, and Markdown file content matches. It may not surface undocumented domain knowledge or conventions not explicitly written in the searched files.