Run any Skill in Manus with one click

gemma4d-tui-operator-ux

Stars2

Forks0

UpdatedJune 30, 2026 at 05:27

Use when implementing or reviewing the Gemma4D Ratatui operator console, including page architecture, async event loops, terminal lifecycle, provider boundaries, config/benchmark UX, snapshots, and safety constraints.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jscott3201

jscott3201/Helios

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	gemma4d-tui-operator-ux
description	Use when implementing or reviewing the Gemma4D Ratatui operator console, including page architecture, async event loops, terminal lifecycle, provider boundaries, config/benchmark UX, snapshots, and safety constraints.

Gemma4D TUI Operator UX Skill

Use this skill when

Adding or changing crates/gemma4d-tui.
Designing Ratatui pages, widgets, keybindings, command palette, or navigation.
Connecting the TUI to mock/file/http runtime providers.
Adding TUI snapshot tests or terminal lifecycle tests.
Reviewing TUI integration with benchmarks, profiling, adapters, cache, MTP, or server controls.

Required reading

spec/13-tui-operator-ux.md
milestones/M05-tui-operator-console.md
references/tui-screen-map.md
references/tui-keybindings.md
references/configs/tui.toml

Hard rules

Do not call native MLX scheduler APIs from the TUI.
Keep TUI logic behind provider traits: mock, file, then HTTP/control provider.
Restore terminal state on normal exit, Ctrl-C, and controlled error paths.
Destructive actions require confirmation.
Avoid unbounded redraw loops; use bounded frame/tick rates.
Make snapshot renders deterministic.
TUI pages must degrade gracefully when the daemon is not running.
Remote adapter loading remains disabled unless explicitly trusted by local config.

Review checklist

Does the page show exact commands and raw output paths for benchmarks?
Can the operator reproduce a run from the TUI output?
Are config writes explicit and diffed before save?
Are cache/adapters/MTP controls gated by feature readiness?
Does every backend action have a visible pending/success/error state?
Are keybindings documented in Help and tested in the reducer?
Are terminal raw mode and alternate screen owned by one lifecycle object?

More from this repository

same repository

helios-mtp-acceptance-analysis

jscott3201/Helios

Diagnose Gemma 4 MTP acceptance and speculative decoding behavior in Helios using real-context prompts, trace records, and exactness gates.

2026-06-302

helios-native-mlx-ab-profiling

jscott3201/Helios

Profile and optimize Helios native MLX/C++ execution paths with A/B evidence, memory gates, and feature-flagged experimental kernels.

2026-06-302

helios-real-workload-ab

jscott3201/Helios

Build and run Helios real-context A/B benchmarks with deterministic workload manifests, correctness gates, and decision artifacts.

2026-06-302

gemma4d-16gb-mac-profiling

jscott3201/Helios

Use for tiny16 MacBook profiling: memory pressure, context-length limits, TTFT/decode metrics, cache effectiveness, MTP acceptance, and release-gate benchmark reports.

2026-06-302

gemma4d-dynamic-adapters

jscott3201/Helios

Use for dynamic LoRA/QLoRA adapter import, validation, loading, routing, adapter-aware KV cache keys, aLoRA planning, and adapter memory residency.

2026-06-302

gemma4d-kv-cache-offload

jscott3201/Helios

Use for Gemma4D KV cache, prefix cache, SSD cold tier, cache manifests, cache-key correctness, quantized/compressed KV experiments, and restore parity.

2026-06-302

name	gemma4d-tui-operator-ux
description	Use when implementing or reviewing the Gemma4D Ratatui operator console, including page architecture, async event loops, terminal lifecycle, provider boundaries, config/benchmark UX, snapshots, and safety constraints.

Gemma4D TUI Operator UX Skill

Use this skill when

Adding or changing crates/gemma4d-tui.
Designing Ratatui pages, widgets, keybindings, command palette, or navigation.
Connecting the TUI to mock/file/http runtime providers.
Adding TUI snapshot tests or terminal lifecycle tests.
Reviewing TUI integration with benchmarks, profiling, adapters, cache, MTP, or server controls.

Required reading

spec/13-tui-operator-ux.md
milestones/M05-tui-operator-console.md
references/tui-screen-map.md
references/tui-keybindings.md
references/configs/tui.toml

Hard rules

Do not call native MLX scheduler APIs from the TUI.
Keep TUI logic behind provider traits: mock, file, then HTTP/control provider.
Restore terminal state on normal exit, Ctrl-C, and controlled error paths.
Destructive actions require confirmation.
Avoid unbounded redraw loops; use bounded frame/tick rates.
Make snapshot renders deterministic.
TUI pages must degrade gracefully when the daemon is not running.
Remote adapter loading remains disabled unless explicitly trusted by local config.

Review checklist

Does the page show exact commands and raw output paths for benchmarks?
Can the operator reproduce a run from the TUI output?
Are config writes explicit and diffed before save?
Are cache/adapters/MTP controls gated by feature readiness?
Does every backend action have a visible pending/success/error state?
Are keybindings documented in Help and tested in the reducer?
Are terminal raw mode and alternate screen owned by one lifecycle object?