tui-self-test

Verify Neko TUI rendering via component tests and live screenshots.

4|1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/meiiie/neko-core --skill tui-self-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tui-self-test
Source: https://github.com/meiiie/neko-core/tree/main/skills/tui-self-test
Command: npx skills add https://github.com/meiiie/neko-core --skill tui-self-test

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about tui-self-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify terminal UI rendering changes without manual eyeballing?

To verify terminal UI rendering without manual eyeballing, apply structured render verification workflows combining deterministic component testing and live screenshot analysis. This catches broken glyphs, incorrect colors, and layout misalignment before merging code.

What is the best way to test terminal UI glyph codepoints and truncation logic?

The best way to test terminal UI glyph codepoints and truncation logic is using the ink-testing-library devDependency. It tests UI component layout, crash behavior, and truncation deterministically without launching a real terminal environment.

How do I check terminal UI color accuracy and font rendering as end users see it?

To check terminal UI color accuracy and font rendering as end users see it, launch the application in a real console and capture live screenshots. Vision tools then analyze the screenshots to verify real-world full TUI layout and rendering fidelity.

Can I use screenshot testing to audit cross-platform TUI compatibility on Windows?

Yes, you can use screenshot testing to audit cross-platform TUI compatibility on Windows. Live screenshot verification launches the application in a real console to capture and validate how the TUI displays across different operating system environments.

When do I need render verification for transcript, markdown, approval, and diff rendering?

You need render verification for transcript, markdown, approval, and diff rendering when modifying these specific TUI components. It ensures pixel-level layout validation, glyph compatibility checks, and color accuracy verification before code changes are merged.