opentui-design

Design CLI screens and components for OpenTUI applications.

8|3|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/akiojin/skills --skill opentui-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opentui-design
Source: https://github.com/akiojin/skills/tree/main/cli-opentui/skills/opentui-design
Command: npx skills add https://github.com/akiojin/skills --skill opentui-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designing and implementing CLI interfaces with OpenTUI and SolidJS can be complex, requiring cohesive patterns for screens, navigation, input handling, and mouse interactions.

Core Features & Use Cases

  • Design and implement CLI screens and components using OpenTUI and SolidJS.
  • Debug input handling, navigation, and mouse event handling in terminal apps.
  • Reference-guided patterns and practical examples to accelerate UI engineering.

Quick Start

Create a new screen using OpenTUI components and test navigation between screens using keyboard input.

Frequently Asked Questions about opentui-design

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

FAQPage Schema
How do I design CLI screens with OpenTUI and SolidJS?

To design CLI screens with OpenTUI and SolidJS, use reference-guided component patterns and YAML frontmatter to define screen structures, enabling cohesive terminal interface architecture and navigation.

What patterns are recommended for terminal input handling and mouse events in SolidJS CLI apps?

Terminal input handling and mouse events in SolidJS CLI apps require frontmatter-driven operational guidance and reference components to debug and implement cohesive interaction patterns across terminal environments.

How do I implement screen navigation for terminal applications using OpenTUI?

Implementing screen navigation for OpenTUI terminal applications involves using component architecture references and keyboard input testing to transition between CLI screens built with SolidJS.

Does OpenTUI require specific dependencies or directory structures for SolidJS component architecture?

OpenTUI does not require external dependencies, but expects optional references, scripts, and assets directories alongside YAML frontmatter to structure SolidJS component architecture and provide operational guidance.

What is the best way to optimize CLI performance across different terminal environments?

Optimizing CLI performance across terminal environments requires using OpenTUI's reference-guided patterns to refine component architecture, debug input handling, and streamline SolidJS screen rendering.