Scaffold a Go Microservice

The opinionated "this is the layout you'd land on after building 3 Go services" scaffold. No frameworks beyond chi. No code generators that create magic. Idiomatic Go that an experienced reader recognizes immediately.

When to use

• New Go service, day 1.
• Internal service or public API; HTTP/JSON.
• You want sqlc (typed SQL) over GORM (ORM with reflection cost).
• You'll deploy to Kubernetes or Cloud Run / Fly / Railway.

When NOT to use

• gRPC-first service → use grpc-services skill (different scaffold).
• Tiny CLI tool → use scaffold-cli-tool.
• Adding structure to an existing service — different problem.
• You want a heavy framework (Gin, Fiber, Echo) — this scaffold is net/http + chi.

Decisions made for you