Rust Router

This is a meta-router that decides which specialized Rust skill Claude should load based on your question. It works in three layers: language mechanics (ownership, lifetimes, error codes), design patterns (performance, anti-patterns, domain modeling), and domain constraints (fintech, web, embedded). When you hit a borrow checker error or ask about async patterns, it traces through the layers to pull in the right combination of skills. The negotiation protocol is interesting: it forces Claude to show confidence levels and gaps when you ask comparative questions like "tokio vs async-std" or request best practices. It's essentially a dispatch table with 30+ routing rules, error code lookups, and domain keyword detection. If you work in Rust and want more structured responses that acknowledge what they don't cover, this shapes how Claude approaches your questions.

skills.sh installs: 2.9K
GitHub stars: 1.6K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add actionbook/rust-skills --skill rust-router --agent claude-code

Installs into .claude/skills of the current project.

Files

Rust Question Router

Version: 2.0.0 | Last Updated: 2025-01-22

v2.0: Context optimized - detailed examples moved to sub-files

Meta-Cognition Framework

Core Principle

Don't answer directly. Trace through the cognitive layers first.

Layer 3: Domain Constraints (WHY)
├── Business rules, regulatory requirements
├── domain-fintech, domain-web, domain-cli, etc.
└── "Why is it designed this way?"

Layer 2: Design Choices (WHAT)
├── Architecture patterns, DDD concepts
├── m09-m15 skills
└── "What pattern should I use?"

Layer 1: Language Mechanics (HOW)
├── Ownership, borrowing, lifetimes, traits
├── m01-m07 skills
└── "How do I implement this in Rust?"