When to Use

Use this skill when:

• Adding screens or menu options
• Changing key bindings or navigation flows
• Updating list rendering and detail views

UX Rules

1. Keyboard behavior must be consistent across screens.
2. Empty/loading/error states must be explicit and readable.
3. Long lists require clear truncation/scroll cues.
4. Back navigation should preserve context predictably.

Test Rules

• Add update tests for new key transitions.
• Add view tests for new rendering branches.
• Add model tests for async commands/data-loading paths.

No TUI behavior change ships without deterministic tests.