Rust Mega Eng

Use this skill as the explicit orchestration layer for broad Rust architecture and product engineering work. For ordinary local Rust edits, use rust-expert or a specialist skill instead.

Invocation Rule

Do not invoke this skill implicitly for normal Rust questions, compiler errors, single-crate fixes, broad architecture wording, or isolated CLI/TUI/Tauri/service work. Invoke only when the user explicitly names rust-mega-eng for broad, cross-cutting Rust architecture and execution planning.

Operating Model

1. Map the product surface: libraries, binaries, services, desktop apps, terminal UI, deployment targets, public APIs, and release obligations.
2. Identify canonical ownership: crate boundaries, app/service boundaries, shared domain types, generated code, test fixtures, config, docs, and CI gates.
3. Choose leverage first: mature crates, official frameworks, platform conventions, and repo-native workflows before custom infrastructure.
4. Split delivery into reviewable lanes: architecture/design, code movement, behavior changes, test hardening, release/distribution, and docs.
5. Keep a decision ledger for major choices, with explicit tradeoffs and verification evidence.

Reference Map

• references/orchestration.md for workspace strategy, crate portfolio defaults, decision scoring, fanout planning, release engineering, and anti-patterns.