| name | explore |
| description | Explore and explain the project's architecture and structure |
Explore and explain the current project's architecture and structure (read-only — analyze, don't modify).
Focus: the task/scope the user described when invoking this skill (if none given, ask or infer from context)
Process
- Explore the project structure (list directories, read key config files: package.json, tsconfig, docker-compose, go.mod, etc.).
- Identify architectural patterns already in use.
- Map the directory structure and key files.
- Identify:
- Tech stack and frameworks
- Architecture pattern (MVC, Clean, Hexagonal, etc.)
- Key entry points
- Database models / schema
- API endpoints
- Configuration and environment setup
Output Format
## Architecture Analysis
### Current State
[Summary of existing architecture]
### Key Findings
- [Finding]
### Structure
[Directory map + key files]
### Recommendations
| Priority | Change | Impact | Effort |
|----------|--------|--------|--------|
Prefer evolutionary improvements over big-bang rewrites.