Rust Router

Load this first for non-trivial Rust work, then load only the smallest useful follow-on skill.

Working stance

• Start from the concrete problem: error, boundary, hot path, or unsafe edge.
• Prefer one language skill plus at most one domain or architecture skill.
• Use the general leta skill for code navigation, references, implementations, and refactors.
• If the answer starts turning into a tutorial, stop and cut back to the decision that matters.
• When a local fix needs clones, locks, trait-object escape hatches, or unsafe code, re-check the design before keeping the patch.

Establish borrow-checker posture