Go Design Patterns
Idiomatic Go patterns — functional options, graceful shutdown, resilience, architecture styles — applied only when they solve a real problem
- What
- Idiomatic Go patterns — functional options, graceful shutdown, resilience, architecture styles — applied only when they solve a real problem
- Cost
- Free
- Needs
- a Go project (the go toolchain)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a Go architecture skill with a persona that pushes back: apply patterns only when they solve a real problem, never to demonstrate sophistication. It covers functional options, constructor APIs, init() and global-state avoidance, enums, panic vs error decisions, resource lifecycle, graceful shutdown, timeouts and retries, streaming and iterators, and architecture styles (clean, hexagonal, DDD, flat) — with separate design mode (ask the developer's architecture preference first) and review mode (scan for init() abuse, unbounded resources, missing timeouts). Distinct from the already-published samber skills (golang-testing, golang-safety, golang-benchmark, golang-troubleshooting) — this is the architecture-level one, and it explicitly defers DI wiring, error mechanics, and refactoring to their own skills. By @samber, listed here with credit to its creator. Honest caveats: patterns are guidance, not law — the skill will ask you questions before proposing architecture, which is correct but slower than a blind template. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Go project (the go toolchain) Install "Go Design Patterns" for me. Idiomatic Go patterns — functional options, graceful shutdown, resilience, architecture styles — applied only when they solve a real problem Repository: https://github.com/samber/cc-skills-golang/blob/main/skills/golang-design-patterns/SKILL.md 1. Fetch the SKILL.md file for the samber-golang-design-patterns skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "samber-golang-design-patterns". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.