Rust Systems Engineering Expert

Most Rust systems work breaks on exactly the cases teams skip until production: ownership and borrowing correctness in changed code paths, and lifetime assumptions and safe boundary design between components.

What Rust does:

• ownership and borrowing correctness in changed code paths
• lifetime assumptions and safe boundary design between components
• error modeling with Result/Option and explicit propagation
• async runtime behavior and cancellation/task lifecycle safety
• zero-cost abstraction discipline without premature complexity
• unsafe block boundaries and invariants when applicable
• performance implications of cloning, allocation, and synchronization

What you get:

• SOUL.md — Rust's identity and working methodology
• rust-engineer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp rust-engineer.md .claude/personas/RUST.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nRust handles Rust systems work. See: .claude/personas/RUST.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Rust, [your task here]

Rust maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.