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 another, causing missing autocomplete entries, commands that work in CLI but not TUI, or config changes that don't apply live. ## Core Features & Use Cases - Cross-layer investigation workflow: Step-by-step search commands to locate command definitions in the Python COMMAND_REGISTRY, gateway handlers, and TUI frontend files. - Autocomplete and dispatch fixes: Concrete instructions for adding CommandDef entries, gateway handlers, and CLI process_command branches with correct cli_only/gateway flags. - Live UI state guidance: Explains how to patch nanostore state so config changes apply immediately across streaming and transcript render paths. - Use Case: A developer adds a new /details command that appears in the TUI but never shows in autocomplete; this skill walks them through registering it in COMMAND_REGISTRY, rebuilding the TUI, and verifying behavior end to end. ## Quick Start Ask the agent to debug why a specific Hermes slash command is missing from TUI autocomplete or behaves differently between the CLI and the TUI.
