go-dev-guidelines

Go projects should follow idiomatic patterns with standardized directory layouts, small focused interfaces, constructor-based dependency injection, and explicit error handling. This Skill provides the architectural guidelines to set up maintainable, testable Go services from the start, avoiding refactoring later.

TDD in Go uses testify/require for assertions and mockery for mock generation stored in mocks/. This Skill enforces a complete TDD workflow that ensures comprehensive test coverage before implementation, reducing bugs and improving code quality.

Idiomatic Go enforces go vet, gofmt formatting, and godoc documentation standards. This Skill applies these tools and patterns consistently across services and packages, eliminating coding inconsistencies and maintaining readability.

Apply these guidelines when creating new features, refactoring existing code, or writing tests across Go services. Starting with them from day one standardizes practices and prevents accumulation of technical debt in microservices.

These guidelines apply to both new Go microservices and existing codebases undergoing refactoring or new feature development. They enforce consistent patterns incrementally without requiring a complete rewrite.

This Skill requires mockery for mock generation and testify/require for test assertions. These tools are standard Go testing dependencies that enable automated mocking and clear, maintainable test code.