ls-litetui

Generate Textual TUI and Click CLI wrappers for existing software packages.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/ahostbr/liteharness --skill ls-litetui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-litetui
Source: https://github.com/ahostbr/liteharness/tree/main/liteharness/catalog/skills/ls-litetui
Command: npx skills add https://github.com/ahostbr/liteharness --skill ls-litetui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn any existing software into a polished terminal experience—an interactive Textual TUI plus an automation-ready Click CLI—so you can browse, monitor, and operate the tool without building everything from scratch.

Core Features & Use Cases

  • Dual-output app generation: Produces both a Textual TUI for interactive workflows and a Click CLI for scripted usage from the same core backend.
  • Professional terminal UX: Provides tabbed layout, sidebar status/metadata, streaming logs, data tables, and a command palette, plus starter themes (dark, light, high_contrast, brand).
  • Shared backend core: Centralizes binary discovery/invocation and session state so the TUI and CLI stay consistent.
  • Use case: When you need to wrap a complex tool (like a media processor, batch job runner, or internal binary) with a user-friendly interface and repeatable automation commands.

Quick Start

Ask LiteHarness to generate a LiteTUI wrapper for a tool by running: "Generate a Textual TUI and Click CLI wrapper for ffmpeg into ./output with the description 'FFmpeg video processing TUI'."

Frequently Asked Questions about ls-litetui

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

FAQPage Schema
How do I generate a Textual TUI and Click CLI wrapper for an existing binary?

You can generate a Textual TUI and Click CLI wrapper by providing a software package description, which produces a dual-output application with a shared backend core for consistent behavior across interactive and scripted usage.

What is the best way to build a terminal UI with tabs and a persistent sidebar for a command line tool?

Generating a themed Textual TUI wrapper organizes tool features into a tabbed layout with a persistent status sidebar, streaming logs, and data tables, providing a professional terminal user experience for command line tools.

Can I keep behavior consistent between an interactive TUI and automated CLI commands?

Yes, keeping behavior consistent between an interactive TUI and automated CLI commands is achieved by centralizing binary discovery and session state in a shared backend core, ensuring both interfaces operate identically.

Does the generated Click CLI support scripted automation for complex tools like media processors?

Yes, the generated Click CLI supports scripted automation for complex tools by exposing command line entry points that map directly to the shared backend core, enabling repeatable automated workflows for media processors or batch runners.

What terminal UI themes are available when generating a Textual wrapper?

When generating a Textual wrapper, available terminal UI themes include dark, light, high_contrast, and brand options, allowing customization of the terminal interface to match visual preferences and accessibility requirements.

When should I not use a dual TUI and CLI wrapper approach for my application?

You should not use a dual TUI and CLI wrapper approach for simple scripts without complex features, as the overhead of a shared session core, tabbed layout, and dual entry points is designed for tools requiring organized interactive operation and automation.