| name | designing-hardware-products |
| description | AI-automated hardware product pipeline: from requirements to manufacturable Gerber + compiled firmware + cross-platform app. Orchestrates system design, ESP-IDF firmware, KiCad PCB, UniApp client, and release packaging in a zero-human-touch flow. |
| user-invocable | true |
| argument-hint | <product-brief: MCU, sensors, features, form-factor> |
| allowed-tools | Read, Bash, Write, Edit, Agent, Workflow |
Designing Hardware Products
From empty directory to shippable product. Requirements in, Gerber + .bin + .apk out.
When to use
| Scenario | Use | Why |
|---|
| New IoT / embedded product from scratch | Yes | Full pipeline |
| Adding BLE app to existing hardware | Partial | Phase 4 only |
| PCB redesign with existing firmware | Partial | Phase 3 only |
| One-off breadboard prototype | No | Overkill, just wire it |
Pipeline phases
Phase 1: System Design โ DESIGN.md (architecture, topology, protocol)
Phase 2: Firmware โ ESP-IDF components, FreeRTOS tasks, BLE GATT
Phase 3: Hardware โ KiCad schematic โ PCB โ route โ DRC โ Gerber
Phase 4: Mobile App โ UniApp (BLE, i18n, dev mode, SVG icons)
Phase 5: Verify + Package โ build all โ zip release
Each phase is independently re-runnable. Skip phases that already exist.
Key decision points
- MCU selection โ ESP32-C3 (BLE+WiFi, RISC-V, cheap) vs ESP32-S3 (AI, USB) vs STM32 (low power) vs nRF (BLE-only)
- HV topology โ if product needs high voltage (mosquito swatter, taser), see references/hv-design.md
- PCB form factor โ match physical product shape, not default rectangle
- App framework โ UniApp (WeChat+Android+iOS) vs React Native vs Flutter
Companion skills
- operating-kicad-eda โ Phase 3 detail, KiCad MCP tool routing
- developing-software โ firmware language patterns (C for ESP-IDF)
- developing-mobile-apps โ app framework patterns
Usage
/designing-hardware-products "BLE mosquito swatter with kill counting, ESP32-C3, 30x100mm PCB strip"
References
Exit criteria
