Skip to content
Skills Library
Design & UX · Planning

rust-ui

/rust-ui

Choosing and building Rust user interfaces for Cybercore and Omarchy apps. Use when deciding CLI vs ratatui vs a native GUI, or when adding a TUI. Do not add a GUI toolkit the repo does not already use without approval.

Licence
MIT
Last repository change
11.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Choosing and building Rust user interfaces for Cybercore and Omarchy apps. Use when deciding CLI vs ratatui vs a native GUI, or when adding a TUI. Do not add a GUI toolkit the repo does not already use without approval.

Original author description

Choosing and building Rust user interfaces for Cybercore and Omarchy apps. Use when deciding CLI vs ratatui vs a native GUI, or when adding a TUI. Do not add a GUI toolkit the repo does not already use without approval.

How it works

  1. Scope
  2. Safety Rules (Non-Negotiable)
  3. Choice
  4. TUI Structure
  5. Tests
  6. Verification
Original SKILL.md headings · 52 lines, 339 words
SKILL.md preview
---
name: rust-ui
description: Choosing and building Rust user interfaces for Cybercore and Omarchy apps. Use when deciding CLI vs ratatui vs a native GUI, or when adding a TUI. Do not add a GUI toolkit the repo does not already use without approval.
metadata:
  version: "1"
---

# Rust UI

You are a Rust UI specialist focused on Cybercore and Omarchy applications.

## Scope
- Choosing CLI, TUI, or GUI
- `ratatui` application structure
- Keeping domain logic out of the widget layer
- Omarchy and terminal constraints

## Safety Rules (Non-Negotiable)

**STOP AND REPORT before any of these:**
- Adding GPUI, iced, egui, or another GUI crate the project does not already depend on
- A TUI that cannot be quit with a normal key (Esc or `q`) and Ctrl-C
- Drawing UI in a library crate that other binaries use as a pure library
- Grabbing the real terminal in tests without restoring it

## Choice

| Need | Use |
|---|---|
| Scripts, agents, pipes | CLI only (`rust-config-and-cli`) |
| Interactive terminal session | `ratatui` + `crossterm` |
| Native desktop | Only the toolkit already in the repo. If none, stop and ask |

- Default is CLI. A TUI is an extra surface, not a replacement: the same actions stay available as subcommands.
- Do not add a GUI “for later.”

## TUI Structure

- Domain state lives in the library. The TUI holds a view model and sends commands down.
- One event loop: tick, input, render. No ad-hoc threads drawing the screen.
- Restore the terminal on panic (a panic hook or `drop` guard) so the user’s shell is not left broken.
- Keys are documented in a help view.
- Respect terminal width. Do not assume 200 columns.
- On Omarchy, the TUI runs inside the user’s terminal. Do not take over the Hyprland session.

## Tests

- Test the view model and reducers without a tty.
- Snapshot full screen buffers only for a stable, narrow widget. Do not snapshot entire frames that include timestamps.

## Verification

- CLI path still works if you added a TUI
- Quit and Ctrl-C restore the terminal
- No new GUI crate without approval
- Domain tests do not open a terminal
- Help lists the keys you added

Versions

The database has no other skills named rust-ui.

Database snapshot: 13.11.2026 · package version 6af329950df5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ratatui-themes
    Use when building or styling a Rust terminal UI (TUI) application with ratatui and you need to apply a consistent color theme, switch between themes at runtime, or use semantic status colors (error, warning, success). Trigger terms: ratatui theme, TUI color scheme, Dracula…
  • 96tui-tests
    Use when adding or modifying tests for one of GitButler's Ratatui TUIs
  • 100tui-design
    Design, build, refactor, or review terminal interfaces—full-screen TUIs, interactive prompts, and command-line tools. Use for terminal-app layout and UX, CLI behavior, ncurses-style tools, dashboards, REPLs, fzf-like pickers, and libraries such as Bubble Tea, Ratatui, Textual,…
  • 100tui-design
    Use this skill when designing terminal user interfaces, creating TUI layouts, choosing TUI color schemes, implementing keyboard navigation, building terminal dashboards, or working with any TUI framework. Activates on mentions of TUI design, terminal UI, Ratatui layout, Ink…
  • 90tui-design
    Decide whether a full-screen TUI is warranted (vs a scriptable CLI), pick the framework (Ink / Bubble Tea / Textual / ratatui), and design the render-loop + non-TTY fallback. Use for interactive terminal dashboards, pickers, and wizards.
  • 100rust-app-architecture
    Rust application layout for Cybercore apps. Use when structuring a binary, splitting a library from main, layering CLI/config/domain, or deciding crate boundaries. Publishing and MSRV stay in rust-development.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.