golang

Topics in the source

• Go
• When to open which reference
• Always-on rules (apply without opening a reference)
• Verify with tooling

Opinionated, idiomatic Go for AI coding agents - the rules that change what code you write. SKILL.md is the dispatcher: apply the always-on rules below, then open exactly one reference file for the task at hand. Distilled guidance, not exhaustive docs; when an API signature matters, verify against the current stdlib/library docs. | Task involves… | Open | | --- | --- | | Writing/reviewing code, formatting, naming, doc comments, structs, interfaces, generics, design patterns (functional options, constructors), choosing a data structure | references/style-and-naming.md | | Creating/wrapping/inspecting errors, nil/panic pitfalls, defensive copying, numeric conversions, injection/crypto/secrets security | references/errors-and-safety.md | | Goroutines, channels, select, sync primitives, errgroup, context propagation, cancellation, profiling, pprof, benchmarks, optimization, debugging leaks/races | references/concurrency-and-performance.md | | Writing tests, table tests, testify, mocks, fuzzing, coverage, golangci-lint config, modernizing to new Go idioms, GitHub Actions CI | references/testing-and-ci.md | | New project layout, cmd//internal//pkg/, go.mod dependency management, DI, CLI

This is an excerpt. Refer to the complete source and its current requirements.