go-development
Installation
SKILL.md
When to Use
Use for any Go task; load the referenced skills below as needed.
Procedure
- This is a router, not a bundle: load ONLY the sub-skill(s) the current task actually needs, never all of them.
- coding-style: simple boring idiomatic Go, stdlib-first, behavior comments, TDD table-driven tests, vet/fmt/lint.
- go-quirks-and-safety: nil maps/slices/pointers, nil-interface trap, bounds, slice aliasing, goroutine and resource leaks.
- api-library-design: public API naming, options with defaults, small surface, semver, examples.
- architecture-planning: boring-first, failure modes, one recommendation.
- debugging: reproduce, error, logs, isolate, fix cause, always report.
- git-workflow: conventional atomic commits, gh CLI, CI gate then tag release.
- azure-deployment: status-first, az direct, systemd/Caddy/Postgres, deploy after CI.
- readme-writing: title, what, why, alternatives, features, explained example, gotchas.
Pitfalls
- Skipping the relevant skill for the task at hand.
Verification
- Correct sub-skill consulted before writing, reviewing, or shipping Go code.