golang-patterns
Skill0 starsChanged 23 days agoMITView on GitHub
Idiomatic Go patterns covering error handling, interfaces, goroutines, channels, testing, and common pitfalls. Activate when writing or reviewing Go code.
36 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- egkike/mcp-appointments-crmtheir own version, first seen Nov 8, 2026
- Lukk17/agent-standardstheir own version, first seen Nov 7, 2026
- TsinHzl/claude-code-configtheir own version, first seen Nov 1, 2026
- damacus/agent-skillstheir own version, first seen Oct 29, 2026
- renepf/claude-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use nuxt4-patterns, configure-ecc and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
loulanyueSkillnuxt4-patterns
Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.
Also in 9 projects that use this
royaluniondesign-sysSkillconfigure-ecc
Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.
Also in 10 projects that use this
RojiosSkilldart-flutter-patterns
Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.
Also in 6 projects that use this
TironFoxSkillagent-payment-x402
Add x402 payment execution to AI agents — per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents need to pay for APIs, services, or other agents.
Also in 5 projects that use this
royaluniondesign-sysSkillcontent-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
Also in 13 projects that use this
junimnjwSkillralphinho-rfc-pipeline
RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
Also in 9 projects that use this
- +1 more from royaluniondesign-sys
Other versions36 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- peopleforrester/claude-dotfiles★ 315% same
Wrote their own version · 35
- carrot-hu23/dst-admin-go★ 920same name
- sazardev/goca★ 299same name
- loulanyue/awesome-claude-notes★ 272same name
- Fmarzochi/EGC★ 61same name
- jmrplens/gitlab-mcp-server★ 47same name
- 1024XEngineer/bytemind★ 43same name
- jmrplens/libgen-mcp★ 31same name
- FaisalAlqarni/sp-ecc★ 9same name
- gongyijie85/dsh-ecc★ 8same name
- jdanigo/hydraia★ 8same name
25 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- api-designSkill
- arch-constraint-guardSkill
- backend-patternsSkill
- clean-architectureSkill
- codebase-mappingSkill
- context-budgetSkill
- cqrsSkill
- ddd-architectureSkill
- debug-flowSkill
- dependency-auditSkill
- django-patternsSkill
- django-tddSkill
- event-driven-architectureSkill
- fd-codenavSkill
- fd-mapSkill
- frontend-patternSkill
- git-releaseSkill
- git-workflowSkill
- hexagonal-architectureSkill
- java-patternsSkill
- layered-architectureSkill
- performance-profilingSkill
- postgres-patternsSkill
- python-patternsSkill
- refactor-guideSkill
- research-firstSkill
- rust-patternsSkill
- saga-architectureSkill
- security-scanSkill
- tdd-workflowSkill
- test-gap-detectorSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 86
Keep interfaces small. A one-method interface is a feature, not a limitation.
- Distinctive: line 325
Never use panic/recover as a substitute for regular error handling.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Go Patterns Skill
Idiomatic Go for production systems. Focuses on simplicity, explicitness, and composition.
When to Activate
Activate when:
- Writing new Go packages or services
- Reviewing Go code for idiom and correctness
- Designing concurrent processing pipelines
- Debugging goroutine leaks or race conditions
- Setting up module structure or build configuration
Error Handling
Go errors are values. Handle them at the point where you have enough context to act.
Wrapping and Unwrapping
import "errors"
import "fmt"
// Wrap with %w to preserve the chain
func loadConfig(path string) (*Config, error) {
data, err := os.ReadFile(path)
if err != nil {
return nil, fmt.Errorf("loadConfig %q: %w", path, err)
}
// ...
}
// Inspect with errors.Is (sentinel) and errors.As (type)
var ErrNotFound = errors.New("not found")
if err := loadConfig("app.yaml"); err != nil {
if errors.Is(err, os.ErrNotExist) {
// file missing
}
var pathErr *os.PathError
if errors.As(err, &pathErr) {
log.Printf("path problem: %s", pathErr.Path)
}
}Sentinel Errors
// Define at package level, exported when callers need to check
var (
ErrNotFound = errors.New("not found")
ErrPermission = errors.New("permission denied")
)
// Prefer typed errors when you need to attach data
type ValidationError struct {
Field string
Message string
}
func (e *ValidationError) Error() string {
return fmt.Sprintf("validation: %s %s", e.Field, e.Message)
}Error String Conventions
// ✅ lowercase, no trailing punctuation
errors.New("connection refused")
fmt.Errorf("user %d not found", id)
// ❌ uppercase or punctuation
errors.New("Connection refused.")Interface Design
Keep interfaces small. A one-method interface is a feature, not a limitation.
The io.Reader / io.Writer Pattern
// Standard library interfaces — use them where they fit
type Reader interface {
Read(p []byte) (n int, err error)
}
type Writer interface {
Write(p []byte) (n int, err error)
}
// Compose for more complex contracts
type ReadWriter interface {
Reader
Writer
}
// Accept interfaces, return concrete types
func Process(r io.Reader) ([]byte, error) {
return io.ReadAll(r)
}
// os.File, bytes.Buffer, http.Response.Body all satisfy io.ReaderDefine Interfaces at the Consumer
// ❌ Defining in the producer package forces coupling
package store
type Repository interface { ... } // in the store package
// ✅ Define in the consumer package
package service
type userStore interface {
FindByID(ctx context.Context, id int64) (*User, error)
Save(ctx context.Context, u *User) error
}
type UserService struct {
store userStore
}Single-Method Naming
// Verb + "er" for single-method interfaces
type Reader interface { Read(...) }
type Writer interface { Write(...) }
type Stringer interface { String() string }
type Closer interface { Close() error }
type Handler interface { ServeHTTP(...) }Goroutines and Channels
Worker Pool Pattern
func workerPool(ctx context.Context, jobs <-chan Job, workers int) <-chan Result {
results := make(chan Result)
var wg sync.WaitGroup
wg.Add(workers)
for range workers {
go func() {
defer wg.Done()
for job := range jobs {
select {
case results <- process(job):
case <-ctx.Done():
return
}
}
}()
}
go func() {
wg.Wait()
close(results)
}()
return results
}Fan-Out / Fan-In
// Fan-out: send work to N goroutines
func fanOut(in <-chan int, n int) []<-chan int {
outs := make([]<-chan int, n)
for i := range n {
ch := make(chan int)
outs[i] = ch
go func() {
defer close(ch)
for v := range in {
ch <- v * 2
}
}()
}
return outs
}
// Fan-in: merge N channels into one
func merge(channels ...<-chan int) <-chan int {
out := make(chan int)
var wg sync.WaitGroup
wg.Add(len(channels))
for _, ch := range channels {
go func(c <-chan int) {
defer wg.Done()
for v := range c {
out <- v
}
}(ch)
}
go func() {
wg.Wait()
close(out)
}()
return out
}Select and Context Cancellation
func doWork(ctx context.Context) error {
ticker := time.NewTicker(500 * time.Millisecond)
defer ticker.Stop()
for {
select {
case <-ctx.Done():
return ctx.Err()
case t := <-ticker.C:
if err := tick(t); err != nil {
return fmt.Errorf("tick: %w", err)
}
}
}
}Channel Ownership Rule
The goroutine that creates a channel is responsible for closing it. Closing a channel from a reader or having multiple goroutines close the same channel causes panics.
Struct Embedding vs Composition
Embedding for Behaviour Promotion
type Logger struct {
level string
}
func (l *Logger) Log(msg string) {
fmt.Printf("[%s] %s\n", l.level, msg)
}
type Server struct {
Logger // promotes Log method
addr string
}
s := Server{Logger: Logger{level: "INFO"}, addr: ":8080"}
s.Log("starting") // calls s.Logger.LogPrefer Explicit Fields for Data
// ❌ Embedding for data models creates implicit API surface
type FullUser struct {
User // every User field/method becomes part of FullUser's API
Profile
}
// ✅ Explicit fields make dependencies obvious
type FullUser struct {
User User
Profile Profile
}defer, panic, recover
defer — Always for Cleanup
func writeFile(path string, data []byte) error {
f, err := os.Create(path)
if err != nil {
return err
}
defer f.Close() // runs even if Write returns error
_, err = f.Write(data)
return err
}
// defer evaluates arguments immediately — useful for timing
func trace(name string) func() {
start := time.Now()
return func() { log.Printf("%s: %v", name, time.Since(start)) }
}
defer trace("expensiveOp")()panic / recover — Only at Boundaries
// Use panic only for programmer errors (invariant violations)
func mustPositive(n int) int {
if n <= 0 {
panic(fmt.Sprintf("expected positive, got %d", n))
}
return n
}
// Recover at the top of a goroutine or HTTP handler to convert to error
func safeExec(fn func()) (err error) {
defer func() {
if r := recover(); r != nil {
err = fmt.Errorf("panic: %v", r)
}
}()
fn()
return nil
}Never use panic/recover as a substitute for regular error handling.
Table-Driven Tests
func TestParseDate(t *testing.T) {
cases := []struct {
name string
input string
want time.Time
wantErr bool
}{
{
name: "ISO format",
input: "2024-01-15",
want: time.Date(2024, 1, 15, 0, 0, 0, 0, time.UTC),
},
{
name: "empty string",
input: "",
wantErr: true,
},
{
name: "invalid format",
input: "15/01/2024",
wantErr: true,
},
}
for _, tc := range cases {
t.Run(tc.name, func(t *testing.T) {
got, err := ParseDate(tc.input)
if (err != nil) != tc.wantErr {
t.Fatalf("ParseDate(%q) error = %v, wantErr %v", tc.input, err, tc.wantErr)
}
if !tc.wantErr && !got.Equal(tc.want) {
t.Errorf("ParseDate(%q) = %v, want %v", tc.input, got, tc.want)
}
})
}
}Go Modules
go.mod Structure
module github.com/org/myservice
go 1.23
require (
github.com/some/dep v1.2.3
)Workspace Mode (go.work) for Multi-Module Repos
go 1.23
use (
./cmd/api
./internal/core
./pkg/client
)go work init ./cmd/api ./internal/core
go work use ./pkg/clientModule Commands
go mod tidy # add missing, remove unused
go mod vendor # copy deps to vendor/
go get github.com/x@v1.2.3 # add or upgrade
go mod why github.com/x # explain why dep is neededsync Package
var mu sync.Mutex
mu.Lock()
defer mu.Unlock()
// RWMutex — many readers, one writer
var rw sync.RWMutex
rw.RLock()
defer rw.RUnlock()
// WaitGroup — wait for goroutines to finish
var wg sync.WaitGroup
wg.Add(1)
go func() {
defer wg.Done()
// ...
}()
wg.Wait()
// Once — run exactly once (e.g., lazy init)
var once sync.Once
var instance *DB
func getDB() *DB {
once.Do(func() { instance = newDB() })
return instance
}
// Atomic operations — simple counters without a mutex
var counter atomic.Int64
counter.Add(1)
n := counter.Load()Build Tags
//go:build linux && amd64
package platform
// This file only compiles on 64-bit Linux.
func pageSize() int { return 4096 }go build -tags integration ./...
go test -tags integration ./...Common Pitfalls
Goroutine Leaks
// ❌ Nothing reads from results — goroutines block forever
func leak() {
results := make(chan int)
go func() { results <- compute() }()
// forgot to read results
}
// ✅ Always ensure goroutines can exit — use buffered channels or context
func noLeak(ctx context.Context) {
results := make(chan int, 1)
go func() {
select {
case results <- compute():
case <-ctx.Done():
}
}()
}nil Interface vs nil Pointer
// ❌ Returning a typed nil as an interface is NOT nil
func getErr() error {
var p *os.PathError = nil
return p // error interface is not nil!
}
// ✅ Return untyped nil
func getErr() error {
return nil
}Map Race Conditions
// ❌ Concurrent read/write on map causes data race
m := map[string]int{}
go func() { m["a"] = 1 }()
go func() { _ = m["a"] }()
// ✅ Use sync.Map or protect with a mutex
var mu sync.RWMutex
mu.Lock()
m["a"] = 1
mu.Unlock()Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

