What problem does it solve? Onboarding onto an unfamiliar codebase is slow and error-prone because there is no structured map of what each directory does. This Skill automates repository mapping by selecting relevant source files, tracking file and folder hashes for change detection, and scaffolding per-folder codemap.md documents that agents or humans fill in with architectural knowledge. ## Core Features & Use Cases - Hierarchical Codemap Generation: Creates empty codemap.md templates in every relevant folder and a root-level Repository Atlas aggregating each directory's responsibility. - Change Detection: Stores file and folder MD5 hashes in .slim/codemap.json so subsequent runs report added, removed, and modified files plus affected folders, enabling incremental updates instead of full remapping. - Pattern-Based File Selection: Uses include/exclude glob patterns with .gitignore support and mandatory exclusion of tests, docs, and build artifacts to focus on core code. - Use Case: When starting work on a new repository, run the init command to generate the state file and codemap templates, delegate folder documentation to fixer agents, then register the map in AGENTS.md so every future session automatically discovers the architecture. ## Quick Start Ask the agent to generate a codemap for this repository so it initializes the state file and creates codemap.md templates in each folder.