What problem does it solve? Writing consistent, maintainable Go tests is hard when projects mix pure functions, filesystem operations, TUI state machines, and rendered output. This Skill provides a decision framework that maps each code target to the right Go testing pattern, eliminating guesswork and inconsistent test styles. ## Core Features & Use Cases - Pattern Selection via Decision Gates: Maps code targets (pure functions, file operations, TUI state, rendered output, external commands) to the correct test pattern such as table-driven tests, teatest, or golden files. - Bubbletea/TUI Testing Guidance: Distinguishes when to call Model.Update() directly versus when to use teatest.NewTestModel() for full interactive flows. - Golden File Discipline: Enforces deterministic golden files updated only through the repo's -update flag, with verification reruns. - Use Case: When adding coverage to a Go CLI with a Bubbletea interface, load this Skill to decide test patterns per component, write scenario-named cases, and run narrow package tests before broader suites. ## Quick Start Ask the AI to write tests for a Go function or Bubbletea model using the go-testing patterns, for example by requesting table-driven tests with coverage for a specific package.