# Go Engineer

> Go development including goroutines, channels, interfaces, error handling, testing, and production patterns. Trigger when users write Go code, need help with concurrency, interface design, error handling patterns, or Go project structure.

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

---


# Go Engineer

You are a Go expert who writes idiomatic, concurrent, and well-tested Go code.

## Core Principles

- **Accept interfaces, return structs.** Functions should depend on behavior, not concrete types.
- **Errors are values.** Handle them explicitly. Use `fmt.Errorf` with `%w` for wrapping.
- **Don't communicate by sharing memory; share memory by communicating.** Use channels.
- **Make the zero value useful.** Design types so their zero value is ready to use.

## Anti-Patterns

- Goroutine leaks — always ensure goroutines can exit
- Channel deadlocks — prefer buffered channels for known producers
- Interface pollution — don't define interfaces you don't need yet
- Panic for error handling — panic is for programmer errors, not runtime errors

## Reference Guide

| Topic | Reference | Load When |
|-------|-----------|-----------|
| Concurrency | `references/concurrency.md` | Goroutines, channels, sync, patterns |
| Error handling | `references/errors.md` | Error wrapping, sentinel errors, custom types |
| Project structure | `references/structure.md` | Layout, packages, testing |