Skill

codebase-map

Analyze and map the current codebase structure, key files, and architecture. Use when running 'map codebase', 'analyze project', or when starting work on an unfamiliar project.

From wheee

Install

Run in your terminal

npx claudepluginhub skatekowski/wheee-plugin --plugin wheee

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Skill Content

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

cost-aware-llm-pipeline

Provides Python patterns for LLM API cost optimization: model routing by complexity, immutable budget tracking, narrow retries, prompt caching. For apps calling Claude/GPT with budgets.

ecc

144.6k

Stats

Stars1

Forks0

Last CommitFeb 25, 2026

Actions

View Source View Plugin View on GitHub View README

Process

Read project root files: package.json, Cargo.toml, pyproject.toml, go.mod, etc.

Map directory structure (2 levels deep)

Identify framework and language

Find entry points (main, index, app, server)

Map key architectural layers:

Routes / API endpoints
Data models / schemas
Business logic / services
Configuration / environment
Tests

Count files by type and estimate project size

Check for existing documentation (README, ARCHITECTURE, CLAUDE.md)

Output Format

## Codebase Map ### Project - Name: [name] - Language: [lang] / Framework: [framework] - Size: ~X files, ~Y lines ### Structure [directory tree, 2 levels] ### Entry Points - [file] — [purpose] ### Architecture Layers - **Routes**: [directory/pattern] - **Models**: [directory/pattern] - **Services**: [directory/pattern] - **Config**: [directory/pattern] - **Tests**: [directory/pattern] ### Key Files - [file] — [why it matters] ### Dependencies - X production deps, Y dev deps - Notable: [key libraries]

Codebase Map

Analyze the project structure and produce a comprehensive codebase overview.

Process

Read project root files: package.json, Cargo.toml, pyproject.toml, go.mod, etc.
Map directory structure (2 levels deep)
Identify framework and language
Find entry points (main, index, app, server)
Map key architectural layers:
- Routes / API endpoints
- Data models / schemas
- Business logic / services
- Configuration / environment
- Tests
Count files by type and estimate project size
Check for existing documentation (README, ARCHITECTURE, CLAUDE.md)

Output Format

## Codebase Map

### Project
- Name: [name]
- Language: [lang] / Framework: [framework]
- Size: ~X files, ~Y lines

### Structure
[directory tree, 2 levels]

### Entry Points
- [file] — [purpose]

### Architecture Layers
- **Routes**: [directory/pattern]
- **Models**: [directory/pattern]
- **Services**: [directory/pattern]
- **Config**: [directory/pattern]
- **Tests**: [directory/pattern]

### Key Files
- [file] — [why it matters]

### Dependencies
- X production deps, Y dev deps
- Notable: [key libraries]