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
- Map the product surface: libraries, binaries, services, desktop apps, terminal UI, deployment targets, public APIs, and release obligations.
- Identify canonical ownership: crate boundaries, app/service boundaries, shared domain types, generated code, test fixtures, config, docs, and CI gates.
- Choose leverage first: mature crates, official frameworks, platform conventions, and repo-native workflows before custom infrastructure.
- Split delivery into reviewable lanes: architecture/design, code movement, behavior changes, test hardening, release/distribution, and docs.
- 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.
Use the specialist skills for detailed implementation:
rust-cli-clap for CLI and clap command surfaces.rust-tui-ratatui for terminal UI architecture.rust-tauri-apps for Tauri v2 Rust app backends and IPC.rust-web-services for Axum/Tokio/Tower services.rust-expert for core Rust ownership, async, errors, crates, testing, performance, and security.
Verification
For broad Rust work, define a validation ladder early:
cargo fmt --all --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test --all-targets --all-features
cargo nextest run --all-targets --all-features
cargo deny check
cargo audit
cargo semver-checks check-release
Run only gates that are relevant and available, but report any skipped gate with the reason.
1---2name: rust-mega-eng3description: Explicit-only Rust architecture orchestrator. Use only when the user explicitly invokes rust-mega-eng for broad Rust ecosystem architecture, multi-crate workspace strategy, large refactors, release engineering, crate selection portfolios, or end-to-end Rust product planning across CLI, TUI, Tauri, services, libraries, CI, security, and distribution.4license: MIT5---6
7# Rust Mega Eng
8
9Use 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.
10
11## Invocation Rule
12
13Do 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.
14
15## Operating Model
16
171. Map the product surface: libraries, binaries, services, desktop apps, terminal UI, deployment targets, public APIs, and release obligations.
182. Identify canonical ownership: crate boundaries, app/service boundaries, shared domain types, generated code, test fixtures, config, docs, and CI gates.
193. Choose leverage first: mature crates, official frameworks, platform conventions, and repo-native workflows before custom infrastructure.
204. Split delivery into reviewable lanes: architecture/design, code movement, behavior changes, test hardening, release/distribution, and docs.
215. Keep a decision ledger for major choices, with explicit tradeoffs and verification evidence.
22
23## Reference Map
24
25- `references/orchestration.md` for workspace strategy, crate portfolio defaults, decision scoring, fanout planning, release engineering, and anti-patterns.
26
27Use the specialist skills for detailed implementation:
28
29- `rust-cli-clap` for CLI and `clap` command surfaces.
30- `rust-tui-ratatui` for terminal UI architecture.
31- `rust-tauri-apps` for Tauri v2 Rust app backends and IPC.
32- `rust-web-services` for Axum/Tokio/Tower services.
33- `rust-expert` for core Rust ownership, async, errors, crates, testing, performance, and security.
34
35## Verification
36
37For broad Rust work, define a validation ladder early:
38
39```bash
40cargo fmt --all --check
41cargo clippy --all-targets --all-features -- -D warnings
42cargo test --all-targets --all-features
43cargo nextest run --all-targets --all-features
44cargo deny check
45cargo audit
46cargo semver-checks check-release
47```
48
49Run only gates that are relevant and available, but report any skipped gate with the reason.
aibot88