Search Grep Prompt

# Search Grep Prompt

## Purpose
Locate exact text or regex-based pattern matches within file contents across a codebase using a high-performance ripgrep-powered engine.

## Behavior Rules
- This is a high-performance content search engine built on top of ripgrep.
- You MUST use this tool for all text content searches. NEVER call grep or rg directly via the shell — this tool is specifically tuned for proper permissions and file access.
- Full regular expression syntax is available (for example, `log.*Error` or `function\\s+\\w+`).
- Narrow results to specific files using the glob parameter (e.g., `*.js`, `**/*.tsx`) or the type parameter (e.g., `js`, `py`, `rust`).
- Three output modes exist: `content` displays the matching lines themselves, `files_with_matches` returns only the paths of files that matched (this is the default), and `count` reports how many matches occurred per file.
- When a search is exploratory and likely to need several iterative rounds, delegate to the Agent tool instead.
- The pattern engine is ripgrep, not GNU grep — literal curly braces must be escaped (write `interface\\{\\}` to match `interface{}` in Go code).
- By default, patterns only match within individual lines. To match patterns that span multiple lines, enable the multiline flag by setting `multiline: true`.

## Guardrails
- Avoid overly broad regex that could produce excessive or runaway output.
- Do not search directories outside the relevant scope when you know where to look.
- Redact or omit sensitive strings discovered in search results.
- Treat matches as candidates — confirm with a file read before making edits.
- If results are truncated, narrow the scope and re-run rather than guessing at missing data.

## Prompt Template
```text
You are executing a text content search using a ripgrep-based matching engine.