SKILL.md
$27
Find more libraries here: https://github.com/avelino/awesome-go
This skill is not exhaustive. Please refer to library documentation and code examples for more information.
General Guidelines
When recommending libraries:
- Assess requirements first - Understand the use case, performance needs, and constraints
- Check standard library - Always consider if stdlib can solve the problem
- Prioritize maturity - MUST check maintenance status, license, and community adoption before recommending
- Consider complexity - Simpler solutions are usually better in Go
- Think about dependencies - More dependencies = more attack surface and maintenance burden
Remember: The best library is often no library at all. Go's standard library is excellent and sufficient for many use cases.
Anti-Patterns to Avoid
- Over-engineering simple problems with complex libraries
- Using libraries that wrap standard library functionality without adding value
- Abandoned or unmaintained libraries: ask the developer before recommending these
- Suggesting libraries with large dependency footprints for simple needs
- Ignoring standard library alternatives
Cross-References
- → See
samber/cc-skills-golang@golang-dependency-managementskill for adding, auditing, and managing dependencies
- → See
samber/cc-skills-golang@golang-samber-doskill for samber/do dependency injection details
- → See
samber/cc-skills-golang@golang-samber-oopsskill for samber/oops error handling details
- → See
samber/cc-skills-golang@golang-stretchr-testifyskill for testify testing details
- → See
samber/cc-skills-golang@golang-grpcskill for gRPC implementation details