skills/rust-mega-eng/SKILL.md
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.
npx skillsauth add bjornmelin/dev-skills rust-mega-engInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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.
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.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.
development
Pre-PR multi-model review, parallel opus and codex exec adversarial lanes, then adversarial verification of merged findings. Read-only. Use before shipping nontrivial diffs.
tools
Independent gpt-5.6 diff review via the Codex CLI, normal or steerable adversarial with JSON findings. Use before shipping nontrivial changes.
development
Delegate implementation, investigation, or bulk work to gpt-5.6 codex via pinned codex exec. Use for clear-spec builds, migrations, debugging, or any task MODELS.md routes to codex.
development
Adversarial pre-mortem: imagine the plan failed, work backwards to surface risky assumptions + irreversible bets, then harden them. Proactively offer it (after the current request; confirm first) before a hard-to-reverse or one-way-door call (API, schema, framework, a hire), an all-upside plan, or unvalidated assumptions. Also on request.