What problem does it solve? Engineers repeatedly re-derive what a module or service does when onboarding, handing off, or refactoring code with unclear boundaries. This Skill produces a durable architectural CONTEXT.md for a component so that knowledge is captured once instead of rediscovered. ## Core Features & Use Cases - Grounded code exploration: Reads entry points, public interfaces, inbound and outbound dependencies, owned data, and tests before writing anything. - Structured CONTEXT.md output: Generates a fixed-format doc covering responsibility, public interface, key files, dependencies, data owned, invariants, tests, and related domain terms. - Path taxonomy integration: Places the doc under docs/resources/<area>/components/<component-slug>/ following the knowledge-base skill's ownership rules, with an optional CONTEXT_DOCS_DIR external storage override. - Use Case: Before refactoring a billing service whose boundaries are fuzzy, run this Skill on services/billing/ to produce a component doc that maps its public API, callers, and hidden invariants. ## Quick Start Ask the agent to describe the component at src/auth/ and generate its CONTEXT.md.