Go Naming Conventions
Go naming — packages, constructors, errors, booleans, MixedCaps always, the utils/helpers anti-pattern
- What
- Go naming — packages, constructors, errors, booleans, MixedCaps always, the utils/helpers anti-pattern
- 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 naming skill covering the full identifier surface: packages (lowercase single words, no utils/helpers), files, constructors (New vs NewTypeName), structs, interfaces, constants, enums, errors (ErrNotFound vs NotFoundError), booleans, receivers, getters/setters (no Get prefix), functional options, acronyms, and test/subtest names. The iron rule: MixedCaps always, never underscores; capitalization controls visibility. Distinct from the already-published samber skills — and it explicitly defers general implementation questions to other skills, naming decisions only. By @samber, listed here with credit to its creator. Honest caveats: naming is the one place Go is genuinely opinionated — the skill settles debates fast, which is great until your team's existing convention disagrees; the quick-reference table is the part you'll actually use. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Go project (the go toolchain) Install "Go Naming Conventions" for me. Go naming — packages, constructors, errors, booleans, MixedCaps always, the utils/helpers anti-pattern Repository: https://github.com/samber/cc-skills-golang/blob/main/skills/golang-naming/SKILL.md 1. Fetch the SKILL.md file for the samber-golang-naming 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-naming". 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.