tui-builder

Build and debug Syllago CLI TUI components with golden rules and message contracts.

15|1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/OpenScribbler/syllago --skill tui-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tui-builder
Source: https://github.com/OpenScribbler/syllago/tree/main/.claude/skills/tui-builder
Command: npx skills add https://github.com/OpenScribbler/syllago --skill tui-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The tui-builder Skill simplifies the debugging and development process of your Syllago CLI text user interface (TUI) components. It offers a golden rules checklist, component message contracts, and insights into common pitfalls to speed up development and maintenance.

Core Features & Use Cases

  • Golden Rules Checklist: Verify interactive element parity, layout constraints, and state changes for robust TUI components.
  • Component Message Contracts: Understand the messaging system for different components to build seamless interactivity.
  • Gotchas: Avoid common traps with detailed notes on known issues and best practices.
  • Use Case: When building the Syllago CLI TUI, this Skill can help developers quickly resolve layout bugs and implement new features without unexpected side effects.

Quick Start

Invoke the tui-builder Skill within the cli/internal/tui/ directory when working on the TUI of Syllago CLI.

Frequently Asked Questions about tui-builder

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

FAQPage Schema
How do I debug text user interface layout constraints in a CLI application?

You can resolve text user interface layout bugs by applying a golden rules checklist that verifies interactive element parity, layout constraints, and state changes for robust TUI components.

How does component message contracting work for CLI TUI interactivity?

Component message contracts define the messaging system between TUI components, establishing communication protocols to build seamless interactive text user interface element interactions within the CLI.

What are common gotchas when building a text user interface for a CLI?

Common TUI gotchas include interactive element parity mismatches, incorrect layout constraint handling, and state synchronization errors that disrupt text user interface component behavior and layout.

How do I maintain state consistency across TUI components in a CLI developer tool?

Maintain TUI state consistency by enforcing golden rules for state checks and utilizing component message contracts to synchronize interactive element states across the text user interface.