dist/pi/skills/smart-explore/SKILL.md
Token-efficient local code navigation and extraction. Use when exploring a known file or bounded module outline, finding a known symbol in a scoped area, or extracting exact function/type bodies with smart_outline, smart_search, and smart_unfold. NOT for repo-wide structural pattern search, architecture or trace-flow questions, ast-grep/codegraph/GitNexus evidence, or broad caller/implementation maps.
npx skillsauth add alexei-led/claude-code-config smart-exploreInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use cheap local structure before reading large files. The goal is a tight outline or exact extraction from a known area, not repo-wide codebase search.
Use this skill for:
Do not use this skill for repo-wide structural patterns, ast-grep rules, trace-flow, "how does X work", zoom-out maps, all-callers searches, codegraph, GitNexus, or architecture evidence. Use a dedicated repo-wide search or architecture-analysis workflow first; return here only after the scope is a known file, module, or symbol.
rg for exact text or symbol fallback in a bounded scope.fd for candidate file discovery when the path is missing.read after narrowing.fd only to find candidate files or language roots.rg for imports, declarations, and exact symbol text inside the bounded
scope.python -m ast, ruff, pyrightgo list, go test, go doc, gofmt -w only when editingtsc --noEmit, bun testfd '\.(go|py|ts|tsx|js|jsx)$' src
rg -n 'class |def |func |export |interface |type ' src/module
rg -n 'UserService|createUser' src/module
## Smart Explore
### Scope
<known file/module/symbol>
### Files
- `path` — why it matters
### Symbols
- `path:line` — symbol and role
### Edges
- caller -> callee or import relationship
### Read Next
1. `path:line-range` — reason
tools
Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview. NOT for generic implementation planning that does not read or write `.spec/` files.
development
Simple web development with HTML, CSS, JS, and HTMX. Use when working with .html, .css, or .htmx files, web templates, stylesheets, or vanilla JS scripts. NOT for React/Vue/Angular (use writing-typescript) or Node.js backends.
tools
Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or TypeScript design advice. Emphasizes strict typing, boundary validation, composition, fast feedback, behavior tests, and project-configured tooling. NOT for Go, Python, Rust, plain HTML/CSS/JS, or server-rendered templates (use writing-web).
tools
Idiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CI shell steps, and scriptable CLI glue. Use when writing or changing `.sh`, `.bash`, `.zsh`, `.fish`, `.bats`, shell functions, shell pipelines, CI `run:` shell bodies, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Python, Rust, TypeScript, Go, web code, or GitHub Actions workflow/job/permissions semantics; use operating-infra.