← ClaudeAtlas

tui-designlisted

Design, build, and review terminal user interfaces — pane layout, keybinding grammar, color semantics, chart rendering, redraw discipline, and resize handling. Use this whenever the user is working on anything that draws a full-screen interface in a terminal, including work with Ratatui, Bubble Tea, Lip Gloss, Textual, Rich, tview/tcell, blessed, or ncurses. Trigger it even when the request sounds purely functional or cosmetic — "my dashboard looks off", "add a panel to this", "the bars are misaligned", "make this chart look better", "the layout breaks when I resize", "why does my TUI only fill half the window" — because the overwhelming majority of TUI defects are layout, redraw, and alignment bugs rather than logic bugs. Also use it when the user shares a screenshot of a terminal app and asks what is wrong with it, or asks how well-regarded TUIs (btop, lazygit, k9s, yazi, zellij) achieve their look.
SeanoChang/seanock · ★ 0 · Web & Frontend · score 70
Install: claude install-skill SeanoChang/seanock
# TUI design ## The core constraint A TUI draws into a fixed grid of monospace cells. A maximized terminal at a typical font size is roughly 180 × 55 — about 10,000 cells, against millions of pixels in a GUI. Two properties of that grid generate almost every rule that follows: - **Cells are scarce.** Anything permanently on screen has to earn its rows against the content it displaces. - **Cells are discrete.** Alignment is integer arithmetic, so an off-by-one is not a subtle rendering artifact — it is visibly broken. Good TUIs are not the ones with the most color. They are the ones that spend a small cell budget deliberately. Work through the laws below when building; use the review pass at the end when critiquing. Read `references/layout.md` before deciding pane geometry or column widths, `references/rendering.md` before writing drawing code, and `references/frameworks.md` once the framework is known. ## Law 1 — Draw the frame before the content Bordered, titled panes are not decoration. They are the reference edges that make alignment readable. A value two cells out of position inside a border reads as a bug instantly; the same value floating in open space reads as intentional, so misalignment hides and accumulates. Draw the frame first, then fill it. When a layout "looks sloppy" and nobody can say why, missing frames is the usual cause. Corollary: if a region has no content, it should not be an unbordered void. Either shrink the layout, merge the region into its n