Go interface design patterns and best practices
Pro scans all 4 files and shows the line behind each finding
Scanned 2/12/2026
Skills Directorynpx -y skills add JamesPrial/claudefiles --skill interfaces --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Interfaces?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jamesprial-interfaces)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: go-interfaces
description: Go interface design patterns and best practices
---
# Interface Design
Master Go's approach to interfaces: implicit satisfaction, consumer-driven design, and composition patterns.
## Route by Concern
- **Accept/return patterns** → see [design/](design/)
- Accept interfaces, return structs principle
- When to deviate from the rule
- **Interface pollution** → see [pollution/](pollution/)
- Detecting unnecessary abstractions
- Premature interface creation
- **Embedding patterns** → see [embedding/](embedding/)
- Interface composition techniques
- Method set expansion
## Quick Check
- [ ] Interface defined by consumer, not producer
- [ ] Keep interfaces small (<5 methods)
- [ ] Return concrete types from functions
- [ ] No interface{} unless truly necessary
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
