domain-embedded

What problem does it solve?

Writing robust embedded Rust is hard without standard libraries and safe interrupt handling. This skill defines domain constraints and Rust implications to guide correct hardware ownership and ISR-safe patterns, reducing risk of heap usage, data races, and unsafe misuse.

Core Features & Use Cases

• Domain rules for bare-metal Rust: No_std, deterministic memory, and ISR safety through patterns like Mutex<RefCell<T>> and HAL singletons.
• Hardware ownership model: Use take() to acquire peripherals and avoid conflicts across components.
• Guided design decisions: Layered view from PAC to HAL to Framework (RTIC/Embassy) to enforce safe concurrency and resource ownership in firmware.

Quick Start

Create a no_std embedded project, declare peripherals as HAL singletons with take().unwrap(), and implement a minimal ISR that toggles a GPIO using a mutex-protected shared state.