debugging-Titan-tui-commands

Align Python command registry, TUI gateway routing, and Ink/TypeScript slash handlers.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill debugging-titan-tui-commands
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-Titan-tui-commands
Source: https://github.com/devMoez/titan/tree/main/skills/software-development/debugging-titan-tui-commands
Command: npx skills add https://github.com/devMoez/titan --skill debugging-titan-tui-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose why Titan TUI slash commands fail to appear in autocomplete or behave inconsistently across the Python command registry, the TUI gateway, and the Ink/TypeScript frontend.

Core Features & Use Cases

  • Cross-layer command tracing: Identify mismatches between the canonical COMMAND_REGISTRY in Titan_cli/commands.py, gateway dispatch in tui_gateway/, and UI handlers in ui-tui/src/app/slash/.
  • Autocomplete repair: Ensure the command is registered with the correct canonical name, description, args hint, and subcommands so TUI suggestions match backend definitions.
  • Live UI behavior fixes: Verify that config persistence updates the correct nanostore/UI state immediately, preventing “saved but not applied” scenarios in the TUI.
  • End-to-end validation: Rebuild the UI and confirm behavior on Titan --tui, and—when applicable—validate gateway behavior on a messaging platform or gateway tests.

Quick Start

Use debugging-Titan-tui-commands when a slash command works in the CLI but is missing in Titan TUI autocomplete or doesn’t dispatch correctly, then compare the Python registry entry with the corresponding TypeScript/gateway handlers.

Frequently Asked Questions about debugging-Titan-tui-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why are slash commands missing from Titan TUI autocomplete after config changes?

Slash commands are missing from Titan TUI autocomplete due to drift between the Python command registry, gateway routing, and Ink/TypeScript UI handlers. Aligning the canonical command definitions across these layers ensures autocomplete suggestions match backend definitions consistently.

How do I fix Titan TUI slash commands that dispatch incorrectly through the gateway?

To fix Titan TUI slash commands dispatching incorrectly, trace mismatches between the Python command registry and gateway JSON-RPC routing. Aligning gateway dispatch logic with registered command names ensures correct routing behavior on `Titan --tui`.

How does command registration sync work between Python and TypeScript in the Titan TUI?

Command registration sync requires aligning the Python `COMMAND_REGISTRY` with TypeScript slash handlers and gateway known commands. This cross-layer tracing ensures command names, descriptions, and args hints match across backend, gateway, and frontend UI.

Can I use this debugging approach for TUI state updates that save but do not apply live?

Yes, this approach fixes TUI state updates that save but do not apply live by verifying config persistence updates the correct nanostore state. Aligning the UI state handlers ensures live behavior reflects saved configurations immediately.

What are the limitations of troubleshooting Titan TUI command registry mismatches?

Troubleshooting Titan TUI command registry mismatches requires checking three distinct codebases: Python commands, gateway routing, and TypeScript UI handlers. It cannot fix issues caused by network failures or external messaging platform limitations outside the gateway dispatch layer.