# Go Interfaces

> Go interface design patterns and best practices Use when this capability is needed.

- Skill: `tomevault-io/go-interfaces-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/go-interfaces-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/go-interfaces-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/go-interfaces-2

---


# 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

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/jamesprial) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->