tui-state-validation

Compare TUI output against session state to document mismatches.

5|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/lhy0718/AutoLabOS --skill tui-state-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tui-state-validation
Source: https://github.com/lhy0718/AutoLabOS/tree/main/.codex/skills/tui-state-validation
Command: npx skills add https://github.com/lhy0718/AutoLabOS --skill tui-state-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers reproduce and analyze concrete AutoLabOS TUI/web symptoms by validating the actual user-visible behavior against expected state across fresh sessions, resumed sessions, and persisted artifacts.

Core Features & Use Cases

  • Structured validation records to document TUI symptoms and results.
  • Cross-session comparison to surface stale or divergent UI states.
  • Guided evidence gathering and regression-oriented triage for UI issues.

Quick Start

Ask the AI to perform a live TUI validation by comparing a fresh session against a resumed session and reporting discrepancies in a structured format.

Frequently Asked Questions about tui-state-validation

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

FAQPage Schema
How do I validate TUI output against session state in AutoLabOS?

To validate TUI output against session state, compare the actual user-visible behavior with the underlying state across fresh, resumed, and persisted sessions to identify mismatches and triage UI issues using a structured validation record.

What is structured live validation for TUI symptoms?

Structured live validation for TUI symptoms is a process of documenting mismatches between actual output and expected state, enforcing a 12-section record that includes reproduction steps, observed versus expected behavior, and a recommended next action.

How do I triage UI issues when a resumed session shows stale TUI states?

To triage UI issues with stale TUI states, perform a cross-session comparison by validating a fresh session against a resumed session and persisted artifacts to surface divergent UI states for regression-oriented bug triage.

Does this validation approach work with persisted artifacts and resumed sessions?

Yes, this validation approach works with persisted artifacts and resumed sessions by applying structured evidence gathering to compare actual user-visible behavior against expected state across all three session types.

What's the best way to document TUI bugs for regression testing?

The best way to document TUI bugs for regression testing is to enforce a structured validation record with 12 sections, capturing reproduction steps, observed versus expected behavior, and recommended next actions to guide evidence gathering.