Skip to the content
4 layers130 × 90 mmFinal chain, the printed circuit board in 3D

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 × 90 mm
Copper layers
4
Thickness
1.6 mm
Parts
206
Nets
200
Pads
851
Tracks, vias
4,046, 596
Pours
3
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
16 Jul 2026
Updated
3 Nov 2026

Overview

Final chain 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 × 90 mm with 206 parts on 200 nets, routed with 4,046 tracks and 596 vias.

It is built around the STM32G0B1CBT6, LM5116MHX and USB2517I-JZX, with the AP63203WU, USBLC6-2SC6 and FSUSB42MUX among its other parts. Its parts include 79 capacitors, 73 resistors, 20 ICs, 7 diodes and 7 connectors. It belongs with the STM32 boards of this library.

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

206
QtyValueFootprintReferences
24100nFCapacitor_SMD:C_0603_1608MetricC22, C32, C33, C34, C35, C38, C39, C42, C111, C211, C412, C414, C415, C422, C424, C425 +8
1410kΩResistor_SMD:R_0603_1608MetricR36, R37, R412, R413, R419, R422, R423, R429, R432, R433, R439, R442, R443, R449
12100kΩResistor_SMD:R_0603_1608MetricR32, R33, R107, R207, R410, R416, R420, R426, R430, R436, R440, R446
8100uFCapacitor_SMD:C_1210_3225MetricC112, C113, C114, C115, C212, C213, C214, C215
810uFCapacitor_SMD:C_1210_3225MetricC107, C108, C109, C110, C207, C208, C209, C210
81kΩResistor_SMD:R_0603_1608MetricR415, R418, R425, R428, R435, R438, R445, R448
81uFCapacitor_SMD:C_0603_1608MetricC36, C37, C40, C41, C105, C106, C205, C206
63.3nFCapacitor_SMD:C_0603_1608MetricC102, C202, C410, C420, C430, C440
50ΩResistor_SMD:R_0603_1608MetricR2, R108, R109, R208, R209
5C7519Package_TO_SOT_SMD:SOT-23-6U5, U17, U18, U19, U20
42.2nFCapacitor_SMD:C_0603_1608MetricC411, C421, C431, C441
422uFCapacitor_SMD:C_1210_3225MetricC413, C423, C433, C443
436.5kΩResistor_SMD:R_0603_1608MetricR411, R421, R431, R441
468kΩResistor_SMD:R_0603_1608MetricR417, R427, R437, R447
4976ΩResistor_SMD:R_0603_1608MetricR414, R424, R434, R444
4C11355Package_SO:MSOP-10_3x3mm_P0.5mmU13, U14, U15, U16
4C3662799programmable_usb2_hub:Texas_RPW0010A_VQFN-HR-10_2x2mm_P0.45mm_ThermalViasU9, U10, U11, U12
4C404363programmable_usb2_hub:PowerPAK_SO-8_Single_Paste65Q3, Q4, Q5, Q6
4C85098Diode_SMD:D_SMAD4, D5, D6, D7
4MountingHole_3.2mm_M3MountingHole:MountingHole_3.2mm_M3H1, H2, H3, H4
4USB1130-15-Aprogrammable_usb2_hub:USB_A_GCT_USB1130_HorizontalJ3, J4, J5, J6
3Fiducial_1mm_Mask2mmFiducial:Fiducial_1mm_Mask2mmFID1, FID2, FID3
21.21kΩResistor_SMD:R_0603_1608MetricR103, R203
2100nFCapacitor_SMD:C_1206_3216MetricC2, C3
2100pFCapacitor_SMD:C_0603_1608MetricC103, C203
210mΩResistor_SMD:R_2512_6332MetricRS1, RS2
210nFCapacitor_SMD:C_0603_1608MetricC104, C204
212.4kΩResistor_SMD:R_0603_1608MetricR101, R201
218kΩResistor_SMD:R_0603_1608MetricR104, R204
218pFCapacitor_SMD:C_0603_1608MetricC30, C31
21nFCapacitor_SMD:C_0805_2012MetricC116, C216
22.2ΩResistor_SMD:R_1206_3216MetricR110, R210
222uFCapacitor_SMD:C_1206_3216MetricC23, C24
23.92kΩResistor_SMD:R_0603_1608MetricR102, R202
2330pFCapacitor_SMD:C_0603_1608MetricC101, C201
24.7kΩResistor_SMD:R_0603_1608MetricR34, R35
249.9kΩResistor_SMD:R_0603_1608MetricR105, R205
26.98kΩResistor_SMD:R_0603_1608MetricR106, R206
2C13755Package_SO:HTSSOP-20-1EP_4.4x6.5mm_P0.65mm_EP3.4x6.5mm_Mask2.75x3.43mmU2, U3
2C2128Diode_SMD:D_SOD-323D2, D3
2C408523Inductor_SMD:L_Sunlord_MWSA1206S-6R8L1, L2
2C454269Package_TO_SOT_SMD:TDSON-8-1Q1, Q2
110uFCapacitor_SMD:C_1206_3216MetricC21
111.5kΩResistor_SMD:R_0603_1608MetricR5
112kΩResistor_SMD:R_0603_1608MetricR31
11MΩResistor_SMD:R_0603_1608MetricR30
1220nFCapacitor_SMD:C_0603_1608MetricC1
14.75kΩResistor_SMD:R_0603_1608MetricR3
14.7uFCapacitor_SMD:C_0603_1608MetricC43
188.7kΩResistor_SMD:R_0603_1608MetricR1
190.9kΩResistor_SMD:R_0603_1608MetricR4
1C19191796Connector_PinHeader_1.27mm:PinHeader_2x05_P1.27mm_VerticalJ7
1C1985204Crystal:Crystal_SMD_3225-4Pin_3.2x2.5mmY1
1C266428Inductor_SMD:L_Sunlord_SWPA6028SL3
1C2847904Package_QFP:LQFP-48_7x7mm_P0.5mmU7
1C315992Diode_SMD:D_SMBD1
1C3215601Package_SON:WSON-12-1EP_3x3mm_P0.5mm_EP1.5x2.5mmU1
1C478081Package_DFN_QFN:QFN-64-1EP_9x9mm_P0.5mm_EP4.7x4.7mm_ThermalViasU6
1C5249699Fuse:Fuseholder_Blade_Mini_Keystone_3568F1
1C6053Package_SO:TSSOP-14_4.4x5mm_P0.65mmU8
1C780769Package_TO_SOT_SMD:TSOT-23-6U4
1C8404programmable_usb2_hub:TerminalBlock_KANGNEX_WJ126V_2P_P5.0J1
1C86462programmable_usb2_hub:USB_B_TE_292304-1_HorizontalJ2

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
  • 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
  • 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.

    172 parts3MIT

