rust-architecture

To structure a Rust workspace, you need a virtual manifest and clear dependency direction layering. This skill helps you split modules into crates based on concrete drivers like team size and deployment independence to ensure maintainable growth.

Organizing Rust module organization during a monolith refactor requires diagnosing failure modes like crate sprawl and accidental common crates. This skill provides trade-off-based reasoning to propose the lowest-cost fix for your directory layout and visibility boundaries.

Choosing between anyhow and thiserror for Rust error handling depends on your layering model. This skill helps you select a hybrid error strategy that keeps domain code isolated from adapters and infrastructure.

You need to separate sync core from async edges to prevent async from polluting pure logic. This skill diagnoses accidental async in pure logic and helps you choose the right sync-core/async-edge boundaries for your runtime targets.

Splitting a large Rust service into crates often risks accidental common crates and dependency cycles. This skill applies an explicit acyclic layering model to ensure crate boundaries match your scale constraints without visibility mismatches.

Rust workspace architecture supports planning for future microservices by choosing between a modular monolith or split crates based on deployment independence. This skill guides trade-off decisions to structure modules for maintainable growth and runtime targets.