Designing Hardware Products

What it does

When your agent uses it

• Tasks that involve Embedded systems

Example prompts

• “/designing-hardware-products”

Requirements

• Python 3
• Node.js
• Pre-approved tools (allowed-tools): Read, Bash, Write, Edit, Agent, Workflow

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

1. 1MCU selection — ESP32-C3 (BLE+WiFi, RISC-V, cheap) vs ESP32-S3 (AI, USB) vs STM32 (low power) vs nRF (BLE-only)
2. 2HV topology — if product needs high voltage (mosquito swatter, taser), see references/hv-design.md
3. 3PCB form factor — match physical product shape, not default rectangle
4. 4App framework — UniApp (WeChat+Android+iOS) vs React Native vs Flutter

What it can do on your machine

Read from SKILL.md and the folder at commit 2544577. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Bash
  • Write
  • Edit
  • Agent
  • Workflow

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • npx

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Designing Hardware Products loads about 788 tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 197 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~69

When it runs · the whole SKILL.md, loaded when a task matches

~788

With references · SKILL.md plus every file in references/, read only if the agent opens them

~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

  allowed-tools: Read, Bash, Write, Edit, Agent, Workflow

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from telagod/code-abyss at commit 2544577, republished under its MIT licence (© telagod). 197 words, ~788 tokens.

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.

allowed-tools

Read, Bash, Write, Edit, Agent, Workflow

user-invocable

true

argument-hint

<product-brief: MCU, sensors, features, form-factor>

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

/designing-hardware-products "BLE mosquito swatter with kill counting, ESP32-C3, 30x100mm PCB strip"

© telagod, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/designing-hardware-products of telagod/code-abyss.

• SKILL.md
• references/esp-idf-patterns.md
• references/hv-design.md
• references/kicad9-quirks.md
• references/pipeline-phases.md
• references/uniapp-patterns.md

Open the folder on GitHubat commit 2544577