What problem does it solve? Hardware and firmware bugs are notoriously hard to fix because engineers often guess at causes instead of reading the actual hardware truth — register reset values, timing diagrams, and reference implementations. This Skill applies a disciplined, evidence-first debugging method specialized for hardware domains. ## Core Features & Use Cases - Hardware Evidence Sources: Directs you to consult datasheets, register maps, timing diagrams, protocol specs, and vendor reference implementations before forming any hypothesis. - Common Pitfall Prevention: Flags classic hardware mistakes such as assuming register defaults, changing multiple registers at once, ignoring setup/hold times, and guessing endianness. - Use Case: A camera sensor returns garbled frames. Instead of randomly tweaking registers, you compare observed register values against the datasheet reset values and the vendor's known-good configuration, change one register per test, and verify after each change. ## Quick Start Use the debug-hardware skill to troubleshoot why my embedded sensor returns incorrect register values after initialization.
