What problem does it solve? Developers often jump straight into building features or adding dependencies without checking whether a maintained, well-tested solution already exists, leading to duplicated effort, dependency bloat, and unnecessary maintenance burden. ## Core Features & Use Cases - Adopt/Extend/Compose/Build Decision Matrix: Provides a structured framework for choosing between reusing an existing library, extending one, composing multiple small tools, or building from scratch. - Multi-Source Search Process: Covers searching npm/PyPI, GitHub (via gh CLI), MCP registries, and existing local skills before writing any code. - Candidate Evaluation Criteria: Defines concrete checks for maintenance activity, popularity, quality, bundle size, license compatibility, and API fit. - Use Case: Before adding a date-formatting dependency, run the search process to discover that native Intl.DateTimeFormat covers the requirement, avoiding an unnecessary package. ## Quick Start Ask the agent to research existing solutions before implementing a new feature, for example: "search for existing libraries before we build a retry mechanism."