Use this skill whenever defining, modifying, or reviewing structure and boundaries to ensure related code, tests, docs, templates, and scripts are co-located at the narrowest meaningful scope (slice, shared library, monorepo, or API version), with shared extraction only when reuse is proven.
Ensure deliverable functionality is organised as atomic vertical slices, with related interfaces, classes, services, tests, documentation, templates, and scripts co-located at the narrowest meaningful scope.
This skill exists to preserve clarity, traceability, and ownership; enable independent build/test/deploy; prevent duplication and architectural drift; and apply DRY/YAGNI via disciplined reuse boundaries across repository structure.
README.md.P1 – Quality & Correctness
(Escalate to P0 if release traceability/immutability or deployment guarantees are compromised.)
Core
Governance
This skill is intentionally strict. Violations often indicate systemic drift rather than a local choice.