exploration

<objective> Exploration runs a 5-phase reconnaissance protocol for rapid codebase discovery: initial reconnaissance (root files, config, entry points), structure mapping, entry-point detection per language, dependency analysis (package.json/pyproject.toml/go.mod/Cargo.toml/composer.json), and architecture-pattern detection (MVC, Clean, Hexagonal, feature-based, layered, modular monolith, Next.js App Router, and more). It is evidence-based only -- no assumptions without code proof -- and produces a structured report of tech stack, entry points, and detected architecture pattern for whoever consumes it (typically the APEX Analyze phase or a domain expert). </objective> **Session:** ${CLAUDE_SESSION_ID} # Exploration Skill ## Exploration Protocol Run these 5 phases in order — full commands in `references/exploration-protocol.md`: 1. **Initial Reconnaissance** — list root files, find config files, check common entry points 2. **Structure Mapping** — tree view (excluding noise dirs), identify main directories 3. **Entry Points Detection** — grep for `main`/`index`/server bootstrap per language 4. **Dependency Analysis** — read `package.json`/`pyproject.toml`/`go.mod`/`Cargo.toml`/`composer.json` 5. **Pattern Detection** — check for MVC, Clean/Hexagonal, feature-based, Next.js App Router directories --- ## Architecture Pattern Detection ### Pattern Indicators | Pattern | Key Directories | Indicators | |---------|-----------------|------------| | **MVC** | `controllers/`, ...