go-project-layout

The standard Go project layout uses cmd for entrypoints, internal for private packages, and pkg for public libraries. This structure reduces setup errors by cleanly separating multi-binary applications from shared internal logic and versionable public APIs.

Organize Go modules by initializing with go mod init and maintaining dependency hygiene using tidy, verify, and graph commands. This establishes a clean go.mod file and ensures consistent dependency management across the project lifecycle.

Use the internal directory for private packages restricted to your module, and pkg for public libraries safe for external import. This Go project layout convention keeps public APIs clean and versionable while hiding implementation details.

Set up a Makefile with standard build, run, cross-compilation, and testing commands to streamline Go project workflows. This provides a unified entry point for compiling target binaries across architectures and executing test suites consistently.

Yes, this Go project layout supports modern Go version features and module workflows. It provides guidance on go.mod version management and applies current conventions for initializing repositories and organizing dependencies.