search-first

To discover existing libraries before implementing new code, use a parallel research process that searches npm, PyPI, MCP servers, and GitHub to score candidates by functionality, maintainability, documentation, and licensing, yielding explicit decisions to adopt, extend, compose, or build.

The best way to find reusable tools for a new software feature is orchestrating parallel discovery workflows across package managers like npm and PyPI, assessing existing patterns to reduce code duplication and risk before initiating development.

Yes, you can assess dependency updates and code reuse patterns by running parallel searches across GitHub and npm, evaluating the functionality and dependencies of existing candidates to determine whether to adopt or wrap them.

You need a tool discovery workflow during feature initiation, dependency updates, or when introducing a new utility, ensuring you maximize code reuse and reduce duplication by finding proven patterns before implementation.

When assessing existing libraries and patterns, you can expect explicit decision outcomes to adopt as-is, extend or wrap, compose multiple tools, or build a new implementation based on structured criteria scoring.