Skip to the content
4 layers130 × 100 mmUsb controlled debug hub, the printed circuit board in 3D

Usb controlled debug hub

misko/prompt2device3

The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

Size
130 × 100 mm
Copper layers
4
Thickness
1.6 mm
Parts
172
Nets
184
Pads
707
Tracks, vias
2,523, 509
Pours
56
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
16 Jul 2026
Updated
3 Nov 2026

Overview

Usb controlled debug hub is an open-source printed circuit board by misko, from the misko/prompt2device repository on GitHub, published under the MIT licence. It is a 4-layer board of 130 × 100 mm with 172 parts on 184 nets, routed with 2,523 tracks and 509 vias.

It is built around the USB2517I-JZX, AP63203QWU and MCP2221A-I/SL, with the TPS56637RPAR, CH224K and TPS259470ARPW among its other parts.

Main components

12

README

README.md

prompt2device

The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

The Crow carrier + pod public design package provides native designs and fabrication exports for the 5-carrier/10-pod prototype batch. It is a subset of the local sealed release, not order authorization.

Prompt to device: give an agent a plain-language hardware brief, work through explicit design, review, and physical-test cycles, and finish with the artifacts needed to manufacture the device—not merely a plausible CAD image.

Quick start

1. Give the PCB skill a brief

text
/pcb-design 3S LiPo input → 4× USB-A outputs at 5 V / 1.5 A each + 1× USB-C output at 5 V / 5 A.

2. See fabricated examples

These two projects show the path from a plain-English request to electrical CAD, mechanical CAD, and fabricated hardware. The prompt cells preserve the compact original wording; the links retain the corresponding design-lineage records. Photographs are bench evidence, not production-qualification claims. Exact provenance and claim limits are in fabricated-examples.md.

pluto-rx2-8way-v5 is the fabricated eight-way RF switch board. Its immutable PCB design archive is v0.2.1-2026-08-14, with a sealed 3D PCB render, and its independently versioned v0.8.0-2026-08-28 enclosure has a corresponding installed-assembly render. That enclosure remains an honest INCOMPLETE candidate pending sliced and printed fit, retention, connector-service, and thermal tests. The PCB archive itself predates fabrication and still records DO-NOT-ORDER; RF first-article measurements remain open. The current human-readable engineering study is RF isolation, leakage paths, and a v6 mitigation strategy.

usb-hub-3s-v3 is the closest existing hardware to the quick-start brief: three USB-A outputs and one USB-C output rather than four USB-A outputs. Its latest sealed and fabricated archive is v1.12-2026-07-28. The bring-up journal records physical v1.12 boards and the replacement assembly's successful no-load regulation checks; full load, transient, and thermal qualification is still open.

The exact v1.12 board also has an independently versioned v0.4.0-2026-08-28 enclosure with a corresponding installed-assembly render. Its authored source and replay instructions remain mutable, while the release is an immutable INCOMPLETE candidate: structural and collision screens pass, but printed fit, connector service, retention, and thermal evidence remain open.

3. Follow the prompt-to-device loop

text
plain-language brief
  → fact locks and architecture
  → schematic, placement, routing, and enclosure development
  ↺ independent review, correction, regeneration, and measurement
  → sealed fabrication and mechanical artifacts
  → first article, physical findings, and the next development cycle

Today the governed output can include:

  • native KiCad schematics and a rendered schematic PDF;
  • the routed KiCad PCB plus Gerbers, drill files, BOM, and CPL for fabrication;
  • top, bottom, and 3D PCB renders plus a STEP assembly;
  • when mechanical work is selected, enclosure source, printable STLs, assembly renders, and clearance evidence; and
  • governed Markdown investigations under each project's 01_docs/reports/.

The pipeline already uses board-level CAD/assembly twins as verification instruments. Governed firmware releases and an integrated product-level digital twin are forward work, tracked by IMP-234 and IMP-236.

What this repository is

prompt2device is a code-first prompt-to-device engineering system. It turns a user brief into generated KiCad source, bounded routing candidates, independently graded fabrication evidence, immutable releases, printable enclosures, and measured first-article records.

The product is the workflow under skills/. Boards under projects/ are its active applications; sealed release folders are immutable evidence, not templates to copy.

Manual commissioning

Clone the repository, create a branch, and save the user's original request as a UTF-8 text file:

bash
git clone https://github.com/misko/prompt2device.git
cd prompt2device
git switch -c codex/my-board

Create the governed project scaffold and choose its capability profile:

