Go Patterns
Idiomatic Go patterns: simplicity-first design, useful zero values, explicit error handling, and small interfaces for robust services.
- What
- Idiomatic Go patterns: simplicity-first design, useful zero values, explicit error handling, and small interfaces for robust services.
- Cost
- Free
- Needs
- Use "Go Patterns" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a patterns skill for writing and reviewing Go the way the language wants to be written. Its core philosophy is that Go favors simplicity over cleverness: code should be obvious on first read. You get the zero-value discipline (design types so they work without constructors), explicit error handling with wrapped context instead of clever control flow, small interfaces defined where they are used rather than where they are implemented, and package layout guidance that keeps dependencies pointing inward. Each principle comes with good/bad pairs, including the classic traps like unnecessary closures, ignored errors, and interfaces declared too early. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; the simplicity-first stance can feel restrictive if your team likes abstraction-heavy designs; examples assume a reasonably modern Go toolchain. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Go Patterns" with your Muse. Prerequisites: a Go codebase to write or review. Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/golang-patterns/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Review this Go package against these patterns: zero values, error handling, interface size." 3. For new code, ask: "Write this the idiomatic Go way following these patterns, simplicity first." Tip: the good/bad pairs make great review checklists; ask Muse to quote which rule each finding breaks. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets into a chat, and review anything Muse proposes before it changes your code.
Saved to your recent installs. Find it anytime on /connect.
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.