Designing Hardware Products

This is a full stack hardware development pipeline that takes you from a product brief to Gerber files, compiled ESP-IDF firmware, and a cross-platform mobile app without manual handoffs between phases. It's deliberately opinionated about the toolchain (ESP32 variants, KiCad, UniApp) and orchestrates them through five sequential phases you can run or skip individually. The pitch is zero-human-touch automation, which is ambitious for hardware where physical constraints matter, but the phase structure is solid and the references cover real gotchas like high voltage topology and KiCad 9 quirks. Best for IoT products where you're starting from scratch and comfortable with the ESP-IDF ecosystem. If you're doing something exotic or already have half the stack built, you'll spend time working around the assumptions.

GitHub stars: 224
last updated: Jun 10, 2026

View on GitHub

Install

$ npx -y skills add telagod/code-abyss --skill designing-hardware-products --agent claude-code

Installs into .claude/skills of the current project.

Files

Designing Hardware Products

判断先于执行：决定「是否做 / 选什么 / 如何取舍」（栈、方案、架构、权衡）前，先读领域判断内核 skills/_kernel/hardware/SKILL.md——它管 judgment，本秘典管 execution；冲突时以内核判断为准。

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.