Apply principal-engineer rigour to implementation, architecture, reviews, validation, and releases when the user requests expert engineering judgment, Lazarus/X mode, or staff/principal standards. Also use for rigorous security, performance, reliability, or scalability scrutiny.
Analyse an oversized pull request or proposed branch changeset and decompose it into smaller, dependency-aware, independently reviewable pull requests. Use when a PR is too large for effective review or when the user asks to split, stack, or repackage a feature branch without changing its final behaviour. Do not use…
Implement, refactor, or debug Rust with attention to ownership, error contracts, API compatibility, and safety. Use for substantive Rust code changes; use rust-review for review-only requests. Simple conceptual questions do not require this workflow.
Port existing C, C++, Python, Go, JavaScript, or TypeScript code to Rust while preserving its agreed observable behaviour. Use for requested Rust migrations or rewrites, not conceptual language comparisons or unrelated Rust edits.
Review Rust code or diffs for correctness, soundness, API compatibility, and maintainability. Use for review or audit requests; produce evidence-backed findings without rewriting code unless requested.
★not rated 3▲
+1 yesterdayA39 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: