learn-codebase
The learn-codebase skill systematically reads every source file in a project to build comprehensive understanding of its structure and functionality. Use this skill when beginning work on a new or unfamiliar codebase, or when explicitly asked to learn, read, or prime a project. For large files, the skill pages through content in chunks to manage token usage efficiently while establishing a detailed knowledge base for subsequent development work.
git clone --depth 1 https://github.com/thedotmack/claude-mem /tmp/learn-codebase && cp -r /tmp/learn-codebase/plugin/skills/learn-codebase ~/.claude/skills/learn-codebaseSKILL.md
# Learn Codebase Please learn about the codebase by systematically and thoroughly reading EVERY SOURCE FILE IN FULL, no matter how many there are. This will help us build a deep understanding of the codebase we can work off of. This is critical and non negotiable. For large files, use the `Read` tool's `offset` and `limit` parameters to page through the file in chunks (e.g. `offset: 1, limit: 500`, then `offset: 501, limit: 500`). ## Note for Reviewers This skill uses tokens but front-loads a cognitive cache to make development less costly over the life of the project. Please keep this in mind before deciding to warn the user over cost.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design audit", or asks for a critique that should lead to a plan.
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
Build and query AI-powered knowledge bases from claude-mem observations. Use when users want to create focused "brains" from their observation history, ask questions about past work patterns, or compile expertise on specific topics.
Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.
Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.