dhpk-codebase-explorationlisted

# Codebase exploration Use the smallest mode that answers the question. The default is a single perspective symbol/flow trace: locate the entry point, follow callers and callees, and report evidence with file and line references. Do not turn a simple lookup into a review or a speculative architecture redesign. ## Modes | Invocation | Behavior | Additional reading | |---|---|---| | default | Symbol/flow trace with one coherent report | `references/search-patterns.md` when search strategy is unclear | | `--dual` | Run Claude and Codex independently, then reconcile agreements and gaps. Keep the Codex prompt clean: pass the question and project path, never Claude's conclusion. | `references/dual-perspective.md` | | `--explain --depth brief\|normal\|deep` | Ask for an explanation of a target file or symbol. `brief` is one sentence; `normal` adds flow and concepts; `deep` adds dependencies, complexity, and risks. | `references/explain.md` | If `--dual` and `--explain` are combined, use the explanation depth for both perspectives and still keep their research independent. If depth is omitted, use `normal`. ## Default workflow 1. Identify the question, repository root, and target symbol or entry point. 2. Inspect definitions and references; prefer symbol-level evidence over loading unrelated files. 3. Trace the data/control flow until the observable output or failure edge is accounted for. 4. Record assumptions, edge cases, and unresolved links. A clean prompt and inde