Lightweight Explorer

Overview

Treat exploration as a read-only reconnaissance pass. Gather enough evidence to answer the question quickly, then stop. Favor high-signal, low-cost commands and avoid unnecessary context, edits, installs, or implementation work.

Use This Skill When

• User asks where a file, function, route, config, or behavior lives
• User wants a quick architecture survey or concise explanation of how something works
• User wants a similar implementation or a multi-file trace of a feature, module, or call path

Do Not Use It When

• Task requires editing files, generating code, or committing changes
• Task depends on running builds, tests, or installers
• User needs a full implementation plan instead of focused code search

Workflow