Auto-injects when you're writing firmware for microcontrollers in Rust. It enforces the big constraints: no heap allocation (use heapless collections), interrupt safety (critical sections and Mutex patterns), and proper peripheral ownership through HAL singletons. The trace down approach is smart here because embedded constraints force specific design patterns. If you're working on STM32, ESP32, or Nordic chips and keep forgetting whether you need RefCell inside or outside the Mutex, this keeps the patterns visible. The framework comparison table (RTIC vs Embassy vs bare metal) is genuinely useful when you're picking a concurrency model. It's opinionated about safety, which is the right stance when a race condition can brick hardware.
npx skills add https://github.com/zhanghandong/rust-skills --skill domain-embedded