What problem does it solve? When starting work in an unfamiliar part of a codebase, narrow file-by-file reading loses the bigger picture. This Skill steps up a layer of abstraction and produces a one-screen architectural map of the relevant modules, callers, and boundaries, grounded in the project's domain glossary. ## Core Features & Use Cases - Structured area map: Produces purpose, inputs, outputs, internal shape (3-7 key modules), edges and seams, and open questions for a named code area. - Glossary-aligned language: Reads docs/resources/CONTEXT.md first and bolds canonical domain terms, noting aliases where code names differ from glossary names. - Bounded scope: Stops at the map — it does not propose changes or critique design, deferring follow-up to architecture or diagnosis skills. - Use Case: You are assigned a bug in a billing module you have never touched. Run this Skill to get a one-screen map of the module's callers, outputs, and database boundary before reading any implementation code. ## Quick Start Ask the agent to zoom out on the billing module and map its callers, outputs, and boundaries using the project glossary.
