Map Codebase
Derives the tech-stack doc from scratch by scanning the codebase — analyzes stack, architecture, and gray areas (error handling, API shapes) and persists findings into specs/tech-architecture/tech-stack.md. Run when the tech doc doesn't exist yet; use survey-context to consume it once it does.
Install
npx skills add danielvm-git/bigpowers --skill map-codebasegit clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/map-codebase ~/.claude/skills/map-codebasePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Map Codebase Perform a deep architectural and structural analysis of the codebase. Unlike `survey-context` which identifies "where we are", `map-codebase` identifies "what we are dealing with" and "how things are done". > **Use this vs survey-context:** `map-codebase` BUILDS the tech-stack doc by scanning the codebase from scratch. `survey-context` READS existing specs/tech-architecture docs without re-deriving them. Run `map-codebase` when `specs/tech-architecture/tech-stack.md` doesn't exist yet; run `survey-context` when it does. > **HARD GATE** — Cold analysis only. Do NOT assume architectural patterns without reading the code. If the codebase structure surprises you, call out the delta. ## Process ### 1. Identify Core Stack & Dependencies - Scan `package.json`, `Cargo.toml`, `requirements.txt`, etc. - Identify primary framework, runtime, and critical libraries (ORM, Auth, State, UI). - Note version constraints and any deprecated or unusual dependencies. ### 2. Map High-Level Architecture - Identify the entry points (CLI, Web, API). - Map the primary data flow (e.g., Controller → Service → Repository). - Identify where business logic lives vs. where I/O lives. - Look for established patterns (e.g., hexagonal, layered, feature-folders). ### 3. Analyze "Gray Areas" (The "How") Search for patterns and anti-patterns in these categories: - **Error Handling:** Are exceptions caught early or bubbled? Is there a global error handler? Are error messages structured?
Details
- Skill name
map-codebase- Repository
- danielvm-git/bigpowers
- Path
.cline/skills/map-codebase/SKILL.md- License
- MIT
- Repo updated
- 9 November 2026
FAQ
What does the Map Codebase skill do?
Derives the tech-stack doc from scratch by scanning the codebase — analyzes stack, architecture, and gray areas (error handling, API shapes) and persists findings into specs/tech-architecture/tech-stack.md. Run when the tech doc doesn't exist yet; use survey-context to consume it once it does.
How do I install the Map Codebase skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill map-codebase. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Map Codebase popular?
It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.
Related skills
Align Grid
292danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i
Assess Impact
292danielvm-git/bigpowers
Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".
Audit Code
292danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
Persona Architecture
207Owl-Listener/ai-design-skills
Defining AI character, voice, and personality traits.
Develop TDD
292danielvm-git/bigpowers
Test-driven development with red-green-refactor loop using vertical slices. Use for features (epic tasks) or bugs (specs/bugs/BUG-*.md).
Plan Refactor
292danielvm-git/bigpowers
Create a detailed refactor plan with tiny commits via user interview, then save it as specs/REFACTOR_LATEST.md. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.