← ClaudeAtlas

go-scaffoldlisted

Scaffolds a production-ready Go modular-monolith REST API — chi, contract-first oapi-codegen + sqlc, Postgres/pgx, JWT+argon2id+RBAC, users/posts example modules. Triggers: 'scaffold go api', 'create go rest api', 'new go backend', or a repo with no go.mod.
tammai/bigin-skills · ★ 0 · API & Backend · score 65
Install: claude install-skill tammai/bigin-skills
# go-scaffold This skill is mechanical: gather config, run the script, relay its output. Do not deliberate — no thinking needed on any step here. Scaffolds a Go REST API from a single template. The mechanical work is done by a deterministic script — `scripts/scaffold.mjs` (Node stdlib only, cross-platform, zero prompts). This skill's only jobs: **decide the CLI flags, run the script, report the result.** Do not perform any scaffolding steps yourself. Stack: Go ≥1.24, chi router, contract-first via `oapi-codegen` (`api/openapi.yaml` → per-module server interface + models) and `sqlc` (per-module SQL → typed queries), `pgx/v5` + Postgres, `caarlos0/env` config, structured `log/slog`, `go-chi/cors` + `go-chi/httprate`, `golang-migrate` for schema migrations. One template only — no variant menu like nuxt-scaffold's. The generated app is a modular monolith with two modules (`users` and `posts`) plus a shared auth kernel (JWT + argon2id + RBAC): signup/login/refresh/logout, CRUD with optimistic concurrency, soft-delete erasure with a synchronous cross-module anonymize, and a batched cross-module read (no N+1) — proving the full pipeline and the module boundary end-to-end. Everything else about the shape is fixed. > Governance (CLAUDE.md, `.claude/rules/`, AI guides, `bash-guard.mjs`) is **not** this skill's job — run `bigin-harness-setup` afterward to overlay it. Prerequisites: Go ≥1.24 on PATH, git. Docker/staticcheck are optional — staticcheck runs if found on PATH and is sk