cartographer

You can maintain persistent codebase memory by recording module details, conventions, and landmines into structured markdown files, allowing agents to consult or load this context in future sessions without redundant discovery.

The best way to provide module-specific context is to inject detailed module knowledge from a persistent map into subagents, ensuring they have the correct structural awareness and preventing incorrect assumptions during task execution.

To map a codebase and prevent redundant discovery, use a record mode to capture new findings and a consult mode to surface high-level structure, storing everything in structured markdown for continuous contextual awareness.

Yes, you can use codebase mapping to document project conventions and landmines by accumulating information across sessions into structured markdown files, preventing agents from repeating past mistakes or violating established standards.

Yes, persistent codebase memory works without external dependencies by utilizing structured markdown files to store the map, conventions, landmines, and per-module details directly within the project environment.

You need a living map of a codebase for developer productivity when starting new feature implementations, allowing you to consult existing module dependencies and responsibilities to ensure new code integrates smoothly without wasting time.