What problem does it solve? Adding a new sensor, display, or peripheral to the espforge ESP32 framework requires coordinated changes across a no_std runtime crate and a host-side code-generation crate, plus YAML examples and compile verification. This Skill guides that entire workflow so nothing is missed. ## Core Features & Use Cases - Dual-crate driver implementation: Creates the no_std runtime wrapper in espforge_devices and the DevicePlugin code generator in espforge_devices_builder, with correct feature flags and module registration. - Driver strategy evaluation: Decides between wrapping an external embedded-hal v1 crate or writing an in-tree driver, using scripts that query crates.io for dependency and async/blocking compatibility. - Reference-backed patterns: Ships canonical I2C (SSD1306), SPI+GPIO (ILI9341), and optional-config (FT6206) templates, plus decision guides for delay handling, init patterns, and common compile errors. - Use Case: Ask to add a BMP180 pressure sensor to espforge; the Skill inspects the chosen crate, writes the runtime device and builder plugin, generates a YAML example, and verifies with cargo build. ## Quick Start Add the bmp180 sensor to espforge using the crate documented in bmp180_api.md and compile the result.