Embedded Systems Engineer makes Claude work through firmware tasks in six steps: analyze constraints, design the architecture, implement drivers, validate with strict compiler flags and static analysis, optimize resources, then test timing and stack use.
Five reference files hold C examples for FreeRTOS patterns, bare-metal microcontroller programming, power management, communication protocols (I2C, SPI, UART, CAN) and memory optimization.
What You Get
- Hardware initialization code for clocks, peripherals and GPIO
- Driver and interrupt handler code with volatile shared state
- FreeRTOS tasks, queues and synchronization
- A resource usage summary for flash, RAM and power
- Notes on timing and optimization choices
Common Use Cases
- Configuring a UART or timer interrupt on an STM32 board
- Structuring sensor reading and processing as FreeRTOS tasks
- Cutting battery drain with sleep and stop modes
- Fitting firmware into limited flash and RAM
What Makes It Unique
The rules are the ones firmware engineers rely on: volatile for registers and ISR-shared variables, short ISRs that defer work to tasks, a watchdog timer, bounded memory allocation and critical sections around shared data. The workflow compiles with -Wall -Werror, runs cppcheck, checks register fields against the datasheet and measures stack headroom and ISR latency before it finishes.
Under The Hood
The skill is a SKILL.md with five reference files and no scripts, and the references load by topic. The instructions name compiler and tooling steps for the agent to run, such as compiling with -Wall -Werror and running cppcheck, and ask the user to confirm timing with a logic analyzer or oscilloscope. The references and templates are C code for STM32 and FreeRTOS that the agent writes into your project. The skill does not fetch web pages or call outside APIs, and does not flash a device by itself.