Go Style Core

This is your baseline for Go formatting and readability. It covers gofmt defaults, reducing nesting through early returns, when naked returns are acceptable (short functions only), and why opening braces stay on the same line due to semicolon insertion. The priority order matters here: clarity beats simplicity beats concision, which is a useful tiebreaker when you're staring at two valid approaches. It explicitly punts on naming, error handling, and testing to other skills, so think of this as the fallback when you have a style question that doesn't fit elsewhere. The examples are practical, especially the nested loop refactoring that shows how continue keeps code flat.