Skip to the content
4 layers130 × 90 mmRoute, 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.2 mm
Parts
83
Nets
60
Pads
312
Tracks, vias
379, 50
Pours
40
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
16 Jul 2026
Updated
3 Nov 2026

Overview

Route 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 83 parts on 60 nets, routed with 379 tracks and 50 vias.

It is built around the TPSM63610RDFR, TPS25810RVCR and TPSM63604RDLR, with the TPS2557DRB, TPS2513ADBV and EEEFK1A151P among its other parts. Its parts include 21 capacitors, 21 resistors, 8 ICs, 6 diodes and 5 connectors.

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

83
QtyValueFootprintReferences
12TPTestPoint:TestPoint_Pad_D1.5mmTP1, TP2, TP3, TP4, TP5, TP6, TP7, TP8, TP9, TP10, TP11, TP12
7100kΩResistor_SMD:R_0603_1608MetricR7, R13, R14, R15, R17, R19, R21
6100nFCapacitor_SMD:C_0402_1005MetricC12, C14, C15, C16, C20, C21
647uFCapacitor_SMD:C_1210_3225MetricC6, C7, C8, C9, C10, C11
510uFCapacitor_SMD:C_1210_3225MetricC2, C3, C4, C5, C13
4MountingHole_3.2mm_M3MountingHole:MountingHole_3.2mm_M3H1, H2, H3, H4
339.2kΩResistor_SMD:R_0603_1608MetricR16, R18, R20
3C130056Package_SON:VSON-8-1EP_3x3mm_P0.65mm_EP1.65x2.4mm_ThermalViasU4, U5, U6
3C264054Capacitor_SMD:CP_Elec_6.3x5.8C17, C18, C19
3C5815149usb_hub_3s_v4:USB_A_GCT_USB1130-15-A_HorizontalJ2, J3, J4
3C7519Package_TO_SOT_SMD:SOT-23-6D2, D3, D4
3Fiducial_1mm_Mask2mmFiducial:Fiducial_1mm_Mask2mmFID1, FID2, FID3
20ΩResistor_SMD:R_0603_1608MetricR3, R9
210kΩResistor_SMD:R_0603_1608MetricR6, R12
21MΩResistor_SMD:R_0603_1608MetricR1, R2
2C473910Package_TO_SOT_SMD:SOT-23-6U7, U8
113kΩResistor_SMD:R_0603_1608MetricR10
115.8kΩResistor_SMD:R_0603_1608MetricR4
120kΩResistor_SMD:R_0603_1608MetricR8
141.2kΩResistor_SMD:R_0603_1608MetricR5
141.7kΩResistor_SMD:R_0603_1608MetricR11
1C124196Diode_SMD:D_SOD-123D5
1C264098usb_hub_3s_v4:Diodes_PowerDI3333-8_Type_UXQ1
1C273394usb_hub_3s_v4:E_Switch_EG1218SW1
1C3020560usb_hub_3s_v4:GCT_USB4105_GF_AJ5
1C3817933usb_hub_3s_v4:Phoenix_MKDS_1.5_2_1715022J1
1C473913Package_DFN_QFN:Texas_RVC0020A_WQFN-20-1EP_3x4mm_P0.5mm_EP1.6x2.6mm_ThermalViasU3
1C5219289usb_hub_3s_v4:Texas_RDL0020A_B3QFN-20_5x5.5mm_ThermalViasU2
1C5249699usb_hub_3s_v4:Keystone_3568_Mini_Blade_Fuse_HolderF1
1C7125816usb_hub_3s_v4:Texas_RDF0022A_B3QFN-22_6.5x7.5mm_ThermalViasU1
1C83846Diode_SMD:D_SMBD1
1C88744usb_hub_3s_v4:Rubycon_TZV_D6.3x8C1
1C97502Package_TO_SOT_SMD:SOT-9X3D6

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 layers80 × 50 mmUSB POWER, the printed circuit board in 3D

    USB POWER

    ssmo-oss/UMI-Power-distribution

    Three separate boards distribute a 12 V supply to the UMI system. D6 is the current prototype revision. It has not been physically qualified or approved for production.

    38 parts
  • 2 layersCoralC5-Motor, the printed circuit board in 3D

    CoralC5-Motor

    SmallCoral/c5-car

    用 KiCad 10 打开 CoralC5-Expansion.kicadpro。这是 Coral-C5 的单槽扩展板,顶部 J14 接核心板,左右 J9、J8 各一组 2×24 排针,下方放 RJ45 和 microSD,右侧放 ESP32-C3-MINI-1U。100×86mm 板框为本项目暂定尺寸。

    180 parts
  • 4 layers60 × 73.5 mmAnthracite bottom, the printed circuit board in 3D

    Anthracite bottom

    trope-oshw/anthracite

    MIDI-controllable fuzz pedal: open hardware (CERN-OHL-S-2.0), firmware (GPL-3.0-or-later)

    224 parts5CERN-OHL-S-2.0
  • 8 layers120 × 100 mmGeeks ecu, the printed circuit board in 3D

    Geeks ecu

    synthesissolutions/geeksforkids

    458 parts2
  • 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
  • 4 layers65 × 56 mmEWS, the printed circuit board in 3D

    EWS

    eiten/EWS

    Universal 3D-Printer HAT for SBC with CAN-Interface and USB Hub

    124 parts1
  • 2 layers99.1 × 78.7 mmPrototype 1, the printed circuit board in 3D

    Prototype 1

    22Limac/prototype_1

    41 parts
  • 4 layers86.4 × 54.6 mmBeagleBone cape, the printed circuit board in 3D

    BeagleBone cape

    wasyl07/skylark

    Drone control board based on AM335 BeagleBone Black and Ardupilot

    108 partsGPL-3.0

Questions

How big is the Route PCB?

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

What parts does the Route use?

83 parts, built around the TPSM63610RDFR, TPS25810RVCR, TPSM63604RDLR and TPS2557DRB. 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 Route KiCad files?

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

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