m01-ownership

Rust borrow checker errors like E0382 occur when ownership and borrowing rules are violated. This skill guides a layered analysis of data ownership to map lifetime requirements and identify fixes for move-out issues without runtime changes.

To fix E0597 lifetime errors, you must add explicit lifetime annotations to your Rust structs and APIs. This skill provides pattern-driven guidance for enforcing lifetime constraints and resolving scope mismatches across modules.

The best way to share data across Rust modules while satisfying the borrow checker is using Arc or Rc wrappers. This skill provides anti-patterns and practical examples for proper sharing via Arc/Rc and references.

Resolving Rust move semantics issues requires using borrowing where possible instead of transferring ownership. This skill helps you walk through layered reasoning to identify ownership boundaries and apply appropriate fixes across functions.

You need explicit lifetime annotations in Rust when the compiler cannot infer the relationships between references, often in structs and APIs. This skill helps diagnose these constraints and enforces proper annotations to resolve errors.