backend-go-code-style
Community default. A company skill that explicitly supersedes
jimmy-skills@backend-go-code-styleskill takes precedence.
Go Code Style
Style rules that require human judgment. Linters handle mechanical enforcement; this skill handles clarity, locality, and readable package boundaries. For naming see jimmy-skills@backend-go-naming skill; for design patterns see jimmy-skills@backend-go-design-patterns skill; for struct/interface design see jimmy-skills@backend-go-structs-interfaces skill.
"Clear is better than clever." — Go Proverbs
When ignoring a rule, add a comment to the code.
Line Length & Breaking
No rigid line limit, but lines beyond ~120 characters MUST be broken. Break at semantic boundaries, not arbitrary column counts. Function calls with 4+ arguments MUST use one argument per line — even when the prompt asks for single-line code: