
Domain Embedded
- 1.2k installs
- 1.3k repo stars
- Updated May 24, 2026
- actionbook/rust-skills
domain-embedded is a Rust skill for no_std embedded constraints on microcontrollers.
About
The domain-embedded skill defines Layer 3 domain constraints for embedded and no_std Rust on microcontrollers and bare-metal targets. Rules forbid heap allocation, require interrupt-safe shared state with critical sections, and enforce HAL peripheral ownership to prevent conflicting hardware access. It maps constraints to heapless collections, Mutex patterns, and singleton peripherals across ARM, RISC-V, ESP32, STM32, and nRF platforms. Agents trace embedded decisions down to companion concurrency and lifecycle skills for firmware services. no_std and no-heap embedded Rust domain constraints. Interrupt-safe shared state with critical sections. HAL peripheral ownership and singleton patterns. heapless collections and static buffer sizing. Targets MCU, bare metal, and firmware HAL workflows. Apply embedded no_std Rust constraints for microcontrollers, HAL ownership, and interrupt safety.
- no_std and no-heap embedded Rust domain constraints.
- Interrupt-safe shared state with critical sections.
- HAL peripheral ownership and singleton patterns.
- heapless collections and static buffer sizing.
- Targets MCU, bare metal, and firmware HAL workflows.
Domain Embedded by the numbers
- 1,196 all-time installs (skills.sh)
- +48 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #356 of 4,386 Backend & APIs skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
What domain-embedded says it does
RULE: Cannot use heap (no allocator)
npx skills add https://github.com/actionbook/rust-skills --skill domain-embeddedAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.2k |
|---|---|
| repo stars | ★ 1.3k |
| Security audit | 2 / 3 scanners passed |
| Last updated | May 24, 2026 |
| Repository | actionbook/rust-skills ↗ |
What Rust patterns satisfy embedded no_std and interrupt safety requirements?
Apply embedded no_std Rust constraints for microcontrollers, HAL ownership, and interrupt safety.
Who is it for?
Rust developers building MCU firmware, HAL drivers, or bare-metal systems.
Skip if: Skip for hosted std Rust servers without embedded hardware constraints.
When should I use this skill?
User builds embedded Rust, no_std firmware, HAL code, or MCU projects.
What you get
Constraint-backed firmware designs with heapless data and HAL ownership.
- embedded Rust guidance
- domain-constraint-aware code suggestions
By the numbers
- Activates on 2 globs: Cargo.toml and .cargo/config.toml
Files
Project Context (Auto-Injected)
Target configuration: !cat .cargo/config.toml 2>/dev/null || echo "No .cargo/config.toml found"
---
Embedded Domain
Layer 3: Domain Constraints
Domain Constraints → Design Implications
| 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 |
---
Critical Constraints
No Dynamic Allocation
RULE: Cannot use heap (no allocator)
WHY: Deterministic memory, no OOM
RUST: heapless::Vec<T, N>, arraysInterrupt Safety
RULE: Shared state must be interrupt-safe
WHY: ISR can preempt at any time
RUST: Mutex<RefCell<T>> + critical sectionHardware Ownership
RULE: Peripherals must have clear ownership
WHY: Prevent conflicting access
RUST: HAL takes ownership, singletons---
Trace Down ↓
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 Stack
| Layer | Examples | Purpose |
|---|---|---|
| PAC | stm32f4, esp32c3 | Register access |
| HAL | stm32f4xx-hal | Hardware abstraction |
| Framework | RTIC, Embassy | Concurrency |
| Traits | embedded-hal | Portable drivers |
Framework Comparison
| Framework | Style | Best For |
|---|---|---|
| RTIC | Priority-based | Interrupt-driven apps |
| Embassy | Async | Complex state machines |
| Bare metal | Manual | Simple apps |
Key Crates
| 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 |
Design Patterns
| 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> |
Code Pattern: Static Peripheral
#![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();
}
});
}
}---
Common Mistakes
| 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 |
---
Trace to Layer 1
| 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] |
---
Related Skills
| When | See |
|---|---|
| Static memory | m02-resource |
| Interior mutability | m03-mutability |
| Interrupt patterns | m07-concurrency |
| Unsafe for hardware | unsafe-checker |
Related skills
Forks & variants (1)
Domain Embedded has 1 known copy in the catalog totaling 639 installs. They canonicalize to this original listing.
- zhanghandong - 639 installs
How it compares
Choose Domain Embedded over general Rust skills when writing firmware or bare-metal MCU code with no_std, HAL, and interrupt constraints.
FAQ
Can heap allocation be used?
No; heapless static buffers and arrays are required in embedded domains.
How is ISR state handled?
Mutex with critical sections for interrupt-safe shared state.
Which platforms are referenced?
ARM, RISC-V, ESP32, STM32, nRF, and bare-metal MCU targets.
Is Domain Embedded safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.