From fuse-ai-pilot
Rapidly explores and maps unfamiliar codebases using a 5-phase protocol: reconnaissance, structure mapping, entry points, dependencies, and architecture pattern detection.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fuse-ai-pilot:exploration [directory] [--thorough][directory] [--thorough]fuse-ai-pilot:explore-codebaseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Session:** ${CLAUDE_SESSION_ID}
Session: ${CLAUDE_SESSION_ID}
Run these 5 phases in order — full commands in references/exploration-protocol.md:
main/index/server bootstrap per languagepackage.json/pyproject.toml/go.mod/Cargo.toml/composer.json| Pattern | Key Directories | Indicators |
|---|---|---|
| MVC | controllers/, models/, views/ | Rails, Laravel, Express |
| Clean Architecture | domain/, application/, infrastructure/ | DDD, Use cases |
| Hexagonal | adapters/, ports/, core/ | Ports & adapters |
| Feature-based | features/[name]/ | All layers per feature |
| Layered | presentation/, business/, data/ | Traditional 3-tier |
| Monolith | Single src/ | Mixed concerns |
| Microservices | Multiple services/ | Separate repos/folders |
| Next.js App Router | app/, components/, lib/ | Server/Client components |
| Modular Monolith | modules/[name]/ | Bounded contexts |
references/exploration-protocol.md — Load when running the 5-phase protocol (exact shell commands per phase)references/tech-stack-detection.md — Load when identifying framework/ORM/tooling per language (JS/TS, Python, Go, PHP, Rust)references/code-organization-checks.md — Load when auditing interface separation, business-logic location, or state managementreferences/response-format.md — Load when writing the final exploration reportreferences/quick-analysis-commands.md — Load for one-liner full-stack assessment, file counts, or large-file detectionnpx claudepluginhub fusengine/agents --plugin fuse-ai-pilotAnalyzes codebases to reveal structure, tech stack, patterns, and conventions. Useful for onboarding to new projects or exploring unfamiliar code.
Explores project structure, configurations, code patterns, conventions, tests, and dependencies before modifying existing code to understand context and avoid bugs.
Maps unfamiliar codebases in phases: structure, entry points, data flow, patterns, landmines. Use before coding in new, inherited, or revisited projects.