go

Start with the fewest cohesive packages that fit the program, keeping startup and wiring near cmd/ and organizing internal packages around domains. Add transport or storage adapters like internal/httpapi or internal/postgres only when they create a useful boundary.

Use the standard net/http package by default, adding Chi when its routing features help. Keep handlers and middleware compatible with standard http.Handler contracts, and configure explicit server timeouts and graceful shutdown.

Never ignore errors, add context when returning them, and wrap with %w only when callers should inspect the underlying error using errors.Is or errors.As. Log an operational failure once at the boundary that handles it rather than at every layer.

Yes, since Go 1.21 the go directive is a mandatory minimum toolchain requirement and also selects the language version for module packages. Confirm GOTOOLCHAIN, CI images, and release builders all use the intended version when upgrading.

Give every goroutine a clear owner and termination condition, use errgroup.WithContext for related tasks, and avoid unbounded fan-out. Run go test -race ./... for non-trivial concurrent code to detect data races.

Use the latest patch release of a supported Go line since patches carry security and correctness fixes. Read release notes for skipped minor releases, review GODEBUG default changes, and rerun tests, benchmarks, and race checks after upgrading.