skills

Go 语言核心 idioms、命名规范、包结构与接口设计准则。Use when writing or reviewing any Go code — naming conventions, package layout, interface design, enum patterns, anti-patterns, or verifying Go code correctness. Trigger whenever the user writes Go functions, types, packages, or asks about idiomatic Go style.

Go error handling using ErrorX sentinel pattern and errno directory structure. Use when defining errors, wrapping errors, propagating errors across layers, checking error types, handling GORM/database errors, or when to log vs return an error in Go projects. Apply whenever writing or reviewing error handling code in any Go layer.

Go structured logging using Zap Sugar API with context propagation. Use when initializing loggers, writing log statements, extracting request context into logs, configuring log output, or deciding which layer should log. Apply whenever user writes log.Infow/Errorw/Warnw calls, uses zap fields, or asks about request-ID propagation in Go projects.

Clean Architecture layer design and Google Wire dependency injection for Go services. Use when structuring a new service, wiring dependencies, defining layer interfaces, deciding where business logic belongs, or when a handler is accessing the database directly. Always apply this skill when the user writes or reviews handler/biz/store/model layers, Wire setup, or asks about Go service architecture.

Go testing with Ginkgo BDD suites, Gomega matchers, uber-go/mock mocks, and benchmarks. Use when writing unit tests, generating mocks for interfaces, setting up test suites, or running parallel tests in Go projects. Apply whenever user writes Describe/It/BeforeEach blocks, uses mockgen, or asks about Ginkgo setup.