codebase-mapping
The codebase-mapping skill automatically catalogs a project's structure, file types, entry points, dependencies, and test patterns to build a comprehensive index. This index is invisibly injected into Claude's context during user interactions, enabling the model to generate code and suggestions that align with the project's conventions and architecture without requiring explicit user description of the codebase. Use it at the start of ClaudeKit sessions or when project structure changes significantly.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/codebase-mapping && cp -r /tmp/codebase-mapping/library/methodologies/claudekit/skills/codebase-mapping ~/.claude/skills/codebase-mappingSKILL.md
# Codebase Mapping ## Overview Auto-indexes the project structure to build a comprehensive codebase map. This map is used for invisible context injection via the UserPromptSubmit hook, providing Claude with project awareness without explicit user prompting. ## Map Contents ### Project Structure - Directory tree with depth-limited enumeration - Key file identification (entry points, configs, lock files) ### File Type Distribution - Language breakdown (TypeScript, JavaScript, Python, etc.) - Framework detection (React, Next.js, Express, etc.) ### Entry Points - Main entry files (index, main, app) - CLI entry points - API route definitions ### Module Dependencies - Import graph analysis - Package boundary mapping - Circular dependency detection ### Test Layout - Test directory structure - Test file patterns and conventions - Test framework identification ## Context Injection The codebase map is injected as invisible context during UserPromptSubmit, providing: - Project type and framework awareness - Convention awareness for code generation - Dependency awareness for import suggestions - Test pattern awareness for test generation ## When to Use - Automatically at ClaudeKit session start - When project structure changes significantly - Before research or specification tasks ## Processes Used By - `claudekit-orchestrator` (session initialization) - `claudekit-research` (context for research agents) - `claudekit-spec-workflow` (context for spec creation)
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement