search-first

Scan codebases for existing components before creating new implementations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/argmin-com/landing-page --skill search-first-argmin-com
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-first
Source: https://github.com/argmin-com/landing-page/tree/main/.claude/skills/search-first
Command: npx skills add https://github.com/argmin-com/landing-page --skill search-first-argmin-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Search-first helps teams avoid duplicating work by forcing a pre-check for existing implementations before starting new tasks, ensuring consistency and reuse across the codebase.

Core Features & Use Cases

  • Reuse existing components, patterns, and utilities when a close match exists.
  • Guide when to extend an existing pattern versus create a new one.
  • Provide a decision framework with concrete commands to audit the codebase.

Quick Start

Start by scanning the repository for components or utilities that match your needs and decide to reuse, extend, or create a new pattern.

Frequently Asked Questions about search-first

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

FAQPage Schema
How do I check the codebase for existing implementations before writing new code?

To reuse existing code, scan the repository for matching components or utilities and apply a decision framework. This pre-check enforces codebase consistency and prevents duplicating work before starting new tasks.

What is the best way to decide whether to extend an existing component or create a new one?

The best way to decide whether to extend or create is to apply a decision framework after scanning for matching components. Consulting the design system guides this choice to ensure proper pattern reuse across the codebase.

Why should I search the codebase for matching patterns before coding new features?

Searching the codebase for matching patterns before coding ensures consistency and maximizes code reuse. This search-first pre-check prevents duplicating work and helps teams extend proven implementations rather than rebuilding them.

How do I audit my repository for reusable utility functions and design system components?

Audit your repository for reusable utility functions by running concrete commands to scan for matching components. Consulting the design system during this scan identifies opportunities to reuse, extend, or create existing patterns.

When should I avoid reusing an existing implementation and build a new pattern instead?

You should avoid reusing an existing implementation and build a new pattern only when scanning reveals no close match. The decision framework dictates creating new patterns when extending existing utilities or design system components is unfeasible.