Embedded Safety Engineer

🛡️ Embedded Safety Engineer

A Smart Claude Code Skill for Professional Embedded Firmware, Real-Time Systems & Hardware-Aware Security

**Current version:** `0.1.0` **Status:** Foundation / Early Release **License:** MIT

**Embedded Safety Engineer** is a modular engineering Skill designed to help Claude Code write, review, refactor, and audit embedded firmware and RTL with explicit attention to hardware constraints, real-time behavior, concurrency, memory safety, reliability, and defensive security.

---

🚀 Why this Skill?

Embedded software is fundamentally different from ordinary application software.

A program can compile successfully and still fail because:

• an ISR takes too long;
• a shared variable is accessed without proper synchronization;
• volatile is incorrectly treated as thread safety;
• CPU and DMA access the same buffer concurrently;
• cache coherency is ignored;
• a protocol parser trusts an attacker-controlled length;
• an integer overflow changes a buffer boundary;
• a watchdog is refreshed by a partially dead system;
• a firmware update accepts an unauthorized image;
• a production debug interface exposes privileged functionality;
• an FPGA design crosses clock domains incorrectly;
• timing constraints do not match the actual hardware architecture.

**Embedded Safety Engineer** adds a hardware-aware engineering layer to Claude Code so that code generation is accompanied by structured safety, reliability, real-time, and security reasoning.

It is designed around:

Discover
   ↓
Detect Hardware / Software Context
   ↓
Classify Risk
   ↓
Load Relevant Rules
   ↓
Threat + Failure Modeling
   ↓
Design
   ↓
Implement
   ↓
Review
   ↓
Verify
   ↓
Report Remaining Risks

---

✨ Key Capabilities

🧠 Smart Context Detection

The Skill first attempts to understand the project instead of blindly applying generic rules.

It looks for evidence such as:

• MCU / SoC / FPGA
• CPU core
• compiler and toolchain
• SDK / HAL /