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 — so bugs like missing autocomplete entries, commands working in CLI but not TUI, or config changes not applying live are hard to trace. This Skill provides a systematic investigation and fix workflow for these cross-layer mismatches. ## Core Features & Use Cases - Cross-Layer Investigation: Step-by-step search commands to locate command definitions in the Python COMMAND_REGISTRY, gateway handlers, and Ink frontend handlers. - Autocomplete Fixes: Instructions for registering CommandDef entries with correct cli_only, gateway_only, aliases, and subcommands settings. - Live State Sync Guidance: Explains how to patch nanostore UI state so config changes apply immediately, not just after restart. - Use Case: A developer adds a new /details command that persists config but the TUI display doesn't update. This Skill walks them through patching the UI state, threading it through both streaming and transcript render paths, and verifying with a rebuild. ## Quick Start Ask the AI to debug why a specific Hermes TUI slash command is missing from autocomplete or behaves differently between the CLI and the TUI.