coding-guidance-golisted

# Go Coding Guidance Portable Go implementation, refactoring, testing, optimization, and review guidance. ## Adjacent Skills Compose with: - **Workflow:** `thinking` for ambiguous decision framing, `recursive-thinking` for stress-testing, `security` for threat modeling - **Domain overlays:** `backend-guidance` for server-side code, `backend-systems-guidance` for deeper backend architecture/reliability/trust boundaries, `project-core-dev` for repo-specific completion discovery and reporting when needed, and `project-config-and-tests` for config contracts and deterministic tests at config or path seams - **Testing:** `go-testing-with-testify` when the main artifact is testify-based Go test code, test review, or Go test flake triage - **TUI specialization:** `coding-guidance-go-tui` when Bubble Tea state, Bubbles components, Lip Gloss layout, or an interactive terminal screen is the main concern ## When Not to Lean on This Skill - non-Go work - interactive Bubble Tea or Charmbracelet terminal screens; use `coding-guidance-go-tui` - pure test strategy without implementation code or concrete Go test code; use `tester-mindset` - testify-specific assertion, mock, suite, or flake work; use `go-testing-with-testify` - security as the primary job; use `security` and compose this skill only for Go-specific implementation details - repo-specific framework rules that should live in local docs, generated-code policy, linter config, or domain overlays ##