Here are three lines from my AGENTS.md that make agents a lot better with Go.

[filippo@abyssdomain.expert]

Here are three lines from my AGENTS.md that make agents a lot better with Go.

Go has great CLI tools, but many people don't know about them, and so agents are not trained to reach for them.

Maybe the Go project should maintain a Go development skill?

[miki@dragonscave.space]

@filippo This is a general problem with agents, not just in GO. They really like editing project files by hand, which often means that they install old versions of some dependencies.

I always have to explicitly ask them to use dependency management tools instead of manual file editing.

[loop0@freeradical.zone]

@filippo I use the copilot instructions for go from https://github.com/github/awesome-copilot and it does understand how to use those tools

[trode@hachyderm.io]

@filippo I would welcome an skill that is maintained for current practices!

[djspiewak@fosstodon.org]

@filippo Is there a good way to make this language specific aside from just bracketing with “when writing Go”? I frequently jump between many languages.

[filippo@abyssdomain.expert]

@djspiewak in theory, agents load skills only when they are useful. I haven't tested how effective that is for language-specific instructions.

[popey@mastodon.social]

@filippo
Great idea. I've been doing a lot more Go with Claude at work recently.
We're trying to solve exactly these kinds of context engineering problems. This blog post is from one of our Go engineers and explains what we're doing. May be of interest. 🙏

https://tessl.io/blog/making-claude-good-at-go-using-context-engineering-with-tessl/