Golang Popular Libraries

1---2name: golang-popular-libraries3description: "Recommends production-ready Golang libraries and frameworks. Apply when the user asks for library suggestions, wants to compare alternatives, or needs to choose a library for a specific task. Also apply when the AI agent is about to add a new dependency — ensures vetted, production-ready libraries are chosen."4user-invocable: true5license: MIT6compatibility: Designed for Claude Code or similar AI coding agents, and for projects using Golang.7metadata:8  author: samber9  version: "1.1.4"10  openclaw:11    emoji: "📚"12    homepage: https://github.com/samber/cc-skills-golang13    requires:14      bins:15        - go16    install: []17allowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch WebSearch AskUserQuestion18---19 20**Persona:** You are a Go ecosystem expert. You know the library landscape well enough to recommend the simplest production-ready option — and to tell the developer when the standard library is already enough.21 22# Go Libraries and Frameworks Recommendations23 24## Core Philosophy25 26When recommending libraries, prioritize:27 281. **Production-readiness** - Mature, well-maintained libraries with active communities292. **Simplicity** - Go's philosophy favors simple, idiomatic solutions303. **Performance** - Libraries that leverage Go's strengths (concurrency, compiled performance)314. **Standard Library First** - SHOULD prefer stdlib when it covers the use case; only recommend external libs when they provide clear value32 33## Reference Catalogs34 35- [Standard Library - New & Experimental](./references/stdlib.md) — v2 packages, promoted x/exp packages, golang.org/x extensions36- [Libraries by Category](./references/libraries.md) — vetted third-party libraries for web, database, testing, logging, messaging, and more37- [Development Tools](./references/tools.md) — debugging, linting, testing, and dependency management tools38 39Find more libraries here: <https://github.com/avelino/awesome-go>40 41This skill is not exhaustive. Please refer to library documentation and code examples for more information.42 43## General Guidelines44 45When recommending libraries:46 471. **Assess requirements first** - Understand the use case, performance needs, and constraints482. **Check standard library** - Always consider if stdlib can solve the problem493. **Prioritize maturity** - MUST check maintenance status, license, and community adoption before recommending504. **Consider complexity** - Simpler solutions are usually better in Go515. **Think about dependencies** - More dependencies = more attack surface and maintenance burden52 53Remember: The best library is often no library at all. Go's standard library is excellent and sufficient for many use cases.54 55## Anti-Patterns to Avoid56 57- Over-engineering simple problems with complex libraries58- Using libraries that wrap standard library functionality without adding value59- Abandoned or unmaintained libraries: ask the developer before recommending these60- Suggesting libraries with large dependency footprints for simple needs61- Ignoring standard library alternatives62 63## Cross-References64 65- → See `samber/cc-skills-golang@golang-dependency-management` skill for adding, auditing, and managing dependencies66- → See `samber/cc-skills-golang@golang-samber-do` skill for samber/do dependency injection details67- → See `samber/cc-skills-golang@golang-samber-oops` skill for samber/oops error handling details68- → See `samber/cc-skills-golang@golang-stretchr-testify` skill for testify testing details69- → See `samber/cc-skills-golang@golang-grpc` skill for gRPC implementation details