search-first

Identify existing tools, libraries, and patterns before writing custom code.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/Mark393295827/house-maint-ai --skill search-first-mark393295827
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-first
Source: https://github.com/Mark393295827/house-maint-ai/tree/main/skills/search-first
Command: npx skills add https://github.com/Mark393295827/house-maint-ai --skill search-first-mark393295827

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematizes the "search for existing solutions before implementing" workflow to prevent duplication of effort and accelerate delivery.

Core Features & Use Cases

  • Structured research workflow: identify language/framework constraints and surfaces existing libraries, tools, and patterns.
  • Evaluation and decision points: apply a decision matrix to choose Adopt, Extend, Compose, or Build based on fit, maintenance, licensing, and integration effort.
  • Guided deployment: steps from NEED ANALYSIS to IMPLEMENT to ensure alignment with project goals.

Quick Start

Execute a quick pre-code research pass before implementing a feature to identify existing tools and patterns.

Frequently Asked Questions about search-first

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

FAQPage Schema
How do I research existing libraries and tools before writing custom code?

To research existing libraries and tools before writing custom code, execute a structured pre-code research pass that identifies language and framework constraints, surfaces reusable patterns, and evaluates candidates using a decision matrix to prevent duplicated effort.

What is the adopt, extend, compose, or build decision matrix for software dependencies?

The adopt, extend, compose, or build decision matrix is a framework for evaluating software dependencies, scoring existing libraries and patterns on fit, maintenance, licensing, and integration effort to document the rationale for implementation choices.

When should I search for existing patterns instead of implementing a new feature from scratch?

You should search for existing patterns instead of implementing from scratch whenever starting feature work, dependencies, integrations, or utility creation, ensuring a guided deployment workflow from need analysis to implement prevents duplicated effort and accelerates delivery.

What's the best way to prevent duplicated effort when adding utility functions or integrations?

The best way to prevent duplicated effort when adding utility functions or integrations is to systematize a search-first workflow that identifies existing tools and evaluates them against project goals before writing custom code.