Writing Rust

Overview

Apply this modifier when Rust's ownership, type, error, async, or unsafe rules materially constrain the design. Keep generic implementation work in the primary skill and load only the Rust reference needed for the current pressure.

When to Use

• Ownership and borrowing affect the API or implementation
• Trait, generic, or typestate design is the main question
• Error surfaces, docs, async, or unsafe boundaries need Rust-specific judgment

When Not to Use

• Use engineering as the primary skill for generic implementation structure
• Use test-design when test selection is the primary task
• Use designing-data-intensive-systems for workload or storage architecture

Minimal Workflow