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 |
references/design-doc.md
View on GitHub# DESIGN.md for a terminal product
Keep it at the project root or `design/DESIGN.md`. Describe first, then give the exact value in parentheses, and say where and why each token is used. Add 1-3 named rules per section (`**The One Fact Rule.** ...`). Never overwrite an existing file silently; propose a diff.
## Frontmatter tokens
```yaml
colors: # roles mapped to theme color keys, not hex literals
canvas: ...
rail: ...
text: { primary: ..., secondary: ..., muted: ... }
accent: ...
state: { success: ..., warning: ..., error: ..., info: ... }
border: ...
roles: # type roles as attribute combinations
title: bold + accent
value: normal
label: dim
meta: dim italic
glyphs: # one family, by meaning
done: ✓
running: ●
pending: ○
expanded: ▾
collapsed: ▸
spacing: # in cells and rows
inset: 1 col
group-gap: 1 row
section-gap: 1 row
widths:
rail: 50
breakpoint: 140
```
## Sections (fixed order)
1. Overview: product, users, and a one-line north star metaphor (for example "an IDE inside a terminal").
2. Colors: roles and where each appears.
3. Type roles: hierarchy and where each role applies.
4. Layout: panes, rail, status bar, widths and breakpoints.
5. Surfaces: canvas vs rail vs elevated; how regions separate.
6. Glyphs: the family and meaning table.
7. Components: each panel/bar/card with its states.
8. Do's and Don'ts: named rules and refusals specific to this product.
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 |