What problem does it solve? Slash commands in the Hermes TUI span three layers — the Python command registry, the tui_gateway JSON-RPC bridge, and the Ink/TypeScript frontend — and bugs occur when one layer falls out of sync with the others. This Skill provides a systematic workflow to locate and fix commands that are missing from autocomplete, behave differently between CLI and TUI, or persist config without updating the live UI. ## Core Features & Use Cases - Cross-layer investigation: Step-by-step search commands to check whether a command exists in the Python COMMAND_REGISTRY, the gateway, and the Ink frontend. - Autocomplete fixes: Instructions for adding CommandDef entries with correct cli_only, gateway_only, aliases, and subcommands settings so autocomplete data ships correctly to the TUI. - Live UI state patching: Guidance on updating nanostore state (patchUiState) alongside config.set so changes apply immediately, not just after restart. - Use Case: A developer adds a new /details command that saves config but the TUI display does not change until restart; this Skill walks them through patching the live nanostore state and threading it through both streaming and transcript render paths. ## Quick Start Ask the agent to debug why a specific Hermes TUI slash command is missing from autocomplete or not applying live, and it will trace the command across the Python registry, gateway, and Ink frontend.