rust-coding-engine

Routes Rust development tasks into doctrine references, diagnostic agents, and interop workflows.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/joySUSY/violet-plugin-place --skill rust-coding-engine-joysusy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rust-coding-engine
Source: https://github.com/joySUSY/violet-plugin-place/tree/main/plugins/rust-coding-engine
Command: npx skills add https://github.com/joySUSY/violet-plugin-place --skill rust-coding-engine-joysusy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Rust developers often struggle to find the right guidance for ownership errors, architecture decisions, concurrency choices, and cross-language interop, scattering effort across disconnected notes and donor repositories. This Skill provides a doctrine-first control center that routes Rust-heavy tasks to the correct reference lane, command, or specialist agent. ## Core Features & Use Cases - Doctrine Routing: A pressure-based router maps tasks to canonical lanes covering foundations, architecture, async/concurrency, error patterns, production, quality, ecosystem, and interop. - Specialist Agents: Bounded agents diagnose borrow-checker failures, review architecture, scout FFI/interop paths (PyO3, NAPI-RS, WASM, Tauri), and analyze performance bottlenecks. - Compile-and-Check Script: A Python script creates a temporary Cargo project, auto-detects dependencies from use statements, runs cargo check, and formats code with rustfmt. - Use Case: When you hit a borrow-checker error like "value moved here", invoke the engine to classify the failure, identify the ownership boundary, and get the exact doctrine file and fix family to apply next. ## Quick Start Ask the assistant to diagnose your Rust borrow-checker error or choose the right concurrency pattern for your workload using the rust-coding-engine skill.

Frequently Asked Questions about rust-coding-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a Rust borrow checker error?▼

Use the borrow-checker-diagnostician agent or the diagnose/borrow-checker command to classify the failure, identify the ownership boundary, and get the smallest correct architectural fix. It avoids reflexive fixes like clone-spam or blind lifetime annotations.

How do I choose between Tokio, rayon, channels, and locks in Rust?▼

Use the choose-concurrency-pattern route command, which applies workload-shape-first doctrine from the async-concurrency lane. It matches your task's scheduling and coordination pressure to the right runtime, channel, or synchronization model.

What Rust interop path should I use for Python, Node, or WASM?▼

The ffi-interop-scout agent and choose-interop-path command route you to the correct lane: PyO3 with Maturin for Python, NAPI-RS for Node, wasm-bindgen with ts-rs or tsify for WASM/TypeScript, and Tauri core-shell boundaries for desktop apps.

Does the cargo check script require specific dependencies?▼

The script auto-detects dependencies from use statements in your code and writes them into a temporary Cargo.toml. It includes enhanced configurations for common crates like serde, tokio, reqwest, and clap with the right features enabled.

When should I not use this engine for a task?▼

Route outward when the real bottleneck belongs to another engine: TypeScript consumer ergonomics belong to typescript-coding-engine, Python consumer ergonomics to python-dev-skill, and general plugin or cross-platform operations to developer-tool.