skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
wedsamuel1230/embedded-engineering-skills84 installs

hardware-tdd

Use when planning tests for Arduino, ESP32, ESP32-S3, Pico, or Pico W firmware; deciding what can run off-target; using Wokwi or simulation; writing host fakes; or accepting a physical hardware feature without confusing compile proof with system proof.

How do I install this agent skill?

npx skills add https://github.com/wedsamuel1230/embedded-engineering-skills --skill hardware-tdd
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    No security issues were found. The skill is entirely instructional, providing guidelines for hardware development and testing without any executable code, network operations, or obfuscation.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Hardware TDD

Build the test ladder before claiming a feature is complete. Pure behavior can often be tested off-target; voltage, pin mux, timing under load, and physical assembly still require target evidence.

Intake

Record exact board/revision, framework/toolchain, hardware invariants, safety inhibits, simulator model, available instruments, test fixtures, and the proof stage required by the user.

Process

  1. Turn requirements into observable behavior and safety invariants.
  2. Write host tests for pure C/C++ logic using fakes for time, serial, sensors, and actuators. Keep hardware adapters thin.
  3. Use Wokwi or another simulator only for peripherals and timing that its model actually represents; record model limitations.
  4. Run an exact-board compile and static checks with the selected toolchain.
  5. Create a one-change target checklist: power-off continuity, controlled power-up, input observation, output inhibit, reset/recovery, and logs.
  6. Ask a physical gate for measurements, photos, or serial output. Do not infer target success from a host test or compile log.
  7. Record failures as evidence and keep the next test bounded.

Test matrix

LayerExampleProvesDoes not prove
Hostdebounce/state/packet parserdeterministic logicpin voltage or wiring
Simulationmodeled sensor/LED/UARTmodeled interactionsregulator, clone, EMI, thermal behavior
Buildexact FQBN/environmentsource and dependency compileupload or behavior
Targetserial, meter, scope, photoobserved hardware behaviorfield reliability unless loaded
Systemintegrated load/failure caserequirement under scenariofuture deployment safety

Anti-rationalization

ShortcutResponse
"The unit test passed."Keep all physical and system stages open.
"Wokwi matches the board."List what the model omits and verify those items on hardware.
"The sketch compiled."Require upload identity and target observations separately.
"The photo proves it works."Require board identity, measurement context, and observed result.
"Mark it done and test later."Keep the loop item blocked or needs-review until evidence exists.

Verification

  • Every requirement maps to a test, proof stage, and artifact path.
  • Host/simulation/build/target/system results are labeled separately.
  • Physical-only steps emit the concrete Physical gate format from embedded-project-loop.
  • Failed and unverified cases remain visible in the report.

Shared output contract

Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, known limitations, and recovery/security notes.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/wedsamuel1230/embedded-engineering-skills/hardware-tdd">View hardware-tdd on skillZs</a>