How it works
A hardware brief in, a manufacturable PCB out, with one human gate. The full technical description of Tracgen — what it does, what it is made of, and what state it is in.
The premise
Tracgen takes a hardware product description — natural language, uploaded specification documents, or both — and autonomously produces a manufacturable PCB: schematic, placed and routed board, verification reports and a complete manufacturing package with Gerbers, drill files, a priced BOM, pick-and-place and PDFs.
The pipeline is autonomous end to end with exactly one mandatory human gate: schematic review. Everything after approval — footprints, board setup, placement, routing, DRC and outputs — runs without intervention. Every artifact is a native KiCad file validated with kicad-cli, so the output is editable in a real EDA tool rather than trapped in the system.
What is included
Autonomous schematic → layout → route → DRC → manufacturing package
Native KiCad artifacts throughout, validated with kicad-cli and routed with freerouting
Live part sourcing and pricing through Nexar, Digi-Key and Mouser
Exactly one human approval gate, at schematic review
How it is built
Tracgen is built on Python, TypeScript, KiCad 10, Claude API and Nexar.
The repository is 79% Python, 21% TypeScript by volume — a description of what the work actually consists of rather than what it is filed under.
It carries 22 commits since Jun 2026, most recently changed in Jun 2026.
The method behind it
Every project here starts as a written specification, and the specification stays authoritative once code exists. The repository keeps a build plan with live status, an append-only decision log recording where the implementation departed from the plan, and a handoff document describing the true current state — including the parts that are not finished.
That is why a portfolio this wide is not a shallow one, and it is why this page can describe the product without overstating it.
Current state
Prototype. Working, not yet finished.
The source is private. What this page claims is checkable against the product itself, not the repository.
Next
Put Tracgen in your pipeline
Ask about integrating it with the repositories and agents you already run.