What problem does it solve? Navigating a large three-tier codebase (C++/GGML engine, Node/Express server, React UI) is slow and error-prone when you cannot tell which tier owns a feature or bug. This Skill maps every HOT-Step CPP feature to its exact route file, service, UI folder, and engine subsystem, including port topology and the browser-to-engine request path. ## Core Features & Use Cases - Feature-to-file mapping: A route β service β UI β engine table covering generation, stem separation, adapters, mastering, VST chains, and more, with line-number anchors. - Request-path tracing: Documents the full browser β Express β ace-server β audio file flow, including the LM/synth sideband gotcha and job polling model. - Failure triage: A symptom β cause β fix table for crash respawns, silent fork-hook loss after upstream syncs, stalled generations, and build pitfalls. - Use Case: A bug report says solver settings are ignored. The Skill tells you this is the silent pipeline-synth-ops.cpp hook loss after an upstream sync, and to run engine\verify-hooks.ps1. ## Quick Start Ask the AI where a specific HOT-Step feature or bug lives and which tier owns it, for example: where is the code for stem separation and how does a generation request flow from the browser to the engine?
