opção
LarLar Skill Outros opentui

Habilidade abrangente do OpenTUI para a criação de interfaces de usuário de terminal. Abrange a API imperativa principal, o reconciliador do React e o reconciliador do Solid. Utilize-a para qualquer tarefa de desenvolvimento de TUI, incluindo componentes, layout, gerenciamento de teclado, animações e testes.

...Expandir tudo
53
Tempo atualizado 4 de Agosto de 2026

OpenTUI Habilidade em plataformas

Conjunto de habilidades para a criação de interfaces de usuário de terminais com o OpenTUI. Use as árvores de decisão abaixo para encontrar a estrutura e os componentes adequados e, em seguida, acesse as referências detalhadas.

Regras essenciais

Siga estas regras em todo o código do OpenTUI:

  1. Use o create-tui para novos projetos. Consulte os REFERENCE.md guias de introdução rápida.
  2. create-tui As opções devem vir antes dos argumentos. bunx create-tui -t react my-app funciona, bunx create-tui my-app -t react NÃO funciona.
  3. Nunca chame process.exit() diretamente. Use renderer.destroy() (veja core/gotchas.md).
  4. A formatação de texto requer tags aninhadas no React/Solid. Use elementos modificadores, não props (veja components/text-display.md).

Como usar esta habilidade

Estrutura do arquivo de referência

As referências à estrutura seguem um padrão de 5 arquivos. Conceitos transversais são guias de um único arquivo.

Cada framework em ./references// contém:

Conceitos transversais em ./references// têm REFERENCE.md como ponto de entrada.

Ordem de leitura

  1. Comece com REFERENCE.md pela estrutura escolhida
  2. Em seguida, leia os arquivos adicionais relevantes para sua tarefa:
    • Criação de componentes -> api.md + components/.md
    • Configurar o projeto -> configuration.md
    • Layout/posicionamento -> layout/REFERENCE.md
    • Manipulação do teclado/entrada -> keyboard/REFERENCE.md
    • Animações -> animation/REFERENCE.md
    • Solução de problemas -> gotchas.md + testing/REFERENCE.md

Caminhos de exemplo

./references/react/REFERENCE.md           # Start here for React
./references/react/api.md              # React components and hooks
./references/solid/configuration.md    # Solid project setup
./references/components/inputs.md      # Input, Textarea, Select docs
./references/core/gotchas.md           # Core debugging tips

Notas de execução

OpenTUI É executado no Bun e usa o Zig para compilações nativas. Leia ./references/core/gotchas.md os requisitos de execução e as orientações de compilação.

Árvores de decisão rápidas

“Qual framework devo usar?”

Which framework?
├─ I want full control, maximum performance, no framework overhead
│  └─ core/ (imperative API)
├─ I know React, want familiar component patterns
│  └─ react/ (React reconciler)
├─ I want fine-grained reactivity, optimal re-renders
│  └─ solid/ (Solid reconciler)
└─ I'm building a library/framework on top of OpenTUI
   └─ core/ (imperative API)

“Preciso exibir conteúdo”

Display content?
├─ Plain or styled text -> components/text-display.md
├─ Container with borders/background -> components/containers.md
├─ Scrollable content area -> components/containers.md (scrollbox)
├─ ASCII art banner/title -> components/text-display.md (ascii-font)
├─ Data table with borders/wrapping -> components/code-diff.md (TextTable)
├─ Code with syntax highlighting -> components/code-diff.md
├─ Diff viewer (unified/split) -> components/code-diff.md
├─ Line numbers with diagnostics -> components/code-diff.md
└─ Markdown content (streaming) -> components/code-diff.md (markdown)

“Preciso de entrada do usuário”

User input?
├─ Single-line text field -> components/inputs.md (input)
├─ Multi-line text editor -> components/inputs.md (textarea)
├─ Select from a list (vertical) -> components/inputs.md (select)
├─ Tab-based selection (horizontal) -> components/inputs.md (tab-select)
└─ Custom keyboard shortcuts -> keyboard/REFERENCE.md

“Preciso de layout/posicionamento”

