ddd-go-idiomatic
Tactical Domain-Driven Design written as idiomatic Go, not translated Java: value objects, entities, aggregates, bounded contexts, repositories/ports, use cases and the file layout of a context. Use when designing, generating or reviewing Go domain code or deciding where logic, a use case or a file goes. Triggers: "value object", "entity", "aggregate", "bounded context", "use case", "repository pattern", "DDD in Go", "hexagonal/clean architecture in Go", "where should this logic live", service.go, usecase.go, handler.go, "file naming", "how do I name this file", "one use case per file".
- License
- MIT
Pinned to revision a2c346f89684, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/ddd-go-idiomatic/SKILL.md
- skills/ddd-go-idiomatic/references/aggregates.md
- skills/ddd-go-idiomatic/references/antipatterns.md
- skills/ddd-go-idiomatic/references/application-layer.md
- skills/ddd-go-idiomatic/references/bounded-contexts.md
- skills/ddd-go-idiomatic/references/entities.md
- skills/ddd-go-idiomatic/references/value-objects.md
- skills/ddd-go-idiomatic/references/worked-example.md
Every link opens the file at its source, pinned to the revision this page describes.