원클릭으로
find-symbols
Use when locating where a symbol, function, type, command, or constant is defined or referenced, instead of grep/find/read chains.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when locating where a symbol, function, type, command, or constant is defined or referenced, instead of grep/find/read chains.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when waiting for servers, jobs, files, tests, queues, or external processes.
Use when a bounded subtask is summarization, mechanical review, fixture inspection, proposal triage, verification, or boilerplate.
Use when tempted to add broad abstractions, future-proofing, or extra product surface beyond the requested change.
Use before asking the user about infrastructure, preferences, conventions, prior decisions, or past incidents.
Use when evaluating reviewer feedback, review delegates, or suggested code changes.
Use when you need a project fact, document, relationship, investigation note, or prior finding that may already be captured.
| name | find-symbols |
| description | Use when locating where a symbol, function, type, command, or constant is defined or referenced, instead of grep/find/read chains. |
| source | bundled |
| triggers | {"tool":["Bash"],"arg_pattern":["rg ","grep ","find "]} |
Use Aimee's code index before starting a broad text search for a code symbol.
Preferred route:
find_symbol tool or run aimee index find <symbol> for definitions and references.rg only when the index has no entry, is stale, or the target is plain text rather than a code symbol.The index is meant to avoid exploratory grep/find/read chains. If it gives a precise file and line, use that as the starting point.