Layout?
├─ Flexbox-style layouts (row, column, wrap) -> layout/REFERENCE.md
├─ Absolute positioning -> layout/patterns.md
├─ Responsive to terminal size -> layout/patterns.md
├─ Centering content -> layout/patterns.md
└─ Complex nested layouts -> layout/patterns.md

“Preciso de animações”

Animations?
├─ Timeline-based animations -> animation/REFERENCE.md
├─ Easing functions -> animation/REFERENCE.md
├─ Property transitions -> animation/REFERENCE.md
└─ Looping animations -> animation/REFERENCE.md

"Preciso processar entradas"

Input handling?
├─ Keyboard events (keypress, release) -> keyboard/REFERENCE.md
├─ Focus management -> keyboard/REFERENCE.md
├─ Paste events -> keyboard/REFERENCE.md
├─ Mouse events -> components/containers.md
├─ Text selection & copy-on-select -> keyboard/REFERENCE.md (selection)
└─ Clipboard (OSC 52) -> keyboard/REFERENCE.md (clipboard)

"Preciso testar minha TUI"

Testing?
├─ Snapshot testing -> testing/REFERENCE.md
├─ Interaction testing -> testing/REFERENCE.md
├─ Test renderer setup -> testing/REFERENCE.md
└─ Debugging tests -> testing/REFERENCE.md

"Preciso depurar/resolver problemas"

Troubleshooting?
├─ Runtime errors, crashes -> /gotchas.md
├─ Layout issues -> layout/REFERENCE.md + layout/patterns.md
├─ Input/focus issues -> keyboard/REFERENCE.md
└─ Repro + regression tests -> testing/REFERENCE.md

Índice de resolução de problemas

  • Limpeza do terminal, travamentos -> core/gotchas.md
  • Estilo do texto não está sendo aplicado -> components/text-display.md
  • Foco de entrada/atalhos -> keyboard/REFERENCE.md
  • Desalinhamento do layout -> layout/REFERENCE.md
  • Instantâneos instáveis -> testing/REFERENCE.md

Para diferenças na nomenclatura de componentes e modificadores de texto, consulte components/REFERENCE.md.

Índice de Produtos

Frameworks

Conceitos Transversais

Categorias de componentes

Recursos

Repositório : https://github.com/anomalyco/opentui Documentação do núcleo : https://github.com/anomalyco/ opentui /tree/main/packages/core/docs Exemplos : https://github.com/anomalyco/ opentui /tree/main/packages/core/src/examples Lista do Awesome : https://github.com/msmps/awesome- opentui

Mais deste repositório mesmo repositório

Mais deste repositório

Use ao preparar, marcar e publicar uma versão do aplicativo de desktop Cline Code (apps/examples/desktop-app). Orientações para a elaboração do changelog, atualizações de versão nos arquivos package.json e tauri.conf.json, tags desktop-vX.Y.Z e o fluxo de trabalho desktop-publish no GitHub que compila, assina, certifica e atualiza o feed de atualização automática.publish-desktopcline/cline2026-07-2165,Prepare, valide e publique versões autônomas do @cline/ui no npm. Use ao aumentar a versão do pacote UI, publicar a versão mais recente ou a próxima por meio do ui-publish.yml, verificar se a versão do UI está pronta para lançamento ou concluir a inicialização única do npm trusted-publishing.1kpublish-uicline/cline2026-07-1865,1kpublish-clicline/cline2026-06-0465Use ao preparar, marcar e publicar uma versão npm do apps/cli. Orienta a elaboração do changelog, o aumento de versão do apps/cli/package.json, as tags cli-vX.Y.Z, a publicação local no npm e o fluxo de trabalho publish-cli no GitHub.,Conhecimento abrangente do Cline SDK para a criação de agentes de IA. Abrange o tempo de execução do agente, sessões do ClineCore, ferramentas personalizadas, plug-ins, eventos, provedores de LLM, agendamento, equipes com múltiplos agentes e implantação em produção. Use para qualquer tarefa envolvendo @cline/sdk ou seus subpacotes.1kcline-sdkcline/cline2026-05-1465.1kcreate-pull-requestcline/cline2026-02-2465Crie uma solicitação de pull no GitHub seguindo as convenções do projeto. Use quando o usuário solicitar a criação de uma solicitação de pull, enviar alterações para revisão ou abrir uma solicitação de pull. Lida com a análise de commits, gerenciamento de ramificações, uso de modelos de solicitação de pull e criação de solicitações de pull usando a ferramenta gh CLI..1k
Ver no GitHub

