G

golang-popular-libraries

by @samberv
4.6(20)

本番レベルのGoライブラリとフレームワークを推奨。車輪の再発明を避け、標準ライブラリと成熟したオープンソースソリューションを優先。

api-developmentbackend-developmentgo-ecosystemlibrary-recommendationbest-practicesGitHub
インストール方法
npx skills add https://github.com/samber/cc-skills-golang --skill golang-popular-libraries
compare_arrows

Before / After 効果比較

1
使用前

GitHubを検索し、ドキュメントを読み、複数のライブラリのスター数、アクティビティ、パフォーマンスを比較する必要がある。HTTPクライアントの選定には1〜2時間の調査が必要で、未熟なライブラリを選んでしまう可能性もある。

使用後

要件に基づいて最適な本番レベルのライブラリを自動で推薦し、長所と短所、適用シナリオを説明し、直接サンプルコードを提供し、5分で選定と統合を完了する。

SKILL.md

golang-popular-libraries

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:

  • Production-readiness - Mature, well-maintained libraries with active communities

  • Simplicity - Go's philosophy favors simple, idiomatic solutions

  • Performance - Libraries that leverage Go's strengths (concurrency, compiled performance)

  • Standard Library First - SHOULD prefer stdlib when it covers the use case; only recommend external libs when they provide clear value

Reference Catalogs

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-management skill for adding, auditing, and managing dependencies

  • → See samber/cc-skills-golang@golang-samber-do skill for samber/do dependency injection details

  • → See samber/cc-skills-golang@golang-samber-oops skill for samber/oops error handling details

  • → See samber/cc-skills-golang@golang-stretchr-testify skill for testify testing details

  • → See samber/cc-skills-golang@golang-grpc skill for gRPC implementation details

Weekly Installs754Repositorysamber/cc-skills-golangGitHub Stars1.1KFirst SeenMar 22, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled onopencode719cursor713codex709gemini-cli707github-copilot706amp705

ユーザーレビュー (0)

レビューを書く

効果
使いやすさ
ドキュメント
互換性

レビューなし

統計データ

インストール数32.5K
評価4.6 / 5.0
バージョン
更新日2026年7月9日
比較事例1 件

ユーザー評価

4.6(20)
5
50%
4
50%
3
0%
2
0%
1
0%

この Skill を評価

0.0

対応プラットフォーム

🔧Claude Code

タイムライン

作成2026年4月9日
最終更新2026年7月9日
🎁 Agent 知識カード
アンケート