What problem does it solve? Go projects often drift into tangled package structures with import cycles, misplaced responsibilities, and ambiguous ownership. This Skill translates already-decided logical responsibilities (domain, repository, usecase, query, handler) into a deterministic Go 1.27 directory and package layout, then fixes import direction violations. ## Core Features & Use Cases - Logical-to-physical mapping: Converts confirmed aggregate boundaries and Command/Query classifications into a per-aggregate package tree (domain, repository, usecase/command, usecase/query, query, handler). - Import direction enforcement: Applies a strict import permission table so domain never imports outer layers, query implementations depend on usecase/query contracts, and handlers never touch DB implementations directly. - Verification and repair: Rewrites import paths, generation configs, and composition roots, then validates with gofmt, go list, go build, go vet, and import cycle checks. - Use Case: Given a reservation aggregate with a read port and sqlc-based implementation, place the contract in reservation/usecase/query and the implementation in reservation/query, with imports flowing from implementation to contract. ## Quick Start Ask the AI to apply the Go package layout convention to your module by providing the module root path and the confirmed logical responsibilities for each code element.
