mkimprove-codebase-architecturelisted

# mk:improve-codebase-architecture Surface architectural friction and propose **deepening opportunities** — refactors that turn shallow modules into deep ones. The aim is testability and AI-navigability. This skill owns three things only: **structural analysis**, **dependency mapping**, and **type-safe patch emission**. It owns no rendering. Every visual artifact (before/after diagrams, candidate report, HTML) is produced by `mk:preview`. The skill emits structured findings; `mk:preview` draws them. ## Architecture vocabulary (use exactly) Self-contained glossary — every suggestion uses these nouns/verbs and no synonyms. - **module** — a unit with an interface and an implementation. Never "component", "service", "unit", "layer", "wrapper". - **interface** — the surface a caller depends on. Never "API", "signature". - **depth** — implementation complexity hidden behind a small interface. **deep** = small interface, large implementation. **shallow** = interface nearly as wide as implementation. - **seam** — the line where two modules meet. Never "boundary". - **adapter** — a substitutable implementation behind a seam. Rule: *one adapter = hypothetical seam, two = real seam.* - **leverage** — one interface serving N call sites. - **locality** — related logic (and its bugs) concentrated in one module, not scattered. - **deletion test** — would deleting this module *concentrate* complexity (good — it was shallow) or merely *move* it (it was load-bearing)? "Concentrates" is th