Define Rust architectural rules for ownership, error design, traits, and async concurrency.
npx skills add https://github.com/Muvon/octomind-tap --skill programming-rust
Please help me install this Agent Skill. Skill: programming-rust Source: https://github.com/Muvon/octomind-tap/tree/main/skills/programming-rust Command: npx skills add https://github.com/Muvon/octomind-tap --skill programming-rust
This Skill helps you avoid common Rust architecture pitfalls that lead to fragile code, borrow-checker fights, and long-term maintenance pain.
Arc<Mutex<_>>, especially across .await, to prevent deadlocks and cancellation bugs.Ask the Skill: “Review my Rust crate’s data flow and propose an ownership-first architecture, including async state handling, error boundaries, and a suggested module layout.”
High-intent search queries and answers about installing and using this skill.
A maintainable Rust architecture relies on ownership-first API design to reduce lifetime complexity and clarify mutation boundaries. By establishing clear data flow and orthogonal trait abstractions, you prevent borrow-checker fights and long-term maintenance pain.
Handling async state in Rust without deadlocks requires using actor and channel patterns over shared mutable state like `Arc<Mutex<_>` across `.await` points. This isolation prevents deadlocks and cancellation bugs by avoiding concurrent lock contention.
Structuring error boundaries in a Rust crate involves defining crate-boundary error enums with clean foreign error conversion. Pair this with minimal, orthogonal trait abstractions to ensure the architecture remains maintainable and avoids unnecessary complexity.
Yes, this Rust architecture guidance works for refactoring existing codebases by applying consistent rules for ownership, error boundaries, and async concurrency. It resolves inconsistent designs to eliminate borrow-checker churn and long-term maintenance pain.
Using `Arc<Mutex<_>` for async concurrency causes maintenance pain in Rust because sharing mutable state across `.await` points frequently leads to deadlocks and cancellation bugs. Actor and channel patterns are recommended to isolate state safely.
You need cargo and clippy as foundational dependencies to review your Rust crate's data flow and module layout effectively. They support the architectural review by validating ownership-first designs, error boundaries, and async state handling.
FalkorDBRun advanced Clippy linting on Rust codebases with pedantic, nursery, and cargo lints, optionally auto-fixing detected issues.
gar-aiDesign Rust error hierarchies with thiserror and anyhow.
nwiizoRefactors ccswarm codebase using Rust-native design patterns like type-state, channels, and actor model.
JakkuSakura...