search-first

To research existing libraries before writing code, you can automate a structured pre-coding exploration across npm, PyPI, GitHub, and web sources to identify reusable tools and patterns. This systematizes the discovery process to accelerate delivery and reduce duplication.

The best way to decide whether to adopt, extend, compose, or build a dependency is to apply a structured decision framework after researching existing tools. This evaluates your findings against project needs and outputs a concise plan for concrete next steps.

To find existing tools on npm and PyPI when starting a new feature, run a structured pre-coding research session. This coordinates searches across package registries, GitHub, and web sources to identify available libraries and integration patterns.

You should run a pre-coding research session when starting a new feature, integrating dependencies, or evaluating new tech. It guides rapid exploration across MCP servers and web sources to record concrete next steps before development begins.

Yes, you can integrate MCP servers into your dependency evaluation workflow. The research-oriented workflow coordinates exploration across MCP servers, package registries, and GitHub to identify existing tools and patterns before you write code.

You need to research existing solutions before integrating dependencies to reduce duplication and accelerate delivery. Systematizing this practice ensures you identify and evaluate existing tools and patterns, preventing unnecessary code generation.