Apply strict internal-first Go project layout practices from golang-standards/project-layout.
Use this skill when creating or refactoring Go application repositories.
cmd/<app>/main.go thin.internal/....pkg/... only when intentionally exposing reusable public APIs.src/ directories.internal/<domain>.pkg/<name>.main.go doing orchestration logic?
internal/app and keep main minimal.internal/app for startup flow and wiring.internal/config for load/save/precedence.internal/gitlab for GitLab client abstraction.internal/project for git remote parsing and context detection.internal/tui for Bubble Tea models and UI logic.internal/logging for debug log initialization.just fmtjust testjust buildpkg package added unless justified.cmd/lazygitlab/main.go only handles flags + app startup.