What problem does it solve?
When a task spans multiple packages, public contracts, persistence layers, or runtime wiring in an unfamiliar codebase, editing code without understanding the architecture leads to broken invariants and misplaced changes. This Skill builds an evidence-backed map of the repository before any mutation begins.
Core Features & Use Cases
- Architecture Mapping: Traces user-visible entry points through contracts, runtime ownership, persistence, and downstream consumers.
- Ownership & Invariant Identification: Pinpoints the owning layer, canonical test suite, and the narrowest relevant verification lane for a change.
- Reuse Discovery: Searches for existing primitives and adjacent implementations before proposing new abstractions.
- Use Case: You are asked to add a feature that touches an API contract and its database layer in a repo you have never seen. Use this Skill to produce a concise orientation covering affected surfaces, call and data flow, invariants, the working file set, and open questions before writing any code.
Quick Start
Use the repository-orientation skill to map this repository and identify the owning layer and verification path for my planned change.