build-tui-view

Design modular TUI views for the Hatchet CLI with bubbletea and lipgloss.

4|5|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/sacenox/Zoea-Nova --skill build-tui-view
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-tui-view
Source: https://github.com/sacenox/Zoea-Nova/tree/main/.opencode/skills/build-tui-view
Command: npx skills add https://github.com/sacenox/Zoea-Nova --skill build-tui-view

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides comprehensive guidance for designing and maintaining Terminal User Interface (TUI) views in the Hatchet CLI using the Bubble Tea and Lipgloss toolchain. It helps teams create modular, reusable views that align with the Hatchet design system and frontend references.

Core Features & Use Cases

  • Frontend reference discovery: Locate corresponding frontend views to understand structure, columns, and API calls before implementing a TUI view.
  • Reusable components: Use standardized header, instructions, and footer components to ensure a consistent look and feel across all views.
  • Primary and detail views: Implement primary list views and detail views with matched columns for a cohesive user experience.
  • Modal and form support: Integrate modals, filters, and forms while preserving the same layout and theming.

Quick Start

  1. Open the Hatchet CLI project in your Go workspace.
  2. Ensure you have Go tooling and dependencies installed.
  3. Implement a new view under cmd/hatchet-cli/cli/tui/ and wire it into the root TUI model, using the provided reusable components.

Frequently Asked Questions about build-tui-view

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

FAQPage Schema
How do I build TUI views with bubbletea and lipgloss in Go?

Building TUI views with bubbletea and lipgloss involves creating modular view files, wiring them into the root TUI model, and using standardized header, footer, and instruction components to maintain a consistent layout and design system.

What is the best way to structure terminal user interface modals and detail views?

The best way to structure terminal user interface modals and detail views is by using a primary and detail view pattern with matched columns, integrating modals and forms while preserving the same responsive layout and theming across the application.

Do I need the Hatchet CLI codebase to implement terminal user interfaces?

Yes, you need the Hatchet CLI codebase along with Go tooling, bubbletea, lipgloss, and the project's style guide to implement and test terminal user interface views that align with the existing design system.

How does frontend reference discovery help when creating Bubble Tea views?

Frontend reference discovery helps when creating Bubble Tea views by allowing you to locate corresponding frontend views to understand existing structures, columns, and API calls before implementing the terminal equivalent, ensuring feature parity.

Can I use reusable components for consistent layouts across multiple TUI screens?

Yes, you can use reusable components like standardized headers, instructions, and footers to ensure a consistent look and feel across multiple TUI screens, applying them uniformly to primary list views and detail views alike.