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: [DOCUMENTSTRUCTUREPROTOCOL.md](../standards/DOCUMENTSTRUCTUREPROTOCOL.md)

Pre-Handoff Validation (Hard Stop)

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

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/TECHDEBTPROTOCOL.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.