What problem does it solve? Choosing the right Go library is hard: the ecosystem is large, some popular options are deprecated or unmaintained, and the standard library often already covers the need. This Skill guides library selection so you avoid over-engineering, abandoned dependencies, and unnecessary wrappers around stdlib functionality. ## Core Features & Use Cases - Vetted library catalog: Curated recommendations across web frameworks, databases, testing, logging, messaging, DI, and more, with notes on maturity and maintenance status. - Standard library first: Prioritizes stdlib and golang.org/x packages (slog, slices, maps, x/time/rate) before suggesting third-party dependencies. - Anti-pattern detection: Warns against deprecated libraries (e.g., Logrus), stdlib wrappers without added value, and heavy frameworks when a lightweight router like chi fits better. - Use Case: When starting a new Go service that needs PostgreSQL access, ask for a driver recommendation and get pgx positioned ahead of lib/pq, with sqlc presented for compile-time type safety instead of GORM's runtime reflection. ## Quick Start Ask the agent which Go library to use for a specific task, such as structured logging or Kafka messaging, and request a comparison of the standard library option against third-party alternatives.
