How do I install the Tui Charm Expert skill?

Run npx skillmds add ydnikolaev/tui-charm-expert in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Tui Charm Expert skill do?

Expert in Terminal UI (TUI) using Charm stack (BubbleTea, Lipgloss). It is listed under Coding & Dev Tools on SkillMD.

Is Tui Charm Expert safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tui Charm Expert?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tui Charm Expert free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tui Charm Expert?

ydnikolaev (@ydnikolaev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tui Charm Expert by ydnikolaev — Agent Skill

Name: Tui Charm Expert
Rating: 4.2 (5 reviews)
Author: ydnikolaev

File contents

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"

File	Purpose
`project/CONFIG.yaml`	Stack versions, modules, architecture
`mcp.yaml`	Project MCP server config
`mcp/`	Project-specific MCP tools/resources

This skill makes the terminal beautiful using BubbleTea and Lipgloss.

Tech Stack

Framework: bubbletea (The Elm Architecture).
Styling: lipgloss.
Forms: huh.

Team Collaboration

CLI Architect: @cli-architect (Integrate my models into Cobra commands)

Workflow

Define Model state.
Implement Update() (Message handling).
Implement View() (Lipgloss layout).
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.

Document Lifecycle

Protocol: 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:

Save final document to project/docs/ path

Change file status from Draft to Approved in header/frontmatter

Update project/docs/ARTIFACT_REGISTRY.md status to ✅ Done

Use notify_user for final approval

THEN delegate to next skill

Tech Debt Protocol (Hard Stop)

[!CAUTION] Follow ../standards/TECH_DEBT_PROTOCOL.md. When creating workarounds:

Add // TODO(TD-XXX): description in code

Register in project/docs/TECH_DEBT.md

Forbidden: Untracked TODOs, undocumented hardcoded values.

Git Protocol (Hard Stop)

[!CAUTION] Follow ../standards/GIT_PROTOCOL.md.

Branch: Work in feat/<name> or fix/<name>.

Commit: Use Conventional Commits (feat:, fix:).

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.

---name: tui-charm-expertdescription: Expert in Terminal UI (TUI) using Charm stack (BubbleTea, Lipgloss).---# 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`.## Team Collaboration- **CLI Architect**: `@cli-architect` (Integrate my models into Cobra commands)## Workflow1. 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.## 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.

Frequently asked questions