AI coding agents write functional Go, but they default to whatever patterns show up most in their training data. That usually means older syntax, pre-modern standard library calls, and zero awareness of features added in recent releases.
The GoLand team at JetBrains just shipped Modern Go Guidelines, an open source MIT licensed plugin that gives your AI agent a current, version-matched reference for writing Go code.
How It Works
The plugin includes a CLI tool with two subcommands: list and explain. The use-modern-go skill tells the agent to run list before editing any Go file, then call explain when it needs more detail on a specific rule.
The list subcommand reads the Go version from your go.mod file and returns only the guidelines that apply. A project declaring go 1.25 gets skills for Go 1.25 and earlier. It does not receive guidelines for Go 1.26 or Go 1.27 features the project cannot compile.
go-modern-guidelines list --file-path ./internal/worker/worker.goEach guideline comes with a stable ID. When the agent needs the full picture, explain delivers a before-and-after code example showing the old pattern alongside its modern replacement.
go-modern-guidelines explain generic_methodsWhat the Guidelines Cover
The ruleset spans Go 1.0 through Go 1.27 and includes patterns from the Go modernize analyzer. A few concrete examples:
slices.Containsinstead of a manual search loopminandmaxinstead of handwritten comparisonssync.WaitGroup.Goinstead of separateAdd,go, andDonecalls (Go 1.25)errors.AsTypefor type-safe error matching (Go 1.26 and later)strings.CutLastandbytes.CutLastinstead ofLastIndexand manual slicing (Go 1.27)

Installation
Install from the Claude marketplace in two commands:
/plugin marketplace add JetBrains/go-modern-guidelines
/plugin install modern-go-guidelinesThen activate with /use-modern-go. The integration requires the Go toolchain on your PATH. On first use it runs go install and caches the binary locally. It does not modify your project files.
A local repository install path is also available for teams that want to test before publishing. The GoLand team positions this as complementary to go fix: the guidelines help agents write current code from the start, while go fix updates patterns already in the codebase.
