skills/domain-embedded/SKILL.md
Use when developing embedded/no_std Rust. Keywords: embedded, no_std, microcontroller, MCU, ARM, RISC-V, bare metal, firmware, HAL, PAC, RTIC, embassy, interrupt, DMA, peripheral, GPIO, SPI, I2C, UART, embedded-hal, cortex-m, esp32, stm32, nrf, 嵌入式, 单片机, 固件, 裸机
npx skillsauth add actionbook/rust-skills domain-embeddedInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Target configuration:
!cat .cargo/config.toml 2>/dev/null || echo "No .cargo/config.toml found"
Layer 3: Domain Constraints
| Domain Rule | Design Constraint | Rust Implication | |-------------|-------------------|------------------| | No heap | Stack allocation | heapless, no Box/Vec | | No std | Core only | #![no_std] | | Real-time | Predictable timing | No dynamic alloc | | Resource limited | Minimal memory | Static buffers | | Hardware safety | Safe peripheral access | HAL + ownership | | Interrupt safe | No blocking in ISR | Atomic, critical sections |
RULE: Cannot use heap (no allocator)
WHY: Deterministic memory, no OOM
RUST: heapless::Vec<T, N>, arrays
RULE: Shared state must be interrupt-safe
WHY: ISR can preempt at any time
RUST: Mutex<RefCell<T>> + critical section
RULE: Peripherals must have clear ownership
WHY: Prevent conflicting access
RUST: HAL takes ownership, singletons
From constraints to design (Layer 2):
"Need no_std compatible data structures"
↓ m02-resource: heapless collections
↓ Static sizing: heapless::Vec<T, N>
"Need interrupt-safe state"
↓ m03-mutability: Mutex<RefCell<Option<T>>>
↓ m07-concurrency: Critical sections
"Need peripheral ownership"
↓ m01-ownership: Singleton pattern
↓ m12-lifecycle: RAII for hardware
| Layer | Examples | Purpose | |-------|----------|---------| | PAC | stm32f4, esp32c3 | Register access | | HAL | stm32f4xx-hal | Hardware abstraction | | Framework | RTIC, Embassy | Concurrency | | Traits | embedded-hal | Portable drivers |
| Framework | Style | Best For | |-----------|-------|----------| | RTIC | Priority-based | Interrupt-driven apps | | Embassy | Async | Complex state machines | | Bare metal | Manual | Simple apps |
| Purpose | Crate | |---------|-------| | Runtime (ARM) | cortex-m-rt | | Panic handler | panic-halt, panic-probe | | Collections | heapless | | HAL traits | embedded-hal | | Logging | defmt | | Flash/debug | probe-run |
| Pattern | Purpose | Implementation |
|---------|---------|----------------|
| no_std setup | Bare metal | #![no_std] + #![no_main] |
| Entry point | Startup | #[entry] or embassy |
| Static state | ISR access | Mutex<RefCell<Option<T>>> |
| Fixed buffers | No heap | heapless::Vec<T, N> |
#![no_std]
#![no_main]
use cortex_m::interrupt::{self, Mutex};
use core::cell::RefCell;
static LED: Mutex<RefCell<Option<Led>>> = Mutex::new(RefCell::new(None));
#[entry]
fn main() -> ! {
let dp = pac::Peripherals::take().unwrap();
let led = Led::new(dp.GPIOA);
interrupt::free(|cs| {
LED.borrow(cs).replace(Some(led));
});
loop {
interrupt::free(|cs| {
if let Some(led) = LED.borrow(cs).borrow_mut().as_mut() {
led.toggle();
}
});
}
}
| Mistake | Domain Violation | Fix | |---------|-----------------|-----| | Using Vec | Heap allocation | heapless::Vec | | No critical section | Race with ISR | Mutex + interrupt::free | | Blocking in ISR | Missed interrupts | Defer to main loop | | Unsafe peripheral | Hardware conflict | HAL ownership |
| Constraint | Layer 2 Pattern | Layer 1 Implementation | |------------|-----------------|------------------------| | No heap | Static collections | heapless::Vec<T, N> | | ISR safety | Critical sections | Mutex<RefCell<T>> | | Hardware ownership | Singleton | take().unwrap() | | no_std | Core-only | #![no_std], #![no_main] |
| When | See | |------|-----| | Static memory | m02-resource | | Interior mutability | m03-mutability | | Interrupt patterns | m07-concurrency | | Unsafe for hardware | unsafe-checker |
development
CRITICAL: Use for ALL Rust questions including errors, design, and coding. HIGHEST PRIORITY for: 比较, 对比, compare, vs, versus, 区别, difference, 最佳实践, best practice, tokio vs, async-std vs, 比较 tokio, 比较 async, Triggers on: Rust, cargo, rustc, crate, Cargo.toml, 意图分析, 问题分析, 语义分析, analyze intent, question analysis, compile error, borrow error, lifetime error, ownership error, type error, trait error, value moved, cannot borrow, does not live long enough, mismatched types, not satisfied, E0382, E0597, E0277, E0308, E0499, E0502, E0596, async, await, Send, Sync, tokio, concurrency, error handling, 编译错误, compile error, 所有权, ownership, 借用, borrow, 生命周期, lifetime, 类型错误, type error, 异步, async, 并发, concurrency, 错误处理, error handling, 问题, problem, question, 怎么用, how to use, 如何, how to, 为什么, why, 什么是, what is, 帮我写, help me write, 实现, implement, 解释, explain
development
Internal maintenance support for checking and fixing generated Rust skill documentation references. Use only when explicitly invoked by /fix-skill-docs.
development
Internal command support for dynamic Rust crate skill management. Use only when explicitly invoked by /sync-crate-skills, /clean-crate-skills, or /update-crate-skill.
tools
Internal support skill for agent-browser CLI workflows used by rust-learner, docs-researcher, and crate-researcher. Use only when browser automation is explicitly required.