bash
python3 skills/pcb-design/scripts/commission_project.py my-board \
  --brief-file /path/to/original-brief.txt \
  --signal-integrity ordinary \
  --assembly jlcpcb \
  --firmware forbidden \
  --target design

Use high_speed_digital for USB and similar controlled digital links. Use rf only when the board intentionally carries RF/microwave signals. Add --foreign-mating when the floorplan consumes geometry from third-party hardware. Run the command with --help for enclosure and target options. Here --assembly jlcpcb selects the populated JLCPCB PCBA evidence path, not merely bare-board fabrication.

The command reports PCB-SCAFFOLD OK and leaves PCB-COMMISSION explicitly INCOMPLETE. It preserves the prompt and creates an executable commission hold; it does not accept requirements, adopt the seeded schema examples, or run a board producer.

Inspect the selected lifecycle before spending engineering time:

bash
python3 skills/pcb-design/scripts/skill_reference_router.py \
  --profile projects/my-board/01_docs/capability-profile.json \
  --at-stage PCB-COMMISSION \
  --json

Then give Codex this instruction:

text
Read and follow skills/pcb-design/SKILL.md for projects/my-board. Preserve the
original brief, close the commission fact locks, and stop at the first evidence
or operator checkpoint. Do not create firmware unless the brief explicitly
asks.

Do not run rebuild_all.sh yet. The scaffold contains visible schema examples and 01_docs/COMMISSIONING-HOLD.md; both rebuild conductors refuse to run until the commission boundary is reviewed and that marker is deliberately removed.

Start with skills/pcb-design/SKILL.md. Its canonical lifecycle and runnable command map is execution-graph.md.

How execution is structured

The repository deliberately separates three layers:

text
capability profile
  -> disclosure graph (what stages/references are selected)
  -> project conductor (what bounded commands actually run)
  -> owning gates (what exact subjects passed)
  -> review/seal/publication/physical claims
  • The router is planning only. Its output is never execution evidence.
  • projects/<name>/03_src/rebuild_all.sh is the full source/schematic conductor. It intentionally pauses at review and operator checkpoints.
  • rebuild_reuse.sh is the deterministic route-authority replay when the schematic is unchanged; route.yaml selects the authenticated source.
  • Fresh route exploration is a separate candidate workflow; canonical rebuild replays the authenticated route source selected by route.yaml.
  • Layout seal, PCB release seal, publication, ordering, and first article are different claims with different owners.

The declarative lifecycle is:

text
commission -> architecture -> sourcing
  -> schematic -> placement -> routing -> layout seal
  -> fabrication -> assembly verification
  -> release review -> release seal
  -> publication | first article -> production

RF context/source/realized/fabrication stages and foreign-mating import are conditional branches. High-speed digital composes inside the ordinary stages. Enclosures have an implemented parallel INCOMPLETE-candidate release stream and may bind an unchanged PCB release without resealing it. Higher readiness still requires the enclosure skill's recomputable CAD and physical evidence. Firmware is currently an explicit handoff, not a governed release stream; IMP-234 tracks that missing boundary.

Skills and authority

SkillOwns
pcb-designCommission, lifecycle composition, backtracking, reviews, release seal, publication, first article.
kicad-pcbTSX/KiCad schematic conversion, netlist/parity, placement, geometry, routing, DRC, SI/RF realization.
jlcpcb-fabGerber/drill/BOM/CPL, stock/population/rotation, JLC CAD twin, manufacturer staging, bring-up cards.
pcb-enclosureMechanical commission, PCB interface binding, independent fasteners, motion/clearance, mesh/physical evidence, enclosure releases.
shopping-listProvenance-bound purchase lists for self-supplied parts.

Authority is singular. A skill links to another owner's procedure rather than copying it. Project contracts.md files own exact artifact membership. Script --help text owns exact flags. improvements.md tracks work and rationale but never overrides an executable gate or accepted ADR.

Repository map

PathPurpose
skills/Reusable workflow, references, tools, and project templates.
projects/Active boards, including manufactured and still-evolving designs.
archived_projects/Retired scaffolds and frozen regression/history units.
docs/Documentation index, accepted ADRs, measured proof, and historical context.
tests/Clean and known-bad fixtures proving gates can both pass and fail.
external_hardware/Measured/cited facts about foreign devices this repo must mate with.
improvements.mdForward work registry and retained improvement history.

See docs/README.md for the documentation authority map.

Design model

