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 almost always come from one layer being out of sync with another. This Skill provides a systematic workflow to find and fix commands that are missing from autocomplete, work in the CLI but not the TUI, or persist config without updating the live UI. ## Core Features & Use Cases - Cross-layer investigation steps: Search patterns for locating command definitions in the Python backend (hermes_cli/commands.py), gateway (tui_gateway/server.py), and TUI frontend (ui-tui/src/app/slash/). - Autocomplete and registration fixes: Guidance for adding CommandDef entries to COMMAND_REGISTRY with correct cli_only, gateway_only, aliases, and subcommands settings. - Common issue catalog: Covers five recurring failure modes including silent gateway dispatch, CLI/TUI behavior divergence, and config changes not applying live to nanostore UI state. - Use Case: A developer adds a new /details command that saves config but the TUI display doesn't change until restart. This Skill walks them through patching the nanostore state and threading it through both streaming and transcript render paths. ## Quick Start Ask the AI to debug why a specific Hermes TUI slash command is missing from autocomplete or not applying its changes live in the interface.