Conciseness

The body is mostly lean — patterns, a decision tree, and code with little concept re-explanation — but Pattern 4 and Example 3 overlap on scroll handling, and inline placeholder comments like '// Add new state here' could be trimmed.

Actionability

It provides copy-paste-ready Go code for each pattern, a concrete decision tree, and real build/test commands; the examples cover the common cases (screens, navigation, scrolling, custom messages).

Workflow Clarity

The decision tree sequences the new-screen workflow clearly (constant → state → handler → view → title) and the Commands section supplies build/test checkpoints, but there is no explicit validate-then-fix feedback loop, so it falls short of anchor 5.

Progressive Disclosure

Sections are well-organized (When to Use, Critical Patterns, Decision Tree, Code Examples, Commands, Resources) and the Resources block points one level deep to real source files; the single-file body is fairly long but appropriately sectioned, leaving minor organization gaps versus a fully split structure.

Specificity

The phrase 'Bubbletea TUI patterns for Gentleman.Dots installer' names the domain but offers no concrete actions — 'patterns' is generic; the real actions (add screens, handle input, create components) appear only in the trigger clause, not as stated capabilities.

Completeness

Both 'what' (Bubbletea TUI patterns) and 'when' (explicit 'Trigger:' clause) are present; the 'what' is somewhat vague ('patterns'), so it stops short of the fully concrete anchor 5.

Trigger Term Quality

'editing Go files in installer/internal/tui/', 'working on TUI screens', and 'adding new UI features' are natural phrases a user would say, though common synonyms like 'terminal UI', 'menu', or 'navigation' are absent.

Distinctiveness Conflict Risk

The niche is tightly scoped to one project's installer TUI with a path-specific trigger, giving it a clear, distinct trigger with minimal overlap risk.