golang

This skill provides a comprehensive framework for Go (Golang) development, grounded in industry-standard best practices validated by companies like Uber and Google. It focuses on writing production-ready code that emphasizes simplicity, safety, and performance. Designed for backend engineers and system developers, this skill helps users navigate the complexities of Go's unique features—such as goroutines, channels, and interface composition—while ensuring code remains readable, maintainable, and idiomatic. Whether you are building high-concurrency microservices, robust CLI tools, or distributed systems, this skill guides you through the entire development lifecycle, from project structure to testing and error management.

• Advanced Concurrency: Master the use of goroutines and channels with a focus on explicit termination, safe state synchronization, and avoiding common deadlocks.

• Idiomatic Error Handling: Implement Go’s signature error-value patterns, distinguishing between sentinel errors and internal failures to improve code reliability.

• Strategic Interface Design: Leverage small, consumer-side interfaces to decouple packages and enhance testability through dependency injection and mocking.

• Architecture Principles: Apply composition over inheritance, package naming standards, and clean abstraction layers that keep business logic decoupled from implementation details.

• Testing & Quality: Integrate test patterns using the standard testing package and testify framework, ensuring code coverage, benchmarking, and robust validation.

• Performance Optimization: Follow tooling-first workflows, including formatting, vetting, and performance profiling for optimal execution.

• Use this skill when initiating new Go projects to ensure correct folder structures and package naming conventions.

• Ideal for refactoring existing code to improve adherence to the 'Happy Path at Left Margin' principle, reducing cyclomatic complexity.

• Use during code reviews to validate the application of idiomatic patterns versus anti-patterns like Java-style getters or deep nesting.

• Input typically involves Go source files or design requirements; output includes idiomatic code refactors, structural advice, or unit test generation.

• Constraints: Focuses on backend development and system software paradigms; assumes basic familiarity with Go syntax and build tools.