search-first

To find existing npm packages and GitHub repositories before coding, initiate a parallel search across package registries and code repositories to surface reusable solutions and avoid recreating patterns. This scans npm, PyPI, GitHub, and Claude Code skills for viable options.

The best way to evaluate existing libraries for reuse is to score candidates across four dimensions: functionality, maintainability, licensing, and integration fit. This evaluation framework ensures the selected tool aligns with project constraints and long-term viability.

You need to search PyPI libraries and npm packages before building a feature whenever you want to avoid reinventing the wheel and wasting development time. Thorough pre-research surfaces existing tools and patterns to identify reusable solutions before writing code.

Yes, you can compare GitHub repositories and Claude Code skills for integration fit by running parallel searches across these sources and evaluating the candidates. The workflow scores each option to help you decide whether to adopt, wrap, or build.

To decide whether to adopt, wrap, or build a tool after pre-code research, evaluate the scored candidates based on functionality, maintainability, licensing, and integration fit, then choose the implementation pathway that best fits your project constraints.

The limitations of relying on pre-research for npm and PyPI package evaluation include the need to accurately assess maintainability and integration fit, as surface-level search results may not fully expose long-term maintenance risks or complex dependency conflicts.