go

Idiomatic Go services

Targets Go 1.22+ (Go 1.26 is the current stable release): enhanced net/http routing (mux.HandleFunc("GET /users/{id}", h) + r.PathValue), log/slog structured logging, and fixed loop-variable semantics (no more tt := tt).

⚠️ SDD new-feature gate — read this first. If this skill fired on a new, non-trivial feature or behaviour change and there is no approved spec + plan under 02-DOCS/wiki/sdd/, STOP — do not write feature code yet. Hand off to ../specify/SKILL.md first: it runs brainstorm → spec → plan → tasks before any code, then routes back here once the plan is approved. Build here directly only for a genuinely one-line / low-risk change. Method: ../sdd/SKILL.md.

Boundary

Go error handling and HTTP contract design (status-code taxonomy, REST resource naming) live here — this skill is the canonical authority for both in Go. Delegate outward:

• Language-agnostic abuse/authz review, threat modeling, OWASP-class bugs -> secure-coding. This skill keeps the Go-specific controls: SQL params, server timeouts, govulncheck, TLS defaults.
• Containerfile / k8s / CI pipeline authoring -> deployment. This skill ships only a Docker note + ldflags.
• Recording per-project conventions in a workspace wiki -> harness (see "Project grounding" below).

Non-service Go (CLI tooling, codegen, ML): the patterns apply, but the HTTP/production half is irrelevant.

Idioms

Useful zero value. Design types so the zero value works before any constructor.

// Good: zero-value Counter is ready; the zero-value mutex is unlocked. var b bytes.Buffer too.
type Counter struct {
	mu sync.Mutex
	n  int
}

func (c *Counter) Inc() { c.mu.Lock(); c.n++; c.mu.Unlock() }

// Bad: nil map field panics on first write (assignment to entry in nil map); hidden init step.
type Registry struct{ items map[string]int }

func (r *Registry) Add(k string) { r.items[k]++ } // panic if items was never make()'d