Gentleman-Programming/gentle-shell / skills/tui-design
gentle-ai-tui-design
VerifiedTrigger: terminal UI design, TUI redesign, Gentle Shell look, IDE in a terminal, sidebar/status bar polish, critique TUI. Refine terminal UIs with visual proof.
| File | Kind | Size |
|---|---|---|
| NOTICE.md | markdown | 403 B |
| SKILL.md | skill md | 3.3 KB |
| references/commands.md | markdown | 3.1 KB |
| references/critique.md | markdown | 2.1 KB |
| references/design-doc.md | markdown | 1.4 KB |
| references/terminal-craft.md | markdown | 3.9 KB |
| references/visual-loop.md | markdown | 1.8 KB |
SKILL.md
View on GitHub---
name: gentle-ai-tui-design
description: "Trigger: terminal UI design, TUI redesign, Gentle Shell look, IDE in a terminal, sidebar/status bar polish, critique TUI. Refine terminal UIs with visual proof."
license: Apache-2.0
metadata:
author: gentleman-programming
version: "1.0"
---
## Activation Contract
Use for designing, reviewing or refining a terminal interface (panels, rails, status bars, cards, prompts), especially Gentle Shell. The target feel is an IDE inside a terminal: dense, calm, developer-first, never a costume of retro TUI chrome. Not for web pages (use `gentle-design`).
## Hard Rules
- Never judge a terminal UI from code or memory: capture it (`references/visual-loop.md`) and look at the PNG before and after every change.
- Read `references/terminal-craft.md` before any UI edit; it is the floor, not a suggestion.
- Operate mode: familiarity beats expression. Use IDE vocabulary (panes, tree, tabs, status bar, command palette); the brand lives in palette, density and one signature move.
- Every row costs. Hierarchy comes from color role, weight and alignment, never from blank rows or nested boxes.
- Say each fact once per screen. Data shown in the header never repeats in a panel.
- One command, one target. Refinement preserves the system; redesign replaces it. Never polish a look being thrown away.
- Rendering stays cheap: no I/O or recomputation in render paths, cache keyed on everything that changes output (style, width, theme).
- Mockups (via `gentle-design`) must be terminal-expressible: monospace cell grid in `ch` units, only fg/bg colors, bold/dim/italic/underline/strikethrough, box-drawing and glyphs.
## Decision Gates
| Ask | Command | Load |
|-----|---------|------|
| No product/design context yet | `document` | `references/design-doc.md` |
| New surface or redesign | `shape`, then mockups, then implement | `references/commands.md` |
| "How does it look / what is wrong" | `critique` | `references/critique.md` |
| Too busy, wasted space, redundant | `distill` / `layout` / `quieter` | `references/commands.md` |
| Flat, no hierarchy, unreadable | `typeset` / `colorize` / `bolder` | `references/commands.md` |
| Edge cases, narrow terminals, long text | `harden` / `adapt` | `references/commands.md` |
| Final pass before commit | `polish` | `references/commands.md` |
## Execution Steps
1. Load `DESIGN.md` context if the project has one; otherwise propose `document` first.
2. Capture the current state with the visual loop at the shipped sizes (wide 180x50, breakpoint 140, narrow 80x24).
3. Run the chosen command against one named target; write findings before changing code.
4. Change, re-capture, compare against the previous PNG and the brief; iterate at most 3 rounds, then report.
5. End every refine command with `polish` checks and the repository's focused tests (render counts, overflow).
## Output Contract
Return: target, command run, before/after PNG paths, findings fixed with P0-P3 tags, findings left open, and checks run.
## References
- `references/terminal-craft.md`: floor rules and terminal anti-patterns.
- `references/commands.md`: command playbooks adapted to terminals.
- `references/critique.md`: scored critique and severity rubric.
- `references/design-doc.md`: DESIGN.md shape for a terminal product.
- `references/visual-loop.md`: screenshot harness and comparison loop.
- `NOTICE.md`: attribution.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |