How it works

The premise

Give Tracgen a description of a hardware product (in plain English, as uploaded spec documents, or both) and it designs a PCB you can have made. You get the schematic, a placed and routed board, verification reports, and a full manufacturing package with Gerbers, drill files, a priced BOM, pick-and-place files and PDFs.

It runs on its own from start to finish, with two places it stops for a person: a quick confirmation of the board spec near the start, and a required review of the schematic. After you approve the schematic, footprints, board setup, placement, routing, DRC and outputs all happen automatically. Everything it produces is a native KiCad file checked with kicad-cli, so you can open and edit the design in KiCad like any other project.

What’s included

Schematic, layout, routing, DRC and manufacturing package, all automated

Native KiCad files throughout, checked with kicad-cli and routed with freerouting

Live part sourcing and pricing through Nexar, Digi-Key and Mouser

Two human checkpoints: confirm the spec, then approve the schematic

How it’s built

Tracgen is built on Python, TypeScript, KiCad 10, Claude API and Nexar.

The repository is 79% Python, 21% TypeScript by volume.

It carries 22 commits since Jun 2026, most recently changed in Jun 2026.

How the work is done

Every project here starts as a written spec, and the spec stays the source of truth once there’s code. The repository keeps a build plan with current status, an append-only decision log of where the code departed from the plan, and a handoff document that describes where things stand, including the unfinished parts.

That’s how one person keeps this many projects moving, and it’s what this page is written from.

Current state

Prototype. Works, but isn’t finished.

The source is private, so the way to check what this page says is to use the product.