omo-profiler

Sincroniza o repositório omo-profiler com o upstream oh-my-openagent usando o clone local canônico em ~/dev/oh-my-openagent (branch dev). Compara o schema JSON embarcado (internal/schema/schema.json) contra o artefato upstream, propaga mudanças de schema para internal/config/types.go, os wizard steps, testes e AGENTS.md, detecta drift de código desde o último anchor (internal/schema/.upstream-sha) mesmo quando o schema não mudou, valida com build/test/lint e paridade de hash entre os 3 arquivos de schema, e só então persiste o novo anchor. Use sempre que o usuário pedir para atualizar/sincronizar o omo-profiler com o upstream, verificar se o schema ou os tipos Go estão desatualizados/com drift, checar novidades do oh-my-openagent, revisar campos de config novos/removidos, ou invocar /update-omo-profiler. Keywords: sync schema, upstream sync, schema drift, oh-my-openagent, oh-my-opencode.schema.json, .upstream-sha, wizard fields.

Refactor and modernize an EXISTING TUI's UI/UX by reading its codebase, reverse-engineering the current design, diagnosing design smells, and producing an optimized target design plus a file-level refactor plan. Unlike tui-design (starts from a spec) this starts from real code; unlike tui-validator (only audits) this redesigns. Does NOT modify source code — outputs an actionable migration plan. Use whenever the user asks to refactor, redesign, modernize, overhaul, improve, clean up, standardize, or optimize a terminal UI/CLI app that already has code. Triggers include "refactor this TUI", "redesign my CLI UI", "modernize this terminal app", "melhorar UX da TUI", "refatorar TUI", "redesenhar CLI", "modernizar interface terminal", and "/tui-refactor". Prefer over tui-design when codebase exists; prefer over tui-validator when the user wants design improvement rather than only bugs/findings.

Audit a terminal user interface (TUI) by driving it inside a tmux session, capturing both text and pixel screenshots (live Wayland or headless Chromium fallback), probing every keybinding, hammering it with special characters and resize events, and producing a markdown diagnostic that lists broken bindings, shortcut conflicts, dropped inputs, rendering glitches and visual degradation. Use this skill whenever the user asks to validate, audit, smoke-test, QA, fuzz, regression-check or "find bugs in" a terminal/CLI UI — even when they don't name tmux, grim, or screenshots — including phrases like "test this TUI", "check keybindings", "see if the layout breaks", "review the design of my CLI tool", "does this TUI render correctly", "find shortcut conflicts" or "validate the keyboard shortcuts of <something>". Strongly prefer this skill over ad-hoc tmux scripting whenever the target is interactive (Bubble Tea, Textual, blessed, ratatui, ncurses, etc.).