Golang Architect

This is a Go architecture consultant that actually starts with "what are we building" before throwing patterns at you. It walks through project classification (CLI tool vs CRUD API vs operator), matches complexity to architecture (no Clean Architecture for 200-line tools), then designs your module structure using Go idioms like internal packages and interface placement. The core philosophy is refreshingly blunt: every best practice is a tradeoff, and over-engineering is as bad as under-engineering. Includes concrete directory layouts for different project types and a solid take on dependency injection without frameworks. Use it when you're past hello world but before you've committed to a structure you'll regret.