Agent skill
golang-patterns
Idiomatic Go patterns and policies. Use when writing, reviewing, or refactoring Go application code. Do NOT use for test code -- use golang-testing instead.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/golang-patterns-cooldaemon-dotfiles
SKILL.md
Go Development Patterns
Core Principles
| Principle | Description |
|---|---|
| Simplicity > Cleverness | Code should be obvious and easy to read |
| Zero value useful | Types should work without initialization |
| Accept interfaces, return structs | Functions accept interface params, return concrete types |
| Errors are values | Handle errors explicitly, never ignore |
| Clear > Clever | Prioritize readability |
Error Handling (CRITICAL)
Always Wrap with Context
if err != nil {
return nil, fmt.Errorf("load config %s: %w", path, err)
}
Use errors.Is and errors.As
if errors.Is(err, sql.ErrNoRows) { /* specific error */ }
var validationErr *ValidationError
if errors.As(err, &validationErr) { /* error type */ }
Never Ignore Errors
// BAD
result, _ := doSomething()
// GOOD
result, err := doSomething()
if err != nil {
return err
}
Interface Design
Define Where Used (Consumer Package)
// In service package, NOT in repository package
type UserStore interface {
GetUser(id string) (*User, error)
}
Small, Focused Interfaces
Prefer single-method interfaces — enables composition and testing flexibility. Compose as needed.
Concurrency Policies
Context Rules
- Context is ALWAYS first parameter
- Never store context in structs
- Use
context.WithTimeoutfor external calls
Avoid Goroutine Leaks
// Use buffered channel or select with ctx.Done()
ch := make(chan []byte, 1)
select {
case ch <- data:
case <-ctx.Done():
}
Use errgroup for Coordinated Goroutines
g, ctx := errgroup.WithContext(ctx)
g.Go(func() error { /* ... */ })
if err := g.Wait(); err != nil { /* ... */ }
Package Organization
myproject/
├── cmd/myapp/main.go # Entry point
├── internal/ # Private packages
│ ├── handler/
│ ├── service/
│ └── repository/
├── pkg/ # Public packages
└── Makefile
Package Naming
- Short, lowercase, no underscores
- No redundant suffixes (
usernotuserService)
No Package-Level State
Use dependency injection, not global variables.
Struct Design
Functional Options for Configurability
func NewServer(addr string, opts ...Option) *Server
// Usage
server := NewServer(":8080", WithTimeout(60*time.Second))
Performance Policies
| Policy | Why |
|---|---|
| Preallocate slices | make([]T, 0, len) avoids reallocations |
| Use strings.Builder | Avoid += in loops |
| Use sync.Pool | For frequent allocations |
Anti-Patterns
| Anti-Pattern | Correct Approach |
|---|---|
| Naked returns in long functions | Explicit returns |
| panic for control flow | Return errors |
| Context in struct | Context as first param |
| Mixed receivers | Consistent value OR pointer |
Ignoring errors with _ |
Handle or explicitly document |
Commands
See makefile-first skill for command execution policy.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?