Golang Project Layout

This is a project scaffolding guide that stops you from over-engineering. It asks what architecture you actually need before suggesting structure, which is refreshing. The quick-start table breaks down when to use CLI versus library versus service layouts, and it's opinionated about keeping main packages minimal in cmd/ while business logic lives in internal/. Includes practical templates for Makefile and .gitignore, plus strong opinions on module naming (lowercase, hyphens, match your repo URL). The initialization checklist reminds you to ask about DI preferences and right-size your structure before creating directories. Works well as a first step when spinning up any Go project, especially if you tend to cargo-cult complex layouts onto simple tools.