What problem does it solve? Rust work in Ordo-style projects often fails through patch-style edits, ignored compiler warnings, hidden side channels, and features shipped without real usage verification. This Skill enforces an architecture-first workflow so changes stay narrow, warning-free, and operator-confirmable. ## Core Features & Use Cases - Architecture-first Rust workflow: Inspect Cargo manifests, module contracts, tests, and callers before implementing, then rebuild affected modules natively instead of patching .rs files. - Warning-denied verification gates: Run cargo check, test, and clippy with RUSTFLAGS='-D warnings', broadening from focused crate checks to workspace checks when shared types or runtime wiring change. - Completion discipline: Require human-like usage tests, a launched app for operator confirmation, milestone notes, and release hygiene that excludes secrets, logs, and personal data. - Use Case: When asked to add a device-pairing feature to an Ordo app, trace the primitive-adapter-provider-orchestrator-UXI slice, implement it with approval-gated writes, pass warning-denied gates, and launch the app for confirmation. ## Quick Start Use the rust-vibe-coder skill to inspect this Rust crate, plan the smallest native change, and verify it with warning-denied cargo checks.
