MUST use as the first discovery step for repository and code search -- locating a feature, concept, symbol, component, setting, or keybind; reading a definition; tracing callers or references; mapping a file's structure or the project architecture; or…
Use when reviewing or understanding a code repository, exploring an unfamiliar codebase, finding where a function, symbol, component, setting, or keybind is defined, tracing who calls or imports a file, or extracting how a specific feature works. Reach for…
Use when about to edit, refactor, rename, or delete code, or before committing or opening a pull request, or when resuming a task and needing to see what was left unfinished. Reach for prowl-agent impact before a change to see its blast radius, prowl-agent…
Use right after you resolve something that cost real effort and will come up again: why a design is the way it is, a convention the code does not state, a trap that bit you, a question a teammate will ask twice, or an answer you had to reconstruct because a…