Go Project Layout
cmd/internal/pkg conventions, module naming, go.work workspaces — right-size structure to the problem, ask the developer first
- What
- cmd/internal/pkg conventions, module naming, go.work workspaces — right-size structure to the problem, ask the developer first
- Cost
- Free
- Needs
- a Go project to organize, or a new one to start (the go toolchain)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a Go project-structure skill with one hard rule: ask first. When starting a new project it asks the developer for their architecture preference and DI approach before creating anything — because a 100-line CLI tool does not need layers of abstraction, and getting either answer wrong early cascades into every file created afterward. It covers cmd/internal/pkg directory conventions, module and package naming, go.work workspaces, monorepos with multiple packages, multi-binary CLIs, and the essential configuration files. Distinct from the already-published samber skills — this is the scaffolding one, and it explicitly defers detailed architecture guides to golang-design-patterns and code moves without layout changes to golang-refactoring. By @samber, listed here with credit to its creator. Honest caveats: it will interrogate you before scaffolding — if you wanted a silent template, this will feel slow; right-sizing is a judgment the skill shares with you, not one it makes for you. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Go project to organize, or a new one to start (the go toolchain) Install "Go Project Layout" for me. cmd/internal/pkg conventions, module naming, go.work workspaces — right-size structure to the problem, ask the developer first Repository: https://github.com/samber/cc-skills-golang/blob/main/skills/golang-project-layout/SKILL.md 1. Fetch the SKILL.md file for the samber-golang-project-layout 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-project-layout". 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.