Skip to the content
4 layers65 × 42 mmCrowsync recorder, the printed circuit board in 3D

Crowsync recorder

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
65 × 42 mm
Copper layers
4
Thickness
1.6 mm
Parts
55
Nets
44
Pads
176
Tracks, vias
412, 108
Pours
5
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
16 Jul 2026
Updated
3 Nov 2026

Overview

Crowsync recorder 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 65 × 42 mm with 55 parts on 44 nets, routed with 412 tracks and 108 vias.

It is built around the TLV9062IDR-MS, TPS7A2033PDBVR-TP and USB4105-GF-A. Its parts include 21 capacitors, 18 resistors, 4 diodes, 3 ICs and 3 connectors.

Main components

3

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

55
QtyValueFootprintReferences
4MountingHole_2.7mm_M2.5MountingHole_2.7mm_M2.5H1, H2, H3, H4
1100R PPS seriesResistor_SMD:R_0603_1608MetricR14
1100R amp outResistor_SMD:R_0603_1608MetricR13
1100R mic seriesResistor_SMD:R_0603_1608MetricR9
1100k bias->VCOMResistor_SMD:R_0603_1608MetricR10
1100n 3V3A U2Capacitor_SMD:C_0603_1608MetricC16
1100n 5VCapacitor_SMD:C_0603_1608MetricC13
1100n biasCapacitor_SMD:C_0603_1608MetricC18
110k div bottomResistor_SMD:R_0603_1608MetricR16
110u 3V3ACapacitor_SMD:C_0603_1608MetricC15
110u 5V bulkCapacitor_SMD:C_0603_1608MetricC12
110u Cg (15.9Hz)Capacitor_SMD:C_0603_1608MetricC20
110u VCCCICapacitor_SMD:C_0603_1608MetricC1
110u VCOMCapacitor_SMD:C_0603_1608MetricC2
110u bias resCapacitor_SMD:C_0603_1608MetricC17
112MHz 3225 20pFCrystal:Crystal_SMD_3225-4Pin_3.2x2.5mmY1
11M XTI-XTOResistor_SMD:R_0603_1608MetricR6
11k LED SSPNDResistor_SMD:R_0603_1608MetricR17
11k RgResistor_SMD:R_0603_1608MetricR12
11k5 D+ pullup (VDDI)Resistor_SMD:R_0603_1608MetricR3
11n RF stopCapacitor_SMD:C_0603_1608MetricC21
11u LDO inCapacitor_SMD:C_0603_1608MetricC14
11u VBUS pinCapacitor_SMD:C_0603_1608MetricC11
11u VCCP1ICapacitor_SMD:C_0603_1608MetricC8
11u VCCP2ICapacitor_SMD:C_0603_1608MetricC7
11u VCCXICapacitor_SMD:C_0603_1608MetricC4
11u VDDICapacitor_SMD:C_0603_1608MetricC3
11u VINL coupleCapacitor_SMD:C_0603_1608MetricC9
11u VINR coupleCapacitor_SMD:C_0603_1608MetricC10
11u mic coupleCapacitor_SMD:C_0603_1608MetricC19
122R D+ seriesResistor_SMD:R_0603_1608MetricR1
122R D- seriesResistor_SMD:R_0603_1608MetricR2
122k div topResistor_SMD:R_0603_1608MetricR15
12R2 VBUS filterResistor_SMD:R_0603_1608MetricR7
12k2 LED 5VResistor_SMD:R_0603_1608MetricR18
12k2 mic biasResistor_SMD:R_0603_1608MetricR8
133p XTICapacitor_SMD:C_0603_1608MetricC5
133p XTOCapacitor_SMD:C_0603_1608MetricC6
13k01 Rf (gain 4.0)Resistor_SMD:R_0603_1608MetricR11
15k1 Rd CC1 (UFP)Resistor_SMD:R_0603_1608MetricR4
15k1 Rd CC2 (UFP)Resistor_SMD:R_0603_1608MetricR5
1600R@100MHz biasInductor_SMD:L_0603_1608MetricFB1
1JST-GH PPSConnector_JST:JST_GH_SM02B-GHS-TB_1x02-1MP_P1.25mm_HorizontalJ3
1JST-GH micConnector_JST:JST_GH_SM03B-GHS-TB_1x03-1MP_P1.25mm_HorizontalJ2
1PCM2900CDBRPackage_SO:SSOP-28_5.3x10.2mm_P0.65mmU1
1TLV9062IDRPackage_SO:SOIC-8_3.9x4.9mm_P1.27mmU2
1TPS7A2033PDBVRPackage_TO_SOT_SMD:SOT-23-5U3
1USB4105-GF-AConnector_USB:USB_C_Receptacle_GCT_USB4105-xx-A_16P_TopMnt_HorizontalJ1
1USBLC6-2SC6 USBPackage_TO_SOT_SMD:SOT-23-6D1
1USBLC6-2SC6 harnessPackage_TO_SOT_SMD:SOT-23-6D2
1green ACTLED_SMD:LED_0805_2012MetricD3
1green PWRLED_SMD:LED_0805_2012MetricD4

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 layers61.3 × 61.3 mmCyton Mod, the printed circuit board in 3D

    Cyton Mod

    flosimn/Cyton-Mod

    135 parts1
  • 4 layers49.6 × 40 mmFsoc rx, the printed circuit board in 3D

    Fsoc rx

    SharbelMarshi/txrx-optical-communication-kicad

    A Free-Space Optical Communication link KiCad project

    62 parts1
  • 4 layers36 × 36 mmWisp, the printed circuit board in 3D

    Wisp

    2shaurya4/wisp-daughter-board

    37 parts
  • 4 layers94.2 × 69.7 mmTAS5806M, the printed circuit board in 3D

    TAS5806M

    smileym4n-collab/Kicadprojects

    132 parts
  • 2 layers73 × 99.8 mmSodium, the printed circuit board in 3D

    Sodium

    kanengomibako/Sodium

    85 parts14Unlicense
  • 2 layers60 × 60 mmScbs pico, the printed circuit board in 3D

    Scbs pico

    CoolNamesAllTaken/scbs

    Single Cell Battery Simulator for testing a BMS.

    64 parts4
  • 4 layers116 × 112 mmBldc esc, the printed circuit board in 3D

    Bldc esc

    EwoudVV/bldc-esc

    A custom STM32 motor controller for BLDC and PMSM motors.

    453 parts2

Questions

How big is the Crowsync recorder PCB?

It measures 65 × 42 mm and has 4 copper layers, 1.6 mm thick.

What parts does the Crowsync recorder use?

55 parts, built around the TLV9062IDR-MS, TPS7A2033PDBVR-TP and USB4105-GF-A. 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 Crowsync recorder KiCad files?

From the misko/prompt2device repository on GitHub, at the commit this page was made from: the board is archived_projects/crowsync-recorder/04_kicad/crowsync_recorder.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.

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