What problem does it solve? Rust changes in large Cargo workspaces often land in the wrong crate, break architectural boundaries, or pass with lingering warnings. This Skill enforces Ordo's crate ownership rules, dependency discipline, and verification gates so fixes address root causes instead of symptoms. ## Core Features & Use Cases - Crate Boundary Enforcement: Maps behavior to the correct owning crate (protocol, bus, runtime, MCP, plugins, jobs, memory/RAG, security, transport, Tauri backend) and keeps contracts in shared lower crates. - Dependency and Error Rules: Requires workspace dependency versions, minimal feature flags, typed actionable errors, and no hidden side effects or duplicate UI surfaces. - Verification Gates: Mandates cargo check, test, and clippy per crate or workspace, plus npm Tauri checks for Ordo Studio, with zero-warning completion criteria. - Use Case: When asked to fix a compile error in an Ordo provider crate, the Skill identifies the owning crate, repairs the root cause, adds regression tests, and runs the appropriate cargo gates before reporting. ## Quick Start Ask the assistant to fix the clippy warnings in the Ordo MCP client crate and verify the change with the proper cargo gates.
