dev-explore
Explore and understand codebases with interconnected documentation. Use when onboarding to a new project, exporting docs for external LLM tools, or generating portfolio artifacts.
When & Why to Use This Skill
This Claude skill facilitates systematic codebase exploration and automated documentation generation. It is designed to help developers quickly master unfamiliar repositories, optimize project documentation for external LLM tools, and transform technical work into professional portfolio artifacts through specialized analysis and export modes.
Use Cases
- Rapid Onboarding: Automatically analyze a new codebase to generate tech stack breakdowns, directory structures, and architecture diagrams, significantly reducing the time needed to understand a project.
- LLM Context Preparation: Consolidate fragmented project documentation into structured, numbered Markdown files optimized for ingestion by external tools like NotebookLM or custom GPTs.
- Portfolio & Resume Building: Extract key technical achievements from a repository to generate elevator pitches, problem-solution narratives, and interview talking points for career advancement.
- Architecture Visualization: Generate Mermaid diagrams and file-by-file analysis to audit system design and maintain up-to-date technical documentation.
| name | dev-explore |
|---|---|
| description | Explore and understand codebases with interconnected documentation. Use when onboarding to a new project, exporting docs for external LLM tools, or generating portfolio artifacts. |
dev-explore
Systematic codebase exploration and documentation generation.
Scope
This skill covers codebase understanding—exploring unfamiliar code, generating analysis, and creating consolidated documentation. Part of the dev-* family alongside dev-inquiry, dev-reports, and dev-context.
Routing
Based on what you need, I'll reference the appropriate mode:
Analyze Mode
When: Understanding a new codebase, onboarding
Template: templates/analyze-base.md + tech-specific templates
Output: codebase_analysis.md
Generates:
- Tech stack breakdown
- Directory structure analysis
- File-by-file breakdown
- Architecture patterns
- Mermaid diagrams
Export Mode
When: Consolidating docs for external LLM tools (NotebookLM, etc.)
Template: templates/export.md
Output: docs/exports/ directory
Consolidates documentation into numbered files for easy upload:
docs/exports/
├── 01-project-overview.md # CLAUDE.md
├── 02-architecture-decisions.md # All ADRs
├── 03-design-docs.md # Design documentation
├── 04-mlx-system.md # MLX-specific docs
├── 05-devlog-current.md # Active devlogs
├── 06-devlog-archive.md # Archived devlogs
├── 07-specs.md # Issue specs
└── 08-uml.md # UML diagrams
Process:
- Clear
docs/exports/directory - For each category, concatenate source files with source headers
- Write consolidated output files
Portfolio Mode
When: Resume/interview preparation, showcasing work
Template: templates/portfolio.md
Output: PROJECT.md
Generates:
- Elevator pitch
- Problem/solution narrative
- Technical implementation
- Resume bullet points
- Interview talking points
How to Use
- Identify the mode from the request
- Load the appropriate template from
templates/ - Detect technology stack and load tech templates from
templates/tech/ - Reference examples in
examples/for output quality
Default to analyze mode if unclear.
Technology Detection
Auto-detect and load specialized templates:
| Indicator | Technology | Template |
|---|---|---|
Package.swift, *.xcodeproj |
iOS/Swift | templates/tech/ios-swift.md |
build.gradle.kts with android |
Android/Kotlin | templates/tech/android-kotlin.md |
wrangler.toml |
Cloudflare Worker | templates/tech/cloudflare-worker.md |
@modelcontextprotocol/sdk |
MCP Server | templates/tech/mcp-server.md |
tsconfig.json |
TypeScript | templates/tech/typescript.md |
jest.config.js |
Jest | templates/tech/jest-testing.md |
Best Practices
- Run Analyze first when joining a project
- Use Export before uploading docs to external LLM tools
- Use Portfolio after milestones while context is fresh
- Regenerate Export after major documentation changes
Related Skills
- dev-inquiry - Investigation and technical decisions
- dev-reports - Journals and status reports
- dev-context - ADR/Design/Spec/Plan scaffolding