rust-router_skill

Overview

This skill routes all Rust-related questions to the correct analysis and helper skills. It prioritizes error-code lookups, negotiates for comparative or ambiguous queries, and loads domain-specific skills when domain keywords are present. The goal is fast, accurate dispatch so downstream skills return focused, actionable Rust guidance.

How this skill works

The router inspects user input for error codes, keywords (ownership, async, tokio, etc.), domain markers (web, fintech, embedded), and comparison triggers (compare, vs, best practice). It maps signals to a three-layer cognitive framework: Language Mechanics (how), Design Choices (what), and Domain Constraints (why), then loads one or more target skills and returns a negotiated plan when required. It enforces default project settings and error-to-skill routing for consistent responses.

When to use it

• Any Rust question about compilation errors, borrow/lifetime issues, types, traits, or concurrency.
• Design and architecture questions where domain constraints matter (web APIs, embedded, fintech).
• Comparisons (tokio vs async-std) or requests for best practices — negotiation is mandatory.
• When a query includes a Rust error code (E0382, E0597, E0502, etc.).
• When the problem mixes domain context with language mechanics (e.g., trading system + ownership error).

Best practices

• Always include the exact error message, minimal reproducible code, and Cargo.toml details when asking an error question.
• If asking comparisons or best practices, state constraints (performance, safety, runtime) so negotiation can synthesize recommendations.
• Specify domain keywords (web, cli, embedded, fintech) to trigger dual-skill loading for accurate domain guidance.
• Prefer small focused queries to allow the router to pick a single layer; use negotiation for cross-cutting or ambiguous questions.
• Follow the router's negotiation gaps: fill missing context rather than asking follow-ups repeatedly.

Example use cases

• You get E0382: paste the error and small code snippet to route to ownership diagnostics.
• Deciding between tokio and async-std for a web server — router enables negotiation and loads domain-web + concurrency skills.
• Designing error handling strategy for a payment service — loads domain-fintech and domain-error skills.
• Asking why a type mismatch occurs in generics — routes to zero-cost abstraction and trait diagnostics.
• Creating a new Cargo project — enforces default project settings and lint configuration.