Similar boards

  • 4 layers132 × 107 mmBidirectionalSupply, the printed circuit board in 3D

    BidirectionalSupply

    ddowling/BidirectionalSupply

    Hardware and firmware for a bidirectional DC-DC convertor

    278 parts2
  • 8 layers120 × 100 mmGeeks ecu, the printed circuit board in 3D

    Geeks ecu

    synthesissolutions/geeksforkids

    458 parts2
  • 2 layers153 × 95.8 mmSpekky Matrix, the printed circuit board in 3D

    Spekky Matrix

    jc-SpaceXp/Spekky-Matrix

    Spectrum analyser displayed on a LED matrix board connected to a STM32 device

    390 parts1MIT
  • 2 layers150 × 180 mmElec, the printed circuit board in 3D

    Elec

    Chen-Xuan-Ng/project_initium_2.0_mcu

    59 parts
  • 2 layers150 × 160.8 mmProcessingUnit, the printed circuit board in 3D

    ProcessingUnit

    senrobo/open

     . │ ├──  l1 │ ├──  3dmodels │ │ ├──  .DSStore │ │ ├──  0603Inductor.step │ │ ├──  1040Inductor.step │ │ ├──  ALS-PT19.step │ │ ├──  C0603.step │ │ ├──  CAPPRD750W80D1600H2500.stp │ │ ├──  CD74HC4067M.step │ │…

    136 partsMIT
  • 4 layers70 × 157.5 mmController Tv Lift, the printed circuit board in 3D

    Controller Tv Lift

    vyrubaev/TV-Lift-Controller

    TVLift Controller is an intelligent controller for TV lift and lower mechanisms, based on the ESP32 microcontroller.

    103 parts
  • 2 layers40 × 38 mmShield, the printed circuit board in 3D

    Shield

    murexrobotics/electrical

    Highly integrated electronics design and printed circuit boards (PCBs) for the MATE ROV Competition. Attempt the impossible.

    32 parts192MIT

Questions

How big is the Final chain PCB?

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

What parts does the Final chain use?

206 parts, built around the STM32G0B1CBT6, LM5116MHX, USB2517I-JZX and AP63203WU. 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 Final chain KiCad files?

From the misko/prompt2device repository on GitHub, at the commit this page was made from: the board is archived_projects/programmable-usb2-hub/03_src/route/final_chain.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.

Can I use the Final chain 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).