search-first

To prevent duplicate logic, enforce a search-first approach using glob and grep_search to locate existing utilities and patterns before writing new code. This ensures you reuse established implementations and align new work with existing structures.

A search-first protocol is a strict policy requiring developers to search for existing functions and tests before modifying the codebase. It involves defining need and scope, running code lookups, and analyzing reuse opportunities to reduce maintenance risk.

Find existing utilities and tests by executing glob-like searches and code-lookups across the repository. This discovery phase identifies established patterns and test coverage, allowing you to adapt current implementations instead of creating redundant ones.

Yes, applying a search-before-write policy scales to large code repositories by using glob and grep_search tools to locate established patterns. It prevents redundant work by enforcing a reuse-first analysis phase before any code modification occurs.

You should search for existing patterns to avoid duplicating logic and missing established tests. Reusing or adapting current utilities reduces rework, lowers maintenance costs, and minimizes risk by ensuring new features align with the codebase.