The board is generated from committed human-owned source:

  • TSX/tscircuit is the standard schematic authoring front end.
  • Shared scripts convert the circuit, generate KiCad geometry/rules, and grade exact identities. Per-board source is configuration, not a copied backend.
  • KiCad's Python API owns geometry and saves; kicad-cli owns headless ERC/DRC/netlist/export checks.
  • Routing operates on immutable candidates. Only a clean, independently graded candidate can become the promoted route chain.
  • Generated 04_kicad/ is a mutable current snapshot and is never hand-source authority. Immutable history lives under release streams.

This makes design changes diffable and rebuildable. It also means a generator defect can become a physical defect, so freshness, parity, nonzero coverage, registered models, and independent review are first-class gates.

Claims and releases

A release is an immutable reviewed candidate archive. It is not automatically an order event. A design can be electrically sound and sealed while remaining DO-NOT-ORDER because stock, uploader selections, physical fit, or first- article evidence is owed.

PCB and enclosure versions are independent streams. Current enclosure release tooling publishes immutable INCOMPLETE candidates bound to one exact PCB release without forcing that PCB to be resealed; it does not yet publish a higher readiness claim from caller-supplied scope status. A future firmware stream, exact product lock, and integrated product-level digital twin remain tracked work, not current release authority.

Toolchain

Core documentation and planning use normal Python 3. KiCad operations require the KiCad-bundled Python where import pcbnew succeeds plus kicad-cli. TSX generation requires the pinned tscircuit/Bun environment. Fresh routing requires the configured KiCadRoutingTools installation; replaying a selected authenticated route authority does not.

Python entry points expose --help; shell-conductor forms are documented in the execution graph. Use the owning current command rather than copying an old invocation from a project journal.

Validate a workflow change

At minimum:

bash
python3 skills/pcb-design/scripts/skill_authority_check.py
python3 tests/t1_skill_progressive_disclosure.py
python3 tests/t1_pcb_documentation.py
python3 scripts/contracts_audit.py --walk --root skills/pcb-design

Run the domain suites affected by the change, then commit at a green boundary.

License

Except where otherwise noted, all original content in this repository is licensed under the MIT License. This includes software, documentation, prompts, schematics, PCB layouts, mechanical CAD files, and generated design artifacts.

Third-party materials remain subject to their respective copyright and license terms and are not relicensed by this repository.

See third-party notices for material provenance and contribution guidelines for new submissions.

Parts