OpenTUI Platform Skill

Consolidated skill for building terminal user interfaces with OpenTUI. Use decision trees below to find the right framework and components, then load detailed references.

Critical Rules

Follow these rules in all OpenTUI code:

  1. Use create-tui for new projects. See framework REFERENCE.md quick starts.
  2. create-tui options must come before arguments. bunx create-tui -t react my-app works, bunx create-tui my-app -t react does NOT.
  3. Never call process.exit() directly. Use renderer.destroy() (see core/gotchas.md).
  4. Text styling requires nested tags in React/Solid. Use modifier elements, not props (see components/text-display.md).

How to Use This Skill

Reference File Structure

Framework references follow a 5-file pattern. Cross-cutting concepts are single-file guides.

Each framework in ./references/<framework>/ contains:

Cross-cutting concepts in ./references/<concept>/ have REFERENCE.md as the entry point.

Reading Order

  1. Start with REFERENCE.md for your chosen framework
  2. Then read additional files relevant to your task:
    • Building components -> api.md + components/<category>.md
    • Setting up project -> configuration.md
    • Layout/positioning -> layout/REFERENCE.md
    • Keyboard/input handling -> keyboard/REFERENCE.md
    • Animations -> animation/REFERENCE.md
    • Troubleshooting -> gotchas.md + testing/REFERENCE.md

Example Paths

./references/react/REFERENCE.md           # Start here for React
./references/react/api.md              # React components and hooks
./references/solid/configuration.md    # Solid project setup
./references/components/inputs.md      # Input, Textarea, Select docs
./references/core/gotchas.md           # Core debugging tips

Runtime Notes

OpenTUI runs on Bun and uses Zig for native builds. Read ./references/core/gotchas.md for runtime requirements and build guidance.

Quick Decision Trees

"Which framework should I use?"

Which framework?
├─ I want full control, maximum performance, no framework overhead
│  └─ core/ (imperative API)
├─ I know React, want familiar component patterns
│  └─ react/ (React reconciler)
├─ I want fine-grained reactivity, optimal re-renders
│  └─ solid/ (Solid reconciler)
└─ I'm building a library/framework on top of OpenTUI
   └─ core/ (imperative API)

"I need to display content"

Display content?
├─ Plain or styled text -> components/text-display.md
├─ Container with borders/background -> components/containers.md
├─ Scrollable content area -> components/containers.md (scrollbox)
├─ ASCII art banner/title -> components/text-display.md (ascii-font)
├─ Data table with borders/wrapping -> components/code-diff.md (TextTable)
├─ Code with syntax highlighting -> components/code-diff.md
├─ Diff viewer (unified/split) -> components/code-diff.md
├─ Line numbers with diagnostics -> components/code-diff.md
└─ Markdown content (streaming) -> components/code-diff.md (markdown)

"I need user input"

User input?
├─ Single-line text field -> components/inputs.md (input)
├─ Multi-line text editor -> components/inputs.md (textarea)
├─ Select from a list (vertical) -> components/inputs.md (select)
├─ Tab-based selection (horizontal) -> components/inputs.md (tab-select)
└─ Custom keyboard shortcuts -> keyboard/REFERENCE.md

"I need layout/positioning"

Layout?
├─ Flexbox-style layouts (row, column, wrap) -> layout/REFERENCE.md
├─ Absolute positioning -> layout/patterns.md
├─ Responsive to terminal size -> layout/patterns.md
├─ Centering content -> layout/patterns.md
└─ Complex nested layouts -> layout/patterns.md

"I need animations"

Animations?
├─ Timeline-based animations -> animation/REFERENCE.md
├─ Easing functions -> animation/REFERENCE.md
├─ Property transitions -> animation/REFERENCE.md
└─ Looping animations -> animation/REFERENCE.md

