What problem does it solve?
Neko's terminal UI (TUI) changes cannot be reliably verified by eye, leading to missed rendering bugs like broken glyphs, incorrect colors, layout misalignment, or missing characters that only appear in real terminal environments.
Core Features & Use Cases
- Deterministic component testing: Uses the ink-testing-library devDependency to test UI component layout, glyph codepoints, crash behavior, and truncation logic without launching a real terminal.
- Live screenshot verification: Launches Neko in a real console, captures screenshots, and uses vision tools to check real-world font rendering, color accuracy, and full TUI layout as end users see it.
- Use case: Use this skill when modifying Neko's transcript, markdown, approval, or diff rendering, or auditing how the TUI displays on Windows or other cross-platform environments.
Quick Start
Use the tui-self-test skill to verify that recent changes to Neko's TUI render correctly with expected layout, colors, and glyphs before merging code.