zephyr-driver-development — Claude Code skill: full driver lifecycle
zephyr-driver-development is a Claude Code skill for developing Zephyr RTOS drivers in C/C++. It covers bindings, implementation, build integration, and native_sim testing.
no license 1 installs updated 2026-10-24
npx skills add ale-alfaro/dotfiles --skill zephyr-driver-development -a claude-codeWhat zephyr-driver-development does
This skill walks developers through the end-to-end process of creating and maintaining Zephyr RTOS drivers. It structures the work into preparation (clarifying scope, finding reference drivers in $ZEPHYR_BASE, laying out project files), then implementation (writing YAML bindings, C code conforming to subsystem APIs, Kconfig and CMake integration).
The skill covers device model fundamentals: compatible strings, devicetree properties like reg and status, data types (int, string, phandle, phandle-array), and how to organize drivers in drivers/, bindings in dts/bindings/, and tests in the project structure. It includes patterns for device API wiring and instantiation macros specific to the target subsystem.
Requires Zephyr installed with $ZEPHYR_BASE set, knowledge of the target bus (I2C, SPI, etc.), and a target board. Testing uses native_sim and bus emulators to validate drivers without physical hardware.
What it helps with
- write devicetree bindings and C implementation for a new Zephyr driver
- integrate device API and instantiation macros into the driver lifecycle
- configure Kconfig and CMake to register and build the driver
- test a driver on native_sim before deploying to hardware
Example prompts for the agent
- Create an I2C sensor driver using a reference driver from the Zephyr tree
- Generate YAML bindings for an SPI device with registers and GPIO pins
- Organize project files and integrate the driver through CMake
How to install zephyr-driver-development
1Skills CLI (Vercel)
npx skills add ale-alfaro/dotfiles --skill zephyr-driver-development -a claude-code2Manually: put the files in place
~/.claude/skills/zephyr-driver-development/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/zephyr-driver-development/
1Skills CLI (Vercel)
npx skills add ale-alfaro/dotfiles --skill zephyr-driver-development -a codex2Manually: put the files in place
.agents/skills/zephyr-driver-development/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ale-alfaro/dotfiles --skill zephyr-driver-development -a cursor2Manually: put the files in place
.cursor/skills/zephyr-driver-development/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ale-alfaro/dotfiles common/llm/skills/zephyr-driver-development2Manually: put the files in place
.github/skills/zephyr-driver-development/SKILL.md1Skills CLI (Vercel)
npx skills add ale-alfaro/dotfiles --skill zephyr-driver-development -a gemini-cli2Platform CLI
gemini skills install https://github.com/ale-alfaro/dotfiles --path common/llm/skills/zephyr-driver-developmentManually: put the files in place
.devin/skills/zephyr-driver-development/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ale-alfaro/dotfiles --skill zephyr-driver-development -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about zephyr-driver-development
How do I install zephyr-driver-development in Claude Code?
Run npx skills add ale-alfaro/dotfiles --skill zephyr-driver-development -a claude-code, then open ~/.claude/skills/zephyr-driver-development/SKILL.md.
What does zephyr-driver-development do?
It guides the complete driver development workflow: clarifying scope, locating and reusing reference drivers, writing YAML bindings, implementing C code, integrating with Kconfig and CMake, and testing on native_sim.
What do I need to use this skill?
Zephyr installed with $ZEPHYR_BASE set, familiarity with your target bus (I2C, SPI), and the Zephyr project structure. The skill works on Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.