skills.rest
EvanPluchart
EvanPluchartCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

search-first

Guide systematic searches for existing solutions before custom development.

2|Updated Mar 19, 2026
Search Tags:#code reuse#engineering workflow#library selection#dependency evaluation#mcp skills#semantic grep#pre-implementation research
One-click install
npx skills add https://github.com/EvanPluchart/kyomu --skill search-first-evanpluchart
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: search-first
Source: https://github.com/EvanPluchart/kyomu/tree/main/.claude/skills/search-first
Command: npx skills add https://github.com/EvanPluchart/kyomu --skill search-first-evanpluchart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces wasted engineering effort by forcing a systematic search for already-existing solutions (inside the repo, in the ecosystem, or via tools) before implementing anything custom.

Core Features & Use Cases

  • Project-first discovery: performs semantic grep for relevant functions/components and checks documented patterns in the repository’s known tech directories, plus existing utilities in common code folders.
  • Ecosystem and tooling search: evaluates maintained third-party libraries and checks MCP/skills/available CLIs that could cover the need.
  • Decision matrix with justification: classifies outcomes as Reuse, Adopt, Extend, Compose, or Build, and requires a short research report before coding.

Quick Start

Ask the AI to evaluate your intended feature implementation using Search-First, produce a concise search report, and recommend whether to reuse, adopt, extend, compose, or build.

Frequently Asked Questions about search-first

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

FAQPage Schema
How can I check for existing code and libraries before writing a new feature?▼

You can prevent unnecessary custom development by running a systematic search across your codebase, evaluating external libraries, and checking available MCP skills or CLIs to find existing solutions before writing new code.

How do I evaluate whether to reuse an existing library or build a custom utility?▼

Evaluating whether to reuse or build involves classifying outcomes using a decision matrix that compares existing third-party libraries and internal utilities against your specific requirements before you start coding.

What is the best way to search a codebase for reusable functions before implementing a feature?▼

The best way to find reusable functions is performing a semantic grep across your repository's known tech directories and common code folders to identify existing utilities, components, and documented patterns.

When should I avoid searching for existing solutions and just write custom code?▼

You should only write custom code after completing a pre-coding research report that verifies no suitable existing solutions, maintained libraries, or available MCP skills exist to cover your specific implementation needs.

Related Skills

Explore More Software Engineering Skills→
juanjaragavijuanjaragavi

mgrep-code-search

Perform semantic search across large codebases using natural language queries.

Community
Advanced
djacobsmeyerdjacobsmeyer
3

build-skill

Read a markdown plan file, execute its steps, and report git-diff changes.

Community
Intermediate
AribSudiaAribSudia
2

arib-memory-search

Search project memory files for historical decisions using semantic and lexical methods.

Community
Advanced
zbl91555zbl91555

exa-web-search-free

Search web content, code repositories, and company profiles without API keys.

Community
Basic