"I need to handle input"

Input handling?
├─ Keyboard events (keypress, release) -> keyboard/REFERENCE.md
├─ Focus management -> keyboard/REFERENCE.md
├─ Paste events -> keyboard/REFERENCE.md
├─ Mouse events -> components/containers.md
├─ Text selection & copy-on-select -> keyboard/REFERENCE.md (selection)
└─ Clipboard (OSC 52) -> keyboard/REFERENCE.md (clipboard)

"I need to test my TUI"

Testing?
├─ Snapshot testing -> testing/REFERENCE.md
├─ Interaction testing -> testing/REFERENCE.md
├─ Test renderer setup -> testing/REFERENCE.md
└─ Debugging tests -> testing/REFERENCE.md

"I need to debug/troubleshoot"

Troubleshooting?
├─ Runtime errors, crashes -> <framework>/gotchas.md
├─ Layout issues -> layout/REFERENCE.md + layout/patterns.md
├─ Input/focus issues -> keyboard/REFERENCE.md
└─ Repro + regression tests -> testing/REFERENCE.md

Troubleshooting Index

  • Terminal cleanup, crashes -> core/gotchas.md
  • Text styling not applying -> components/text-display.md
  • Input focus/shortcuts -> keyboard/REFERENCE.md
  • Layout misalignment -> layout/REFERENCE.md
  • Flaky snapshots -> testing/REFERENCE.md

For component naming differences and text modifiers, see components/REFERENCE.md.

Product Index

Frameworks

Cross-Cutting Concepts

Component Categories

Resources

Repository: https://github.com/anomalyco/opentui Core Docs: https://github.com/anomalyco/opentui/tree/main/packages/core/docs Examples: https://github.com/anomalyco/opentui/tree/main/packages/core/src/examples Awesome List: https://github.com/msmps/awesome-opentui

More from this repositorysame repository

More from this repository

publish-desktopcline/cline

Use when preparing, tagging, and publishing a Cline Code desktop app (apps/examples/desktop-app) release. Guides changelog drafting, version bumps in package.json + tauri.conf.json, desktop-vX.Y.Z tags, and the desktop-publish GitHub workflow that builds, signs, notarizes, and updates the auto-update feed.

2026-07-2165.1k
publish-uicline/cline

Prepare, validate, and publish standalone @cline/ui npm releases. Use when bumping the UI package version, publishing latest or next through ui-publish.yml, checking UI release readiness, or completing the one-time npm trusted-publishing bootstrap.

2026-07-1865.1k
publish-clicline/cline

Use when preparing, tagging, and publishing an apps/cli npm release. Guides changelog drafting, apps/cli/package.json version bumps, cli-vX.Y.Z tags, local npm publishing, and the publish-cli GitHub workflow.

2026-06-0465.1k
cline-sdkcline/cline

Comprehensive Cline SDK skill for building AI agents. Covers the Agent runtime, ClineCore sessions, custom tools, plugins, events, LLM providers, scheduling, multi-agent teams, and production deployment. Use for any task involving @cline/sdk or its sub-packages.

2026-05-1465.1k
create-pull-requestcline/cline

Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, PR template usage, and PR creation using the gh CLI tool.

2026-02-2465.1k

Instalar opentui

Baixe e extraia os arquivos de habilidades para o diretório .claude/skills/.

Baixar ZIP

Clone o repositório e copie os arquivos da habilidade para o seu projeto.

git clone https://github.com/cline/cline/tree/main/.agents/skills/opentui # Copy the skill folder to .claude/skills/ or .codex/skills/

Copiar Copiar
Configuração rápida: Copie a pasta da habilidade para .claude/skills/. O Claude detectará e utilizará automaticamente a habilidade
Repositório cline/cline

Habilidades relacionadas

multica-creating-agents
Tempo atualizado 12 de Agosto de 2026
tilemaps
Tempo atualizado 4 de Agosto de 2026
v4-new-features
Tempo atualizado 4 de Agosto de 2026
pixijs-application
Tempo atualizado 4 de Agosto de 2026
OR