smart-explore

# Smart Explore: Local Code Navigation Use cheap structure before reading large files. The goal is precise outline and extraction from a known area, not repo-wide search. ## Boundary Use this skill for: - known-file outlines - known-module outlines - targeted symbol lookup in a bounded scope - exact function, class, method, or type extraction - read-next ranges after another search/review tool narrowed the area Do not use this skill for: - repo-wide structural pattern search - ast-grep rule authoring or code-shape queries - architecture, semantic flow, or "how does X work?" questions - broad "find all implementations/callers in the repo" requests - codegraph, GitNexus, dependency, churn, or blast-radius evidence For those, use a dedicated repo-wide search or architecture-analysis workflow. Return to smart-explore only after the scope is a known file, module, or symbol. ## Tool Order 1. Structure-aware outline tools for known files or modules, when available. 2. Structure-aware symbol search for a known symbol or concept in a bounded scope, when available. 3. Structure-aware unfold/extraction for exact function/type source, when available. 4. `rg` for exact text fallback when structure tools are unavailable. 5. `fd` for candidate file discovery when the file path is missing. 6. Read full files only when smaller structural views are insufficient. ## When to Use Which - File structure at a glance — outline tool when available. - Bounded symbol discovery — symbol searc...