go-modularization

What problem does it solve?

Go monorepos and single-service repositories often suffer from inconsistent folder layouts, layering violations, and ambiguous file placement that slow down development and review. This Skill eliminates that ambiguity by providing opinionated, deterministic rules for where every type of Go source file, adapter, migration, and shared package belongs.

Core Features & Use Cases

• Flat Hexagonal Architecture: Enforces dependency direction between inner layers (domain, interactor, ports, coordinator) and outer adapters (api, consumer, cli, data_repositories, external_services, producer, storage, grpc/ws/sse).
• Promotion Thresholds & Naming: Governs when to promote suffixed files to subfolders (bounded contexts, API versions, middleware, external providers) and forbids combined-context or reserved folder names.
• Validation & Migration: Includes an arch-checks gate script for CI, plus an incremental migration guide for adopting the convention in existing brownfield codebases.

Quick Start

Use the go-modularization skill to determine the correct destination folder and filename for a new Go source file in your service's internal directory.