ultracode-helplisted

# UltraCode Help Explain UltraCode in the user's language. Remain strictly read-only: do not initialize, plan project changes, delegate, run tests or builds, refresh task state, or modify any file. Read [the command guide](../ultracode/references/command-guide.md) completely before answering. Read [the reasoning router](../ultracode/references/reasoning-routing.md) completely for `models` or any question about model or effort selection. ## Select the response mode First remove the invocation token `$ultracode-help` or `ultracode-help` from the request. The invocation token is never itself the `help` topic. Only the remaining words can select a mode. Normalize remaining topics with or without `$`: `ultracode`, `verify`, `init`, `edit`, `flow`, `status`, `help`, `models`, and `examples`. Accept complete command names such as `ultracode-verify`. An explicit Help invocation has precedence over every command name in the remaining words: `$ultracode-help flow` explains Flow and must never execute `$ultracode-flow`. - **No remaining topic:** render the complete overview. A bare `Use $ultracode-help` invocation and a broad request such as "come funziona?", "come inizio?", or "spiegami UltraCode" are not focused topics. - **Explicit topic:** answer that topic first and include only the minimum comparison and example needed to place it correctly. Do not expand into the complete overview. - **Explicit `breve` or `sintetico`:** use compact mode. Compress prose, never truth con