search-first

To find existing libraries before writing custom code, define your functionality needs and framework constraints, then use parallel search to evaluate available tools based on maintenance and documentation.

The best way to evaluate tool selection for development optimization is to score potential solutions against functionality, community support, documentation, and license criteria before deciding to adopt or extend them.

To decide whether to reuse a library or build a custom solution, evaluate candidate tools against your defined constraints and score them, choosing to adopt, extend, or build based on the evaluation results.

Yes, you can integrate existing tools with your current framework constraints by analyzing your needs, searching for compatible libraries, and implementing the selected solution with any minimal custom code required.

You should not use library reuse for a new feature when existing tools score poorly in maintenance or documentation, making it more efficient to build a custom solution rather than extending an unsupported tool.

Yes, search-first works with any programming language because it begins by identifying your specific language and framework constraints before searching for existing community-sourced solutions to prevent redundant coding.