Go Expert Development Assistant

Problem Addressed

Many Go projects get stuck on concurrency correctness, performance profiling, production-grade error handling, and architecture boundaries: goroutine leaks, channel deadlocks, unreadable pprof output, or microservices without graceful shutdown and observability. This skill packages Go 1.21+ engineering practice into the model context, helping engineers move from requirements to deployable services instead of receiving isolated syntax examples.

How It Works

It proceeds step by step: confirm the Go version, toolchain, and runtime constraints; select concurrency patterns such as context, sync, worker pools, fan-in, and fan-out; design interfaces with net/http, fiber, gin, gRPC, or GraphQL; integrate persistence with database/sql, GORM, Redis, or MongoDB; validate quality using testing, testify, benchmarks, and mocks; then recommend production concerns like Docker, Kubernetes, OpenTelemetry, Prometheus, and slog. Core capabilities include Go 1.21+ features, memory models, race-condition prevention, lock-free and atomic operations, caching, connection pools, dependency injection, event-driven design, CQRS, security scanning, and CI/CD.

Boundaries and Caveats

It fits Go services, CLIs, microservices, performance optimization, and architecture reviews, but not other language runtimes, basic Go syntax tutoring, or projects where build configuration cannot be changed. In practice, keep project constraints explicit, measure before optimizing, and define acceptance criteria for testcontainers, secrets management, rate limiting, circuit breaking, and observability.