ss-search-first

To find existing libraries before writing custom code, use a research-first workflow to search package registries, codebases, and code hosting platforms for pre-existing solutions. This prevents redundant work by leveraging existing tools instead of reinventing the wheel.

A research-first workflow for new feature development is the practice of systematically checking codebases, package registries, and code hosting platforms for existing tools before writing custom code. It ensures efficient resource discovery and informed decision making.

Yes, you can use this to discover existing utility functions for common problems. It proactively searches codebases and package registries to identify pre-existing solutions, providing a structured evaluation of potential candidates based on functionality, maintenance, and licensing.

The best way to evaluate dependencies before adding them to a project is to use a research-first discovery process that provides a structured evaluation of potential candidates. It assesses functionality, maintenance, and licensing to support informed decision making for new feature development.

You should avoid writing a custom API client from scratch when a research-first search identifies an existing, well-maintained library for that common service. This prevents redundant work by ensuring existing solutions are identified and leveraged before custom code is written.