search-first

Researching existing solutions before building involves checking repositories, package ecosystems, and web sources to find mature libraries. This helps you decide whether to adopt, extend, compose, or build from scratch, reducing maintenance risk and saving time.

The best way to select dependencies for integration planning is to compare candidate tools across package registries and skills directories. This evaluates adopt, extend, or build decisions to ensure you choose proven patterns over custom implementations.

Searching GitHub repositories and MCP servers for proven patterns involves scanning these sources to discover existing tools. This discovery process helps evaluate if a mature library matches your feature needs before drafting any custom code.

Yes, tool discovery helps you decide between adopting a library or building from scratch by checking repository files and package registries. It compares candidate tools to determine if an existing solution solves your problem better and with less maintenance risk.

You should not use existing libraries and instead write custom implementation when tool discovery yields no mature solution matching your specific feature needs. If searches across package ecosystems and web sources prove insufficient, building from scratch becomes the necessary path.