What problem does it solve? Slow music generations in HOT-Step are hard to attribute: time is split across the LM, DiT denoising, and VAE phases, and two inference backends (GGML and TensorRT) behave very differently. This Skill maps where generation time goes, how the TRT paths activate, and how to benchmark from logs so you can find the real bottleneck instead of guessing. ## Core Features & Use Cases - Phase-level profiling: Read the server-side [Timing] pipeline breakdown table and cross-check it against engine-side wall-clock log markers to locate slow stages. - TRT integration guidance: Understand path-driven backend selection (ONNX path triggers TRT, GGUF triggers GGML), engine build caching, adapter refit, and streaming requirements. - Quality-speed trade-offs: Apply implemented knobs like CFG cutoff, step cache, quantization tiers, co-resident models, and batched CFG to speed up generation. - Use Case: A generation takes 80 seconds and you suspect the adapter apply step. Use this Skill to pull the newest session logs, compare [Adapter-TRT] Applied in against the Node timing table, and discover the table was skewed by stdout pipe buffering. ## Quick Start Ask the assistant to profile why my last HOT-Step generation was slow and identify which phase consumed the most time.