explore

# Codebase Exploration $ARGUMENTS Explore and understand a codebase structure. ## Project context - Config files: !`find . -maxdepth 2 -type f -name "*.json" -o -name "*.toml" -o -name "*.yaml" -o -name "*.yml" 2>/dev/null | head -20` ## Usage ``` /explore [path] ``` ## What This Command Does 1. **Maps** project structure 2. **Identifies** technology stack 3. **Finds** key files and patterns 4. **Reports** architecture overview ## Output Format ```markdown ## Codebase Analysis Report ### Project Type - **Language**: [TypeScript/Python/PHP/etc.] - **Framework**: [Next.js/FastAPI/Laravel/etc.] - **Package Manager**: [npm/pnpm/pip/composer] ### Directory Structure ``` project/ ├── src/ # Source code ├── tests/ # Test files ├── config/ # Configuration └── ... ``` ### Key Files | File | Purpose | |------|---------| | `src/index.ts` | Entry point | | `src/api/` | API routes | ### Dependencies - **Runtime**: [list] - **Dev**: [list] ### Patterns Detected - [Pattern 1] - [Pattern 2] ### Entry Points - [Entry 1] - [Entry 2] ``` ## Technology Detection | Marker | Technology | |--------|------------| | `package.json` | Node.js | | `tsconfig.json` | TypeScript | | `next.config.*` | Next.js | | `nuxt.config.*` | Nuxt | | `pyproject.toml` | Python | | `composer.json` | PHP | | `pubspec.yaml` | Flutter/Dart | | `Cargo.toml` | Rust | | `go.mod` | Go | ## When to Use - Starting work on unfamiliar codebase - Before planning major changes - Understan...