172
QtyValueFootprintReferences
3710kΩResistor_SMD:R_0402_1005MetricR_BOOST0, R_BOOST1, R_CFG0, R_CFG1, R_CFG2, R_CTRL_RESET, R_DATA_CMD1, R_DATA_CMD2, R_DATA_CMD3, R_DATA_CMD4, R_DATA_OE1, R_DATA_OE2, R_DATA_OE3, R_DATA_OE4, R_DATA_OK1, R_DATA_OK2 +21
29100nFCapacitor_SMD:C_0402_1005MetricC_AGG_IN, C_AND_DATA, C_AND_PWR, C_BST, C_CTRL_VDD, C_DATA1, C_DATA2, C_DATA3, C_DATA4, C_EXP_VDD, C_HUB_A1, C_HUB_A2, C_HUB_A3, C_HUB_A4, C_HUB_CR_HF, C_HUB_DD +13
1022uFCapacitor_SMD:C_1210_3225MetricC_BUCK_OUT1, C_BUCK_OUT2, C_PD_OUT1, C_PD_OUT2, C_PD_OUT3, C_PORT1_BULK, C_PORT2_BULK, C_PORT3_BULK, C_PORT4_BULK, C_TRUNK_BULK
8100kΩResistor_SMD:R_0402_1005MetricR_SWAP1, R_SWAP2, R_SWAP3, R_SWAP4, R_SWAP5, R_SWAP6, R_SWAP7, R_VBUS_BOT
71uFCapacitor_SMD:C_0402_1005MetricC_HUB_18, C_HUB_18PLL, C_HUB_A_BULK, C_HUB_CR_BULK, C_HUB_RESET, C_PD_VDD, C_PWR_CTRL_OUT
5C3662799usb_controlled_debug_hub:TI_RPW0010A_VQFN-HR-10_2x2mm_P0.45mmU_PD_IN, U_PWR1, U_PWR2, U_PWR3, U_PWR4
5C3708426Package_TO_SOT_SMD:SOT-23U_ESD_UP, U_ESD1, U_ESD2, U_ESD3, U_ESD4
43.32kΩResistor_SMD:R_0603_1608MetricR_ILIM1, R_ILIM2, R_ILIM3, R_ILIM4
4C11355Package_SO:MSOP-10_3x3mm_P0.5mmU_DATA1, U_DATA2, U_DATA3, U_DATA4
4C503996usb_controlled_debug_hub:KH-AF90DIP-112_HorizontalJ_PORT1, J_PORT2, J_PORT3, J_PORT4
4C85047usb_controlled_debug_hub:Diodes_SOT23_2N7002KQ_DATA1, Q_DATA2, Q_DATA3, Q_DATA4
4MountingHole_3.2mm_M3MountingHole:MountingHole_3.2mm_M3H1, H2, H3, H4
3Fiducial_1mm_Mask2mmFiducial:Fiducial_1mm_Mask2mmFID1, FID2, FID3
210uFCapacitor_SMD:C_1206_3216MetricC_PD_IN1, C_PD_IN2
218pFCapacitor_SMD:C_0402_1005MetricC_XTAL1, C_XTAL2
23.3nFCapacitor_SMD:C_0603_1608MetricC_AGG_DVDT, C_PD_IN_DVDT
24.7kΩResistor_SMD:R_0402_1005MetricR_I2C_SCL, R_I2C_SDA
25.1kΩResistor_SMD:R_0402_1005MetricR_CC1, R_CC2
2C165948usb_controlled_debug_hub:TYPE-C-31-M-12_DatasheetJ_DATA, J_POWER
2C6053Package_SO:TSSOP-14_4.4x5mm_P0.65mmU_AND_DATA, U_AND_PWR
1100pFCapacitor_SMD:C_0402_1005MetricC_PD_FF
110uFCapacitor_SMD:C_0603_1608MetricC_BUCK_IN
112kΩResistor_SMD:R_0402_1005MetricR_RBIAS
1180uFusb_controlled_debug_hub:Panasonic_C6_6.3x5.9C_TRUNK_USB
1187kΩResistor_SMD:R_0402_1005MetricR_ILIM_CTRL
11MΩResistor_SMD:R_0402_1005MetricR_XTAL
11kΩResistor_SMD:R_0603_1608MetricR_PD_IN_ILIM
11kΩResistor_SMD:R_1210_3225MetricR_PD_VDD
11uFCapacitor_SMD:C_0603_1608MetricC_PD_IN_HF
1200kΩResistor_SMD:R_0402_1005MetricR_PD_UV_TOP
120kΩResistor_SMD:R_0402_1005MetricR_PD_FF
127.4kΩResistor_SMD:R_0402_1005MetricR_PD_UV_BOT
128.7kΩResistor_SMD:R_0603_1608MetricR_PD_IN_UV_MID
1300ΩResistor_SMD:R_0603_1608MetricR_AGG_ILIM
1330nFCapacitor_SMD:C_0402_1005MetricC_CTRL_VUSB
135.7kΩResistor_SMD:R_0603_1608MetricR_PD_IN_OV_BOT
1374ΩResistor_SMD:R_0402_1005MetricR_PD_FB_B
1470kΩResistor_SMD:R_0603_1608MetricR_PD_IN_UV_TOP
147kΩResistor_SMD:R_0402_1005MetricR_VBUS_TOP
16.8nFCapacitor_SMD:C_0603_1608MetricC_AGG_TIMER
173.2kΩResistor_SMD:R_0402_1005MetricR_PD_FB_A
1C130056Package_SON:VSON-8-1EP_3x3mm_P0.65mm_EP1.65x2.4mm_ThermalViasU_PWR_CTRL
1C14165Fuse:Fuse_1206_3216MetricF_PD
1C15269usb_controlled_debug_hub:Sunlord_SWPA4030SL_MAIN
1C17700166usb_controlled_debug_hub:Sunlord_MWSA0804SL_PD
1C1985204Crystal:Crystal_SMD_3225-4Pin_3.2x2.5mmY_HUB
1C2649846usb_controlled_debug_hub:TI_DRV0006A_WSON-6_2x2mm_P0.65mmD_PD_TVS
1C2878936usb_controlled_debug_hub:TI_RGE0024M_VQFN24_4x4_SplitPad_TypeVIIU_AGG
1C478081Package_DFN_QFN:QFN-64-1EP_9x9mm_P0.5mm_EP4.7x4.7mm_ThermalViasU_HUB
1C5248536Package_TO_SOT_SMD:TSOT-23-6U_BUCK
1C558584Package_SO:SSOP-28_5.3x10.2mm_P0.65mmU_EXP
1C640876Package_SO:SOIC-14_3.9x8.7mm_P1.27mmU_CTRL
1C841386usb_controlled_debug_hub:TI_RPA0010A_VQFN-HR-10_3x3mmU_PD_BUCK
1C970725usb_controlled_debug_hub:WCH_CH224K_ESSOP10_EPU_PD

