greatwallisme

Production-grade Rust concurrency: threads, atomics, async/await, lock-free data structures, memory ordering, ABA problem, executor design, NUMA, work-stealing, deadlock prevention. Use when: building high-concurrency systems, implementing lock-free algorithms, debugging race conditions, optimizing async runtimes, or handling synchronization primitives.

Expert guidance for embedding Lua in Rust using the mlua crate (https://github.com/mlua-rs/mlua). Use this skill whenever the user is working with mlua, embedding Lua scripting in Rust, writing Lua bindings, creating UserData types, calling Lua from Rust or Rust functions from Lua, using mlua async/await, serde integration, native Lua modules in Rust, or any mlua API question. Trigger on: "mlua", "embed lua in rust", "lua bindings rust", "UserData", "lua_module", "create_function", "LuaResult", "Lua::new", "chunk! macro", "mlua coroutine", "mlua async". Always use this skill before writing any mlua code — even simple examples.

Expert guidance on Rust design patterns, idioms, and anti-patterns combining rust-unofficial/patterns and fadeevab/design-patterns-rust GoF implementations. MUST use when: (1) implementing any GoF pattern in Rust (Builder, Factory, Strategy, Observer, State, etc.), (2) choosing between trait objects vs generics vs enums for polymorphism, (3) encountering borrow checker blocking desired design, (4) asking `idiomatic Rust way to X` or `Rust equivalent of X pattern`, (5) designing FFI boundaries, (6) reviewing Rust code for anti-patterns, (7) structuring ownership for complex state machines,(8) implementing self-referential or recursive data structures. Keywords: design pattern, GoF, idiom, trait object, static dispatch, dynamic dispatch, newtype, RAII, builder, factory, strategy, state, observer, mediator, adapter, decorator, proxy, singleton, prototype, anti-pattern, borrow checker.

Strict Rust code auditor and fixer agent. Uses cargo check, cargo test, cargo clippy, cargo doc, cargo fmt to comprehensively scan all errors and warnings in a project, fixing them one by one according to strictest standards until all checking tools report zero issues. Use when user asks to "audit/fix Rust code quality", "clean clippy warnings", "pre-release code quality check", "zero rust audit", "fix rust compiler errors", "make rust code production ready", "strictest rust lint", "cargo clippy fix all", "resolve rustc warnings", "format rust code", "fix cargo doc warnings". Core constraint: Never bypass issues by modifying Cargo.toml [lints] configuration, adding #![allow(...)] global attributes, or lowering check standards.

Implement hexagonal (ports and adapters) architecture in Rust with clean separation between business logic and external dependencies. Use when: (1) User explicitly asks for "hexagonal architecture", "ports and adapters", or "clean architecture" in Rust, (2) Building testable services requiring clear boundaries between domain and infrastructure, (3) Multi-team projects (3+ developers) where coordination needs clear contracts, (4) Projects with expected lifetime 12+ months, (5) Domain-driven design with bounded contexts requiring isolation, (6) Applications where requirements change frequently and adapters need swapping.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Production-grade Rust concurrency: threads, atomics, async/await, lock-free data structures, memory ordering, ABA problem, executor design, NUMA, work-stealing, deadlock prevention. Use when: building high-concurrency systems, implementing lock-free algorithms, debugging race conditions, optimizing async runtimes, handling synchronization primitives, choosing channel types (mpsc/crossbeam/flume/tokio), working with DashMap/ArcSwap/parking_lot, or asking about thread patterns (scoped threads, ThreadLocal, park/unpark, affinity, priority).

ALWAYS invoke this skill BEFORE writing or modifying ANY Rust code (.rs files) even for simple Hello World programs. Enforces Microsoft-style Rust development discipline, zero-tolerance quality standards (zero errors, zero warnings), and requires consulting the appropriate guideline files before any coding activity. This skill is MANDATORY for all Rust development.

Implement hexagonal (ports and adapters) architecture in Rust with clean separation between business logic and external dependencies. Use when: (1) User explicitly asks for `hexagonal architecture`, `ports and adapters`, or `clean architecture` in Rust, (2) Building testable services requiring clear boundaries between domain and infrastructure, (3) Multi-team projects (3+ developers) where coordination needs clear contracts, (4) Projects with expected lifetime 12+ months, (5) Domain-driven design with bounded contexts requiring isolation, (6) Applications where requirements change frequently and adapters need swapping.