tui-design
Skill293 starsChanged 11 days agoMITView on GitHub
TUI Design System for Egregore slash commands. Use when designing or modifying any command's terminal output to ensure visual consistency. Triggers on: TUI, terminal output, box drawing, command output formatting, sigils, section markers. Do NOT use for browser rendering (use dark-mode) or external prose (use egregore-voice).
12 other projects use a version of this.
Adopted by
Most recently taken up by
- AlbertoVasquezR/panaltheir own version, first seen Nov 16, 2026
- marcus/marcus-skillstheir own version, first seen Nov 16, 2026
- pageton/tui-design-skilltheir own version, first seen Nov 14, 2026
- Praveensenpai/karakuritheir own version, first seen Nov 1, 2026
- castle-x/skills-xtheir own version, first seen Nov 1, 2026
- hyperb1iss/hyperskillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use unslop.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
photon-groveSkillunslop
Detects and rewrites generic, overly polished, or AI-sounding prose while preserving meaning. Use when the user asks to "unslop", humanize, de-AI, tighten, or review whether writing sounds generated.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- pedronauck/skills★ 655same name
- hyperb1iss/hyperskills★ 36same name
- pageton/tui-design-skill★ 31same name
- castle-x/skills-x★ 18same name
- diegomarino/tui-design★ 18same name
- marcus/marcus-skills★ 4same name
- FelipeAngeli/skills★ 2same name
- lrstanley/skills★ 2same name
- aewing/skills★ 1same name
- AlbertoVasquezR/panal★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- notion-connectSkill
- onboardingSkill
- prSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 3 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Not this: browser rendering → dark-mode · external prose → egregore-voice
- Very specific: line 29
Read org name from jq -r '.org_name' egregore.json.
- Very specific: line 75
Header separator: always use ├───┤ between header row and content.
- Very specific: line 77
Section dividers: use ├───┤ between logical groups.
- Distinctive: line 81
All commands use full-width, single-column, stacked sections.
- Very specific: line 86
All content lines must have matching left and right │ borders
- Very specific: line 174
When a command's TUI includes interactive follow-up (like /activity numbered items):
- Very specific: line 177
Add footer text inside the box: Type a number to act, or keep working.
- Distinctive: line 178
Ask with a structured question when available and permitted in this session.
- Distinctive: line 188
No bold, italic, or color codes in the markdown instruction files
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
TUI Design System
Voice Complex
This skill governs TERMINAL RENDERING — structural, not tonal.
Shared aesthetic: voice-bedrock (.claude/rules/voice-bedrock.md).
For product voice in command output prose: product-voice skill.
For browser visual output: dark-mode skill, which takes every color from the design system registry (packages/design-system/themes/registry.json).
For ASCII diagrams in explanations: visual-explain skill.
When to invoke
User says: "TUI", "terminal output", "box drawing", "command output formatting", "sigils", "section markers", or is designing/modifying any slash command's terminal output.
Not this: browser rendering → dark-mode · external prose → egregore-voice
1. Brand Elements
Command Headers
/activity is the flagship — it gets the full branded header with org name:
{ORG_NAME} EGREGORE ✦ ACTIVITY DASHBOARDRead org name from jq -r '.org_name' egregore.json. The ✦ star is reserved exclusively for the activity dashboard and Egregore-wide branding.
Other commands get sigil + command name only — no org name:
| Command | Header | Sigil Meaning |
/activity | {ORG_NAME} EGREGORE ✦ ACTIVITY DASHBOARD | The star — awareness, the full field |
/ask | ? ASK | The question — direct, clear inquiry |
/reflect | ◎ REFLECTION | The eye — looking inward, seeing clearly |
/deep-reflect | ◈ DEEP REFLECT | The faceted eye — looking inward with structure |
/handoff | ⇌ HANDOFF | The bridge — passing context between minds |
/quest | ⚑ QUEST | The flag — planting direction in unknown territory |
/todo | □ TODO | The checkbox — actionable items, personal intent |
/archive | ◇ ARCHIVE | The diamond — crystallized pattern, refined and preserved |
/eval | ⊕ EVAL | The crosshair — measuring, comparing, calibrating |
Section Markers
Used within all TUI boxes to prefix items by category:
●Action items / things needing attention✓Completed / received / done items→Navigation pointers (what to do next, entry points)◦Informational items (sessions, quests, neutral data)⚑Quests⇌Handoffs (in activity action items)◎Reflections□Todos (in activity dashboard)★Priority marker (todo items with priority >= 2)◉Artifacts (in handoff summaries)
2. Box Drawing Rules
Line Patterns (CRITICAL)
LLMs cannot count character widths. Do NOT draw boxes freehand. Instead, produce exactly 4 line patterns. All commands use 72-char outer width (N = 70 fill characters).
- Top:
┌+ 70×─+┐ - Separator:
├+ 70×─+┤ - Content:
│+ 2 spaces + text + pad to 68 text chars +│ - Bottom:
└+ 70×─+┘
Characters: ┌ top-left, ─ horizontal, ┐ top-right, │ vertical, ├ left-tee, ┤ right-tee, └ bottom-left, ┘ bottom-right.
Separator lines are always identical — copy-paste the same 72-char string every time. Content lines have ONLY the outer │ as borders. Pad every content line with trailing spaces so the closing │ lands at position 72.
Header separator: always use ├───┤ between header row and content.
Section dividers: use ├───┤ between logical groups. No sub-boxes — never use ┌─┐/└─┘ inside the outer frame. LLMs cannot reliably align nested borders.
Layout
All commands use full-width, single-column, stacked sections. No column splits — they cause truncation and render poorly. Content flows top-to-bottom with section headers separating groups.
3. Width Standards
- All commands: ~72 characters outer width
- All content lines must have matching left and right
│borders
4. Content Formatting
Session Lines (Compact)
Feb 07 Topic descriptionDate is always Mon DD format, right-padded to 6 chars. Topic follows after 2 spaces.
Team Session Lines
Feb 07 oz: Topic descriptionPerson name prefixed with colon separator.
Numbered Action Items
[1] Description of actionable thing
[2] ⇌ Handoff from ali: blog styling (yesterday)Numbers in brackets. Use section markers after the bracket for typed items.
Status Confirmations
✓ Saved to knowledge/decisions/2026-02-08-...
✓ Memory index updated
✓ Auto-savedProgress Steps
[1/5] ✓ Conversation file
[2/5] ✓ Index updated
[3/5] ✓ Session saved to memory
[4/5] ✓ Pushed + PR created
[5/5] ✓ Oz notifiedLinked Items
◦ Quest: research-agent
◦ Project: egregoreEntry Points
→ memory/knowledge/decisions/2026-02-07-defensibility-...
→ memory/knowledge/decisions/2026-02-07-business-model.mdTruncation
- Topics longer than 35 chars in column layouts get
...suffix - File paths: shorten to last 2 segments when possible
- Never break mid-word
5. Section Visibility Rules
- Empty sections are omitted entirely — no placeholder text, no "none yet", no empty boxes
- Single action item still gets the action items box — consistency over minimalism
- Section headers only appear when their section has content
6. Edge Cases
| Scenario | Handling |
| No sessions yet | Show Projects section instead (first-timer experience) |
| Neo4j down | File-based fallback, simpler layout, no columns |
| Single action item | Still show action items box |
| No team activity | Omit TEAM section |
| Very long org name | Truncate at 20 chars in activity header |
| No quests | Omit quests section |
| No PRs | Omit PRs section |
| No action items + no answers | Omit both sections, go straight to columns |
7. Anti-Patterns
- Avoid sub-boxes entirely — use
├───┤flat dividers instead (LLMs can't count widths for nested borders) - Never use tables with
│column separator AND sub-boxes in the same section (pick one) - Never show empty section headers — omit the entire section
- Never use raw file paths in TUI output — use
→pointer with shortened path - Never break box characters across lines — each line must have valid left/right borders
- Never use the
✦star outside/activityheader - Never include org name in non-activity command headers
- Never use emoji in TUI boxes (sigils and markers only)
8. Structured questions
When a command's TUI includes interactive follow-up (like /activity numbered items):
- Display the full TUI box first
- Add footer text inside the box:
Type a number to act, or keep working. - Ask with a structured question when available and permitted in this session; otherwise ask in plain text. Use options matching the numbered items
- Include a "Skip" option for non-action
9. Color and Emphasis
Terminal output is monospace plain text. Emphasis is structural only:
- Section headers: ALL CAPS
- Sigils and markers provide visual weight
- Sub-boxes create grouping
- Indentation creates hierarchy
- No bold, italic, or color codes in the markdown instruction files
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

