# Golang Popular Libraries

Golang library and framework selection, vetted production-ready options by category...

- Repository: https://github.com/samber/cc-skills-golang (3750 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add samber/cc-skills-golang --skill golang-popular-libraries -g -a claude-code -y`
Codex: `npx skills add samber/cc-skills-golang --skill golang-popular-libraries -g -a codex -y`
Cursor: `npx skills add samber/cc-skills-golang --skill golang-popular-libraries -g -a cursor -y`
Gemini CLI: `npx skills add samber/cc-skills-golang --skill golang-popular-libraries -g -a gemini-cli -y`

## Description

Golang library and framework selection, vetted production-ready options by category (web, database, testing, logging, messaging), new and experimental stdlib packages, standard-library-first tradeoffs, and maturity signals (maintenance, license, importer counts). Apply when the user asks for library suggestions, wants to compare alternatives, needs to choose a library for a specific task, or when a new dependency is being added to the project. Not for a specific library's API once chosen (→ See that library's dedicated skill, e.g. `samber/cc-skills-golang@golang-samber-lo`), nor for go.mod mechanics, upgrades, or vulnerability audits (→ See `samber/cc-skills-golang@golang-dependency-management` skill).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

**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.

# Go Libraries and Frameworks Recommendations

## Core Philosophy

When recommending libraries, prioritize:

1. **Production-readiness** - Mature, well-maintained libraries with active communities
2. **Simplicity** - Go's philosophy favors simple, idiomatic solutions
3. **Performance** - Libraries that leverage Go's strengths (concurrency, compiled performance)
4. **Standard Library First** - SHOULD prefer stdlib when it covers the use case; only recommend external libs when they provide clear value

## Reference Catalogs

- [Standard Library - New & Experimental](./references/stdlib.md), v2 packages, promoted x/exp packages, golang.org/x extensions
- [Libraries by Category](./references/libraries.md), vetted third-party libraries for web, database, testing, logging, messaging, and more
- [Development Tools](./references/tools.md), debugging, linting, testing, and dependency management tools

Find more libraries here: <https://github.com/avelino/awesome-go>

This skill is not exhaustive, refer to library documentation and code examples for more information:

- When exploring a candidate library, → See `samber/cc-skills-golang@golang-pkg-go-dev` skill (`godig`) for docs, symbols, versions, importers, and known vulnerabilities, prefer it over Context7 for Go package facts.
- Once a candidate is added to your build, → See `samber/cc-skills-golang@golang-gopls` skill (`gopls`) to browse its actual resolved source and compare candidates side by side.
- Context7 remains a fallback for docs not indexed on pkg.go.dev.

## General Guidelines

When recommending libraries:

The rest: https://github.com/samber/cc-skills-golang/blob/HEAD/skills/golang-popular-libraries/SKILL.md