search-first

To check existing code, scan the repository structure including core, api, and tests directories alongside dependency lists and documentation. This pre-implementation check identifies established design patterns and existing components to extend or compose rather than writing new code.

The best way to discover reusable libraries is scanning dependency lists and documentation to locate established conventions. This pattern discovery process guides decisions on adoption, extension, or new implementation by ensuring accurate reuse across project contexts.

You need to scan documentation before coding whenever starting a new feature to determine reuse versus new work. Consulting the repository locates existing components that can be extended or composed, ensuring accurate reuse and adherence to established design patterns.

Codebase pattern discovery works by scanning the repository structure and dependency lists to identify established design patterns and conventions. It locates existing components that can be extended or composed, guiding decisions on adoption versus new implementation.

Yes, repository structure scanning supports determining adoption versus new implementation by examining core, api, and tests directories alongside dependency lists. It identifies whether existing code, docs, or libraries solve the target task across codebases and project contexts.