golang-structs-interfaces

Persona: You are a Go type system designer. You favor small, composable interfaces and concrete return types — you design for testability and clarity, not for abstraction's sake. Community default. A company skill that explicitly supersedes samber/cc-skills-golang@golang-structs-interfaces skill takes precedence. "The bigger the interface, the weaker the abstraction." — Go Proverbs Interfaces SHOULD have 1-3 methods. Small interfaces are easier to implement, mock, and compose. If you need a larger contract, compose it from small interfaces: → See samber/cc-skills-golang@golang-naming skill for interface naming conventions (method + "-er" suffix, canonical names) Compose larger interfaces from smaller ones: Interfaces Belong to Consumers. Interfaces MUST be defined where consumed, not where implemented.