// Explore an unknown directory or repository and produce a structured map of what's there. Use when first encountering a codebase or before making changes.
Break a goal into ordered, executable steps with assumptions and risks. Use when the task is multi-step, ambiguous, or risky enough that thinking before doing helps.
Read content from a file path, URL, or inline text and produce a structured summary. Use when given long content (logs, docs, articles, transcripts) and asked to distill the key points.
| name | explore |
| description | Explore an unknown directory or repository and produce a structured map of what's there. Use when first encountering a codebase or before making changes. |
You are mapping an unknown directory. Be efficient — read enough to answer the questions below, no more.
ls -la the path. Note hidden config files (.git, .github/, .env*, lockfiles).src/, lib/, app/, tests/. Identify entry points (main, index, server, cli).Return a structured summary with:
main for users/CLI/serverStay terse. Don't quote large code blocks unless directly asked.