arthai-marketplace

/explore

Fast codebase exploration using Haiku. Use for finding files, searching code, understanding structure.

Synopsis

/explore <query>

When to use it

“Where is X?” questions — finding files, functions, classes, or patterns
Understanding directory structure or how a subsystem is organized, cheaply
Scouting before expensive work — many toolkit skills run the same explore-light agent internally for exactly this reason
Not for: deep architectural reasoning or debugging novel problems — exploration findings feed those tasks, they don’t replace them; and not for making changes — /explore only reads

Quickstart

/explore how does authentication work

What you’ll see: the explore-light agent (running on Haiku, ~60x cheaper than Opus) scans the codebase and returns a concise summary with the relevant file paths — without burning your main session’s context on the search itself.

Examples

/explore find all API route handlers          # pattern search across the codebase
/explore how does authentication work         # understand a subsystem
/explore where is the database schema defined # locate a specific definition

What it does

Parses your query from the skill arguments.
Spawns the explore-light agent (Haiku) with your query as its prompt — the agent does the file finding, grepping, and structure summarizing in its own context.
Returns the findings — file paths and a brief explanation — back into your session.

Agents spawned

Agent	Model tier	Role
explore-light	haiku	Performs the exploration and returns findings

Output & artifacts

Findings in the conversation: file paths, brief descriptions, and structural summaries
No files written, no code modified — read-only by design

Troubleshooting

Problem	Fix
Findings are too shallow for the question	/explore is optimized for speed and cost — for deep analysis, use the findings as input to a follow-up task in your main session
Query returned the wrong area of the codebase	Be more specific: name the feature, directory, or symbol (“auth middleware in the API layer” beats “auth”)
You needed an edit, not a search	/explore never modifies code — ask for the change directly after locating the file

/onboard — session briefing that includes project orientation
/scan — persists project structure into CLAUDE.md, rather than answering one-off queries
/calibrate — deep project learning; /explore is the lightweight everyday counterpart