search-first

Pre-implementation research prevents wasted effort by systematically checking package registries and MCP servers to identify existing solutions. It ensures you evaluate and adopt battle-tested libraries before writing any custom code.

Evaluating candidate solutions against project constraints requires a structured decision matrix framework. This helps you systematically compare dependencies from package registries to decide between adopting, extending, or building custom solutions.

Check MCP servers for existing utilities before feature development, dependency integration, or utility creation tasks. This research-first approach identifies existing tools to adopt, saving development time and reducing maintenance overhead.

Yes, the research-before-coding workflow requires access to external package registries and repository search tools. These dependencies are necessary to query candidate solutions and evaluate existing libraries against project constraints.

Decide between adopting a library or building a custom solution by applying a structured decision matrix to your research results. This framework evaluates candidate solutions found in registries against project constraints to determine whether to adopt, extend, or build.

Researching existing tools before creating a custom HTTP retry utility saves development time and reduces maintenance overhead. The research-before-coding workflow helps you find and adopt battle-tested libraries instead of reinventing existing solutions.