Go projects need a clear structure to stay maintainable. This guide helps you choose the right layout for your project type. Whether you build a CLI tool, a library, a service, or a monorepo, you get clear rules for directories and modules.
Start by asking about the software architecture you want. The guide covers clean architecture, hexagonal, DDD, and flat structures. It never over-structures small projects. A simple script stays flat. A large service gets layers only when needed.
The guide also helps with dependency injection choices and 12-Factor App practices. You learn naming conventions for modules and packages. All code examples use real-world Go patterns.
Global
mkdir -p ~/.claude/skills/golang-project-layoutProject
mkdir -p .claude/skills/golang-project-layoutSource Repository
Grill With Docsmattpocock/skills
Stress-test your plan, refine your terms, and update docs instantly
Lark Doclarksuite/cli
Create read summarize edit translate and manage Lark cloud documents
To Prdmattpocock/skills
Generate a complete PRD from your conversation and codebase understanding
Github Actions Docsxixu-me/skills
Answers your GitHub Actions questions with exact official documentation links
Readme I18nxixu-me/skills
Localize your repo READMEs automatically with structure and selector intact
Domain Modelingmattpocock/skills
Define clear terms and record key decisions for a shared project language
Ubiquitous Languagemattpocock/skills
Build a shared glossary of terms from your conversations with clear definitions
Edit Articlemattpocock/skills
Polish your article drafts by improving clarity structure and flow