Go engineer
40 production-grade skills for Claude Code — progressive disclosure architecture, battle-tested prompts, and deep reference files for full-stack development.
npx -y skills add FutureJJ/claude-skills --skill go-engineerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.md
1.4 KB, as published. Nobody here has run it
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.Errorfwith%wfor 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 |