bubbletea · pedronauck — Claude Code skill: what it does, how to install
Guides coding agents in building Go terminal interfaces with Bubble Tea and Lip Gloss under the Elm architecture.
MIT 276 installs ★ 655 updated 2026-10-20
npx skills add pedronauck/skills --skill bubbletea -a claude-codeWhat bubbletea does
This skill guides assistants through building Go terminal user interfaces with Bubble Tea and Lip Gloss. It enforces the model-update-view loop, keeping side effects separate from the view rendering logic.
The instructions focus on terminal reality: display width differs from byte length and code point count, so strings must use ANSI-aware measurement. Sizing panes requires measuring actual padding and clamping boundaries, while dependencies must be added through the standard Go workflow rather than manually editing go.mod.
What it helps with
- build Go TUI components following the Elm model-update-view pattern
- calculate visual string widths properly with ANSI sequences and emojis
- handle responsive layouts and clamping across varied terminal sizes
- manage keyboard and mouse events alongside component focus
Example prompts for the agent
- Implement a split-pane layout using Lip Gloss that clamps to narrow terminals
- Handle window resize messages in this Bubble Tea model without breaking the layout
- Format multiline terminal output using cell-aware truncation instead of byte slicing
How to install bubbletea
1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill bubbletea -a claude-code2Manually: put the files in place
~/.claude/skills/bubbletea/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/bubbletea/
1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill bubbletea -a codex2Manually: put the files in place
.agents/skills/bubbletea/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill bubbletea -a cursor2Manually: put the files in place
.cursor/skills/bubbletea/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pedronauck/skills skills/mine/bubbletea2Manually: put the files in place
.github/skills/bubbletea/SKILL.md1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill bubbletea -a gemini-cli2Platform CLI
gemini skills install https://github.com/pedronauck/skills --path skills/mine/bubbleteaManually: put the files in place
.devin/skills/bubbletea/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pedronauck/skills --skill bubbletea -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about bubbletea
How do I install bubbletea in Claude Code?
Run npx skills add pedronauck/skills --skill bubbletea -a claude-code in your terminal.
What does bubbletea do?
It guides the assistant on developing Go TUIs using Bubble Tea and Lip Gloss, covering layout sizing, event handling, and Elm architecture constraints.
How does it handle package dependencies?
It instructs the agent to install dependencies through the repository's standard Go package workflow rather than directly editing go.mod.
Source text
SKILL.md · MIT
--- name: bubbletea description: "Build interactive Go TUIs with Bubbletea, Elm architecture, Lipgloss, layouts, and keyboard/mouse handling. Excludes plain-text CLIs, web/desktop GUIs, and other TUI frameworks." license: MIT metadata: author: Pedro Nauck github: https://github.com/pedronauck repository: https://github.com/pedronauck/skills --- # Bubble Tea TUI Development Work with the repository's installed Bubble Tea/Lip Gloss versions and existing model/update/view structure. Use current official docs for version-specific API changes; do not assume bundled examples match the consuming project's major version. ## Implementation - Reuse nearby components and state ownership. A small widget does not require a new project scaffold, YAML configuration, hot reload, mouse handling, or effects library. - Before changing layout, inspect the relevant guidance in `references/golden-rules.md`. Measure the actual frame/padding and clamp small-terminal dimensions; subtracting a fixed two cells is valid only for that exact border. - Use terminal-cell/ANSI-aware measurement and truncation. Do not slice strings by byte length or assume code points equal display width. Choose clipping, wrapping, or scrolling for the content's behavior; not all bordered text must truncate. - Keep hit-testing consistent with the rendered layout and focus state. Proportional sizing is useful for flexible panes; fixed sizes are valid for intentional controls. - Keep effectful work outside rendering and preserve the model/update lifecycle. Validate the changed interaction and relevant narrow/wide terminal sizes; add an owning test only when behavior lacks coverage. ## References | Concern | Read as needed | | --- | --- | | Border sizing, panel alignment | `references/golden-rules.md` | | Existing widget patterns | `references/components.md` | | Rendering failure | `references/troubleshooting.md` | | Unicode/emoji alignment | `references/emoji-width-fix.md` | Bundled templates are optional starting points for a new application. Adapt their API versions and layout assumptions; do not replace a working project structure or add dependencies it does not need. Install required dependencies through the repository's package workflow, not by hand-editing go.mod. Product behavior, terminal constraints, and project conventions take precedence over illustrative examples.
© Pedro Nauck · MIT · pedronauck/skills
Similar skills
All skills for Frontend and UI →bubbletea by other authors comes first.