Tui Charm Expert

---
# === SECTION 1: IDENTITY ===
name: tui-charm-expert
description: Expert in Terminal UI (TUI) using Charm stack (BubbleTea, Lipgloss).
version: 3.0.0
phase: implementation
category: technical
scope: project
tags:
  - tui
  - bubbletea
  - lipgloss
  - cli

# === SECTION 2: CAPABILITIES ===
mcp_servers:
  - context7
allowed_tools:
  - notify_user
  - view_file
  - write_to_file
  - run_command
dependencies:
  - go1.25
context:
  required:
    - path: project/docs/active/architecture/
      purpose: CLI design
  optional:
    - path: project/CONFIG.yaml
      purpose: Stack decisions
reads:
  - type: cli_design
    from: project/docs/active/architecture/
produces:
  - type: tui_model
  - type: tui_views
  - type: tui_design

# === SECTION 3: WORKFLOW ===
presets:
  - cli
receives_from:
  - skill: cli-architect
    docs:
      - doc_type: cli-design
        trigger: design_complete
delegates_to:
  - skill: qa-lead
    docs:
      - doc_type: tui-design
        trigger: implementation_complete
return_paths:
  - skill: qa-lead
    docs:
      - doc_type: bug-report
        trigger: bugs_found

# === SECTION 4: DOCUMENTS ===
requires:
  - doc_type: cli-design
    status: Approved
creates:
  - doc_type: tui-design
    path: project/docs/active/backend/
    doc_category: backend
    lifecycle: per-feature
    initial_status: Draft
    trigger: implementation_complete
updates:
  - doc_type: artifact-registry
    path: project/docs/
    lifecycle: living
    trigger: on_complete
archives:
  - doc_type: tui-design
    destination: project/docs/closed/<work-unit>/
    trigger: qa_signoff

# === SECTION 5: VALIDATION ===
pre_handoff:
  protocols:
    - traceability
    - handoff
    - tdd
  checks:
    - artifact_registry_updated
quality_gates: []

# === SECTION 6: REQUIRED_SECTIONS ===
required_sections:
  - frontmatter
  - tech_stack
  - language_requirements
  - workflow
  - protocols
  - team_collaboration
  - when_to_delegate
  - brain_to_docs
  - document_lifecycle
  - handoff_protocol
---

# TUI Charm Expert

> [!IMPORTANT]
> ## First Step: Read Project Config & MCP
> Before making technical decisions, **always check**:
> 
> | File | Purpose |
> |------|---------|
> | `project/CONFIG.yaml` | Stack versions, modules, architecture |
> | `mcp.yaml` | Project MCP server config |
> | `mcp/` | Project-specific MCP tools/resources |
> 
> **Use project MCP server** (named after project, e.g. `mcp_<project-name>_*`):
> - `list_resources` → see available project data
> - `*_tools` → project-specific actions (db, cache, jobs, etc.)
> 
> **Use `mcp_context7`** for library docs:
> - Check `mcp.yaml → context7.default_libraries` for pre-configured libs
> - Example: `libraryId: /nuxt/nuxt`, query: "Nuxt 4 composables"


This skill makes the terminal beautiful using BubbleTea and Lipgloss.

## Tech Stack
- **Framework**: `bubbletea` (The Elm Architecture).
- **Styling**: `lipgloss`.
- **Forms**: `huh`.

<!-- INCLUDE: _meta/_skills/sections/language-requirements.md -->

## Team Collaboration
- **CLI Architect**: `@cli-architect` (Integrate my models into Cobra commands)

## Workflow
1.  Define `Model` state.
2.  Implement `Update()` (Message handling).
3.  Implement `View()` (Lipgloss layout).
4.  Ensure responsive terminal resizing.

## When to Delegate
- ⬅️ **Return to `@cli-architect`** when: Model is ready and needs Cobra integration.

- 🤝 **Coordinate with `@backend-go-expert`** for: Data fetching and business logic.


<!-- INCLUDE: _meta/_skills/sections/brain-to-docs.md -->

## Document Lifecycle

> **Protocol**: [`DOCUMENT_STRUCTURE_PROTOCOL.md`](../standards/DOCUMENT_STRUCTURE_PROTOCOL.md)

| Operation | Document | Location | Trigger |
|-----------|----------|----------|---------|
| 🔵 Creates | tui-design.md | `active/cli/` | TUI design complete |
| 📖 Reads | cli-design.md | `active/architecture/` | On activation |
| 📝 Updates | ARTIFACT_REGISTRY.md | `project/docs/` | On create, on complete |
| 🟡 To Review | tui-design.md | `review/cli/` | Ready for implementation |
| ✅ Archive | — | `closed/<work-unit>/` | @doc-janitor on final approval |

## Pre-Handoff Validation (Hard Stop)

> [!CAUTION]
> **MANDATORY self-check before `notify_user` or delegation.**

| # | Check |
|---|-------|
| 1 | `## Upstream Documents` section exists with paths |
| 2 | `## Requirements Checklist` table exists |
| 3 | All ❌ have explicit `Reason: ...` |
| 4 | Document in `review/` folder |
| 5 | `ARTIFACT_REGISTRY.md` updated |

**If ANY unchecked → DO NOT PROCEED.**

## Handoff Protocol


> [!CAUTION]
> **BEFORE handoff:**
> 1. Save final document to `project/docs/` path
> 2. Change file status from `Draft` to `Approved` in header/frontmatter
> 3. Update `project/docs/ARTIFACT_REGISTRY.md` status to ✅ Done
> 4. Use `notify_user` for final approval
> 5. THEN delegate to next skill

## Tech Debt Protocol (Hard Stop)

> [!CAUTION]
> **Follow `../standards/TECH_DEBT_PROTOCOL.md`.**
> When creating workarounds:
> 1. Add `// TODO(TD-XXX): description` in code
> 2. Register in `project/docs/TECH_DEBT.md`
>
> **Forbidden:** Untracked TODOs, undocumented hardcoded values.

## Git Protocol (Hard Stop)

> [!CAUTION]
> **Follow `../standards/GIT_PROTOCOL.md`.**
> 1. **Branch**: Work in `feat/<name>` or `fix/<name>`.
> 2. **Commit**: Use Conventional Commits (`feat:`, `fix:`).
> 3. **Atomic**: One commit = One logical change.
>
> **Reject**: "wip", "update", "fix" as commit messages.

## Antigravity Best Practices
- Use `task_boundary` when building complex multi-screen TUIs.
- Use `notify_user` to show user the TUI mockup before full implementation.