What problem does it solve? Writing a Wokwi custom chip requires correctly modeling a device's register encoding, pin behavior, and bus protocol against the Wokwi Chips API, and small encoding mistakes silently produce wrong simulation results. This Skill provides a deterministic pipeline that reuses validated conversion functions, enforces unit-tested register encoding, and validates the chip with zig build test before delivery. ## Core Features & Use Cases - Zig 0.16 chip generation: Produces chip.zig implementing the Wokwi Custom Chips API (GPIO, I2C, SPI, UART, attributes, timers) compiled to WebAssembly. - Canonical conversion reuse: Ports previously validated register-to-real-world-value conversion functions verbatim instead of re-deriving encodings from potentially inconsistent datasheets. - Mandatory unit testing: Requires test blocks asserting exact encoded register values, validated via zig fmt, zig build, and zig build test before outputs are copied. - Use Case: Given a device spec and test spec for a temperature sensor like the TMP102, generate a Wokwi I2C custom chip whose temperature register encoding is unit-tested against known values, with the address derived from a strapped ADD0 pin rather than a fake attribute. ## Quick Start Create a Wokwi custom chip for the tmp102 device in Zig 0.16 using the spec and test spec in the outputs directory.