commit
無料Create a git commit with conventional commit format. Injects current git state automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Design engineering principles for making TUI interfaces feel polished. Use when building Textual widgets, reviewing TUI code, implementing transitions, focus states, alignment, spacing, or any visual detail work. Triggers on TUI polish, design details, "make it feel better", "feels off", layout alignment, color consistency, responsive sizing.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Great TUIs rarely come from a single thing. It's a collection of small details that compound into a professional experience. Apply these principles when building or reviewing Textual/terminal UI code.
| Category | When to Use |
|---|---|
| Layout | Alignment, spacing, responsive sizing, content regions |
| Color | Palette consistency, contrast, semantic color usage |
| Interaction | Focus management, key hints, modal flow, feedback |
| Typography | Text truncation, wrapping, Unicode, monospace alignment |
Use a spacing scale (1, 2, 4 cells). Mismatched padding between related
elements is the most common thing that makes TUIs feel off. Textual's
padding and margin CSS properties use cell units.
When geometric centering looks wrong in a terminal, adjust optically. Asymmetric Unicode characters (arrows, bullets) and mixed-width content need manual nudging. A centered title above left-aligned content often needs 1 cell of left padding removed.
Use 3-4 color tiers consistently:
Never use bright colors for passive elements. Reserve saturation for things the user needs to notice.
The focused widget must be visually distinct at a glance. Use border color changes, not just cursor position. A user glancing at the screen should instantly know where input will go.
TUI must work at 80x24 minimum. Use fr units and max-width/
min-width in Textual CSS to adapt. Content that overflows should
truncate with ellipsis, never wrap into garbage.
Every keypress that does something should produce visible feedback within one frame. If an operation takes time, show a spinner or status message immediately — don't let the user wonder if their input was received.
Textual supports CSS transitions. Use short durations (150-300ms) for background color and opacity changes on hover/focus. Never animate layout properties (width, height) — terminal reflow is not smooth.
Pick one border style and stick with it. tall for primary
containers, round for cards/modals, heavy for emphasis. Mixing
ascii, tall, round, and heavy in one screen looks
incoherent.
Always show available keys in a footer or status bar. Format as
key action pairs separated by thin spaces. Dim the keys relative
to the actions. Update hints contextually as focus moves.
Terminal space is precious. Default to dense layouts. Use blank lines only to separate logical groups, never for decoration. Single-line headers over multi-line. Abbreviate labels when the full form is obvious from context.
| Mistake | Fix |
|---|---|
| Inconsistent padding between similar widgets | Use a spacing constant |
| Bright colors on passive/decorative elements | Reserve bright for actions and focus |
| No visible focus indicator | Add border color or background change on focus |
| Content overflows and wraps badly | Set overflow: hidden with text-overflow: ellipsis |
| No key hints visible | Add contextual footer with available actions |
| Large empty regions at default size | Use fr units to distribute space |
| Mixed border styles in one view | Standardize on one style per element tier |
| No feedback on async operations | Show spinner/status immediately on action |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Create a git commit with conventional commit format. Injects current git state automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Explain system behavior, request flows, architecture, or implementation logic as short 4chan-style greentext lines. Use when the user asks for a step-by-step explanation, says "explain the logic", asks for "greentext", or wants terse sequential reasoning with each line starting with `>`.
日本語の概要は準備中です。原文の説明を表示しています。
Create a GitHub issue using the wingman issue templates (bug, feature). Injects branch and commit context automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Create a pull request using the wingman PR template. Injects git state, commit history, and diff stats automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Review PR comments from GitHub. Fetches inline review comments and issue comments, classifies by blocking vs non-blocking, and summarizes actionable items.
日本語の概要は準備中です。原文の説明を表示しています。
Create a changelog-style promotion PR between two branches. Use for release promotions or branch-to-branch merges with a structured changelog.
日本語の概要は準備中です。原文の説明を表示しています。