go-microservice-scaffold

When to Use

• Creating a new microservice from scratch
• Adding a new domain/module to an existing service
• Reviewing or refactoring service structure
• Onboarding someone to the Go service layout

Architecture principles (dependency rule, ports & adapters, layer responsibilities) live in the clean-architecture skill. Load it first if you need the WHY. This skill covers the HOW for Go.

Service Structure

Each microservice lives under api/ and follows this layout:

Single-Domain Service (Most Common)

When a service has one primary domain (e.g., notification, booking):