Map Is Not the Territory

This skill implements a foundational mental model that helps developers and architects recognize that code comments, architecture diagrams, and project roadmaps are merely simplifications of a system's true state. By enforcing a rigorous check between the 'map' (documentation and abstractions) and the 'territory' (the actual source code and production environment), it ensures that technical decisions are based on empirical facts rather than potentially outdated, biased, or overly simplified representations. It is particularly effective for legacy codebase navigation and architectural auditing.

Key Features

Use Cases