search-first

Identify and compare existing tools, libraries, and patterns before implementing a feature.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/RUSHYOP/imperium-cli --skill search-first-rushyop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-first
Source: https://github.com/RUSHYOP/imperium-cli/tree/main/content/skills/search-first
Command: npx skills add https://github.com/RUSHYOP/imperium-cli --skill search-first-rushyop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematizes the practice of researching existing solutions before coding, reducing rework and promoting reuse.

Core Features & Use Cases

  • Structured discovery: guides you to locate relevant tools, libraries, and patterns before writing custom code.
  • Informed decision-making: evaluates candidates for maintainability, compatibility, and licensing to recommend the best option.
  • Use Case: when starting a feature, run the researcher to identify existing components and decide whether to adopt, extend, or build.

Quick Start

Ask the researcher agent to find existing tools for your feature, evaluate the top candidates, and propose the best approach.

Frequently Asked Questions about search-first

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find existing libraries and patterns before implementing a new feature?

To find existing libraries and patterns, query registries like npm, PyPI, and GitHub to locate relevant tools, evaluate their maintainability and community support, and decide whether to adopt, extend, or build your solution.

What criteria should I use to evaluate and compare libraries for adoption?

Evaluate and compare libraries for adoption using criteria like maintainability, license compatibility, community support, and documentation quality to promote reuse and minimize future rework.

When should I research existing tools instead of writing custom code?

Research existing tools instead of writing custom code when starting feature development, integrating dependencies, or making architecture decisions across frontend, backend, and tooling tasks to promote reuse and reduce rework.

What is the best way to decide whether to adopt, extend, or build a software component?

The best way to decide whether to adopt, extend, or build a software component is to run a structured discovery process that evaluates top candidates against maintainability, compatibility, and licensing criteria to propose the most viable approach.

Does this research approach work for both frontend and backend architecture decisions?

Yes, this research approach applies to feature development, dependency integration, and architecture decisions across frontend, backend, and tooling tasks by identifying and evaluating existing tools before implementation.