What problem does it solve? Translating hardware register specifications into correct, tested code is error-prone: sign extension, bit alignment, duplicate encodings, and out-of-range handling are easy to get wrong and hard to review. This Skill turns a canonical device spec into a Zig 0.16 project with tested conversion functions and a documented manifest of every encoding decision. ## Core Features & Use Cases - Spec-Driven Function Generation: Reads a canonical test specification and creates separate Zig functions for register-to-real-world conversions and complex logic such as CRC calculations, each with unit tests. - Contradiction and Edge-Case Resolution: Enforces mandatory policies for conflicting spec statements (worked-example tables win over prose formulas), duplicate encodings like sign/magnitude ±0, and explicit overflow policies (clamp, wrap, or error) per encode function. - Conversions Manifest: Produces a mandatory manifest recording each function's worked example, exact bit layout, and out-of-range policy, serving as the single source of truth for downstream skills. - Use Case: Given a temperature sensor datasheet spec, generate a Zig project where raw register values like 0x1500 decode to 21.0 °C, with tests derived from the spec's worked examples and all encoding decisions documented. ## Quick Start Create a Zig 0.16 project with tested data conversion functions from the device spec at artifacts/<device>/outputs/spec_<device>.md.