More from misko/prompt2device

12
  • 4 layers220 × 120 mmCandidate filled profile, the printed circuit board in 3D

    Candidate filled profile

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    569 parts3MIT
  • 4 layers156 × 100 mmCrow audio carrier v1, the printed circuit board in 3D

    Crow audio carrier v1

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    340 parts3MIT
  • 6 layers176 × 122 mmRoute, the printed circuit board in 3D

    Route

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    238 parts3MIT
  • 4 layers188 × 92 mmCooksense, the printed circuit board in 3D

    Cooksense

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    226 parts3MIT
  • 4 layers130 × 90 mmProgrammable usb2 hub, the printed circuit board in 3D

    Programmable usb2 hub

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    218 parts3MIT
  • 4 layers130 × 90 mmFinal chain, the printed circuit board in 3D

    Final chain

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    206 parts3MIT
  • 6 layers170 × 120 mmRv2 final, the printed circuit board in 3D

    Rv2 final

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    203 parts3MIT
  • 4 layers150 × 120 mmPi usb port switch, the printed circuit board in 3D

    Pi usb port switch

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    197 parts3MIT
  • 4 layers252 × 92 mmCooksense, the printed circuit board in 3D

    Cooksense

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    195 parts3MIT
  • 4 layers150 × 115 mmUsb controlled debug hub 2a, the printed circuit board in 3D

    Usb controlled debug hub 2a

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    190 parts3MIT
  • 4 layers185 × 120 mmR1b, the printed circuit board in 3D

    R1b

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    182 parts3MIT
  • 4 layers130 × 100 mmUsb controlled debug hub, the printed circuit board in 3D

    Usb controlled debug hub

    misko/prompt2device

    The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

    175 parts3MIT

Similar boards

  • 4 layers50 × 50 mmBusted umbrella, the printed circuit board in 3D

    Busted umbrella

    useless-branch/busted-umbrella

    USB to CAN FD

    45 parts2Apache-2.0
  • 2 layers68.4 × 36.7 mmEmf beacon, the printed circuit board in 3D

    Emf beacon

    PolybiusBiotech/led_beacon

    The PCBA and firmware for the controllable LED Beacons.

    134 parts
  • 4 layers132.7 × 89.5 mmStrain guage r0, the printed circuit board in 3D

    Strain guage r0

    ttosu25/SG-3

    Hardware design for a mixed-signal strain-data acquisition system, incorporating sensor excitation, analogue signal conditioning, ADC, and MCU interface

    97 parts
  • 6 layers50 × 23 mmEsp32p4amoled3.19, the printed circuit board in 3D

    Esp32p4amoled3.19

    v-cu/dpf-load-monitor-wide

    ESP32-P4 diagnostic display for VAG diesels — live DPF and engine data over CAN (UDS) on a 3.19" ultra-wide AMOLED. Firmware, KiCad files, BOM and 3D enclosure.

    115 parts12
  • 2 layers86 × 74 mmKontakt, the printed circuit board in 3D

    Kontakt

    playlogo/billig

    Designing & building a "big" 3D printer from scratch

    65 parts2
  • 4 layers100 × 60 mmT1conv, the printed circuit board in 3D

    T1conv

    ajefferies2/t1conv

    100BASE-T1 ↔ 100BASE-TX media converter + dual CAN FD/USB adapter on one board.

    125 parts
  • 2 layers194.1 × 141.7 mmZenith pcba, the printed circuit board in 3D

    Zenith pcba

    kostareg/zenith

    Zenith is a 64-bit CPU and tensor accelerator.

    63 parts
  • 4 layers85 × 56 mmPiVI, the printed circuit board in 3D

    PiVI

    kuba2k2/PiVI

    A small Pi-sized single board computer for your car

    289 partsGPL-3.0

Questions

How big is the Usb controlled debug hub PCB?

It measures 130 × 100 mm and has 4 copper layers, 1.6 mm thick.

What parts does the Usb controlled debug hub use?

172 parts, built around the USB2517I-JZX, AP63203QWU, MCP2221A-I/SL and TPS56637RPAR. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Usb controlled debug hub KiCad files?

From the misko/prompt2device repository on GitHub, at the commit this page was made from: the board is archived_projects/usb-controlled-debug-hub-v2/04_kicad/usb_controlled_debug_hub.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.

Can I use the Usb controlled debug hub design in my own project?

Its repository publishes it under the MIT licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).