go-clean-architecture

What problem does it solve?

Go projects often struggle with maintaining a clear separation of concerns as codebases grow. This Skill provides expert guidance on implementing a true Clean Architecture in Go, clarifying how to organize domain, application, and infrastructure layers to keep business rules independent from frameworks and external details.

Core Features & Use Cases

• Clear Layered Boundaries: Domain models and business logic live in internal/domain, with outer layers depending inward.
• Dependency Rule Enforcement: Outer layers depend on inner domain interfaces only, preventing leakage of framework concerns.
• Practical Patterns: Concrete Go code samples and guidance for entities, repositories, and services across the three layers.
• Use Case: A Go microservice evolves its domain layer without touching HTTP or persistence code, simplifying testing and maintenance.

Quick Start

Create a new Go module, then structure your code as internal/domain (domain models and interfaces), internal/application (services and use cases), and internal/infrastructure (concrete persistence and adapters). Wire everything in a minimal main.go to bootstrap the application.