1# TUIs
 2
 3This file captures Amolith-specific TUI setup choices only. Load `golang-tui`
 4after this file for Bubble Tea, Lip Gloss, Bubbles, Elm Architecture, layout,
 5keymap, terminal-compatibility, testing, and performance details.
 6
 7TUIs are still command-line binaries. Read `cli.md` alongside this file for
 8Cobra/Fang setup, command ergonomics, completions, and version-policy guidance.
 9
10## Amolith-specific deltas
11
12- Use the Charm v2 stack through `golang-tui` unless the project has already
13  made a different good choice.
14- Do not copy Taskfile examples from `golang-tui`; translate useful commands
15  into `mise.toml` and keep the baseline tasks from `mise.md`.
16- Keep the CLI surface consistent with `cli.md`: stdlib for tiny tools,
17  Cobra/Fang for user-facing commands, and one project-owned version policy when
18  exact versions matter.
19- Use the regular race-enabled Go test task from `mise.md`. Add snapshot/golden
20  update tasks only when the project actually has snapshot tests.
21- Terminal apps should use the same pure-Go static release-build shape as CLIs
22  when their dependencies allow it. Drop static-only flags for terminal
23  integrations that require CGO or native libraries.
24
25If `golang-tui` and this skill conflict, keep `golang-tui` for library/API
26details and keep this skill for Amolith-specific tooling, task-runner,
27packaging, CLI, and release-build policy.