search-firstlisted

# /search-first — Look Outside, Report, Let the Caller Pick The searcher reports what exists outside and how it differs from our situation. The caller — the main loop, a build session, an RFC author — reads the report and decides what to adopt, adopt in part, or leave. An established candidate that matches the need is adopted by default; adopt-in-part means taking the library's code for one piece (its parser, its data model) inside our own control flow, and a piece that transfers is worth the search (RFC-0022). Building our own is chosen when the report names the gap no candidate fills. ## 0. State the question in text Before the first tool call, write 2–3 sentences of plain assistant text: the question, which row(s) of the table below it belongs to, and the constraints (language, existing deps, license, budget). Tool arguments may mirror this text; the chat text is what lets the user redirect before effort is spent. When the need is code to write — an adapter, an API client, a parser, a utility — state it as a Library / tool choice: which established library already does this. Asking which endpoint to call or which algorithm to use yields an answer that can only be hand-coded. ## 1. Check this repo first One `rg` / Glob pass through the relevant modules, skills and notes. The thing may already exist here. Then go outside. ## 2. Search by question type The rows are handles for where to look and when to stop. A question that fits none still runs; a question that fits t