Skill UI

This skill provides comprehensive guidance on idiomatic Go design patterns and best practices for writing production-ready code. It covers functional options, constructor design, graceful shutdown, resource management, dependency injection, and crucial architectural considerations, helping developers write robust and maintainable Go applications.

This comprehensive guide provides best practices for creating, reviewing, and auditing documentation for Go projects. It covers writing principles (e.g., Intent over paraphrase, Concision), structuring documentation (godoc comments, README, CHANGELOG), and workflow orchestration for both libraries and CLI applications. Ideal for technical writers and developers ensuring code is discoverable and maintainable.

A comprehensive guide for writing robust, idiomatic, and production-ready error handling in Go. This skill covers best practices for error creation, wrapping (using %w), inspection (errors.Is/As), combining errors (errors.Join), and structured logging with slog. It promotes reliable code by enforcing principles like the single handling rule and contextual logging, crucial for building scalable applications.

This comprehensive guide covers best practices for building robust, production-ready gRPC microservices in Go. It details proper protobuf organization, utilizing interceptors for cross-cutting concerns (logging, auth), implementing graceful shutdowns, handling gRPC status codes, and optimizing client connections with deadlines and retry policies. Essential for engineers designing reliable distributed systems.

A comprehensive guide and toolset for Go code quality assurance using `golangci-lint`. It enables developers to run multiple linters in parallel, configure best practices via `.golangci.yml`, automate fixes, and interpret complex lint output. Ideal for maintaining code standards, setting up CI/CD pipelines, and cleaning up legacy codebases.

This skill automatically modernizes Go codebases by identifying and replacing outdated patterns, deprecated APIs, and non-idiomatic code. It conducts comprehensive scans across language features, standard library upgrades, testing patterns, and tooling (including running lint checks). It ensures the codebase adheres to the latest Go best practices, improving safety, correctness, and readability for modern Go versions.

A comprehensive guide detailing recommended naming conventions for various Go language elements, including packages, structs, interfaces, constants, functions, and error handling. Use this skill when writing, reviewing, or refactoring Go code to ensure adherence to idiomatic Go style.

This skill provides comprehensive observability tooling for Go services, covering the five essential signals: structured logging (slog), Prometheus metrics, OpenTelemetry tracing, continuous profiling, and RUM. Use it for proactive production monitoring, correlating logs with traces, setting up SLOs, and ensuring all new features are fully instrumented for robust diagnosis.

A comprehensive guide for optimizing Golang applications, covering systematic approaches to identifying and resolving bottlenecks. It details best practices for reducing memory allocations, improving CPU efficiency, tuning GC, and managing concurrency. The methodology emphasizes profiling first (using pprof, fgprof) and following an iterative cycle: Benchmark → Diagnose → Improve → Benchmark.

This skill acts as a Go ecosystem expert, guiding developers through the process of selecting and vetting production-ready third-party libraries and frameworks for Go projects. It enforces best practices by prioritizing the standard library, ensuring library maturity, and evaluating performance and simplicity to avoid over-engineering. Use this when you need to compare alternatives or choose the optimal dependency for a specific task.

This guide serves as a comprehensive blueprint for architecting and structuring Golang projects. It covers best practices for defining project types (CLI, Service, Library, Monorepo), adhering to 12-Factor App principles, standardizing module naming conventions, and establishing optimal directory layouts (cmd/, internal/, pkg/). Use it when starting a new Go application or refactoring a complex codebase to ensure maintainability and scalability.

Defensive Golang guidance for avoiding panics, nil traps, append aliasing, overflow, float comparison bugs, and resource leaks. Useful for writing safer code and reviewing runtime risks.