Golang Popular Libraries

[
  {
    "id": 1,
    "name": "stdlib-first-json",
    "description": "encoding/json should be tried first even for high-throughput use cases; third-party libraries are only justified after profiling confirms JSON is the bottleneck",
    "prompt": "I'm building a high-throughput Go API that processes thousands of JSON requests per second. A colleague says: 'You should use jsoniter or sonic from the start — encoding/json is known to be slow and you'll need the performance. There's no reason to start with a worse library when we know we'll need the fast one.' Is this advice correct? What JSON library should I use?",
    "trap": "The colleague's argument sounds pragmatic — why start with a known-slower library if you'll switch later anyway? But the skill teaches stdlib-first: add dependencies only when profiling confirms they are the bottleneck. The model should push back on the colleague and recommend starting with encoding/json.",
    "assertions": [
      {"id": "1.1", "text": "Pushes back on the colleague's advice — recommends starting with encoding/json despite the high-throughput context"},
      {"id": "1.2", "text": "Explains that the standard library should be the default until profiling confirms JSON is actually the bottleneck"},
      {"id": "1.3", "text": "Notes that encoding/json may be sufficient — thousands of requests per second does not automatically justify a third-party library"},
      {"id": "1.4", "text": "Recommends profiling first (pprof) before reaching for jsoniter or sonic"},
      {"id": "1.5", "text": "If mentioning alternatives (jsoniter, sonic), frames them as options for after measurement proves stdlib is insufficient, not as defaults"}
    ]
  },
  {
    "id": 2,
    "name": "pgx-over-lib-pq",
    "description": "Tests whether the model recommends pgx over lib/pq for PostgreSQL when advanced features or performance matter",
    "prompt": "I'm starting a new Go project that needs to connect to PostgreSQL. Which driver should I use?",
    "trap": "Without the skill, the model recommends lib/pq because it's more commonly seen in tutorials, missing that pgx is faster and has more features",
    "assertions": [
      {"id": "2.1", "text": "Recommends pgx (github.com/jackc/pgx) as the primary recommendation"},
      {"id": "2.2", "text": "Mentions that pgx is faster than lib/pq"},
      {"id": "2.3", "text": "Notes that pgx supports all PostgreSQL types and advanced features"},
      {"id": "2.4", "text": "May mention lib/pq as an alternative but positions pgx as the preferred choice"},
      {"id": "2.5", "text": "Does NOT recommend lib/pq as the primary choice without mentioning pgx"}
    ]
  },
  {
    "id": 3,
    "name": "chi-for-minimal-router",
    "description": "Tests whether the model recommends chi for lightweight routing needs instead of full frameworks",
    "prompt": "I need a simple HTTP router for my Go REST API. It just needs path parameters and middleware support. I want to stay close to net/http. What should I use?",
    "trap": "Without the skill, the model recommends Gin or Echo (full frameworks) when chi's lightweight, net/http-compatible router is a better fit",
    "assertions": [
      {"id": "3.1", "text": "Recommends chi (github.com/go-chi/chi) as a strong match for the stated requirements"},
      {"id": "3.2", "text": "Explains that chi is lightweight and composes well with net/http"},
      {"id": "3.3", "text": "Notes that chi has minimal dependencies"},
      {"id": "3.4", "text": "May mention Gin/Echo as alternatives but positions chi as the better fit for staying close to net/http"},
      {"id": "3.5", "text": "Does NOT recommend a full framework (Gin, Echo, Fiber) as the primary choice when the user explicitly wants to stay close to net/http"}
    ]
  },
  {
    "id": 4,
    "name": "slog-over-external-loggers",
    "description": "Tests whether the model considers log/slog (Go 1.21+) before recommending external logging libraries",
    "prompt": "I need structured l