embedded-guru 0.2.0

Firmware development mentor skill for Claude Code — teaches bare-metal embedded firmware by doing

⚡ EmbeddedGuru

Firmware development mentor for Claude Code — adaptive, project-driven, no hand-holding.

---

What is this?

EmbeddedGuru is a Claude Code skill that teaches bare-metal embedded firmware like a senior engineer would — by making you build things, not by explaining things.

It doesn't write your code. It asks what the peripheral status register says. It assigns real hardware tasks with specific exit criteria. It remembers where you left off, tracks your progress across sessions, and pushes back when you try to copy-paste your way through a concept.

It knows about registers, not libraries. It knows about datasheets, not tutorials.

---

Four Domain Tracks

Track	Hardware	Protocols	Standards
IoT	ESP32 · STM32	UART · I2C · SPI · MQTT	—
Automotive / CAN	STM32 · CAN transceiver	CAN · OBD-II · UDS · ISO-TP	ISO 11898 · ISO 14229
Medical	STM32 · ADC frontend	I2C · SPI · ADC · IWDG	IEC 62304 · IEC 60601-1
Industrial / RTOS	STM32 · RS-485	FreeRTOS · Modbus RTU · DMA	IEC 61508 · MISRA-C

Every track shares a common foundation: GPIO → UART → I2C → SPI → DMA — from registers, not libraries.

---

How it works

pipx install embedded-guru          # install the CLI
embeddedguru install                 # seeds Claude Code with skill + curriculum graph
/guru                                # start your first session

Behind the scenes, the installer:

1. Copies the SKILL.md mentor brain into ~/.claude/skills/embedded-guru/
2. Copies the curriculum knowledge base (protocols, registers, boards, standards) into ~/.claude/embedded_guru/curriculum/
3. Builds a knowledge graph with Graphify — every protocol fact and register value becomes a graph node the mentor queries instead of hallucinating
4. Registers the /guru trigger in ~/.claude/CLAUDE.md

Every session end, your student graph (profile, assignments, milestones, progress) is updated — so the mentor always knows exactly where you are.

---

Knowledge Graph Architecture

~/.claude/embedded_guru/
├── curriculum/
│   ├── concepts/        UART · SPI · I2C · CAN · DMA · FreeRTOS · watchdog
│   ├── hardware/        boards, peripherals, capabilities
│   ├── milestones/      IoT · Automotive · Medical · Industrial roadmaps
│   ├── mistakes/        10 common hardware + firmware mistakes
│   ├── standards/       MISRA-C · ISO 26262 · IEC 62304 · Modbus
│   └── graphify-out/
│       └── graph.json   ← curriculum facts (read-only, seeded at install)
│
└── <your-name>/
    └── graphify-out/
        └── graph.json   ← your profile, progress, assignments (updated each session)

Before generating any output, the mentor queries the graph:

graphify query "I2C pull-up resistor value" --graph ~/.claude/embedded_guru/curriculum/graphify-out/graph.json
# → returns verified fact from curriculum, not a hallucinated value

---

Prerequisites

• Claude Code installed
• Python 3.9+
• pipx

Install pipx:

brew install pipx        # macOS
sudo apt install pipx    # Linux
pip install pipx         # Windows

---

Install

pipx install embedded-guru
embeddedguru install

Note: Run embeddedguru install from Claude Code's built-in terminal — it has your ANTHROPIC_API_KEY available for the one-time curriculum graph build.

Then open Claude Code and type /guru.

---

Upgrade

pipx upgrade embedded-guru
embeddedguru install

---

Session Commands

Command	What happens
/guru	Start or resume your session
/guru debug	Jump straight into a debugging session
/guru roadmap	See your current roadmap and next milestone
/guru assignment	Check your open assignments
/guru goal	Review or update your end goal
/guru profile	See your full student profile

---

Install Options

embeddedguru install --dry-run        # preview without making changes
embeddedguru install --skip-graphify  # skip graph build (offline / CI)

---

Uninstall

embeddedguru uninstall          # keeps student data
embeddedguru uninstall --all    # removes everything including progress
pipx uninstall embedded-guru

---

What the mentor will and won't do

Will do

• Assess your real level (L0–L3) from how you answer questions, not what you claim
• Build a custom roadmap for your domain and board
• Assign real hardware tasks with specific exit criteria
• Tell you which register to read when you're stuck
• Push back on code dumps — "I could. You'd fix this bug and forget how."
• Acknowledge frustration before redirecting
• Track everything across sessions — no re-explaining your background each time

Won't do

• Write your firmware for you
• Accept "it works" as a milestone exit — working code + test output required
• Let you skip Milestone 0 (datasheet literacy) regardless of claimed experience
• Pretend a Raspberry Pi 4 is suitable for bare-metal embedded development
• Teach I2C without first asking what pull-up resistor value you used

---

Supported Boards

Board	Domain	Level	Notes
STM32 Nucleo-F446RE	All	L1–L3	Recommended for most tracks
STM32 Nucleo-F411RE	IoT · Medical	L1–L2	Budget option
ESP32-DevKitC	IoT	L1–L2	WiFi/BT built-in
Raspberry Pi Pico	IoT	L1	Good starter board
STM32F103 Blue Pill	All	L2–L3	Cheap, widely available
Arduino Uno	IoT	L0 → L1 only	HAL-only, no bare-metal CAN
Raspberry Pi 4	—	—	⚠ Not suitable for bare-metal embedded

---

Contributing

PRs welcome for curriculum files, new board entries, and regression tests that expose wrong advice.

git clone https://github.com/nikhil-robinson/embedded_guru
cd embedded_guru
pip install -e .
embeddedguru install --dry-run

Open issues at github.com/nikhil-robinson/embedded_guru/issues

---

License

MIT — see LICENSE

---

Built by Nikhil Robinson

If this helped you understand why your I2C bus was stuck at 3am, consider buying a coffee.