Using hotpath

hotpath is a feature-gated Rust profiler: every macro is a no-op and no dependency is compiled unless the hotpath cargo feature is enabled. This skill does not hold the API; it routes each task to the docs page or agent procedure that does. Fetch those before writing code or answering, and follow them instead of memory.

Fetching the docs

Every page of https://hotpath.rs is served as markdown with an Accept: text/markdown header, which costs far fewer tokens than HTML:

curl -fsSL -H 'Accept: text/markdown' https://hotpath.rs/functions

• Pages under /agent/ are step-by-step procedures, markdown only. When a task routes to one, fetch it and follow it.
• If a fetch fails, stop and tell the user which URL failed; do not guess the API.
• A #fragment is not sent to the server: fetch the whole page and find the heading.
• Fetch only the pages the task needs, each once. Follow a link from a page only when you need the detail it points to.

Routing

Paths are relative to https://hotpath.rs. Fetch the pages listed for the task, plus the page of any other subsystem it touches.

Setup and profiling

hotpath-cloud

Observability and general

Rules

• hotpath version: the docs describe the latest release (cargo search hotpath --limit 1); add it for a new dependency. Keep an existing version (see Cargo.lock) when it supports the task; a hotpath cargo feature that is only not enabled yet needs enabling, not an upgrade. When the installed version lacks functionality the task needs (compare with https://github.com/hotpath-rs/hotpath/blob/main/CHANGELOG.md), upgrade to the latest release without asking: raise the requirement keeping its features, cargo update -p hotpath, no other dependency changes, build with and without the project's hotpath features, and tell the user the old and new version, why and what code changed. If it cannot be made to build, restore the previous Cargo.toml/Cargo.lock state, and report the failure and what stays unavailable.
• Never add hotpath or any hotpath-* feature to default features; profiling stays opt-in.
• Verify instrumentation compiles both ways: cargo check and cargo check --features hotpath.
• Wrapper macros return hotpath::wrap:: types (no-op with the feature off). Do not silently rewrite public APIs to fit them; tell the user.
• When the docs and your memory disagree, the docs win. Cite the page you relied on.
• Do not commit or push unless the user asks.