golang-popular-libraries

Recommends production-ready Go libraries and frameworks with a standard-library-first philosophy.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/rockcookies/skills --skill golang-popular-libraries-rockcookies
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: golang-popular-libraries
Source: https://github.com/rockcookies/skills/tree/main/skills/samber-golang/golang-popular-libraries
Command: npx skills add https://github.com/rockcookies/skills --skill golang-popular-libraries-rockcookies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the right Go library is hard: the ecosystem is large, some popular packages are deprecated or unmaintained, and developers often add dependencies for things the standard library already covers. This Skill guides library selection so you pick mature, well-maintained options and avoid unnecessary dependencies. ## Core Features & Use Cases - Curated library catalogs: Reference lists of vetted third-party libraries organized by category (web frameworks, ORMs, database drivers, testing, logging, messaging, caching, and more), plus new standard library packages (slices, maps, log/slog) and official golang.org/x extensions. - Stdlib-first decision rules: Enforces checking whether the standard library covers the use case before recommending external packages, and warns against wrappers that add no real value. - Maturity and maintenance checks: Directs verification of maintenance status, license, and pkg.go.dev importer counts before recommending a library, flagging deprecated options like Logrus. - Use Case: When asked which PostgreSQL driver to use, it recommends pgx over lib/pq; when asked for structured logging on Go 1.21+, it presents log/slog before suggesting zap or zerolog. ## Quick Start Ask the agent which Go library to use for a specific task, such as "Which Kafka client should I use in my Go application?"

Frequently Asked Questions about golang-popular-libraries

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Which Go PostgreSQL driver should I use, pgx or lib/pq?▼

pgx (github.com/jackc/pgx) is the recommended choice for new projects. It is faster than lib/pq and supports all PostgreSQL types and advanced features, while lib/pq remains a viable but less capable alternative.

What Go library should I use for structured logging?▼

Start with log/slog, the standard library structured logger available since Go 1.21. Consider zap or zerolog only when you need specific capabilities like zero-allocation logging in hot paths, and avoid Logrus since it is deprecated.

Should I use Gin, Echo, or chi for a Go REST API?▼

For a lightweight router that stays close to net/http with path parameters and middleware, chi is the best fit. Gin and Echo are full frameworks suited to larger applications that want more built-in features.

Is GORM or sqlc better for type-safe database access in Go?▼

sqlc is preferred when you want compile-time safety because it generates type-safe Go code from SQL with no runtime reflection. GORM is more feature-rich but uses runtime reflection, so SQL errors surface only at runtime.

When should I avoid adding a third-party Go library?▼

Avoid libraries that merely wrap standard library functionality without adding value, abandoned or unmaintained packages, and heavy dependencies for simple needs. Each added dependency increases attack surface and maintenance burden.

What Kafka client library is recommended for Go?▼

franz-go (github.com/twmb/franz-go) is the recommended modern Kafka client, offering high performance and feature completeness. The older sarama client remains an alternative but franz-go is the preferred choice for new projects.